Difference between revisions of "Scope of the SEBoK"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
 
(111 intermediate revisions by 11 users not shown)
Line 1: Line 1:
−
{{Star|{{#linktree:2|Domain (glossary)|Context (glossary)|Engineered System (ES) (glossary)|Product (glossary)|Acronyms|Service (glossary)|Enterprise (glossary)|Systems of Systems (SoS) (glossary)|Social System (glossary)|Natural System (glossary)|Systems Engineering (SE) (glossary)|Boundary (glossary)|Life Cycle (glossary)|Sociotechnical system (glossary)|Scope (glossary)|Purpose (glossary)|System (glossary)|Problem (glossary)|Opportunity (glossary)|Stakeholder (glossary)|Environment (glossary)|Implementation (glossary)|Project (glossary)|Boundary (glossary)|Engineering (glossary)|Software (glossary)|Requirement (glossary)|Synthesis (glossary)|Design (glossary)|Holistic (glossary)|Verification (glossary)|Validation (glossary)|Solution (glossary)|Disposal (glossary)|Concept (glossary)|Threat (glossary)|Cost (glossary)|Opportunity (glossary)|System Definition (glossary)|User (glossary)}}}}
+
The SEBoK is a large, curated compendium of information about {{Term|Systems Engineering (glossary)|systems engineering}}. It:
 +
*is a guide to the body of SE knowledge which provides references to detailed sources for additional information; it is not a self-contained knowledge resource
 +
*focuses on {{Term|Engineered System (glossary)|Engineered Systems}} contexts, that is socio-technical systems with a recognized SE {{Term|Life Cycle (glossary)|life cycle}}, while treating social and natural systems as relevant and important environmental considerations (see [[Foundations of Systems Engineering|Part 2]])
 +
*describes generic SE life cycle and {{Term|Process (glossary)|process}} knowledge (see [[Systems Engineering and Management|Part 3]])  
 +
*recognizes that SE principles can be applied differently to different types of {{Term|Product (glossary)|products}}, {{Term|Service (glossary)|services}}, {{Term|Enterprise (glossary)|enterprises}}, and {{Term|System of Systems (SoS) (glossary)|systems of systems}} (SoS) context (see [[Applications of Systems Engineering|Part 4]])
 +
*provides resources for organization support of SE activities (see [[Enabling Systems Engineering|Part 5]])
 +
*explores the interaction between SE and other disciplines, highlighting what systems engineers need to know about these disciplines (see [[Systems Engineering and Other Disciplines|Part 6]])
 +
*is domain-independent, with implementation examples to provide domain-specific context (see [[Systems Engineering Implementation Examples|Part 7]])
  
−
The scope of the Guide to the Systems Engineering Body of Knowledge (SEBoK) can be understood in two dimensions:
+
Each of these considerations depends upon the definition and scope of SE itself, which is the subject of the next section.
−
*general boundaries and characteristics, based on the definition and scope of systems engineering (SE) itself
 
−
*life cycle, based on the life cycle of SE in the context of an engineered system (ES)
 
  
−
==Scope of Systems Engineering within the Systems Domain==
+
==SEBoK Purposes==
−
The scope of SE and the SEBoK must ``consider’’ all classes of systems, but ``focuses’’ on the domain of ESs. Sociotechnical systems are treated as a special form of engineered systems. A convenient way to define the scope of ESs and the SEBoK is to relate it to the two other systems domains, natural systems and social systems, as shown in Figure 1 below.  As an example, power generation and distribution systems are purely engineered systems, including software and human operator aspects as well as hardware aspects.  Water and power safety legislation comes from the political processes of a legislature social system.  The resulting water and power safety assurance and safety governance systems are sociotechnical systems involving participants working in both engineered systems and social systems.
 
  
−
[[File:Scope_SystemBoundaries.png|frame|500px|center|'''Figure 1. System Boundaries of Engineered Systems, Social Systems, and Natural Systems.''' (SEBoK Original)]]
+
Ongoing studies of system cost and schedule failures (Gruhl & Stutzke 2005; Johnson 2006, GAO 2016) and safety failures (Leveson 2012) have shown that the failures have mostly come not from their domain disciplines, but from lack of adequate Systems Engineering (NDIA 2003, 2006, 2016). To provide a foundation for the mutual understanding of SE needed to reduce these failures, the SEBoK describes the boundaries, terminology, content, and structure of SE. In so doing, the SEBoK systematically and consistently supports six broad purposes, described in Table 1.
  
−
The nature of and relationships between these system domains is discussed in Part 2, Systems of the SEBoK. Part 2 considers the general nature and purpose of systems and how these ideas are used to ensure better ESs. It covers this by considering:
+
{|
−
*Systems Thinking – a way of understanding complex situations by looking at them as combinations of systems.  
+
|+ '''Table 1. SEBoK Purposes.''' (SEBoK Original)
−
*Systems Science – a collection of disciplines that have created useful knowledge by applying systems thinking and the scientific method to different aspects of the system domains.
+
|-
−
*Systems Approach – a way of tackling real world problems which makes use of the tools of system science to enable useful systems to be engineered and used.  
+
!#
 +
!Purpose
 +
!Description
 +
|-
 +
|1
 +
|Inform Practice
 +
|Inform systems engineers about the boundaries, terminology, and structure of their discipline and point them to useful information needed to practice SE in any application domain.
 +
|-
 +
|2
 +
|Inform Research
 +
|Inform researchers about the limitations and gaps in current SE knowledge that should help guide their research agenda. 
 +
|-
 +
|3
 +
|Inform Interactors
 +
|Inform performers in interacting disciplines (system implementation, project and enterprise management, other disciplines) and other stakeholders of the nature and value of SE.
 +
|-
 +
|4
 +
|Inform Curriculum Developers
 +
|Inform organizations defining the content that should be common in undergraduate and graduate programs in SE.
 +
|-
 +
|5
 +
|Inform Certifiers
 +
|Inform organizations certifying individuals as qualified to practice systems engineering.
 +
|-
 +
|6
 +
|Inform SE Staffing
 +
|Inform organizations and managers deciding which competencies practicing systems engineers should possess in various roles ranging from apprentice to expert.  
 +
|}
  
−
The systems approach requires understanding of both natural and sociotechnical systems to identify and scope the engineering of system problems or opportunities . It is critical to understand each of these system types if ESs are to be deployed into real world situations, achieve their assigned goals, and not adversely impact other outcomes.  
+
The SEBoK is a guide to the body of SE knowledge, not an attempt to capture that knowledge directly. It provides references to more detailed sources of knowledge, all of which are generally available to any interested reader. No proprietary information is referenced, but not all referenced material is free—for example, some books or standards must be purchased from their publishers. The criterion for including a source is simply that the [[Acknowledgements and Release History|authors & editors]] believed it offered the best generally available information on a particular subject.
  
−
The primary focus of the knowledge in Part 3, Systems Engineering and Management and Part 4, Applications of Systems Engineering is on how to create or change ESs to fulfill the goals of all relevant stakeholders within these wider system contexts. The knowledge in Part 5, Enabling Systems Engineering and Part 6, Related Disciplines includes the need for SE itself to be integrated and supported within the human activity systems in which it is performed and the relationships between SE and other engineering and management disciplines.
+
The SEBoK is global in applicability. Although SE is practiced differently from industry to industry and country to country, the SEBoK is written to be useful to systems engineers anywhere. The authors & editors were chosen from diverse locales and industries, and have refined the SEBoK to broaden applicability based on extensive global reviews of several drafts.
  
−
==Scope of Systems Engineering (SE) within the Engineered Systems (ES) Domain==
+
The SEBoK aims to inform a wide variety of user communities about essential SE concepts and practices in ways that can be tailored to different enterprises and activities while retaining greater commonality and consistency than would be possible without the SEBoK. Because the world in which SE is being applied continues to evolve and is dynamic, the SEBoK is designed for easy, continuous updating as new sources of knowledge emerge.
−
The scope of SE does not include the entire ES domain. Activities such as system construction, manufacturing, funding, and general management are part of the SE environment , but other than the specific management of the SE function, are not considered as part of SE. This is reflected in the International Council on Systems Engineering (INCOSE) top-level definition of systems engineering as, “an interdisciplinary approach and means to enable the realization of successful systems.” (INCOSE 2011) For example, SE can enable the realization of successful systems, but cannot ensure a successful realization if the systems’ funding, implementation, general management, and manufacturing are poorly managed and executed.  
 
  
−
Again, a convenient way to define the scope of SE within the ES domain is to develop a Venn diagram showing the relations among SE, system implementation, and project /systems management, as shown in Figure 2. Activities, such as analyzing alternative methods for production, testing, and operations, are part of SE planning and analysis functions. Such activities as production line equipment ordering and installation, and its use in manufacturing, are still important SE environment considerations even though they are “outside” the SE boundary . Note that as defined in Figure 2, system implementation engineering also includes the software production aspects of system implementation. Software engineering, then, is not considered a subset of SE.  
+
==SEBoK Uses==
 +
The communities involved with SE include its various specialists, engineers from disciplines other than systems engineering, managers, researchers, and educators. This diversity means that there is no single best way to use the SEBoK. The SEBoK includes use cases that highlight potential ways that particular communities can draw upon the content of the SEBoK, identify articles of interest to those communities, and discuss primary users (those who use the SEBoK directly) and secondary users (those who use the SEBoK with assistance from a systems engineer). For more on this, see the article [[SEBoK Users and Uses]].
  
−
[[File:Scope_BoundariesSE_PM_SM.png|thumb|600px|center|'''Figure 2. System Boundaries of Systems Engineering, Systems Implementation, and Project/Systems Management.''' (SEBoK Original)]]
+
==SEBoK Domain Independent 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 [[Foundations of Systems Engineering|Part 2: Foundations of Systems Engineering]]. 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 in two ways. 
  
−
Traditional definitions of SE have emphasized sequential performance of SE activities, e.g., “documenting requirements , then proceeding with design synthesis …”. (INCOSE 2011) The SEBoK authors have emphasized the inevitable intertwining of system requirements definition and system design in the following revised definition of SE:
+
Firstly, by means of examples that tell stories of how SE is applied in particular domains. [[Systems Engineering Implementation Examples|Part 7: Systems Engineering Implementation Examples]] ) 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 [[SEBoK Users and Uses|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.
  
−
</blockquote>''Systems Engineering (SE) is an interdisciplinary approach and means to enable the realization of successful 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.'' (INCOSE 2011, modified) </blockquote>
+
In addition, the SEBoK will contain knowledge areas in [[Applications of Systems Engineering|Part 4: Applications of Systems Engineering]] which explicitly describe the domain specific language, approaches, specialized processes and tools, etc. of particular application domains. In this version of the SEBoK, there are a limited set of domain knowledge areas.
  
−
Part 3, Systems Engineering and Management, elaborates on the definition above and offers additional definitions and constructs, providing further context for the other parts of the SEBoK.
+
==References==
  
−
==Context of the SEBoK==
+
===Works Cited===
−
===SEBoK Life Cycle Context===
+
GAO. 2016. ''Weapon System Requirements. Detailed Systems Engineering Prior to Product Development Positions Programs for Success''. Government Accounting Office Report to Congressional Committees.
−
Figure 3 summarizes the main agents, activities, and artifacts involved in the SEBoK life cycle. The SEBoK is one of two primary products of the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) Project. The other product, the Graduate Reference Curriculum in Systems Engineering (GRCSE) uses the content of the SEBoK to define a core body of knowledge (CorBoK) to be included in graduate SE curricula. The GRCSE is not a standard, but a reference curriculum to be tailored and extended to meet the objectives of each university’s graduate program.
 
−
 
 
−
[[File:P1_Scope_and_Con_SEbok_LC_and_Cont_Related_Agents_BB.jpg|400px|thumb|center|'''Figure 3. 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, has drawn on three primary resources. The U.S. Department of Defense (DoD) has provided the funding and includes a representative, but has not constrained or directed 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 over 70 international author team members have been selected for their expertise in SE and their diversity with respect to home country (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 incrementally developed. Each of the 0.25, 0.5, and 0.75 versions has undergone an open review by all interested parties. Reviews have involved over 200 reviewers and 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 (IEEE) and the International Council on Systems Engineering (INCOSE) will become the primary stewards for both the SEBoK and GRCSE. The continuing role of Stevens Institute, Naval Postgraduate School, and the SERC in SEBoK and GRCSE operations and maintenance will also evolve after 2012. Interested parties should be able to undertake development, operations, and support of additional derivative products and services, such as course-ware, education, certification, and domain-specific versions of the SEBoK and GRCSE.
 
−
 
 
−
 
 
−
===SE and Engineered Systems Project Life Cycle Context===
 
−
 
 
−
Figure 4 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 of system definition , system initial operational capability (IOC) development, and system evolution and retirement, it shows the activities being performed by the primary agents (the systems engineers, the systems developers, and the primary project-external bodies (users , owners, external systems) constituting the project environment, in creating the evolving states of the ES, which may be a product, service, and/or enterprise.
 
−
 
 
−
[[File:P1_Scope_and_Con_SE_and_Eng_Sys_Proj_LF_BB.jpg|600px|thumb|center|'''Figure 4. SE and Engineered System Project Life Cycle Context: Related Agents, Activities, and Artifacts.''' (SEBoK Original)]]
 
−
 
 
−
The semantics of the boxes and arrows in Figure 4 are that the boxes in the center three columns show activities being performed by the relevant agents in the column, while the boxes in the right-hand column are the resulting artifacts. An arrow going from box A to box B means that the successful outcome of box B depends on the successful outcome of box A. In some cases in Figure 4, there are two-way dependencies, as in the handling of the inevitable changes that arise during system development and evolution.
 
−
 
 
−
For example, the system’s users and owners may 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. These require negotiation among these stakeholders and the system developers, in which the SEs play a key role in analyzing the relative costs and benefits of alternative change proposals, and in synthesizing mutually satisfactory solutions.  
 
  
 +
Gruhl, W. and Stutzke, R. 2005.  "Werner Gruhl analysis of SE investments and NASA overruns," in R. Stutzke, ''Estimating Software-Intensive Systems''. Boston, MA, USA: Addison Wesley, page 290.
  
−
===Domain Independence Context===
+
Johnson, J. 2006. ''My Life Is Failure: 100 Things You Should Know to Be a Better Project Leader''. Boston, MA, USA: Standish Group International.
  
−
SE is practiced in numerous domains such as telecommunications, finance, medicine, and aerospace. Each of these domains will have its own specialized vocabulary and key domain concepts. The language and concepts contained in the SEBoK are intended to be what is generally accepted for domain-independent SE. For example, there are domain-independent foundations for SE such as the concepts elaborated in Part 2, Systems of the SEBoK. For the SEBoK, the main body is domain-independent. In order to show how the domain-independent material relates to different domains, several case studies and vignettes demonstrating the effect of domain on the application of SE complement the domain-independent information. Initial versions of the case studies and vignettes are provided in Part 7, Systems Engineering Implementation Examples, and also in some of the Use Cases in Part 1. The examples demonstrate how a concept would work 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 including many more case studies would add significantly to the value of the SEBoK, and expect that additional examples will be added during the evolution of the SEBoK.  
+
Leveson, N. 2012. ''Engineering a Safer World: Systems Thinking Applied to Safety''. Cambridge, MA, USA: MIT Press, NDIA (National Defense Industrial Association). 2003. ''Top 5 Systems Engineering Issues within DOD and Defense Industry: Task Report''. Version 9, released 1/23/03. Available at: [https://ndiastorage.blob.core.usgovcloudapi.net/ndia/2006/systems/Wednesday/rassa5.pdf https://www.aticourses.com/sampler/TopFiveSystemsEngineeringIssues_In_DefenseIndustry.pdf]. Accessed October 25, 2019.
  
−
==References==
+
NDIA (National Defense Industrial Association). 2006. '' Top 5 Systems Engineering Issues within DOD and Defense Industry DOD and Defense Industry: Task Report''. Version 8a, released July 26-27, 2006. Available at: https://ndiastorage.blob.core.usgovcloudapi.net/ndia/2006/systems/Wednesday/rassa5.pdf. Accessed October 25, 2019.
  
−
===Works Cited===
+
NDIA (National Defense Industrial Association). 2016. ''Top Systems Engineering Issues In US Defense Industry 2016''. Version 7c. Available at: https://www.ndia.org/-/media/sites/ndia/divisions/systems-engineering/studies-and-reports/ndia-top-se-issues-2016-report-v7c.ashx?la=en. Accessed October 25, 2019.
−
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.
 
  
−
===Primary References===
+
===Primary References===  
−
INCOSE. 2012. ''[[INCOSE Systems Engineering Handbook|Systems Engineering Handbook]]'', version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE). INCOSE-TP-2003-002-03.2.
+
None.
  
 
===Additional References===
 
===Additional References===
−
Sage, A. and W. Rouse (eds). 1999. ''Handbook of Systems Engineering and Management''. Hoboken, NJ, USA: John Wiley and Sons, Inc.  
+
None.
  
 
----
 
----
−
<center>[[SEBoK 1.0 Introduction|< Previous Article]] | [[SEBoK 1.0 Introduction|Parent Article]] | [[Structure of the SEBoK|Next Article >]]</center>
+
<center>[[Introduction to the SEBoK|< Previous Article]] | [[Introduction to the SEBoK|Parent Article]] | [[Structure of the SEBoK|Next Article >]]</center>
  
 
[[Category:Part 1]]
 
[[Category:Part 1]]
 +
[[Category:Introduction to the SEBoK]]
  
−
 
+
<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>
−
 
 
−
{{DISQUS}}
 

Latest revision as of 22:56, 18 November 2023

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

  • is a guide to the body of SE knowledge which provides references to detailed sources for additional information; it is not a self-contained knowledge resource
  • focuses on Engineered SystemsEngineered Systems contexts, that is socio-technical systems with a recognized SE life cyclelife cycle, while treating social and natural systems as relevant and important environmental considerations (see Part 2)
  • describes generic SE life cycle and processprocess knowledge (see Part 3)
  • recognizes that SE principles can be applied differently to different types of productsproducts, servicesservices, enterprisesenterprises, and systems of systemssystems of systems (SoS) context (see Part 4)
  • provides resources for organization support of SE activities (see Part 5)
  • explores the interaction between SE and other disciplines, highlighting what systems engineers need to know about these disciplines (see Part 6)
  • is domain-independent, with implementation examples to provide domain-specific context (see Part 7)

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

SEBoK Purposes

Ongoing studies of system cost and schedule failures (Gruhl & Stutzke 2005; Johnson 2006, GAO 2016) and safety failures (Leveson 2012) have shown that the failures have mostly come not from their domain disciplines, but from lack of adequate Systems Engineering (NDIA 2003, 2006, 2016). To provide a foundation for the mutual understanding of SE needed to reduce these failures, the SEBoK describes the boundaries, terminology, content, and structure of SE. In so doing, the SEBoK systematically and consistently supports six broad purposes, described in Table 1.

Table 1. SEBoK Purposes. (SEBoK Original)
# Purpose Description
1 Inform Practice Inform systems engineers about the boundaries, terminology, and structure of their discipline and point them to useful information needed to practice SE in any application domain.
2 Inform Research Inform researchers about the limitations and gaps in current SE knowledge that should help guide their research agenda.
3 Inform Interactors Inform performers in interacting disciplines (system implementation, project and enterprise management, other disciplines) and other stakeholders of the nature and value of SE.
4 Inform Curriculum Developers Inform organizations defining the content that should be common in undergraduate and graduate programs in SE.
5 Inform Certifiers Inform organizations certifying individuals as qualified to practice systems engineering.
6 Inform SE Staffing Inform organizations and managers deciding which competencies practicing systems engineers should possess in various roles ranging from apprentice to expert.

The SEBoK is a guide to the body of SE knowledge, not an attempt to capture that knowledge directly. It provides references to more detailed sources of knowledge, all of which are generally available to any interested reader. No proprietary information is referenced, but not all referenced material is free—for example, some books or standards must be purchased from their publishers. The criterion for including a source is simply that the authors & editors believed it offered the best generally available information on a particular subject.

The SEBoK is global in applicability. Although SE is practiced differently from industry to industry and country to country, the SEBoK is written to be useful to systems engineers anywhere. The authors & editors were chosen from diverse locales and industries, and have refined the SEBoK to broaden applicability based on extensive global reviews of several drafts.

The SEBoK aims to inform a wide variety of user communities about essential SE concepts and practices in ways that can be tailored to different enterprises and activities while retaining greater commonality and consistency than would be possible without the SEBoK. Because the world in which SE is being applied continues to evolve and is dynamic, the SEBoK is designed for easy, continuous updating as new sources of knowledge emerge.

SEBoK Uses

The communities involved with SE include its various specialists, engineers from disciplines other than systems engineering, managers, researchers, and educators. This diversity means that there is no single best way to use the SEBoK. The SEBoK includes use cases that highlight potential ways that particular communities can draw upon the content of the SEBoK, identify articles of interest to those communities, and discuss primary users (those who use the SEBoK directly) and secondary users (those who use the SEBoK with assistance from a systems engineer). For more on this, see the article SEBoK Users and Uses.

SEBoK Domain Independent 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: Foundations of Systems Engineering. 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 in two ways.

Firstly, by means of examples that tell stories of how SE is applied in particular domains. Part 7: Systems Engineering Implementation Examples ) 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.

In addition, the SEBoK will contain knowledge areas in Part 4: Applications of Systems Engineering which explicitly describe the domain specific language, approaches, specialized processes and tools, etc. of particular application domains. In this version of the SEBoK, there are a limited set of domain knowledge areas.

References

Works Cited

GAO. 2016. Weapon System Requirements. Detailed Systems Engineering Prior to Product Development Positions Programs for Success. Government Accounting Office Report to Congressional Committees.

Gruhl, W. and Stutzke, R. 2005. "Werner Gruhl analysis of SE investments and NASA overruns," in R. Stutzke, Estimating Software-Intensive Systems. Boston, MA, USA: Addison Wesley, page 290.

Johnson, J. 2006. My Life Is Failure: 100 Things You Should Know to Be a Better Project Leader. Boston, MA, USA: Standish Group International.

Leveson, N. 2012. Engineering a Safer World: Systems Thinking Applied to Safety. Cambridge, MA, USA: MIT Press, NDIA (National Defense Industrial Association). 2003. Top 5 Systems Engineering Issues within DOD and Defense Industry: Task Report. Version 9, released 1/23/03. Available at: https://www.aticourses.com/sampler/TopFiveSystemsEngineeringIssues_In_DefenseIndustry.pdf. Accessed October 25, 2019.

NDIA (National Defense Industrial Association). 2006. Top 5 Systems Engineering Issues within DOD and Defense Industry DOD and Defense Industry: Task Report. Version 8a, released July 26-27, 2006. Available at: https://ndiastorage.blob.core.usgovcloudapi.net/ndia/2006/systems/Wednesday/rassa5.pdf. Accessed October 25, 2019.

NDIA (National Defense Industrial Association). 2016. Top Systems Engineering Issues In US Defense Industry 2016. Version 7c. Available at: https://www.ndia.org/-/media/sites/ndia/divisions/systems-engineering/studies-and-reports/ndia-top-se-issues-2016-report-v7c.ashx?la=en. Accessed October 25, 2019.

Primary References

None.

Additional References

None.

< Previous Article | Parent Article | Next Article >
SEBoK v. 2.9, released 20 November 2023
Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Scope_of_the_SEBoK&oldid=69854"