Difference between revisions of "Concept Definition (glossary)"
Jump to navigation
Jump to search
m (Text replacement - "released 5 October" to "released 16 October") |
(Text replacement - "\[\[\s*([^]]*)\s*\(glossary\)\s*\|\s*([^]]+)\]\]" to "{{Term|$1 (glossary)|$2}}") |
||
| Line 5: | Line 5: | ||
===Discussion=== | ===Discussion=== | ||
| − | [[Concept Definition]] is a knowledge area in the SEBoK; it includes systems engineering activities which occur before any formal definition of the | + | [[Concept Definition]] is a knowledge area in the SEBoK; it includes systems engineering activities which occur before any formal definition of the {{Term|System-of-Interest (glossary)|system-of-interest}} (SoI) is developed such as {{Term|Mission Analysis (glossary)| analysis}} and definition of {{Term|Stakeholder Requirement (glossary)|stakeholder needs and requirements}}. This generally defines the problem statement which initiates a "concept stage" as discussed in 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 22:00, 2 October 2019
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 a knowledge area in the SEBoK; it includes systems engineering activities which occur before any formal definition of the
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 16 October 2018