Structure of the SEBoK
As discussed in the Guide to the Systems Engineering Body of Knowledge (SEBoK) SEBoK 1.0 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.
Structure
- Part 1: SEBoK 1.0 Introduction — To help you get the most out of the SEBoK, this section explains the scope, context, and structure of the SEBoK, and then turns to aspects of systems engineering (SE) itself that matter as you begin to use the SEBoK: SE's economic value, history, future, and relationship to other disciplines. An overview of who should use the SEBoK, and for what purpose, is followed by detailed use cases. The Introduction concludes with a summary of how the SEBoK has evolved, and acknowledgments of the many individuals and organizations who have helped the SEBoK come to be.
- Part 2: Systems — Starting what a system is, this section covers systems fundamentals and moves on to describe systems science in terms of history and major questions, systems thinking as a set of ideas to be used in SE, and modeling as a central process of SE. It concludes by looking at how to take a systems approach to an engineered system, which leads naturally into the next two parts, which are concerned with SE management and applications.
- 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 (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 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 (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. ] I propose that we eliminate this sentence. See the rationale in my cover email.
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 (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 article Scope and Context of the SEBoK. These figures will be useful in navigating the SEBoK.
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.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus