Difference between revisions of "System Requirement (glossary)"
m (Text replace - "====Source====" to "===Source===") |
|||
| Line 7: | Line 7: | ||
===Discussion=== | ===Discussion=== | ||
| − | + | For a full discussion of the role and importance of system requirements in Systems Engineering see the [[System Requirements|system requirements]] article. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
{{DISQUS}} | {{DISQUS}} | ||
Revision as of 16:02, 17 March 2013
(1) A statement that converts a stakeholder requirement into technical, usable terms for design activities using a semantic code (natural language, mathematical expression, arithmetic, geometric, or software language, etc.). (Created for SEBoK)
(2) requirement applicable to a system. (Created for SEBoK)
Source
(1) and (2) These definitions were developed for the SEBoK.
Discussion
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