Difference between revisions of "Stakeholder Needs and Requirements (glossary)"
m (Text replace - "====Source====" to "===Source===") |
|||
| Line 5: | Line 5: | ||
===Discussion=== | ===Discussion=== | ||
| − | + | ||
| + | For a full discussion of the role and importance of stakeholder requirements in Systems Engineering see the [[Stakeholder Needs and Requirements]] article. | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
{{DISQUS}} | {{DISQUS}} | ||
Revision as of 17:01, 17 March 2013
The views of users, acquirers, and customers regarding a problem (or opportunity), defined through a set of requirements for a solution that can provide the services needed in a defined environment. (Created for SEBoK)
Source
This definition was developed for the SEBoK.
Discussion
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