Related Disciplines: Difference between revisions

From SEBoK Draft
Jump to navigation Jump to search
m (Text replacement - "SEBoK v. 2.12, released 20 May 2025" to "SEBoK v. 2.12, released 27 May 2025")
 
(28 intermediate revisions by 6 users not shown)
Line 1: Line 1:
----
----
'''''Lead Author:''''' ''Art Pyster'', '''''Contributing Authors:''''' ''Dick Fairley, Tom Hilburn, Alice Squires''
'''''Lead Author:''''' ''Caitlyn Singam''
----
----
Systems engineers routinely work within broad multidisciplinary teams (Pyster et al. 2018) and across many disciplines. Part 6 of the SEBoK presents knowledge that should be useful to systems engineers in two ways: (1) systems engineers benefit from knowing aspects of these disciplines directly; e.g. given how central software is to the functioning of virtually every interesting engineered system, a systems engineer should know a fair amount about software and software engineering; and (2) systems engineers routinely interact with these other fields and professionals in those fields.
One of the most fundamental tenets of systems engineering (SE) is that of approaching systems from an integrated, holistic perspective (INCOSE 2023), with an eye towards how sets of interconnected components and their surrounding environments interface and interact with each other to shape the nature, characteristics, and dynamics of [[System-of-Interest (glossary)|systems of interest]] (SoIs). In a similar fashion, it is possible to regard systems engineering itself as a system, which interacts and intersects with adjoining and related disciplines, communities of practice, and areas of study. These related fields form the [[Context (glossary)|systems context]] in which the field of systems engineering exists, and play a critical role in not only facilitating the effective use of systems engineering in various application areas, but also in shaping the current nature and future evolution of systems engineering as drivers of the overall [[Operational Environment (glossary)|operational environment]] in which systems engineering exists (Singam 2022a). Part 6 of the (SEBoK) provides the reader with an overview of many of these related disciplines, discussion on how these disciplines help enrich and enliven systems engineering, and vice versa.
[[File:SEBoK_Context_Diagram_Inner_P6_Ifezue_Obiako.png|centre|thumb|600x600px|'''Figure 1 SEBoK Part 6 in context (SEBoK Original).''' For more detail see [[Structure of the SEBoK]]]]


SE intersects with virtually every other recognized discipline. Besides the other engineering disciplines such as electrical and mechanical engineering, SE intersects with the physical sciences, social sciences, project management, philosophy, etc. For example, a systems engineer leading the design of an autonomous car would work with electrical engineers, software engineers, project managers, mechanical engineers, computer scientists, radio engineers, data analysts, human factors specialists, cybersecurity engineers, economists, and professionals from many other disciplines. The knowledge areas (KAs) contained in Part 6 and the topics under them provide an overview of some of these disciplines with emphasis on what a systems engineer needs to know to be effective, accompanied by pointers to that knowledge. The KAs included in Part 6 could run into the dozens, but only a handful are addressed in this version of the SEBoK.  Subsequent SEBoK releases will expand the number of related disciplines and offer deeper insight into their relationship with SE.
== Context ==
Systems engineering (SE) is a fundamentally transdisciplinary endeavor (INCOSE 2019): its principles and practices are sufficiently abstract and generic as to be readily applicable to any system, regardless of application area or associated discipline(s) relevant to the system of interest (Kossiakoff et al. 2011). The flexibility and versatility of the SE toolkit is part of what makes it such a valuable asset on projects, especially those involving large or complex systems which require the integration of various disparate elements and technical disciplines into a single, unified system (INCOSE 2023, Elm et. al. 2008). In order to realize that versatility, though, SE practitioners need to have a wide range of technical knowledge that extends beyond that of "pure" SE and across the various disciplines relative to the system(s) of interest. A systems engineer who has responsibility for overseeing the interface between a mechanical subsystem and an electrical subsystem in a biomedical device, for instance, would at minimum need knowledge of mechanical engineering and electrical engineering ''topics'' in order to perform a systems engineering task such as setting interface requirements. However, in the context of a biomedical device for human use, familiarity with concepts in biology, [[System Safety|safety engineering]], [[System Resistance to Electromagnetic Interference|electromagnetic interference]], [[Human Systems Integration|human-systems integration]], and law/policy - just to name a few - are likely to also become relevant in order for the systems engineer to appropriately communicate and integrate information from across the project, as well as ensure that the interface is fit-for-purpose and within acceptable parameters. It thus behooves the well-prepared systems engineer to maintain familiarity with a broad selection of related disciplines.
 
== Purpose and Scope ==
Part 6 of the SEBoK intends to aid systems practitioners and other individuals with an interest in SE in augmenting their technical knowledge of subjects relevant to systems engineering practice, and providing a foundation for independent exploration of associated topics via relevant resources. 
 
Part 6's purview encompasses the many fields and topics which enrich the discipline of SE, inclusive of both commonly-discussed disciplines such as those classified under the science, technology, engineering, and mathematics (STEM) quartet, as well as oft-overlooked disciplines of relevance in the arts and humanities. Part 6 is therefore arguably the most expansive [[Structure of the SEBoK|section of the SEBoK]] in terms of potential scope, as it extends beyond the boundaries of formal SE and SE application areas, and across the breadth of academic and practical [[Knowledge (glossary)|knowledge]]. Even so, the disciplines discussed in this section are only a subset of the full expanse of those which relate to systems engineering: it is, after all, neigh impossible to find a topic or discipline which does not involve or reckon with [[System (glossary)|system]](s), and thus systems engineering, in some way (Singam 2022b). Consequently, rather than attempting a full census of the adjacent or related knowledge areas (KAs) that abut the edges of formal systems engineering, Part 6 instead seeks to proffer a curated smörgåsbord of the many related disciplines which bear relevance to systems engineering, with a focus on KAs that are most likely to be of relevance to a diverse, [[SEBoK Users and Uses|multi-disciplinary audience]] of systems-minded professionals, learners, and educators.  
   
   
[[File:SEBoK_Context_Diagram_Inner_P6_Ifezue_Obiako.png|centre|thumb|600x600px|'''Figure 1. SEBoK Part 6 in context (SEBoK Original).''' For further details, see [[Structure of the SEBoK]].]]


==Knowledge Areas in Part 6==
==Knowledge Areas in Part 6==
Each part of the SEBoK is divided into knowledge areas (KAs), which are groupings of information with a related theme. Part 6 contains the following KAs:  
The KAs covered in Part 6 are all distinct areas of study or practice (i.e., disciplines which are commonly recognized as separate from systems engineering) that meet one or more of the following descriptors:  
*[[Systems Engineering and Environmental Engineering]]
 
*[[Systems Engineering and Geospatial/Geodetic Engineering]]
# disciplines which are independent from, but overlap with, formal SE practice and/or the core SE body of knowledge (e.g., [[Relationships between Systems Engineering and Project Management|project management]]);
*[[Systems Engineering and Industrial Engineering]]
# specialized disciplines focused on in-depth exploration of specific topics that abut or extend beyond the scope of the core/non-specialist SE body of knowledge (e.g., [[Systems Engineering and Quality Attributes|quality engineering]]);
*[[Systems Engineering and Project Management]]
# specialist disciplines which are commonly used to describe or govern the characteristics, dynamics, or life cycle of the composite elements of interdisciplinary or multi-disciplinary systems (e.g., physics, biology, [[Systems Engineering and Mechanical Engineering|mechanical engineering]], [[Systems Engineering and Software Engineering|software engineering]], etc.);
*[[Systems Engineering and Software Engineering]]
# disciplines which are frequently relevant to the effective and/or ethical practice of SE in a commonly encountered system context (e.g., [[Systems Engineering and Environmental Engineering|environmental engineering]], [[Systems Engineering and Enterprise IT|information technology (IT) for enterprise systems]], law);
*[[Systems Engineering and Quality Attributes]]
# specialized disciplines which frequently utilize systems engineering methodologies or have a substantial systems engineering/systems science community of practice (e.g., [[Overview of Geospatial/Geodetic Engineering|geospatial engineering]]), and which can provide new generalizable insights into the improvement and evolution of systems engineering as a field;
# other specialized disciplines which are of substantial interest in non-specialist contexts.


Each KA above except the last is a major well-recognized stand-alone discipline. Each is widely taught in universities around the world, has professional societies devoted to it, standards that assist its practitioners, publications that describe its knowledge and practices, and a vibrant community of practitioners and researchers who often have one or more university degrees in the discipline. The last KA is different. It describes the disciplines associated with engineering system qualities or properties; e.g., security is a system quality. Security engineering is the discipline through which system security is realized in a system. The security of a modern car is widely understood to be a function of many factors such as the strength of its physical exterior, its alarm system which may have extensive sensors and software, and its communications system which can wirelessly alert the owner or police if someone attempts to break into it. Similarly, the reliability of a car is a function of such factors as the reliability of its individual subsystems and components (mechanical, electronic, software, etc.) and how the car has been designed to compensate for a failed subsystem or component (e.g. if the electronic door lock fails, can the driver use a physical key to lock and unlock the car?). The topics included in this KA are among the most important qualities a systems engineer would typically consider.
=== Current Content ===
At present, Part 6 is organized into the following sub-sections, each representing a key KA:
 
* [[Systems Engineering and Environmental Engineering]]
* [[Systems Engineering and Geospatial/Geodetic Engineering]]
* [[Systems Engineering and Industrial Engineering]]
* [[Systems Engineering and Project Management]]
** ''Other sub-topics'': [[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships|project structure and governance]]; [[Procurement and Acquisition|procurement and acquisition]]; [[Portfolio Management|portfolio management]]
* [[Systems Engineering and Software Engineering]]
* [[Systems Engineering and Mechanical Engineering]]
* [[Systems Engineering and Enterprise IT]]
* [[Systems Engineering and Quality Attributes]] (This encompasses quality engineering, but is also the home of the disciplines focused on characteristics of systems, sometimes referred to as "-ilities".)
** ''Other subtopics'': [[Human Systems Integration|human-systems integration (HSI)]]; [[Manufacturability and Producibility|manufacturability and producibility]]; [[System Adaptability|adaptability]]; [[System Affordability|affordability]]; [[System Hardware Assurance|hardware assurance]]; [[System Reliability, Availability, and Maintainability|reliability/availability/maintainability]]; [[System Resilience|resilience]]; [[System Resistance to Electromagnetic Interference|resistance to electromagnetic interference]]; [[System Safety|safety]]; [[System Security|security]]
 
As reflected by the sub-section titles within Part 6 ("Systems Engineering and...."), each main KA is focused on the intersection between systems engineering and a given topic, and contains at least one article discussing aspects of that KA that would be of import to a systems engineer from outside that particular specialty. Some of the broader KAs, such as those on project management and quality attributes, also include articles on KA-relevant sub-topics alongside the KA overview articles, as per the categorization listed above.
 
=== Future Content ===
Astute readers may note that pre-existing content in Part 6 is almost exclusively focused on areas of specialist engineering; as Part 6's content continues to evolve, it is planned that the KAs covered in this section will be updated to better reflect the current range of SE-adjacent knowledge and practice across across various related disciplines, in accordance with broadened interest from both academia and industry (Han et. al. 2023) in exploring interdisciplinary and cross-disciplinary KAs. In particular, it is planned that future versions of Part 6 will include content on related disciplines that are often overlooked in overviews of SE-relevant subject matter, such as topics in the arts and humanities.


==References==  
==References==  
===Works Cited===
===Works Cited===
Pyster, A., N. Hutchison, D. Henry. 2018. The Paradoxical Mindset of Systems Engineers. Hoboken, NJ, USA: Wiley.
Elm, J. P., D.R. Goldenson, K. El Emam, N. Donatelli, and A. Neisa. 2008. ''A Survey of Systems Engineering Effectiveness-Initial Results'' (with Detailed Survey Response Data). Pittsburgh, PA, USA: Software Engineering Institute, CMU/SEI-2008-SR-034. December 2008.


===Primary References===
Han, Siqi, Jack LaViolette, Chad Borkenhagen, William McAllister, and Peter S. Bearman. 2023. “Interdisciplinary College Curriculum and Its Labor Market Implications.” ''Proceedings of the National Academy of Sciences of the United States of America'' 120 (43): e2221915120. <nowiki>https://doi.org/10.1073/pnas.2221915120</nowiki>.
 
INCOSE. 2019. ''Systems Engineering and System Definitions'', version 1.0. San Diego, CA, USA: INCOSE. INCOSE-TP-2020-002-06.
 
INCOSE. 2023. ''Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities'', version 5.0. Hoboken, NJ, USA: John Wiley and Sons, Inc, ISBN: 978-1-119-81429-0.
 
ISO/IEC/IEEE. 2023. ''Systems and Software Engineering -- System Life Cycle Processes''. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2023.
 
Kossiakoff, Alexander, William N. Sweet, Samuel J. Seymour, and Steven M. Biemer. 2011. ''Systems Engineering Principles and Practice''. John Wiley & Sons.


Bourque, P. and R.E. Fairley (eds.). 2014. ''[[SWEBOK: Guide to the Software Engineering Body of Knowledge]]'', version 3.0. Los Alamitos, CA, USA: IEEE Computer Society. Available at: http://www.Swebok.org.
Singam, Caitlyn A. K. 2022. “A Critical Analysis of the Systems Engineering Leadership Pipeline: Closing the Gender Gap.” In ''Emerging Trends in Systems Engineering Leadership: Practical Research from Women Leaders'', edited by Alice F. Squires, Marilee J. Wheaton, and Heather J. Feli, 195–236. Women in Engineering and Science. Cham: Springer International Publishing. <nowiki>https://doi.org/10.1007/978-3-031-08950-3_7</nowiki>.


DAU. 2020. ''[[Defense Acquisition Guidebook (DAG)]]''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/US Department of Defense. Available at: https://www.dau.edu/tools/dag (Accessed on March 19, 2021).
Singam, Caitlyn A. K. 2022. “A Vision for Universal and Standardized Access to Systems Competency Education.” ''INSIGHT'' 25 (3): 30–34. <nowiki>https://doi.org/10.1002/inst.12395</nowiki>.


PMI. 2017. ''[[A Guide to the Project Management Body of Knowledge|A Guide to the Project Management Body of Knowledge (PMBOK® Guide)]]'', 6th ed. Newtown Square, PA, USA: Project Management Institute (PMI).
===Primary References===


Pyster, A., N. Hutchison, D. Henry. 2018. ''[[The Paradoxical Mindset of Systems Engineers]]''. Hoboken'', NJ, USA: Wiley.
None.


===Additional References===
===Additional References===
None.
None.
----
----
<center>[[Ethical Behavior|< Previous Article]] | [[SEBoK Table of Contents|Parent Article]] | [[Systems Engineering and Software Engineering|Next Article >]]</center>
<center>[[Ethical Behavior|< Previous Article (Part 5)]] | [[SEBoK Table of Contents|Parent Article]] | [[Systems Engineering and Environmental Engineering|Next Article >]]</center>


<center>'''SEBoK v. 2.3, released 30 October 2020'''</center>
<center>'''SEBoK v. 2.12, released 27 May 2025'''</center>


[[Category: Part 6]]
[[Category: Part 6]]
[[Category:Part]]
[[Category:Part]]

Latest revision as of 00:13, 24 May 2025


Lead Author: Caitlyn Singam


One of the most fundamental tenets of systems engineering (SE) is that of approaching systems from an integrated, holistic perspective (INCOSE 2023), with an eye towards how sets of interconnected components and their surrounding environments interface and interact with each other to shape the nature, characteristics, and dynamics of systems of interest (SoIs). In a similar fashion, it is possible to regard systems engineering itself as a system, which interacts and intersects with adjoining and related disciplines, communities of practice, and areas of study. These related fields form the systems context in which the field of systems engineering exists, and play a critical role in not only facilitating the effective use of systems engineering in various application areas, but also in shaping the current nature and future evolution of systems engineering as drivers of the overall operational environment in which systems engineering exists (Singam 2022a). Part 6 of the (SEBoK) provides the reader with an overview of many of these related disciplines, discussion on how these disciplines help enrich and enliven systems engineering, and vice versa.

Context

Systems engineering (SE) is a fundamentally transdisciplinary endeavor (INCOSE 2019): its principles and practices are sufficiently abstract and generic as to be readily applicable to any system, regardless of application area or associated discipline(s) relevant to the system of interest (Kossiakoff et al. 2011). The flexibility and versatility of the SE toolkit is part of what makes it such a valuable asset on projects, especially those involving large or complex systems which require the integration of various disparate elements and technical disciplines into a single, unified system (INCOSE 2023, Elm et. al. 2008). In order to realize that versatility, though, SE practitioners need to have a wide range of technical knowledge that extends beyond that of "pure" SE and across the various disciplines relative to the system(s) of interest. A systems engineer who has responsibility for overseeing the interface between a mechanical subsystem and an electrical subsystem in a biomedical device, for instance, would at minimum need knowledge of mechanical engineering and electrical engineering topics in order to perform a systems engineering task such as setting interface requirements. However, in the context of a biomedical device for human use, familiarity with concepts in biology, safety engineering, electromagnetic interference, human-systems integration, and law/policy - just to name a few - are likely to also become relevant in order for the systems engineer to appropriately communicate and integrate information from across the project, as well as ensure that the interface is fit-for-purpose and within acceptable parameters. It thus behooves the well-prepared systems engineer to maintain familiarity with a broad selection of related disciplines.

Purpose and Scope

Part 6 of the SEBoK intends to aid systems practitioners and other individuals with an interest in SE in augmenting their technical knowledge of subjects relevant to systems engineering practice, and providing a foundation for independent exploration of associated topics via relevant resources.

Part 6's purview encompasses the many fields and topics which enrich the discipline of SE, inclusive of both commonly-discussed disciplines such as those classified under the science, technology, engineering, and mathematics (STEM) quartet, as well as oft-overlooked disciplines of relevance in the arts and humanities. Part 6 is therefore arguably the most expansive section of the SEBoK in terms of potential scope, as it extends beyond the boundaries of formal SE and SE application areas, and across the breadth of academic and practical knowledge. Even so, the disciplines discussed in this section are only a subset of the full expanse of those which relate to systems engineering: it is, after all, neigh impossible to find a topic or discipline which does not involve or reckon with system(s), and thus systems engineering, in some way (Singam 2022b). Consequently, rather than attempting a full census of the adjacent or related knowledge areas (KAs) that abut the edges of formal systems engineering, Part 6 instead seeks to proffer a curated smörgåsbord of the many related disciplines which bear relevance to systems engineering, with a focus on KAs that are most likely to be of relevance to a diverse, multi-disciplinary audience of systems-minded professionals, learners, and educators.

Figure 1. SEBoK Part 6 in context (SEBoK Original). For further details, see Structure of the SEBoK.

Knowledge Areas in Part 6

The KAs covered in Part 6 are all distinct areas of study or practice (i.e., disciplines which are commonly recognized as separate from systems engineering) that meet one or more of the following descriptors:

  1. disciplines which are independent from, but overlap with, formal SE practice and/or the core SE body of knowledge (e.g., project management);
  2. specialized disciplines focused on in-depth exploration of specific topics that abut or extend beyond the scope of the core/non-specialist SE body of knowledge (e.g., quality engineering);
  3. specialist disciplines which are commonly used to describe or govern the characteristics, dynamics, or life cycle of the composite elements of interdisciplinary or multi-disciplinary systems (e.g., physics, biology, mechanical engineering, software engineering, etc.);
  4. disciplines which are frequently relevant to the effective and/or ethical practice of SE in a commonly encountered system context (e.g., environmental engineering, information technology (IT) for enterprise systems, law);
  5. specialized disciplines which frequently utilize systems engineering methodologies or have a substantial systems engineering/systems science community of practice (e.g., geospatial engineering), and which can provide new generalizable insights into the improvement and evolution of systems engineering as a field;
  6. other specialized disciplines which are of substantial interest in non-specialist contexts.

Current Content

At present, Part 6 is organized into the following sub-sections, each representing a key KA:

As reflected by the sub-section titles within Part 6 ("Systems Engineering and...."), each main KA is focused on the intersection between systems engineering and a given topic, and contains at least one article discussing aspects of that KA that would be of import to a systems engineer from outside that particular specialty. Some of the broader KAs, such as those on project management and quality attributes, also include articles on KA-relevant sub-topics alongside the KA overview articles, as per the categorization listed above.

Future Content

Astute readers may note that pre-existing content in Part 6 is almost exclusively focused on areas of specialist engineering; as Part 6's content continues to evolve, it is planned that the KAs covered in this section will be updated to better reflect the current range of SE-adjacent knowledge and practice across across various related disciplines, in accordance with broadened interest from both academia and industry (Han et. al. 2023) in exploring interdisciplinary and cross-disciplinary KAs. In particular, it is planned that future versions of Part 6 will include content on related disciplines that are often overlooked in overviews of SE-relevant subject matter, such as topics in the arts and humanities.

References

Works Cited

Elm, J. P., D.R. Goldenson, K. El Emam, N. Donatelli, and A. Neisa. 2008. A Survey of Systems Engineering Effectiveness-Initial Results (with Detailed Survey Response Data). Pittsburgh, PA, USA: Software Engineering Institute, CMU/SEI-2008-SR-034. December 2008.

Han, Siqi, Jack LaViolette, Chad Borkenhagen, William McAllister, and Peter S. Bearman. 2023. “Interdisciplinary College Curriculum and Its Labor Market Implications.” Proceedings of the National Academy of Sciences of the United States of America 120 (43): e2221915120. https://doi.org/10.1073/pnas.2221915120.

INCOSE. 2019. Systems Engineering and System Definitions, version 1.0. San Diego, CA, USA: INCOSE. INCOSE-TP-2020-002-06.

INCOSE. 2023. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 5.0. Hoboken, NJ, USA: John Wiley and Sons, Inc, ISBN: 978-1-119-81429-0.

ISO/IEC/IEEE. 2023. Systems and Software Engineering -- System Life Cycle Processes. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2023.

Kossiakoff, Alexander, William N. Sweet, Samuel J. Seymour, and Steven M. Biemer. 2011. Systems Engineering Principles and Practice. John Wiley & Sons.

Singam, Caitlyn A. K. 2022. “A Critical Analysis of the Systems Engineering Leadership Pipeline: Closing the Gender Gap.” In Emerging Trends in Systems Engineering Leadership: Practical Research from Women Leaders, edited by Alice F. Squires, Marilee J. Wheaton, and Heather J. Feli, 195–236. Women in Engineering and Science. Cham: Springer International Publishing. https://doi.org/10.1007/978-3-031-08950-3_7.

Singam, Caitlyn A. K. 2022. “A Vision for Universal and Standardized Access to Systems Competency Education.” INSIGHT 25 (3): 30–34. https://doi.org/10.1002/inst.12395.

Primary References

None.

Additional References

None.


< Previous Article (Part 5) | Parent Article | Next Article >
SEBoK v. 2.12, released 27 May 2025