Scope of the SEBoK

The SEBoK is a large compendium of information about systems engineering. It:

• is a guide to the body of systems engineering knowledge which provides references to detailed sources for additional information; it is not a self-contained knowledge resource
• is domain-independent, with implementation examples to provide domain-specific context
• focuses on engineered systems (ES), that is, products, services, enterprises, and systems of systems (SoS), while treating social and natural systems as relevant and important environmental considerations for ESs (see the discussion below for more on this as well as look at What is a System? in Part 2)
• recognizes that SE principles can be applied differently to different types of systems (see Part 4)
• explores the interaction between SE and other disciplines, highlighting what systems engineers need to know about these disciplines (see Part 6)

Each of these considerations depends upon the definition and scope of SE itself, which is the subject of the next section.

SE and Engineered Systems Project Life Cycle Context

Figure 1 summarizes the main agents, activities, and artifacts involved in the life cycle of SE, in the context of a project to create and evolve an ES.

For each primary project life cycle phase, we see activities being performed by primary agents, changing the state of the ES.

• Primary project life cycle phases appear in the leftmost column. They are system definition, system initial operational capability (IOC) development, and system evolution and retirement.
• Primary agents appear in the three inner columns of the top row. They are systems engineers, systems developers, and primary project-external bodies (users, owners, external systems) which constitute the project environment.
• The ES, which appears in the rightmost column, may be a product, a service, and/or an enterprise.

In each row:

• boxes in each inner column show activities being performed by the agent listed in the top row of that column
• the resulting artifacts appears in the rightmost box

Arrows indicate dependencies: an arrow from box A to box B means that the successful outcome of box B depends on the successful outcome of box A.

Two-headed arrows indicate a two-way dependencies: an arrow that points both from box A to box B and from box B to box A means that the successful outcome of each box depends on the successful outcome of the other.

For example, consider how the inevitable changes that arise during system development and evolution are handled:

• One box shows that the system’s users and owners may propose changes.
• The changes must be negotiated with the systems developers, who are shown in a second box.
• The negotiations are mediated by systems engineers, who are shown in a third box in between the first two.
• Since the proposed changes run from left to right and the counter-proposals run from right to left, all three boxes are connected by two-headed arrows. This reflects the two-way dependencies of the negotiation.

Figure 1. SE and Engineered System Project Life Cycle Context: Related Agents, Activities, and Artifacts. (SEBoK Original)

An agent-activity-artifact diagram like Figure 1 can be used to capture complex interactions. Taking a more detailed view of the present example demonstrates this:

• The system’s users and owners (stakeholders) propose changes to respond to competitive threats or opportunities, or to adapt to changes imposed by independently evolving external systems, such as Commercial-off-the-Shelf COTS products, cloud services, or supply chain enablers.
• Negotiation among these stakeholders and the system developers follows, mediated by the SEs.
• The role of the SEs is to analyze the relative costs and benefits of alternative change proposals, and synthesize mutually satisfactory solutions.

SEBoK Domain Independence Context

The SEBoK uses language and concepts that are generally accepted for domain-independent SE. For example, the domain-independent conceptual foundations of SE are elaborated in Part 2, Systems. However, each of the numerous domains in which SE is practiced — including telecommunications, finance, medicine, and aerospace — has its own specialized vocabulary and key concepts. Accordingly, the SEBoK is designed to show how its domain-independent material relates to individual domains, by means of examples that tell stories of how SE is applied in particular domains.

While the main body of the SEBoK (Parts 1 through 6) is domain-independent, all of (Part 7 ) consists of examples (case studies and vignettes), each set in a particular domain such as aerospace, medicine, or software, and featuring vocabulary and concepts special to that domain. There are similar vignettes in some of the Use Cases in Part 1.

These examples demonstrate the effect of domain on the application of SE and complement the domain-independent information elsewhere in the SEBoK. They show how a concept works in a given domain and provide a fair opportunity for reviewers to reflect on whether there are better ways to capture application-dependent aspects of SE knowledge.

The authors recognize that case studies and vignettes add significant value to the SEBoK, and expect many more to be added as the SEBoK evolves.

SEBoK Life Cycle Context

Figure 2 summarizes the main agents, activities, and artifacts in the SEBoK life cycle.

The SEBoK is one of two complementary products. The other, which uses the content of the SEBoK to define a core Body of Knowledge to be included in graduate SE curricula, is called the Graduate Reference Curriculum in Systems Engineering (GRCSE) (Pyster et al 2012). GRCSE is not a standard, but a reference curriculum to be tailored and extended to meet the objectives of each university’s graduate program. These products are being developed by the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) project (see http://www.bkcase.org).

Figure 2. SEBoK Life Cycle and Context: Related Agents, Activities, and Artifacts. (SEBoK Original)

The BKCASE project, led by Stevens Institute of Technology and the Naval Postgraduate School, draws upon three primary resources. The U.S. Department of Defense (DoD) has provided the funding and a representative, but does has not constrain or direct the project’s approach and content. The DoD Systems Engineering Research Center (SERC), a DoD university-affiliated research center operated by Stevens Institute of Technology, supports BKCASE management and infrastructure and is the means by which DoD funding is delivered to the BKCASE project. The international author team of 70 members has been selected for expertise in SE and diversity of national origin (authors have come from 15 different countries), economic sector (government, industry, academia), and SE specialty area. Except for travel support in a few cases, authors have donated their time to the development of the SEBoK content.

The SEBoK content has been developed incrementally. Each of the prototype versions (0.25, 0.5, and 0.75) has undergone an open review by all interested parties. Over 200 reviewers have submitted thousands of comments, each of which has been adjudicated. Upon completion of the initial SEBoK and GRCSE development in late 2012, the Institute of Electrical and Electronic Engineers Computer Society (IEEE-CS) and the International Council on Systems Engineering (INCOSE), together with the SERC, are anticipated to become the primary stewards for both the SEBoK and the GRCSE. Interested parties will be able develop, operate, and support derivative products and services such as courseware, education, certification, and domain-specific versions of the SEBoK and the GRCSE. Copyright Information offers complete information about what others may do with the content of the SEBoK.

References

Works Cited

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

Pyster, A., D.H. Olwell, T.L.J. Ferris, N. Hutchison, S. Enck, J.F. Anthony, D. Henry, and A. Squires (eds). 2012. Graduate Reference Curriculum for Systems Engineering (GRCSE™), version 0.5. Hoboken, NJ, USA: The Trustees of the Stevens Institute of Technology ©2012. Available at: http://www.bkcase.org/grcse-05/.

Primary References

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

Pyster, A., D.H. Olwell, T.L.J. Ferris, N. Hutchison, S. Enck, J.F. Anthony, D. Henry, and A. Squires (eds). 2012. Graduate Reference Curriculum for Systems Engineering (GRCSE™), version 0.5. Hoboken, NJ, USA: The Trustees of the Stevens Institute of Technology ©2012. Available at: http://www.bkcase.org/grcse-05/.

Additional References

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

---

< Previous Article | 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