System Requirement (glossary)

From SEBoK
Jump to navigation Jump to search

(1a) A statement that transforms the stakeholder, requirement-driven view of desired services into technical view, of a required (engineered system) that could deliver those services. (ISO/IEC, 2008, section 6.4.2)

(1b) The Requirement Analysis process builds a representation of a future system that will meet stakeholder requirements and that, as far as constraints permit, does not imply any specific implementation. It results in a measurable system requirement that specifies, from the suppliers perspective, what characteristics it is to possess and with what magnitude. This forms the basis for verification. (ISO/IEC, 2008, section 6.4.2)

Source

(1) ISO/IEC. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC), ISO/IEC 15288:2008 (E).

Discussion

Both definitions are taken from the introduction to the Requirements Analysis process, there is no formal definition of the term "System Requirement" in the standard.

the term (engineered system) has been subsituted for the word (product) in definition 1a to better align with the terminology used in the SEBoK.

For a full discussion of the role and importance of system requirements in Systems Engineering see the System Requirements article.


SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus