Difference between revisions of "System Definition (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "SEBoK v. 2.9, released 20 November 2023" to "SEBoK v. 2.10, released 06 May 2024")
 
(28 intermediate revisions by 7 users not shown)
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 (glossary)]], design of the [[Logical Architecture (glossary)]] and [[Physical Architecture (glossary)]], and [[System Analysis (glossary)]].'' (Created for SEBoK)</blockquote>
+
''<blockquote>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, the design of one or more logical and physical architectures, and analysis and selection between possible solution options.'' (Created for SEBoK)</blockquote>
  
 
===Source===
 
===Source===
Line 5: Line 5:
  
 
===Discussion===
 
===Discussion===
"System definition" is also 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.
+
System definition is a knowledge area in the SEBoK that includes several front-end systems engineering activities, such as system requirements development; functional, logical and physical architectural design, and system analysis. This generally aligns with the "concept stage" as discussed in INCOSE (2012). In the SEBoK, [[System Concept Definition|system concept definition]] is used to discuss the assessment of the mission and stakeholder requirements.
  
 
'''Work Cited'''
 
'''Work Cited'''
  
INCOSE. 2011. ''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.
+
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.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
  
{{DISQUS}}
+
<center>'''SEBoK v. 2.10, released 06 May 2024'''</center>

Latest revision as of 22:28, 2 May 2024

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, the design of one or more logical and physical architectures, and analysis and selection between possible solution options. (Created for SEBoK)

Source

This definition was developed for the SEBoK.

Discussion

System definition is a knowledge area in the SEBoK that includes several front-end systems engineering activities, such as system requirements development; functional, logical and physical architectural design, and system analysis. This generally aligns with the "concept stage" as discussed in INCOSE (2012). In the SEBoK, system concept definition is used to discuss the assessment of the mission and stakeholder requirements.

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. 2.10, released 06 May 2024