System Concept Definition
Lead Author: Tami Katz Contributing Author: Lou Wheatcraft
New Title: Concept Definition
Concept Definition is the set of systems engineering (SE) activities in which the problem space and the needs and requirements of the business or enterprise and stakeholders are closely examined. Concept Definition begins before any formal definition of the system-of-interest (SoI) is developed.
The Concept Definition activities include Business or Mission Analysis and Stakeholder Needs Definition. With these two Concept Definition activities, business or enterprise decision makers and other stakeholders describe what a solution should accomplish and why it is needed. Both why and what need to be answered before consideration is given to how the problem will be addressed (i.e., what type of solution will be implemented) and how the solution will be defined and developed.
The specific activities and sequence of Concept Definition activities and their involvement with the life cycle activities of any system, and in particular the close integration with System Definition activities, will be dependent upon the type of life cycle model being utilized. See Applying Life Cycle Processes for further discussion of the concurrent, iterative and recursive nature of these relationships.
Topics
Each part of the SEBoK is divided into knowledge areas (KAs), which are groupings of information with a related theme. The KAs in turn are divided into topics. This KA contains the following topics:
See the article Matrix of Implementation Examples for a mapping of case studies and vignettes included in Part 7 as well as topics covered in Part 3.
Concept Definition Activities
There are two primary activities discussed under concept definition: Business or Mission Analysis and the definition of Stakeholder Needs:
- Business or Mission Analysis activity establishes the problem or opportunity being addressed that could result in a new or modified product, service or enterprise. This process also includes identification of major stakeholders, the mission, goals and objectives of the SoI, the measures of success, identification of business needs and requirements, and identification of the SoI life cycle concepts.
- The Stakeholder Needs Definition activity uses the inputs of the Business or Mission Analysis effort to identify an integrated set of needs [new glossary term] based on inputs from the major stakeholders as well as analysis of the life cycle concepts, drivers, constraints, and risks.
The products and artifacts produced during Concept Definition are then used in the System Definition process.
The SEBoK Part 2 provides guidance on how systems thinking is applicable to concept definition efforts, and in Identifying and Understanding Problems and Opportunities. Additional guidance is also provided in the INCOSE Needs and Requirements Manual.
References
Works Cited
None.
Primary References
INCOSE. 2023. 'Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities', version 5.0. Hoboken, NJ, USA: John Wiley and Sons, Inc, ISBN: 978-1-118-99940-0.
INCOSE. 2022. INOSE Needs and Requirements Manual, version 1.1. INCOSE-TP-2021-002-01.
ISO/IEC/IEEE. 2023. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2023. [to do - ensure link is updated to 2023 writeup]
Additional References
INCOSE. 2022. INOSE Guide to Needs and Requirements Manual, version 1. INCOSE-TP-2021-003-01