Difference between revisions of "System Definition (glossary)"
| Line 1: | Line 1: | ||
| − | ''<blockquote>A set of core technical activities of [[Systems Engineering (glossary)|systems engineering]], including the activities that are completed primarily in the front-end portion of the system design. This consists of the definition of [[System Requirements|system requirements]], design of the [[Architectural Design: Physical|physical]] and [[Architectural Design: Logical|logical]] systems architecture, and [[System Analysis|system analysis]].</blockquote>'' | + | ''<blockquote>A set of core technical activities of [[Systems Engineering (glossary)|systems engineering]], including the activities that are completed primarily in the front-end portion of the system design. This consists of the definition of [[System Requirements|system requirements]], design of the [[Architectural Design: Physical|physical]] and [[Architectural Design: Logical|logical]] systems architecture, and [[System Analysis|system analysis]]. (Created for SEBoK)</blockquote>'' |
====Source==== | ====Source==== | ||
Revision as of 22:13, 11 September 2012
A set of core technical activities of systems engineering, including the activities that are completed primarily in the front-end portion of the system design. This consists of the definition of system requirements, design of the physical and logical systems architecture, and system analysis. (Created for SEBoK)
Source
This definition was developed for the SEBoK v. 1.0.
Discussion
"System definition" is used in the SEBoK as a knowledge area (KA); it includes several front-end systems engineering (SE) activities such as system requirements development, systems architecture, and system analysis. (See System Definition KA.) This generally aligns with the "concept stage" as discussed in the International Council on Systems Engineering (INCOSE) Systems Engineering Handbook (INCOSE 2012). In the SEBoK, "[[Concept Definition}concept definition]]" is used to discuss the assessment of the mission and stakeholder requirements.
INCOSE. 2012. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2.
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