Difference between revisions of "Guidance for Systems Engineering Novices"
Jump to navigation
Jump to search
m (Bkcase moved page Use Case 0: Systems Engineering Novices to Guidance for Systems Engineering Novices: Updating to reflect new persona approach) |
|||
| (28 intermediate revisions by 7 users not shown) | |||
| Line 3: | Line 3: | ||
==Learn the Basic Terms== | ==Learn the Basic Terms== | ||
As discussed in the [[SEBoK Introduction| Introduction to the SEBoK]], there are four key terms that you should first understand when learning about systems engineering (SE): | As discussed in the [[SEBoK Introduction| Introduction to the SEBoK]], there are four key terms that you should first understand when learning about systems engineering (SE): | ||
| − | *A | + | *A {{Term|System (glossary)|system}} is “a collection of elements and a collection of inter-relationships amongst the elements such that they can be viewed as a bounded whole relative to the elements around them.” Open systems exist in an environment described by related systems with which they may interact and conditions to which they may respond. While there are many definitions of the word “system,” the SEBoK authors believe that this definition encompasses most of those which are relevant to SE. |
| − | *An | + | *An {{Term|Engineered System (glossary)|engineered system}} is an open system of technical or {{Term|Sociotechnical System (glossary)|sociotechnical}} elements that exhibits emergent properties not exhibited by its individual elements. It is created by and for people; has a purpose with multiple views; satisfies key stakeholders’ value propositions; has a life cycle and evolution dynamics; has a boundary and an external environment; and is part of a system-of-interest hierarchy. |
| − | * | + | *{{Term|Systems Engineering (glossary)|Systems engineering}} is “an interdisciplinary approach and means to enable the realization of successful (engineered) systems.” 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. |
| − | *A | + | *A {{Term|Systems Engineer (glossary)|systems engineer}} is “a person who practices systems engineering” as defined above, and whose systems engineering capabilities and experience include sustained practice, specialization, leadership, or authority over SE activities. These activities may be conducted by any competent person regardless of job title or professional affiliation. |
==Get an Overview== | ==Get an Overview== | ||
| − | The next step for someone new to SE is get an overview of the discipline. [[SEBoK Introduction|Part 1: SEBoK Introduction]] contains four | + | The next step for someone new to SE is get an overview of the discipline. [[SEBoK Introduction|Part 1: SEBoK Introduction]] contains four articles particularly helpful to one new to SE. |
*The article [[Systems Engineering Overview]] frames systems engineering inside the larger topic of ‘Systems Science.’ | *The article [[Systems Engineering Overview]] frames systems engineering inside the larger topic of ‘Systems Science.’ | ||
*The article [[Economic Value of Systems Engineering]] makes the business case for investing in systems engineering as a way to reduce total ownership cost. | *The article [[Economic Value of Systems Engineering]] makes the business case for investing in systems engineering as a way to reduce total ownership cost. | ||
| − | *The article [[Systems Engineering and Other Disciplines]] discusses briefly how systems engineers and other engineers interact as | + | *The article [[Systems Engineering and Other Disciplines]] discusses briefly how systems engineers and other engineers interact as they develop complex systems together. |
| − | *Finally, the article [[Systems Engineering: Historic and Future Challenges]] gives a quick history of the discipline and discusses what | + | *Finally, the article [[Systems Engineering: Historic and Future Challenges]] gives a quick history of the discipline and discusses what lies ahead. |
| − | ==Learn | + | ==Learn About Systems== |
| − | Engineering is often described as the application of science to develop new products or systems. [[Systems|Part 2: Systems]] describes some of the underlying systems principles that form the foundation for systems engineering. | + | Engineering is often described as the application of science to develop new products or systems. [[Foundations of Systems Engineering|Part 2: Foundations of Systems Engineering]] describes some of the underlying systems principles that form the foundation for systems engineering. |
*The Knowledge Area on [[Systems Fundamentals]] contains five articles. [[What is a System?]] is recommended for a new user. | *The Knowledge Area on [[Systems Fundamentals]] contains five articles. [[What is a System?]] is recommended for a new user. | ||
*The Knowledge Area on [[Systems Science]] presents two articles on its history and approaches. Both are recommended. | *The Knowledge Area on [[Systems Science]] presents two articles on its history and approaches. Both are recommended. | ||
| Line 22: | Line 22: | ||
*One of the most important current research and practice areas of SE is Model Based Systems Engineering (MBSE). The Knowledge Area [[Representing Systems with Models]] provides the foundation for MBSE. The first three of the five articles in the KA are recommended. | *One of the most important current research and practice areas of SE is Model Based Systems Engineering (MBSE). The Knowledge Area [[Representing Systems with Models]] provides the foundation for MBSE. The first three of the five articles in the KA are recommended. | ||
| − | ==Learn | + | ==Learn How the Systems Approach Is Applied to Engineered Systems== |
The Knowledge Area [[Systems Approach Applied to Engineered Systems]] describes how systems science and systems thinking lead to the practice of systems engineering. All eight articles are recommended. | The Knowledge Area [[Systems Approach Applied to Engineered Systems]] describes how systems science and systems thinking lead to the practice of systems engineering. All eight articles are recommended. | ||
*[[Overview of the Systems Approach]] | *[[Overview of the Systems Approach]] | ||
| Line 31: | Line 31: | ||
*[[Implementing and Proving a Solution]] | *[[Implementing and Proving a Solution]] | ||
*[[Deploying, Using, and Sustaining Systems to Solve Problems]] | *[[Deploying, Using, and Sustaining Systems to Solve Problems]] | ||
| − | *[[Stakeholder | + | *[[Stakeholder Needs and Requirements]] |
*[[Applying the Systems Approach]] | *[[Applying the Systems Approach]] | ||
==Explore the Methods of Systems Engineering== | ==Explore the Methods of Systems Engineering== | ||
| − | The SEBoK uses a life-cycle framework to describe the processes that comprise systems engineering. [[Part 3:SE and Management]] contains the plurality of the content of the SEBoK in eight knowledge areas. A new user should be familiar with the introductions to each of these Knowledge Areas, and should read further in those KAs of interest. | + | The SEBoK uses a life-cycle framework to describe the processes that comprise systems engineering. [[Systems Engineering and Management| Part 3: SE and Management]] contains the plurality of the content of the SEBoK in eight knowledge areas. A new user should be familiar with the introductions to each of these Knowledge Areas, and should read further in those KAs of interest. |
*[[Life Cycle Models]] | *[[Life Cycle Models]] | ||
*[[Concept Definition]] | *[[Concept Definition]] | ||
| Line 55: | Line 55: | ||
==Read Case Studies== | ==Read Case Studies== | ||
| − | Finally, the new user should scan the case studies and vignettes in [[Systems Engineering Implementation Examples| | + | Finally, the new user should scan the case studies and vignettes in [[Systems Engineering Implementation Examples|Part 7: SE Implementation Examples]] and read a few of those in areas that appeal to the reader. This will help reinforce the fundamentals as well as illustrate the practice of SE. |
| − | The case studies | + | The following case studies are included: |
| + | *[[Successful Business Transformation within a Russian Information Technology Company]] | ||
| + | *[[Federal Aviation Administration Next Generation Air Transportation System]] | ||
| + | *[[How Lack of Information Sharing Jeopardized the NASA/ESA Cassini/Huygens Mission to Saturn]] | ||
*[[Hubble Space Telescope Case Study]] | *[[Hubble Space Telescope Case Study]] | ||
*[[Global Positioning System Case Study]] | *[[Global Positioning System Case Study]] | ||
| Line 64: | Line 67: | ||
*[[MSTI Case Study]] | *[[MSTI Case Study]] | ||
*[[Next Generation Medical Infusion Pump Case Study]] | *[[Next Generation Medical Infusion Pump Case Study]] | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==For Later Reading== | ==For Later Reading== | ||
| − | [[Related Disciplines|Part 6: Related Disciplines]] contains a broad selection of Knowledge Areas and Topics that describe how systems engineers work with other disciplines. The Knowledge | + | [[Related Disciplines|Part 6: Related Disciplines]] contains a broad selection of Knowledge Areas and Topics that describe how systems engineers work with other disciplines. The Knowledge Area on [[Systems Engineering and Software Engineering|SE and Software Engineering]] is particularly important, as modern systems get much of their functionality from software. |
| − | [[Enabling Systems Engineering|Part 5: Enabling Systems Engineering]] has KAs describing how individuals,teams, and organizations can develop to practice effective systems engineering. | + | [[Enabling Systems Engineering|Part 5: Enabling Systems Engineering]] has KAs describing how individuals, teams, and organizations can develop to practice effective systems engineering. |
| − | A person new to SE should become familiar with several references that are beyond | + | A person new to SE should become familiar with several references that are beyond the SEBoK. They include the [[INCOSE Systems Engineering Handbook|INCOSE Handbook]], several standards (listed in [[Relevant Standards]]), and the main journals of systems engineering (including but not limited to ''Systems Engineering'', the ''Journal of Enterprise Transformation'', and ''Systems, Man, and Cybernetics''). |
==References== | ==References== | ||
| Line 93: | Line 90: | ||
<center>[[SEBoK Users and Uses|Previous Article]] | [[SEBoK Users and Uses|Parent Article]] | [[Use Case 1: Practicing Systems Engineers|Next Article >]]</center> | <center>[[SEBoK Users and Uses|Previous Article]] | [[SEBoK Users and Uses|Parent Article]] | [[Use Case 1: Practicing Systems Engineers|Next Article >]]</center> | ||
| − | [[Category:Part]][[Category: | + | [[Category:Part 1]] [[Category:SEBoK Users and Uses]] |
| − | + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> | |
Latest revision as of 19:19, 19 November 2023
Some users of the Systems Engineering Body of Knowledge (SEBoK) may be new to the field. This article provides recommended readings for such a user.
Learn the Basic Terms
As discussed in the Introduction to the SEBoK, there are four key terms that you should first understand when learning about systems engineering (SE):
- A system is “a collection of elements and a collection of inter-relationships amongst the elements such that they can be viewed as a bounded whole relative to the elements around them.” Open systems exist in an environment described by related systems with which they may interact and conditions to which they may respond. While there are many definitions of the word “system,” the SEBoK authors believe that this definition encompasses most of those which are relevant to SE.
- An engineered system is an open system of technical or sociotechnical elements that exhibits emergent properties not exhibited by its individual elements. It is created by and for people; has a purpose with multiple views; satisfies key stakeholders’ value propositions; has a life cycle and evolution dynamics; has a boundary and an external environment; and is part of a system-of-interest hierarchy.
- Systems engineering is “an interdisciplinary approach and means to enable the realization of successful (engineered) systems.” 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.
- A systems engineer is “a person who practices systems engineering” as defined above, and whose systems engineering capabilities and experience include sustained practice, specialization, leadership, or authority over SE activities. These activities may be conducted by any competent person regardless of job title or professional affiliation.
Get an Overview
The next step for someone new to SE is get an overview of the discipline. Part 1: SEBoK Introduction contains four articles particularly helpful to one new to SE.
- The article Systems Engineering Overview frames systems engineering inside the larger topic of ‘Systems Science.’
- The article Economic Value of Systems Engineering makes the business case for investing in systems engineering as a way to reduce total ownership cost.
- The article Systems Engineering and Other Disciplines discusses briefly how systems engineers and other engineers interact as they develop complex systems together.
- Finally, the article Systems Engineering: Historic and Future Challenges gives a quick history of the discipline and discusses what lies ahead.
Learn About Systems
Engineering is often described as the application of science to develop new products or systems. Part 2: Foundations of Systems Engineering describes some of the underlying systems principles that form the foundation for systems engineering.
- The Knowledge Area on Systems Fundamentals contains five articles. What is a System? is recommended for a new user.
- The Knowledge Area on Systems Science presents two articles on its history and approaches. Both are recommended.
- The Knowledge Area on Systems Thinking has four articles. The first, What is Systems Thinking?, is recommended on a first reading.
- One of the most important current research and practice areas of SE is Model Based Systems Engineering (MBSE). The Knowledge Area Representing Systems with Models provides the foundation for MBSE. The first three of the five articles in the KA are recommended.
Learn How the Systems Approach Is Applied to Engineered Systems
The Knowledge Area Systems Approach Applied to Engineered Systems describes how systems science and systems thinking lead to the practice of systems engineering. All eight articles are recommended.
- Overview of the Systems Approach
- Engineered System Context
- Identifying and Understanding Problems and Opportunities
- Synthesizing Possible Solutions
- Analysis and Selection between Alternative Solutions
- Implementing and Proving a Solution
- Deploying, Using, and Sustaining Systems to Solve Problems
- Stakeholder Needs and Requirements
- Applying the Systems Approach
Explore the Methods of Systems Engineering
The SEBoK uses a life-cycle framework to describe the processes that comprise systems engineering. Part 3: SE and Management contains the plurality of the content of the SEBoK in eight knowledge areas. A new user should be familiar with the introductions to each of these Knowledge Areas, and should read further in those KAs of interest.
- Life Cycle Models
- Concept Definition
- System Definition
- System Realization
- System Deployment and Use
- Systems Engineering Management
- Product and Service Life Management
- Systems Engineering Standards
Explore the Applications of Systems Engineering
The SEBoK partitions the body of knowledge between methods and areas of application. Areas of application are classified as:
- Product Systems Engineering
- Service Systems Engineering
- Enterprise Systems Engineering
- Systems of Systems (SoS)
A new user should read the introduction to Part 4: Applications of Systems Engineering and to the four knowledge areas listed above. The reader’s interests can then suggest which further reading should be done.
Read Case Studies
Finally, the new user should scan the case studies and vignettes in Part 7: SE Implementation Examples and read a few of those in areas that appeal to the reader. This will help reinforce the fundamentals as well as illustrate the practice of SE.
The following case studies are included:
- Successful Business Transformation within a Russian Information Technology Company
- Federal Aviation Administration Next Generation Air Transportation System
- How Lack of Information Sharing Jeopardized the NASA/ESA Cassini/Huygens Mission to Saturn
- Hubble Space Telescope Case Study
- Global Positioning System Case Study
- Medical Radiation Case Study
- FBI Virtual Case File System Case Study
- MSTI Case Study
- Next Generation Medical Infusion Pump Case Study
For Later Reading
Part 6: Related Disciplines contains a broad selection of Knowledge Areas and Topics that describe how systems engineers work with other disciplines. The Knowledge Area on SE and Software Engineering is particularly important, as modern systems get much of their functionality from software.
Part 5: Enabling Systems Engineering has KAs describing how individuals, teams, and organizations can develop to practice effective systems engineering.
A person new to SE should become familiar with several references that are beyond the SEBoK. They include the INCOSE Handbook, several standards (listed in Relevant Standards), and the main journals of systems engineering (including but not limited to Systems Engineering, the Journal of Enterprise Transformation, and Systems, Man, and Cybernetics).
References
Works Cited
None.
Primary References
None.
Additional References
None.