SEBoK Introduction

Systems engineering (SE) is essential to the success of many human endeavors. Today, SE is increasingly recognized worldwide for its importance in the development, deployment, operation, and evolution of systems with a wide variety of scale, complexity, and purpose.

The purpose of the SEBoK is to provide a consensus-based, evolvable baseline of SE knowledge that strengthens mutual understanding among SE practitioners and the people in other disciplines with whom they interact. Shortfalls in such mutual understanding are a major source of system failures, which have increasingly severe impacts as systems become more globally interactive and critical to people’s health, security, and quality of life.

As a first step in this direction, the SEBoK provides the following baseline definitions of its key terms: system, engineered system, systems engineering, and systems engineer.

For the purposes of the SEBoK, a system is primarily defined as "a set of elements and a set of inter-relationships between the elements such that they form a bounded whole relative to the elements around them" (Bertalanffy 1968) and which exists in an environment which contains related systems and conditions. While there are many definitions of the word “system,” the SEBoK authors believe that this definition is comprehensive enough to encompass most of those which are relevant to systems engineering. The SEBoK also specifically defines an engineered system as an open, system of technical or sociotechnical elements that exhibits emergent properties not exhibited by its individual elements. Its characteristics include being created by and for people; having a purpose, with multiple views; satisfying key stakeholders’ value propositions; having a life cycle and evolution dynamics; having a boundary and an external environment; and being a part of a system-of-interest hierarchy.

For the purposes of the SEBoK, systems engineering is defined as “an interdisciplinary approach and means to enable the realization of successful systems” (INCOSE 2011). It focuses on holistically and concurrently understanding stakeholder needs; exploring opportunities; documenting requirements; and synthesizing, verifying, validating, and evolving solutions while considering the complete problem, from system concept exploration through system disposal. For the purposes of the SEBoK, a systems engineer is defined as “a person who practices systems engineering as defined above.” Systems engineering activities may be conducted by any competent person whatever their job title or professional affiliation. A Systems Engineer is a person whose systems engineering capabilities and experience include sustained practice, specialization, leadership or authority over systems engineering activities.

To download a PDF of Part 1, please click here.

Part 1 Articles

The following articles are discussed in Part 1 and provide an introduction to the tenets of the SEBoK:

Purpose of the SEBoK

The purpose of the SEBoK is to provide a consensus-based, evolvable baseline of systems engineering (SE) knowledge that can enable stronger mutual understanding among SE practitioners and among the people in other disciplines with whom they interact. Shortfalls in these mutual understandings are a major source of system failures. Ongoing studies of system cost and schedule failures (Gruhl-Stutzke 2005; Johnson 2006) and safety failures (Leveson 2012) have shown that the failures have mostly come not from their domain disciplines, but from lack of adequate SE.

The SEBoK is intended to enable stronger mutual understanding by describing the boundaries, terminology, content, and structure of systems engineering (SE) that are needed to systematically and consistently support the six broad purposes shown in Table 1.

**Table 1. SEBoK Purposes (Table Developed for BKCASE)**
	Purpose	Description
1	Inform Practice	Inform systems engineers about the boundaries, terminology, and structure of their discipline and point them to useful information needed to practice SE in any application domain.
2	Inform Research	Inform researchers about the limitations and gaps in current SE knowledge that should help guide their research agenda.
3	Inform Interactors	Inform performers in interacting disciplines (system implementation, project and enterprise management, other disciplines) of the nature and value of SE.
4	Inform Curriculum Developers	Inform organizations defining the content that should be common in undergraduate and graduate programs in SE.
5	Inform Certifiers	Inform organizations certifying individuals as qualified to practice systems engineering.
6	Inform SE Staffing	Inform organizations and managers deciding which competencies that practicing systems engineers should possess in various roles ranging from apprentice to expert.

The SEBoK is intended to be a guide to the body of knowledge, but does not seek to capture all the knowledge directly. It provides references to more detailed sources of knowledge, and is constructed to facilitate easy update as the field evolves and new sources of knowledge emerge. All references included in the SEBoK are generally available to any interested reader (i.e., no proprietary information is referenced), but they are not all free (e.g., some books or standards that must be purchased from their publishers). The criterion for including a source is simply that the authors believed it was among the best generally available sources of information on a particular subject.

The SEBoK is also intended to be global in applicability. Despite the challenge that SE is practiced differently from industry to industry and country to country, the SEBoK must be useful to systems engineers around the world. The authors have been chosen from a diverse set of locales and industries to help ensure its broad applicability, and the extensive global review feedback on several drafts has enabled them to refine the SEBoK into something that is even more universally applicable.

The SEBoK should inform a wide variety of user communities on essential SE concepts and practices, in ways that can be tailored to different enterprises and activities, while retaining more commonality and consistency than is currently possible. The dynamism of the world in which SE is being applied will require continuing update of the SEBoK.

Scope and Context of the SEBoK

The SEBoK is one of two products being developed by the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) project. The other product, the Graduate Reference Curriculum in Systems Engineering (GRCSE) uses the content of the SEBoK to define a core Body of Knowledge to be included in graduate SE curricula. The GRCSE is not a standard, but a reference curriculum to be tailored and extended to meet the objectives of each university’s graduate program.

The majority of the SEBoK (Parts 2 – 6) focuses on domain-independent information – that which is universal to systems engineering regardless of the domain in which it is applied. Part 7 includes examples from real projects, which illustrate the concepts discussed in elsewhere in the SEBoK. As real examples, these include considerations relevant to specific domains, such as aerospace, medical, and transportation. The SEBoK scope is primarily focused on SE in the context of Engineered Systems (glossary) (ES), though general systems concepts are also discussed in Part 2 Systems. Also, the SEBoK includes considerations for closely-related disciplines; i.e., disciplines such as software engineering and project management, which are strongly intertwined with the practice of SE.

To elaborate on the context of the SEBoK, Part 1 provides two diagrams. One summarizes the agents, activities, and artifacts involved in the SEBoK’s definition by an international group of volunteer authors; its review by the SE community at large; its life cycle evolution management and support by the two primary international SE-related professional societies, the Institute of Electrical and Electronic Engineers (IEEE) and the International Council on Systems Engineering (INCOSE); and its use in derivative products and services by the community at large.

A similar agent-activity-artifact context diagram summarizes the interactions among systems engineers, systems developers, and an engineered system’s environment across its life cycle of system definition, development, evolution (production, utilization, and support) and retirement. These are further elaborated in Part 2 on the nature of systems and systems engineering and in the Life Cycle Models article in Part 3. Please see the Scope and Context of the SEBoK article for additional information.

Systems and Systems Engineering

Definitions of the terms “System,” “Engineered System,” “Systems Engineering,” and “Systems Engineer” were provided at the beginning of this Introduction. For the purposes of the SEBoK, the elaborated (INCOSE 2011). definition of “Systems Engineering” is modified to, “It focuses on holistically and concurrently understanding stakeholder needs; exploring opportunities; documenting requirements; and synthesizing, verifying, validating, and evolving solutions while considering the complete problem, from system concept exploration through system disposal.”

With respect to terminology, as with many special disciplines, Systems Engineering (SE) uses some terms in ways that may be unfamiliar outside the discipline. For example, in systems science, “open” means “not closed,” in terms of a system’s being able to interact with its environment. But in the area of system interface standards, “open” means “non-proprietary” or “publicly agreed upon.” And, depending on the context, the term “system” may refer to an engineered system, a natural system, a social system, or all three.

As the province of SE is engineered systems, most of the discussions assume that this is the context. Thus, “the system architecture” will refer to the architecture of the system being engineered (e.g., a spacecraft) and not the architecture of a natural system outside its boundary (e.g., the solar system). However, this may produce ambiguities at times: for example, does “management” refer to management of the SE process or management of the system being engineered? In such cases, the SEBoK tries to avoid misinterpretations by elaborating the alternatives into “system management” or “systems engineering management.”

In some cases, terms reflect the historical evolution of SE. “Soft SE” was introduced in (Checkland 1981) to emphasize the criticality of human factors in SE, an emphasis that is now accepted as an integral part of SE. Similarly, “systems architecting” was introduced in (Rechtin 1991) to emphasize that better systems resulted from approaches taken by architects to concurrently rather than sequentially address a system’s operational concept, requirements, architecture, plans, and economics, again an emphasis that is now accepted as an integral part of SE.

In other cases, terms have considerable overlap, such as “enterprise SE” and “system of systems SE.” Here and in general, the SEBoK provides an extensive Glossary to show how these terms are used in the SEBoK, and to identify how the terms may vary in different contexts. When these need further explanation, the Glossary entry includes pointers to the relevant articles providing detailed discussions. For more discussion on the definition of systems, please see the What is a System? article in Part 2; for more on systems engineering, please see Part 3.

SEBoK Uses

The diversity of communities involved with systems engineering (its various specialists, other engineers, managers, researchers, educators) means that its content will be drawn upon in several ways. The SEBoK includes several use cases, showing how these communities will use the SEBoK, and identifying the parts of the SEBoK that will be of most interest to them. These can be found in the article SEBoK Users and Uses. This discussion includes consideration of primary users – those who will directly use the SEBoK – and secondary users – those who are expected to require assistance from a systems engineer to utilize the SEBoK. For more information, please see the SEBoK Users and Uses article.

SEBoK Development

The first version of the SEBoK – a prototype labeled Version 0.25 – was released as a PDF document for limited review in September 2010. A total of 3135 comments were received on this document from 114 reviewers across 17 countries. The author team reviewed these comments, paying particular attention to the reviews related to content and highlighting diversity within the community. The second version of the SEBoK – a prototype labeled Version 0.5 – was released on September 19, 2011. This, the third version 0.75 of the SEBoK, was released on March 15, 2011.

In January 2011, the authors agreed to transition from a document-based SEBoK to a wiki-based SEBoK, with the intent to make the information readily accessible worldwide, provide additional methods for searching and navigating the content, and provide a forum for the community to offer feedback while keeping the content of the SEBoK stable between versions. For more information, please see the SEBoK Evolution article.

References

Works Cited

INCOSE. 2011. INCOSE Systems Engineering Handbook, version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering (INCOSE). INCOSE-TP-2003-002-03.2.

Bertalanffy, L. von. 1968. General System Theory: Foundations, Development, Applications. Revised ed. New York, NY, USA: Braziller.

Checkland, P. 1981. Systems Thinking, Systems Practice. Hoboken, NJ, USA: Wiley (2nd edition 1999).

Gruhl, W. and Stutzke, R. 2005. “Werner Gruhl Analysis of SE Investments and NASA Overruns,” in Stutzke, R., Estimating Software-Intensive Systems. Boston, MA, USA: Addison Wesley, page 290.

Johnson, J. 2006. My Life Is Failure: 100 Things You Should Know to Be a Better Project Leader. Boston, MA, USA: Standish Group International.

Leveson, N. 2012. Engineering a Safer World: Systems Thinking Applied to Safety. Cambridge, MA, USA: MIT Press.

Rechtin, E. 1991. Systems Architecting. Upper Saddle River, NJ, USA: Prentice Hall.

Primary References

INCOSE. 2011. Systems Engineering Handbook, version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering (INCOSE). INCOSE-TP-2003-002-03.2.

Sage, A., and Rouse, W. (eds.) 1999. Handbook of Systems Engineering and Management. Hoboken, NJ, USA: John Wiley and Sons, Inc.

Additional References

Bertalanffy, L. von. 1968. General System Theory: Foundations, Development, Applications. Revised ed. New York, NY, USA: Braziller.

Blanchard, B., and Fabrycky, W. 2010. Systems Engineering and Analysis, (5th edition). Saddle River, NJ, USA: Prentice Hall.

Checkland, P. 1981. Systems Thinking, Systems Practice. Hoboken, NJ, USA: Wiley (2nd edition 1999).

Booher, H. (ed.) 2003. Handbook of Human Systems Integration. Hoboken, NJ, USA: Wiley.

Hitchins, D., 2007. Systems Engineering: A 21st Century Methodology. Chichester, England: Wiley.

< Return to Table of Contents | Parent Article | Next Article >

SEBoK v. 1.9.1 released 30 September 2018

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