design requirement
Sign in to saveAlso known as mandatory, required, involuntary, compulsory, necessarily, necessity, necessary condition, requirement
In engineering, a requirement is a condition that must be satisfied for the output of a work effort to be acceptable. It is an explicit, objective, clear and often quantitative description of a condition to be satisfied by a material, design, product, or service.
In the Vinony graph
Vinony's link graph records 166 inbound references to design requirement, and connects out to use case, specification and user story.
It is catalogued under the topic Software requirements.
Vinony links it to 15 Wikipedia language editions.
Wikidata facts
Show 2 more facts
- equivalent property
- www.purl.org/dc/terms/requires
- Commons category
- Requirements
via Wikidata · CC0
~18 min read
Encyclopedic overview
16 sectionsContents
- Origins of term
- Product versus process requirements
- Types of requirements
- Characteristics of good requirements
- Verification
- Documenting requirements
- Changes in requirements
- Issues
- Competing standards
- Disputes regarding the necessity and effects of software requirements
- Requirements creep
- Multiple requirements taxonomies
- Process corruptions
- See also
- References
- External links
In engineering, a requirement is a condition that must be satisfied for the output of a work effort to be acceptable. It is an explicit, objective, clear and often quantitative description of a condition to be satisfied by a material, design, product, or service.
A specification or spec is a set of requirements that is typically used by developers in the design stage of product development and by testers in their verification process.
Excerpted from Wikipedia’s “design requirement” article, available under the CC BY-SA 4.0 licence.