Difference between revisions of "Applications of Systems Engineering"

Latest revision as of 22:54, 18 November 2023

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.

References

Works Cited

None

Primary References

None.

Additional References

None.

< Previous Article | Parent Article | Next Article > SEBoK v. 2.9, released 20 November 2023

@@ Line 1: / Line 1: @@
-This part of the SEBoK focuses on the application of systems engineering to the creation and [[Life Cycle Management (glossary)]] of various types of systems. In particular, the engineering of [[Product System (glossary)|Product Systems (glossary)]], the engineering of [[Service System (glossary)|Service Systems (glossary)]], the engineering of an [[Enterprise System (glossary)|Enterprise Systems (glossary)]] as well as the engineering of [[System of Systems (SoS) (glossary)|Systems of Systems (glossary)]].
+----
-==Knowledge Areas==
+'''''Lead Author:''''' ''Bud Lawson'', '''''Contributing Author:''''' ''Rick Adcock''
-The following Knowledge Areas are included in Part 4:
+----
+Part 4 of the Guide to the SE Body of Knowledge (SEBoK) focuses on the application of {{Term|Systems Engineering (glossary)|systems engineering}} to the creation and {{Term|Life Cycle Management (glossary)|life cycle management}} of various types of systems.
+[[File:SEBoK_Context_Diagram_Inner_P4_Ifezue_Obiako.png|centre|thumb|600x600px|'''Figure 1 SEBoK Part 4 in context (SEBoK Original).''' For more detail see [[Structure of the SEBoK]]]]
+In particular, the part covers {{Term|Product System (glossary)|product systems}}, {{Term|Service System (glossary)|service systems}},  {{Term|Enterprise System (glossary)|enterprise systems}}, and {{Term|System of Systems (SoS) (glossary)|systems 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:
 *[[Product Systems Engineering]]
 *[[Service Systems Engineering]]
 *[[Enterprise Systems Engineering]]
 *[[Systems of Systems (SoS)]]
+*[[Healthcare Systems Engineering]]
-==Systems Engineering Application Paradigms==
+==Systems Engineering Application==
-In the introduction to Part 3 [[Systems Engineering and Management]], a paradigm was introduced that provides insight into the fundamental goal of all systems engineering efforts; that is transforming the need for operational capabilities into a supplied product or service.  Given this framework, the various knowledge areas of Part 3 have provided deeper insight into how to accomplish systems engineering life cycle-related activities.
+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.
-The following paradigms provide insight into the primary commonalities and differentiators of the various applications of systems engineering presented in this part.  Concerning the commonality, all products and services are developed to provide for the capabilities needed in an [[Operational Environment (glossary)]] in the form of activities.  The supply of the products and services and the nature of the operational environment differentiate the applications.
+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 paradigm in Figure 1 illustrates the main result of TSE (Traditional Systems Engineering), that is, the supply of products and services that fulfill the capability needs as activities in an operational environment.  In TSE, the operational environment is often described by some form of [[Concept of Operations (ConOps) (glossary)]] that can include [[Use Case (glossary)|Use Cases (glossary)]] of the activities of the system in operation.
+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.
-[[File:062611_BL_Product_Services_Provisioning_Paradigm.png|thumb|center|600px|Figure 1. Product/Service Provisioning (Figure Developed for BKCASE)]]
+The Healthcare SE KA contained in this version of the SEBoK is the first such domain specific extension of the SEBoK.
-It is important to take into account the [[Binding (glossary)]] of the products and services to the activities.  As implied by the figure, the operational environmental needs  are met  by directly binding products and/or services to the needs of one or more of the activities of the operational environment. In a manner consistent with ISO/IEC 15288, the products and services are composed of systems in which hardware, software, and human elements are supplied. Thus a mixture of physical products (often including software) and services such as logistics, help-desk functions, etc., may be provided. The supply of products and services can be a result of a direct acquisition or the result of acquiring products or services that have been provided for a marketplace. Note that the provisioning of products and services when humans are involved (a hospital provides a good example) may even be classified as [[Sociotechnical System (glossary)]].
-The paradigm in Figure 2 illustrates the provision of Service Systems. The growth of this model has been stimulated to a large extent due to the widespread availability of IT services such as Service Oriented Architectures (SOA), Software as a System (SaS), and Cloud Computing.
-[[File:062611_BL_Service_Systems_Paradigm.png|thumb|600px|center|Figure 2. Service System Provisioning (Figure Developed for BKCASE)]]
-A primary difference between SSE (Service Systems Engineering) and TSE is the Dynamic [[Binding (glossary)]] of products and services, potentially from multiple providers, in order to provide a desired service. Thus, from a given service request, the service is dynamically composed. In the background there are a variety of hardware, software, and even human elements that provide the elements of a service. In contrast to an operational environment that is sustained, the service requested may be viewed as a temporary environment established to provide the service and it disappears after the service has been provided.
-The paradigm in Figure 3 illustrates the provision of ESE (Enterprise Systems Engineering) to meet the capability needs in the form of enterprise activities.
-[[File:062611_BL_Engineering_of_an_Enterprise_Paradigm.png|thumb|600px|center|Figure 3. Engineering of an Enterprise (Figure Developed for BKCASE)]]
-This form is similar to the TSE with the main difference that the activities of the operational environment typically rely upon services provided by Systems of Processes (both Business Processes and System Life Cycle Processes) that are essential in operating the enterprise. In addition, the products and services that are supplied to the enterprise include those that support their own value added production of products and services as well as their infrastructure systems.
-Finally, the paradigm in Figure 4 illustrates the provisioning of products and services by multiple enterprises in forming a System of Systems that is created in order to meet the complex needs of an operational environment. Note: this could be meeting a crisis situation or meeting the needs of a new type of operation where multiple enterprises provide a new form of added value based upon their combined products and services.
-[[File:062611_BL_Systems_of_Systems_Paradigm.png|thumb|600px|center|Figure 4. System of Systems Provisioning (Figure Developed for BKCASE)]]
-All of the enterprises that contribute to an SoS are independent and provide value-added products or services that are meaningful individually.
-SoSE (System of Systems Engineering), particularly when responding to some form of natural or manmade crisis, is initiated in the form of a request for service in order to meet a complex situation that has arisen. In relationship to the [[System Coupling Diagram (glossary)]] SoSE involves accelerated engineering of the Respondent System that will interact with the Situation System.  Thus, instantiated system assets in the form of products and/or services are supplied from multiple enterprises and quickly integrated in providing the respondent service. In a manner similar to Service Systems, the operational environment disappears when the crises has been handled.
-SoSE (System of Systems Engineering) is also applied in merging the operations of multiple enterprises in order to provide some new form of service. In contrast to unplanned crises, this is the result of planned development. The formation of the Department of Homeland Security in the USA is an example. In the private sector, multiple organizations may integrate their enterprise operations in order to meet an opportunity in a new marketplace.
-These paradigms have provided an introduction to Part 4 and should be kept in mind as the reader proceeds to understand the detailed description of the application of systems engineering in the  Knowledge Areas.
 ==References==
 ===Works Cited===
-None.
+None
 ===Primary References===
-No primary references have been identified for version 0.75.  Please provide any recommendations on additional references in your review.
+None.
 ===Additional References===
-No additional references have been identified for version 0.75.  Please provide any recommendations on additional references in your review.
+None.
 ----
-<center>[[Application of Systems Engineering Standards|<- Previous Article]] | [[SEBoK Table of Contents|Parent Article]] | [[Product Systems Engineering|Next Article ->]]</center>
+<center>[[Application of Systems Engineering Standards|< Previous Article]] | [[SEBoK Table of Contents|Parent Article]] | [[Product Systems Engineering|Next Article >]]</center>
-[[Category:Part 4]][[Category:Part]]
+<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>
-{{5comments}}
+[[Category:Part 4]][[Category:Part]]