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:
“Labor is work that leaves no trace behind it when it is finished, or if it does, as in the case of the tilled field, this product of human activity requires still more labor, incessant, tireless labor, to maintain its identity as a “work” of man.”
—Mary McCarthy (1912–1989)
“... the history of the race, from infancy through its stages of barbarism, heathenism, civilization, and Christianity, is a process of suffering, as the lower principles of humanity are gradually subjected to the higher.”
—Catherine E. Beecher (1800–1878)