Difference between revisions of "Concept Definition (glossary)"

From SEBoK
Jump to navigation Jump to search
Line 5: Line 5:
  
 
===Discussion===
 
===Discussion===
"Concept Definition" is used in the SEBoK as a knowledge area (KA); it includes systems engineering (SE) activities which occur before any formal definition of the [[System-of-Interest  (glossary)|system-of-interest]] (SoI) is developed such as [[Mission Analysis (glossary)| analysis]] and definition of [[Stakeholder Requirement (glossary)|stakeholder needs and requirements]].  (See [[Concept Definition]] KA.) This generally defines the problem statement which initiates a "concept stage" as discussed in the International Council on Systems Engineering (INCOSE) ''Systems Engineering Handbook'' (INCOSE 2012). In the SEBoK, [[System Definition]] is used to discuss the detail description of a solution system.
+
"Concept Definition" is used in the SEBoK as a knowledge area (KA); it includes systems engineering (SE) activities which occur before any formal definition of the [[System-of-Interest  (glossary)|system-of-interest]] (SoI) is developed such as [[Mission Analysis (glossary)| analysis]] and definition of [[Stakeholder Requirement (glossary)|stakeholder needs and requirements]].  (See [[Concept Definition]] KA.) This generally defines the problem statement which initiates a "concept stage" as discussed in the International Council on Systems Engineering (INCOSE) ''Systems Engineering Handbook'' (INCOSE 2012). In the SEBoK, [[System Definition]] is used to discuss the detailed description of a solution system.
  
 
'''Work Cited'''
 
'''Work Cited'''

Revision as of 17:58, 17 April 2013

A set of core technical activities of systems engineering in which the problem space and the needs of the stakeholders are closely examined. This consists of analysis of the problem space and definition of stakeholder needs for required services within it. (Created for SEBoK)

Source

This definition was developed for the SEBoK.

Discussion

"Concept Definition" is used in the SEBoK as a knowledge area (KA); it includes systems engineering (SE) activities which occur before any formal definition of the system-of-interest (SoI) is developed such as analysis and definition of stakeholder needs and requirements. (See Concept Definition KA.) This generally defines the problem statement which initiates a "concept stage" as discussed in the International Council on Systems Engineering (INCOSE) Systems Engineering Handbook (INCOSE 2012). In the SEBoK, System Definition is used to discuss the detailed description of a solution system.

Work Cited

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 v. 1.9.1 released 30 September 2018

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