Applications of Systems Engineering

Lead Author: Bud Lawson, Contributing Author: Rick Adcock

Part 4 of the Guide to the SE Body of Knowledge (SEBoK) focuses on the application of systems engineeringsystems engineering to the creation and life cycle managementlife cycle management of various types of systems.

Figure 1 SEBoK Part 4 in context (SEBoK Original). For more detail see Structure of the SEBoK

In particular, the part covers product systemsproduct systems, service systemsservice systems, enterprise systemsenterprise systems, and systems of systemssystems of systems (SoS). It also contains a knowledge area describing Healthcare SE as a domain extension of these general SE approaches. This is the first of a number of planned domain-based extensions.

Knowledge Areas in Part 4

Each part of the SEBoK is divided into knowledge areas (KAs), which are groupings of information with a related theme. Part 4 contains the following KAs:

Systems Engineering Application

The different ways in which each of these contexts shapes the application of the generic SE Life Cycle and Process knowledge in Part 3 are discussed in detail in the KA above.

It is important to note that none of the contexts above are intended to be wholly separate or mutually exclusive from the others. They should be seen as overlapping and related frameworks which provide a starting point for how generic SE might be used to fulfil real world needs. We might think of each as a model of how SE can work in the real world. Each gives advice on how to use generic SE life cycle and process knowledge against its own viewpoint. If necessary, each may also develop new or extended knowledge relevant to its context, which becomes part of the extended toolkit of SE. Like any set of models, each has its own simplifications, strengths and weaknesses. As a general principle we would always select the simplest model available which fits the purpose and use that. For a complex outcome the combination of a number of models may be needed.

The real-world application of SE is no different. In most real projects, combinations of Product, Service, Enterprise and SoS knowledge may be needed to achieve success. The extent to which these combinations are taken from pre-determined approaches vs. the need for systems engineers to create such combinations as part of the application of SE is a key question for how SE is used. The final part of this knowledge, how SE is applied in the real world, sits within the knowledge base of the various application domain. Some domains have a very detailed set of procedures, guidelines and standards relevant to that domain, while others take general SE and apply it as needed using the judgement of those involved. In general, all domains have parts of both domain specific guidelines and experienced people. The SEBoK was originally written to be domain independent, other than through the application examples in part 7. To complete the SEBoK, we intend to create a series of Domain Application KA. These will give an overview of how SE application maps to domain practice. They are aimed at both the general SE reader who wants to know more about a domain and those working within a domain.

The Healthcare SE KA contained in this version of the SEBoK is the first such domain specific extension of the SEBoK.