Product Versus Process Requirements
Projects are subject to three sorts of requirements:
- Business requirements describe in business terms what must be delivered or accomplished to provide value.
- Product requirements describe properties of a system or product (which could be one of several ways to accomplish a set of business requirements.)
- Process requirements describe activities performed by the developing organization. For instance, process requirements could specify specific methodologies that must be followed, and constraints that the organization must obey.
Product and process requirements are closely linked. Process requirements often specify the activities that will be performed to satisfy a product requirement. For example, a maximum development cost requirement (a process requirement) may be imposed to help achieve a maximum sales price requirement (a product requirement); a requirement that the product be maintainable (a Product requirement) often is addressed by imposing requirements to follow particular development styles (e.g., object-oriented programming), style-guides, or a review/inspection process (process requirements).
Read more about this topic: Requirement
Famous quotes containing the words product and/or process:
“He was the product of an English public school and university. He was, moreover, a modern product of those seats of athletic exercise. He had little education and highly developed muscles—that is to say, he was no scholar, but essentially a gentleman.”
—H. Seton Merriman (1862–1903)
“A designer who is not also a couturier, who hasn’t learned the most refined mysteries of physically creating his models, is like a sculptor who gives his drawings to another man, an artisan, to accomplish. For him the truncated process of creating will always be an interrupted act of love, and his style will bear the shame of it, the impoverishment.”
—Yves Saint Laurent (b. 1936)