Difference between revisions of "System Requirement (glossary)"
| Line 1: | Line 1: | ||
| − | ''<blockquote>(1a) A statement that transforms the stakeholder, | + | ''<blockquote>(1a) ''A statement that transforms the stakeholder, user-oriented view of desired capabilities into a technical view, of a solution that meets the operational needs of the user.'' (ISO/IEC/IEEE, 2015, section 6.4.2) </blockquote> |
| − | ''<blockquote>(1b) The Requirement | + | ''<blockquote>(1b) The System Requirement Definition process creates a set of measurable system requirements that specify, from the supplier’s perspective, what characteristics, attributes, and functional and performance requirements the system is to possess, in order to satisfy stakeholder requirements. |
| + | '' (ISO/IEC/IEEE, 2015, section 6.4.2) </blockquote> | ||
===Source=== | ===Source=== | ||
| − | (1) ISO/IEC. | + | (1) ISO/IEC/IEEE. 2015. ''Systems and Software Engineering - System Life Cycle Processes''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 (E). |
===Discussion=== | ===Discussion=== | ||
Revision as of 14:19, 16 June 2015
(1a) A statement that transforms the stakeholder, user-oriented view of desired capabilities into a technical view, of a solution that meets the operational needs of the user. (ISO/IEC/IEEE, 2015, section 6.4.2)
(1b) The System Requirement Definition process creates a set of measurable system requirements that specify, from the supplier’s perspective, what characteristics, attributes, and functional and performance requirements the system is to possess, in order to satisfy stakeholder requirements. (ISO/IEC/IEEE, 2015, section 6.4.2)
Source
(1) ISO/IEC/IEEE. 2015. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 (E).
Discussion
Both definitions are modified 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 substituted 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 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