Difference between revisions of "Structure of the SEBoK"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
 
(103 intermediate revisions by 11 users not shown)
Line 1: Line 1:
{{Star|{{#linktree:2|Acronyms|Purpose (glossary)|Scope (glossary)|Context (glossary)|Structure (glossary)|Value (glossary)|Concept (glossary)|System (glossary)|Systems Engineering (SE) (glossary)|Use Case (glossary)|Model (glossary)|Governance (glossary)|Organization (glossary)|Competency (glossary)}}}}
+
The '''Guide to the Systems Engineering Body of Knowledge (SEBoK)''' is a living authoritative guide that discusses knowledge relevant to Systems Engineering. SEBoK does not contain all of this knowledge itself but provides a starting point and key resources to allow the reader to navigate the wider body of knowledge that exists in published sources.  To do this, SEBoK:
 +
*Defines relevant knowledge and structures it to facilitate understanding.
 +
*Provides short discussions of key ideas, principles and concepts within that structure.
 +
*Points to reference sources important to the discipline, which explore these ideas in more detail.
  
As discussed in the Guide to the Systems Engineering Body of Knowledge [[Acronyms|(SEBoK)]] [[SEBoK 0.75 Introduction]], the SEBoK is focused primarily on domain-independent knowledge, with one part devoted to implementation examples. The SEBoK is divided into seven parts, as discussed below.  
+
In doing this, it is inevitable that differences in terminology, alternative approaches, and even fundamentally different ways of thinking within the knowledge will appear.  SEBoK attempts were possible to provide clarity of similar or overlapping ideas, or to highlight real differences and the reasons behind them.  In particular, the SEBoK [[Glossary of Terms]] contains the most used or generally agreed upon definitions of terms when it can, but may highlight more than one definition if needed to show breadth of current thinking.
  
==Structure==
+
==SEBoK Structure==
*Part 1 - [[SEBoK 0.75 Introduction]] - This part provides the “opening” material to the SEBoK. Primarily, the section introduces the SEBoK ([[Purpose (glossary)|purpose (glossary)]], [[Scope (glossary)|scope (glossary)]], [[Context (glossary)|context (glossary)]], [[Structure (glossary)|structure (glossary)]], and economic [[Value (glossary)|value (glossary)]]), the [[Concept (glossary)|concepts (glossary)]] of [[System (glossary)|systems (glossary)]] and [[Systems Engineering (glossary)|systems engineering (glossary)]] [[Acronyms|(SE)]], including an introduction to the history and future challenges of SE, an introduction to the discussion of related disciplines, the [[Use Case (glossary)|use cases (glossary)]] for the SEBoK, a discussion of SEBoK development and its future evolution, and acknowledgements.
+
Figure 1, below, illustrates the eight parts of the SEBoK and how they are related.
 
*Part 2 - [[Systems]] - This part focuses on defining what is created by SE, as well as on providing links to the appropriate aspects of systems science. Specifically, Part 2 provides a discussion of what systems are (including aspects of systems thinking), provides system concepts (truisms about systems which are important for SE), discusses the different types of systems, provides information on different [[Representing Systems with Models|representations of systems (models)]], and discusses the [[Systems Approach]] and [[Systems Challenges]]. In particular, the systems approach and SE challenges have strong links to Parts 3, [[Systems Engineering and Management]] and 4, [[Applications of Systems Engineering]].
 
 
*Part 3 - [[Systems Engineering and Management]] - This part specifically focuses on how SE is conducted. It includes discussion of the traditional SE processes, such as [[Concept Definition]] and [[System Definition]], [[System Realization]], and [[System Deployment and Use]], as well as [[Systems Engineering Management]] such as [[Risk Management]], [[Decision Management]], [[Configuration Management]], [[Information Management]], and [[Quality Management]] management. Part 3 also includes an overview of life cycles, as well as product and service life management. This part comprises a large portion of the SEBoK and is focused around what has traditionally been viewed by many as SE. It also includes information on [[Systems Engineering Standards]], documented best practices, and common pitfalls for performing SE or systems management activities as appropriate.
 
 
*Part 4 - [[Applications of Systems Engineering]] - focuses on providing guidance on how the processes and methods presented in Part 3, [[Systems Engineering and Management]] can, and should, be applied to specific types of systems, specifically [[Product Systems Engineering]], [[Service Systems Engineering]], [[Enterprise Systems Engineering]], and [[Systems of Systems]] [[Acronyms|(SoS)]].
 
 
*Part 5 - [[Enabling Systems Engineering]] - This part deals with the different ways in which a group can organize to perform SE activities. Specifically, Part 5 discusses strategies for [[Systems Engineering Organizational Strategy|organizing for SE]], including [[Value (glossary)|value (glossary)]] propositions, [[Purpose (glossary)|purpose (glossary)]], and [[Governance (glossary)|governance (glossary)]], considerations at the [[Enabling Businesses and Enterprises to Perform Systems Engineering|business and enterprise level]], and considerations for [[Enabling Teams to Perform Systems Engineering|teams]] and [[Enabling Individuals to Perform Systems Engineering|individuals]] within an [[Organization (glossary)|organization (glossary)]], including [[Competency (glossary)|competency (glossary)]], personal SE development, and [[Ethical Behavior|ethics]].
 
  
*Part 6 - [[Related Disciplines]] - This part contains knowledge areas which deal with the intertwining of SE with [[Systems Engineering and Software Engineering|software engineering]] [[Acronyms|(SwE)]], [[Systems Engineering and Project Management|project management (PM)]], [[Systems Engineering and Industrial Engineering|industrial engineering]], [[Systems Engineering and Procurement/Acquisition|procurement and acquisition]], and [[Systems Engineering and Specialty Engineering|specialty engineering]], including discussions of the various system "–ilities" to be balanced and integrated by SE.
+
{{Structure|650px|'''Figure 1 Scope of SEBoK Parts and related knowledge '''(SEBoK Original).}}
 
*Part 7 - [[Systems Engineering Implementation Examples]] - This part provides real-world examples of SE activities and links the concepts in those activities to the SEBoK. There are two main types of examples: [[Case Studies]] and [[Vignettes]]. The case studies included in Part 7 are previously existing case studies that examine the successes and challenges in past SE programs; the Part 7 team connects the case study information to the related SEBoK knowledge areas [[Acronyms|(KAs)]] and topics. Vignettes are smaller-scale examples, but are still based on real-world systems. It is important to note that discussion of these examples is centered around links to the SEBoK; it is ‘’not’’ the intention of the SEBoK authors to make value judgments regarding these examples or the systems they describe.  
 
  
A key activity in the integration of the various parts of the SEBoK has been the development, application, and iteration of a Systems Modeling Language [[Acronyms|(SysML)]] concept map. This map shows the relationships among the elements of the SEBoK and its external environment.  Two figures have been developed from this concept map, which can be seen in the [[Scope and Context of the SEBoK]] section.  These figures will be useful in navigating the SEBoK.
+
The scope of each part and the key relationships amongst them are briefly discussed below. For a more detailed discussion of how this structure was evolved, see (Adcock et al, 2016).
  
==References==  
+
==Overview of Parts==
 +
===Part 1: [[SEBoK Introduction]]===
 +
This part explains the scope, context, and structure of the SEBoK, and of {{Term|Systems Engineering (glossary)|systems engineering}} (SE).
  
===Works Cited===
+
An overview of who should use the SEBoK, and for what purpose, is followed by detailed use cases. Systems engineering’s economic value, history, and relationship to other disciplines are discussed.  Part 1 also contains a section which discusses the future evolution of the SEBoK and allows for new areas of content to be introduced before being transitioned into other SEBoK parts.
 +
 
 +
===Part 2: [[Foundations of Systems Engineering]]===
 +
This part provides an introduction and overview of areas of knowledge which provide the foundations of SE.
 +
 
 +
A discussion of the definitions and basic concepts of {{Term|System (glossary)|systems}} is followed by an overview of the principles, concepts, methods, models and patterns of some of the key foundational areas of {{Term|Systems Science (glossary)}}.  This includes a detailed consideration of the foundational knowledge related to systems models and modelling.
 +
 
 +
Part 2 looks in more detail at two aspects of this foundational knowledge of particular value to SE.  The first is to discuss aspects of systems knowledge related to a {{Term|Systems Approach (glossary)}} to complex problems and opportunities.  This approach provides foundations for how SE is defined and practiced (see Parts 3 and 5 below).  The second is to describe the different ways in which system concepts are applied to real world concerns.  The SEBoK defines an {{Term|Engineered System (glossary)|engineered system}} (ES) as the primary focus for the application of SE (see Part 4 below).
 +
 
 +
===Part 3: [[Systems Engineering and Management]]===
 +
This part describes generic knowledge on the practice of SE and related management activities. 
 +
 
 +
Part 3 begins with the {{Term|Life Cycle Model (glossary)|life cycle models}} common in SE and the general principles behind their application.  It then moves on to [[Systems Engineering Management|SE management]] activities.  It covers both technical activities such as requirements, architecture, test and evaluation; and management activities such as planning, measurement, and risk.  Next is [[Product and Service Life Management|product and service life management]], a distinct area of SE management that emphasizes the entire life cycle including retirement and disposal. An account of [[Systems Engineering Standards|SE standards]] concludes this part.
 +
 
 +
Focused on what many think of as the main body of SE, including best practices and common pitfalls, this part constitutes a substantial proportion of the SEBoK. As already discussed, the knowledge in Part 3 is based on the systems approach from Part 2.  The links between Part 3 and the other parts of the SEBoK are discussed below.
 +
 
 +
===Part 4: [[Applications of Systems Engineering]]===
 +
This part describes how to apply SE principles to different types of {{Term|System Context (glossary)}}.
 +
 
 +
Part 4 focuses on four major {{Term|Engineered System (glossary)}} contexts in turn: [[Product Systems Engineering|products]], [[Service Systems Engineering|services]], [[Enterprise Systems Engineering|enterprises]], and [[Systems of Systems (SoS)|systems of systems]] (SoS).  For each one, the system abstraction, commercial relationships and application of generic SE is described.
 +
 
 +
The generalized contexts above should be viewed as overlapping models of how SE can be applied in different kinds of situations.  Combinations of one or more of them are fully realized when applied in an application domain.  Part 4 currently describes this application in a small number of such domains.  This will be expanded in later updates.  The applications of SE in this part describe the real-world practice of SE.  The generalized knowledge in both Parts 2 and 3 evolves through what we learn from these applications.  [[Foundations of Systems Engineering|Part 2]] includes a discussion of this relationship between theory and practice.
 +
 
 +
===Part 5: [[Enabling Systems Engineering]]===
 +
This part describes approaches to organization that may enable the successful performance of SE activities.
 +
 
 +
Part 4 covers knowledge at the [[Enabling Businesses and Enterprises|enterprise]], [[Enabling Teams|team]], or [[Enabling Individuals|individual]] level. The range of considerations extends from value proposition, business purpose, and governance, down to competency, personal development as a systems engineer, and ethics. 
 +
 
 +
All of these relate to the baseline definitions of SE in Part 3, further generalized in the levels of application in Part 4.  The systems approach in Part 2 should also form a foundation for this part.  Since the practice of SE is transdisciplinary, Part 5 also has a link to Part 6 as discussed below.
 +
 
 +
===Part 6: [[Related Disciplines]]===
 +
This part describes the relationships between SE and other disciplines.
 +
 
 +
Part 6 covers the links between SE and software engineering (SwE), project management (PM), industrial engineering (IE) and procurement.  It also describes how SE is related to specialty engineering, which describes the various system “–ilities” (like reliability, availability, and maintainability) that SE must balance and integrate.
 +
 
 +
The knowledge in this part provides an interface to other bodies of knowledge, focused on how it is linked to Parts 3, 4 and 5 above.
 +
 
 +
===Part 7: [[Systems Engineering Implementation Examples]]===
 +
A set of real-world examples of SE activities demonstrates implementations of the systems engineering knowledge in previous parts of the SEBoK. These examples come in two forms: case studies, which refer the reader to and summarize published examinations of the successes and challenges of SE programs, and vignettes, which are brief, self-contained wiki articles. This part is a key place to look within the SEBoK for lessons learned, best practices, and patterns. Many links connect material in the examples to the conceptual, methodological, and other content elsewhere in the SEBoK.
 +
 
 +
===Part 8: [[Emerging Knowledge]]===
 +
One of the challenges associated with a body of knowledge is that cutting edge and/or emerging ideas are difficult to include. Bodies of knowledge are based on existing literature and resources, and these often do not exist for new topics. To address this, Part 8 of the SEBoK contains those emerging ideas and items that are not easily covered in the other sections of the SEBoK. As these areas mature and as a body of literature is created around them, they will be moved into the other Parts of the SEBoK.
 +
 
 +
===Addenda===
 +
The SEBoK contains a [[Glossary of Terms]], which provides authoritatively-referenced definitions of key terms. This information is displayed when the reader hovers the mouse pointer over a glossary term within an article. It also contains a list of [[Primary References]], with additional information about each reference.  Quicklinks in the left margin provide additional background information, including a [[SEBoK Table of Contents|table of contents]], a listing of articles by [http://sebokwiki.org/1.1.1/index.php?title=Category:Topic topic], and a list of [[Acronyms]].
 +
 
 +
==References==
 +
 
 +
=== Works Cited ===
 +
Adcock, R., Hutchison, N., Nielsen, C., 2016, "Defining an architecture for the Systems Engineering Body of Knowledge," Annual IEEE Systems Conference (SysCon) 2016.
 +
 
 +
=== Primary References ===
 
None.
 
None.
  
===Primary References===
+
=== Additional References ===
No primary references have been identified for version 0.75.  Please provide any recommendations on primary references in your review.
+
None.
 
 
===Additional References===
 
No additional references have been identified for version 0.75.  Please provide any recommendations on additional references in your review.
 
  
 
----
 
----
<center>[[Scope and Context of the SEBoK|< Previous Article]] | [[SEBoK 0.75 Introduction|Parent Article]] | [[Economic Value of Systems Engineering|Next Article >]]</center>
+
<center>[[Scope of the SEBoK|< Previous Article]] | [[Introduction to the SEBoK|Parent Article]] | [[Introduction to Systems Engineering |Next Article >]]</center>
  
 
[[Category:Part 1]]
 
[[Category:Part 1]]
[[Category:Part 1]]
+
[[Category:Introduction to the SEBoK]]
 
 
==Comments from SEBok 0.5 Wiki==
 
No comments were logged for this article in the SEBoK 0.5 wiki.  Because of this, it is especially important for reviewers to provide feedback on this article.  Please see the discussion prompts below.
 
  
{{DISQUS}}
+
<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>

Latest revision as of 22:23, 18 November 2023

The Guide to the Systems Engineering Body of Knowledge (SEBoK) is a living authoritative guide that discusses knowledge relevant to Systems Engineering. SEBoK does not contain all of this knowledge itself but provides a starting point and key resources to allow the reader to navigate the wider body of knowledge that exists in published sources. To do this, SEBoK:

  • Defines relevant knowledge and structures it to facilitate understanding.
  • Provides short discussions of key ideas, principles and concepts within that structure.
  • Points to reference sources important to the discipline, which explore these ideas in more detail.

In doing this, it is inevitable that differences in terminology, alternative approaches, and even fundamentally different ways of thinking within the knowledge will appear. SEBoK attempts were possible to provide clarity of similar or overlapping ideas, or to highlight real differences and the reasons behind them. In particular, the SEBoK Glossary of Terms contains the most used or generally agreed upon definitions of terms when it can, but may highlight more than one definition if needed to show breadth of current thinking.

SEBoK Structure

Figure 1, below, illustrates the eight parts of the SEBoK and how they are related.

Part 1. SEBoK IntroductionPart 4. Applications of SEPart 6. Related DisciplinesPart 7. SE Implementation ExamplesPart 5. Enabling SEPart 2. SE FoundationsPart 3. SE & ManagementPart 8. Emerging Knowledge
Figure 1 Scope of SEBoK Parts and related knowledge (SEBoK Original).

The scope of each part and the key relationships amongst them are briefly discussed below. For a more detailed discussion of how this structure was evolved, see (Adcock et al, 2016).

Overview of Parts

Part 1: SEBoK Introduction

This part explains the scope, context, and structure of the SEBoK, and of systems engineeringsystems engineering (SE).

An overview of who should use the SEBoK, and for what purpose, is followed by detailed use cases. Systems engineering’s economic value, history, and relationship to other disciplines are discussed. Part 1 also contains a section which discusses the future evolution of the SEBoK and allows for new areas of content to be introduced before being transitioned into other SEBoK parts.

Part 2: Foundations of Systems Engineering

This part provides an introduction and overview of areas of knowledge which provide the foundations of SE.

A discussion of the definitions and basic concepts of systemssystems is followed by an overview of the principles, concepts, methods, models and patterns of some of the key foundational areas of systems sciencesystems science. This includes a detailed consideration of the foundational knowledge related to systems models and modelling.

Part 2 looks in more detail at two aspects of this foundational knowledge of particular value to SE. The first is to discuss aspects of systems knowledge related to a systems approachsystems approach to complex problems and opportunities. This approach provides foundations for how SE is defined and practiced (see Parts 3 and 5 below). The second is to describe the different ways in which system concepts are applied to real world concerns. The SEBoK defines an engineered systemengineered system (ES) as the primary focus for the application of SE (see Part 4 below).

Part 3: Systems Engineering and Management

This part describes generic knowledge on the practice of SE and related management activities.

Part 3 begins with the life cycle modelslife cycle models common in SE and the general principles behind their application. It then moves on to SE management activities. It covers both technical activities such as requirements, architecture, test and evaluation; and management activities such as planning, measurement, and risk. Next is product and service life management, a distinct area of SE management that emphasizes the entire life cycle including retirement and disposal. An account of SE standards concludes this part.

Focused on what many think of as the main body of SE, including best practices and common pitfalls, this part constitutes a substantial proportion of the SEBoK. As already discussed, the knowledge in Part 3 is based on the systems approach from Part 2. The links between Part 3 and the other parts of the SEBoK are discussed below.

Part 4: Applications of Systems Engineering

This part describes how to apply SE principles to different types of system contextsystem context.

Part 4 focuses on four major engineered systemengineered system contexts in turn: products, services, enterprises, and systems of systems (SoS). For each one, the system abstraction, commercial relationships and application of generic SE is described.

The generalized contexts above should be viewed as overlapping models of how SE can be applied in different kinds of situations. Combinations of one or more of them are fully realized when applied in an application domain. Part 4 currently describes this application in a small number of such domains. This will be expanded in later updates. The applications of SE in this part describe the real-world practice of SE. The generalized knowledge in both Parts 2 and 3 evolves through what we learn from these applications. Part 2 includes a discussion of this relationship between theory and practice.

Part 5: Enabling Systems Engineering

This part describes approaches to organization that may enable the successful performance of SE activities.

Part 4 covers knowledge at the enterprise, team, or individual level. The range of considerations extends from value proposition, business purpose, and governance, down to competency, personal development as a systems engineer, and ethics.

All of these relate to the baseline definitions of SE in Part 3, further generalized in the levels of application in Part 4. The systems approach in Part 2 should also form a foundation for this part. Since the practice of SE is transdisciplinary, Part 5 also has a link to Part 6 as discussed below.

Part 6: Related Disciplines

This part describes the relationships between SE and other disciplines.

Part 6 covers the links between SE and software engineering (SwE), project management (PM), industrial engineering (IE) and procurement. It also describes how SE is related to specialty engineering, which describes the various system “–ilities” (like reliability, availability, and maintainability) that SE must balance and integrate.

The knowledge in this part provides an interface to other bodies of knowledge, focused on how it is linked to Parts 3, 4 and 5 above.

Part 7: Systems Engineering Implementation Examples

A set of real-world examples of SE activities demonstrates implementations of the systems engineering knowledge in previous parts of the SEBoK. These examples come in two forms: case studies, which refer the reader to and summarize published examinations of the successes and challenges of SE programs, and vignettes, which are brief, self-contained wiki articles. This part is a key place to look within the SEBoK for lessons learned, best practices, and patterns. Many links connect material in the examples to the conceptual, methodological, and other content elsewhere in the SEBoK.

Part 8: Emerging Knowledge

One of the challenges associated with a body of knowledge is that cutting edge and/or emerging ideas are difficult to include. Bodies of knowledge are based on existing literature and resources, and these often do not exist for new topics. To address this, Part 8 of the SEBoK contains those emerging ideas and items that are not easily covered in the other sections of the SEBoK. As these areas mature and as a body of literature is created around them, they will be moved into the other Parts of the SEBoK.

Addenda

The SEBoK contains a Glossary of Terms, which provides authoritatively-referenced definitions of key terms. This information is displayed when the reader hovers the mouse pointer over a glossary term within an article. It also contains a list of Primary References, with additional information about each reference. Quicklinks in the left margin provide additional background information, including a table of contents, a listing of articles by topic, and a list of Acronyms.

References

Works Cited

Adcock, R., Hutchison, N., Nielsen, C., 2016, "Defining an architecture for the Systems Engineering Body of Knowledge," Annual IEEE Systems Conference (SysCon) 2016.

Primary References

None.

Additional References

None.


< Previous Article | Parent Article | Next Article >
SEBoK v. 2.9, released 20 November 2023