Structure of the SEBoK

As discussed in SEBoK 0.75 Introduction, the Guide to the Systems Engineering Body of Knowledge (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.

Structure

• Part 1: SEBoK 0.75 Introduction. This part provides the “opening” material to the SEBoK. Principally, the section introduces the SEBoK (purpose, scope, context, structure, and economic value), the concepts of systems and systems engineering (including an introduction to the history and future challenges of SE, an introduction to the discussion of related disciplines, the use cases for the SEBoK, a discussion of SEBoK development and way ahead; and acknowledgements).
• Part 2: Systems. This part focuses on defining what is created by systems engineering and on providing links into 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 systems engineering), discusses the different types of systems, provides information on different representations of systems (models), and discusses the systems approach and systems challenges. The systems approach and systems engineering challenges in particular have strong links to Parts 3 and 4.
• 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 and system definition, realization, and deployment and use, as well as SE management processes such as risk, decision, configuration, information, and quality management. Part 3 also includes an overview of life cycles, and 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 systems engineering. It also includes information on SE standards, documented best practices, and common pitfalls for performing SE or systems management activities as appropriate.
• Part 4: Applications of Systems Engineering. Part 4 focuses on providing guidance on how the processes and methods presented in Part 3 can and should be applied to specific types of systems, specifically products, services, enterprises, and systems of systems (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 organizing for SE, including value propositions, purpose, and governance; considerations at the business and enterprise level; and considerations for teams and individuals within an organization, including competency, personal SE development, and ethics.
• Part 6: Related Disciplines. This part contains knowledge areas which deal with the intertwining of SE with software engineering (SwE), project management (PM), industrial engineering, procurement and acquisition, and specialty engineering, including discussions of the various system "–ilities" to be balanced and integrated by SE.. Part 6 was the last part to be added to the architecture and, as such, is the least mature. The authors have accepted this for version 0.5, but hope that reviewers will provide additional feedback for this part.
• 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. 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 then provides linkages from the case study information to the related SEBoK knowledge areas (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.
• SEBoK Concept Map. A key activity in the integration of the various parts of the SEBoK has been the development, appliaction, and iteration of a Systems Modeling Language (SysML) concept map, showing the relationships among the elements of the SEBoK and its external environment. The Appendix presents and discusses the Concept Map, along with a short SysML summary.

References

Works Cited

None.

Primary References

No primary references have been identified for version 0.75. Please provide any recommendations on primary references in your review.

Additional References

No additional references have been identified for version 0.75. Please provide any recommendations on additional references in your review.

---

<- Previous Article | Parent Article | Next Article ->