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:
“The product of the artist has become less important than the fact of the artist. We wish to absorb this person. We wish to devour someone who has experienced the tragic. In our society this person is much more important than anything he might create.”
—David Mamet (b. 1947)
“The practice of S/M is the creation of pleasure.... And that’s why S/M is really a subculture. It’s a process of invention. S/M is the use of a strategic relationship as a source of pleasure.”
—Michel Foucault (1926–1984)