Difference between revisions of "Stakeholder Needs and Requirements (glossary)"
(→Source) Tag: visualeditor |
|||
| Line 1: | Line 1: | ||
''<nowiki/>''<blockquote>''(1a) The requirements for a system that can provide the services needed by users and other stakeholders in a defined environment.'' (ISO/IEC/IEEE, 2015, section 6.4.1)</blockquote> | ''<nowiki/>''<blockquote>''(1a) The requirements for a system that can provide the services needed by users and other stakeholders in a defined environment.'' (ISO/IEC/IEEE, 2015, section 6.4.1)</blockquote> | ||
| − | ''<nowiki/>''<blockquote>''(1b) The stakeholder requirements definition process identifies stakeholders, | + | ''<nowiki/>''<blockquote>''(1b) The stakeholder needs and requirements definition process identifies stakeholders, or stakeholder classes, involved with the system throughout its life cycle, and their needs. It analyzes and transforms these needs into a common set of stakeholder requirements that express the intended interaction the system will have with its operational environment and that are the reference against which each resulting operational capability is validated. The stakeholder requirements are defined considering the context of the system-of-interest with the interoperating systems and enabling systems. (ISO/IEC/IEEE,2015) </blockquote> |
===Source=== | ===Source=== | ||
| − | ISO/IEC/IEEE. | + | ISO/IEC/IEEE. 2015. ''[[ISO/IEC/IEEE 15288|Systems and Software Engineering -- System Life Cycle Processes]]''. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2015. |
===Discussion=== | ===Discussion=== | ||
Revision as of 14:12, 16 June 2015
(1a) The requirements for a system that can provide the services needed by users and other stakeholders in a defined environment. (ISO/IEC/IEEE, 2015, section 6.4.1)
(1b) The stakeholder needs and requirements definition process identifies stakeholders, or stakeholder classes, involved with the system throughout its life cycle, and their needs. It analyzes and transforms these needs into a common set of stakeholder requirements that express the intended interaction the system will have with its operational environment and that are the reference against which each resulting operational capability is validated. The stakeholder requirements are defined considering the context of the system-of-interest with the interoperating systems and enabling systems. (ISO/IEC/IEEE,2015)
Source
ISO/IEC/IEEE. 2015. Systems and Software Engineering -- System Life Cycle Processes. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2015.
Discussion
Both definitions are taken from the introduction to the "Stakeholder Requirements Definition Process" in ISO/IEC 15288; there is no formal definition of the term "stakeholder requirement" in the standard.
For a full discussion of the role and importance of stakeholder requirements in systems engineering see the Stakeholder Needs and 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