Changes

==Origin==

==Origin==

Old French ''requerement'' , ''requierement'' request, [[petition]], reclamation

Old French ''requerement'' , ''requierement'' request, [[petition]], reclamation

*[http://en.wikipedia.org/wiki/17th_century 1662]

*[https://en.wikipedia.org/wiki/17th_century 1662]

==Definitions==

==Definitions==

*1: a : something wanted or needed : [[necessity]] <production was not sufficient to satisfy [[military]] requirements>  

*1: a : something wanted or needed : [[necessity]] <production was not sufficient to satisfy [[military]] requirements>  

:b : something [[essential]] to the [[existence]] or occurrence of something else : condition <failed to meet the [[school]]'s requirements for [[graduation]]>

:b : something [[essential]] to the [[existence]] or occurrence of something else : condition <failed to meet the [[school]]'s requirements for [[graduation]]>

==Description==

==Description==

In engineering, a '''requirement''' is a singular [[documented]] [[physical]] and [[functional]] need that a particular product or [[service]] must be or [[perform]]. It is most commonly used in a [[formal]] sense in [http://en.wikipedia.org/wiki/Systems_engineering systems engineering], [http://en.wikipedia.org/wiki/Software_engineering software engineering], or [http://en.wikipedia.org/wiki/Enterprise_engineering enterprise engineering]. It is a [[statement]] that identifies a [[necessary]] [[attribute]], capability, characteristic, or [[quality]] of a system for it to have [[value]] and utility to a user.

In engineering, a '''requirement''' is a singular [[documented]] [[physical]] and [[functional]] need that a particular product or [[service]] must be or [[perform]]. It is most commonly used in a [[formal]] sense in [https://en.wikipedia.org/wiki/Systems_engineering systems engineering], [https://en.wikipedia.org/wiki/Software_engineering software engineering], or [https://en.wikipedia.org/wiki/Enterprise_engineering enterprise engineering]. It is a [[statement]] that identifies a [[necessary]] [[attribute]], capability, characteristic, or [[quality]] of a system for it to have [[value]] and utility to a user.

In the [[classical]] engineering approach, sets of requirements are used as inputs into the [[design]] [[stages]] of product [[development]]. Requirements are also an important input into the verification [[process]], since tests should trace back to specific requirements. Requirements show what elements and [[functions]] are necessary for the particular project.

In the [[classical]] engineering approach, sets of requirements are used as inputs into the [[design]] [[stages]] of product [[development]]. Requirements are also an important input into the verification [[process]], since tests should trace back to specific requirements. Requirements show what elements and [[functions]] are necessary for the particular project.

The requirements [[development]] [[phase]] may have been preceded by a feasibility [[study]], or a conceptual [[analysis]] phase of the [[project]]. The requirements phase may be broken down into requirements elicitation (gathering, [[understanding]], reviewing, and articulating the needs of the stakeholders), [[analysis]] (checking for [[consistency]] and completeness), specification (documenting the requirements) and validation (making sure the specified requirements are correct).[http://en.wikipedia.org/wiki/Requirement]

The requirements [[development]] [[phase]] may have been preceded by a feasibility [[study]], or a conceptual [[analysis]] phase of the [[project]]. The requirements phase may be broken down into requirements elicitation (gathering, [[understanding]], reviewing, and articulating the needs of the stakeholders), [[analysis]] (checking for [[consistency]] and completeness), specification (documenting the requirements) and validation (making sure the specified requirements are correct).[https://en.wikipedia.org/wiki/Requirement]

[[Category: General Reference]]

[[Category: General Reference]]