Difference between revisions of "Applications of Systems Engineering"

Revision as of 13:04, 6 September 2016

This part of the SEBoK focuses on the application of systems engineering to the creation and life cycle management of various types of systems. In particular, the part covers product systems, service systems, enterprise systems, and system of systems (SoS).

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 is discussed in detail in the KA above.

It is important to note that none of the context above is 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 are part of the application of SE is a key question for how SE is used. The final part of this knowledge, on how SE is applied in the real world, sits within the knowledge base of the various application domain. Some domains have a very detail 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 a little 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. 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

@@ Line 8: / Line 8: @@
 *[[Systems of Systems (SoS)]]
-==Systems Engineering Application Paradigms==
+==Systems Engineering Application==
-Part 3, [[Systems Engineering and Management]], introduces a paradigm that identifies the general goal of all systems engineering efforts; that is the transformation of the specific stakeholder need into a system product or service that provides for the need.  Given this framework, the various knowledge areas of Part 3 provide deeper insight into how to accomplish activities related to the systems engineering life cycle.
+The different ways in which each of these contexts shapes the application of the generic SE Life Cycle and Process knowledge in Part 3 is discussed in detail in the KA above.
-The following paradigms provide a look into the primary similarities and differences of the various applications of systems engineering presented in Part 4. The similarity is that all systems presented in Part 4 are developed to provide for the capabilities needed in an [[Operational Environment (glossary)|operational environment]] and these capability needs take form of activities.  The supply of the systems and the nature of the operational environment differentiate the applications of systems engineering.
+It is important to note that none of the context above is 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.
-===Product System Provisioning===
+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 are part of the application of SE is a key question for how SE is used.  The final part of this knowledge, on how SE is applied in the real world, sits within the knowledge base of the various application domain.  Some domains have a very detail 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 a little of both domain specific guidelines and experienced people.
-Product Systems Engineering is associated with 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 the [[Concept of Operations (ConOps) (glossary)|concept of operations]] (ConOps), which can include [[Use Case (glossary)|use cases]] of the activities of the system in operation.
+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.
-It is important to take into account the [[Binding (glossary)|binding]] of the products and services to the activities. 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.
+The Healthcare SE KA contained in this version of the SEBoK is the first such domain specific extension of the SEBoK.
-===Service System Provisioning===
-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 (SOAs), software as a system (SaS), and cloud computing.
-A primary difference between service systems engineering (SSE) and TSE is the dynamic binding of products and services, potentially from multiple providers, in order to provide a desired service. Thus, the service is dynamically composed from a given service request. 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.
-=== Enterprise System Provisioning===
-The paradigm in Figure 3 illustrates the provision of enterprise systems engineering (ESE) 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. Enterprise System Provisioning.''' (SEBoK Original)]]
-This form is similar to TSE except that the activities of the operational environment typically rely upon services provided by systems of processes. Both [[Business Process (glossary)|business processes]] and system [[Life Cycle Process (glossary)|life cycle processes]] 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.
-===System of Systems Provisioning===
-Finally, the paradigm in Figure 4 illustrates the provisioning of products and services by multiple enterprises in forming a SoS that is created  to meet the complex needs of an operational environment. Note that 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.''' (SEBoK Original)]]
-All of the enterprises that contribute to an SoS are independent and provide value-added products or services that are meaningful individually.
-System of systems engineering (SoSE), particularly when responding to some form of natural or man made crisis, is initiated in the form of a request for service in order to meet a complex situation that has come up. In relationship to the [[System Coupling Diagram (glossary)|system coupling diagram]], 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 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.
 ==References==
 ===Works Cited===
-ISO/IEC/IEEE. 2015. ''[[ISO/IEC/IEEE 15288|Systems and Software Engineering]] -- System Life Cycle Processes''. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions. ISO/IEC/IEEE 15288:2015.
+None
 ===Primary References===
-ISO/IEC/IEEE. 2015. ''[[ISO/IEC/IEEE 15288|Systems and Software Engineering]] -- System Life Cycle Processes''. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions. ISO/IEC/IEEE 15288:2015.
+None.
 ===Additional References===