Editing Systems engineering (section)

==Related fields and sub-fields==
Many related fields may be considered tightly coupled to systems engineering. The following areas have contributed to the development of systems engineering as a distinct entity:

===Cognitive systems engineering===
{{main|Cognitive systems engineering}}
Cognitive systems engineering (CSE) is a specific approach to the description and analysis of [[human-machine system]]s or [[sociotechnical systems]].<ref>{{cite journal|title=Cognitive systems engineering: New wine in new bottles|last1=Hollnagel|url=https://www.sciencedirect.com/science/article/abs/pii/S0020737383800340|volume=18|pages=583–600|year=1983|journal=International Journal of Man-Machine Studies|access-date=2023-11-16|last2=Woods|issue=6 |doi=10.1016/S0020-7373(83)80034-0|s2cid=15398274 |language=en}}</ref> The three main themes of CSE are how humans cope with complexity, how work is accomplished by the use of [[Artifact (software development)|artifact]]s, and how human-machine systems and socio-technical systems can be described as joint cognitive systems. CSE has since its beginning become a recognized scientific discipline, sometimes also referred to as [[cognitive engineering]]. The concept of a Joint Cognitive System (JCS) has in particular become widely used as a way of understanding how complex socio-technical systems can be described with varying degrees of resolution. The more than 20 years of experience with CSE has been described extensively.<ref>{{cite book|title=Joint cognitive systems: The foundations of cognitive systems engineering|last1=Hollnagel|year=2005|url=https://www.taylorfrancis.com/books/mono/10.1201/9781420038194/joint-cognitive-systems-erik-hollnagel-david-woods|access-date=2023-11-16|last2=Woods|publisher=Taylor & Francis|language=en|doi=10.1201/9781420038194|isbn=9780429122224|url-access=limited}}</ref><ref>{{cite book|title=Joint cognitive systems: Patterns in cognitive systems engineering|last1=Hollnagel|year=2006|url=https://www.taylorfrancis.com/books/mono/10.1201/9781420005684/joint-cognitive-systems-david-woods-erik-hollnagel|access-date=2023-11-16|last2=Woods|publisher=Taylor & Francis|language=en|doi=10.1201/9781420005684|isbn=9780429127663|url-access=limited}}</ref>

===Configuration management===
{{Main|Configuration management}}
Like systems engineering, [[configuration management]] as practiced in the [[Defence industry|defense]] and [[aerospace industry]] is a broad systems-level practice. The field parallels the taskings of systems engineering; where systems engineering deals with requirements development, allocation to development items and verification, configuration management deals with requirements capture, traceability to the development item, and audit of development item to ensure that it has achieved the desired functionality and outcomes that systems engineering and/or Test and Verification Engineering have obtained and proven through objective testing.

===Control engineering===
{{Main|Control engineering}}
[[Control engineering]] and its design and implementation of [[control systems]], used extensively in nearly every industry, is a large sub-field of systems engineering. The cruise control on an automobile and the guidance system for a ballistic missile are two examples. Control systems theory is an active field of applied mathematics involving the investigation of solution spaces and the development of new methods for the analysis of the control process.

===Industrial engineering===
{{Main|Industrial engineering}}
[[Industrial engineering]] is a branch of [[engineering]] that concerns the development, improvement, implementation, and evaluation of integrated systems of people, money, knowledge, information, equipment, energy, material, and process. Industrial engineering draws upon the principles and methods of engineering analysis and synthesis, as well as mathematical, physical, and social sciences together with the principles and methods of engineering analysis and design to specify, predict, and evaluate results obtained from such systems.

===Production Systems Engineering===
Production Systems Engineering (PSE) is an emerging branch of Engineering intended to uncover fundamental principles of production systems and utilize them for analysis, continuous improvement, and design.<ref>{{cite book|url=https://link.springer.com/book/10.1007/978-0-387-75579-3|doi=10.1007/978-0-387-75579-3|title=Production Systems Engineering|date=2009|last1=Li|first1=Jingshan|last2=Meerkov|first2=Semyon M.|isbn=978-0-387-75578-6}}</ref>

===Interface design===
{{Main|Interface design}}
[[Interface design]] and its specification are concerned with assuring that the pieces of a system connect and inter-operate with other parts of the system and with external systems as necessary. Interface design also includes assuring that system interfaces are able to accept new features, including mechanical, electrical, and logical interfaces, including reserved wires, plug-space, command codes, and bits in communication protocols. This is known as [[extensibility]]. [[Human-Computer Interaction]] (HCI) or Human-Machine Interface (HMI) is another aspect of interface design and is a critical aspect of modern systems engineering. Systems engineering principles are applied in the design of [[communication protocols]] for [[local area networks]] and [[wide area networks]].

===Mechatronic engineering===
{{Main|Mechatronic engineering}}
[[Mechatronic engineering]], like systems engineering, is a multidisciplinary field of engineering that uses dynamic systems modeling to express tangible constructs. In that regard, it is almost indistinguishable from Systems Engineering, but what sets it apart is the focus on smaller details rather than larger generalizations and relationships. As such, both fields are distinguished by the scope of their projects rather than the methodology of their practice.

===Operations research===
{{Main|Operations research}}
[[Operations research]] supports systems engineering. Operations research, briefly, is concerned with the optimization of a process under multiple constraints.<ref>{{cite web|title=Operation Everything|url=http://www.boston.com/globe/search/stories/reprints/operationeverything062704.html |website=The Bostom Globe |date=June 27, 2004 |first1=Virginia |last1=Postrel |url-status=dead|access-date=30 November 2005|archive-date=31 March 2012|archive-url=https://web.archive.org/web/20120331035402/http://www.boston.com/globe/search/stories/reprints/operationeverything062704.html}}</ref><ref>{{cite web|title=SHHHH... It's a Secret|url=http://www.sas.com/news/sascom/2004q4/feature_tech.html |first1=Mary |last1=Crissey |date=2004 |website=sas com Magazine |archive-url=https://web.archive.org/web/20050920174512/http://www.sas.com/news/sascom/2004q4/feature_tech.html|archive-date=20 September 2005|access-date=30 November 2005}}</ref>

===Performance engineering===
{{Main|Performance engineering}}
[[Performance engineering]] is the discipline of ensuring a system meets customer expectations for performance throughout its life. Performance is usually defined as the speed with which a certain operation is executed or the capability of executing a number of such operations in a unit of time. Performance may be degraded when operations queued to execute are throttled by limited [[system capacity]]. For example, the performance of a [[packet-switched network]] is characterized by the end-to-end packet transit delay or the number of packets switched in an hour. The design of high-performance systems uses analytical or simulation modeling, whereas the delivery of high-performance implementation involves thorough performance testing. Performance engineering relies heavily on [[statistics]], [[queueing theory]], and [[probability theory]] for its tools and processes.

===Program management and project management===
{{Main|Program management}}{{Main|Project management}}
[[Program management]] (or project management) has many similarities with systems engineering, but has broader-based origins than the engineering ones of systems engineering. [[Project management]] is also closely related to both program management and systems engineering. Both include [[Schedule (project management)|scheduling]] as engineering support tool in assessing interdisciplinary concerns under management process. In particular, the direct relationship of resources, performance features, and risk to the duration of a task or the [[Dependency (project management)|dependency]] links among tasks and impacts across the [[system lifecycle]] are systems engineering concerns.

===Proposal engineering===
Proposal engineering is the application of scientific and mathematical principles to design, construct, and operate a cost-effective proposal development system. Basically, proposal engineering uses the "[[systems engineering process]]" to create a cost-effective proposal and increase the odds of a successful proposal.

===Reliability engineering===
{{Main|Reliability engineering}}
[[Reliability engineering]] is the discipline of ensuring a system meets customer expectations for reliability throughout its life (i.e. it does not fail more frequently than expected). Next to the prediction of failure, it is just as much about the prevention of failure. Reliability engineering applies to all aspects of the system. It is closely associated with [[maintainability]], [[availability]] ([[dependability]] or [[RAMS]] preferred by some), and [[integrated logistics support]]. Reliability engineering is always a critical component of safety engineering, as in [[failure mode and effects analysis]] (FMEA) and [[Fault tree|hazard fault tree]] analysis, and of [[security engineering]].

===Risk management===
{{Main|Risk management}}
[[Risk management]], the practice of assessing and dealing with [[risk]] is one of the interdisciplinary parts of Systems Engineering. In development, acquisition, or operational activities, the inclusion of risk in tradeoffs with cost, schedule, and performance features, involves the iterative complex configuration management of traceability and evaluation to the scheduling and requirements management across domains and for the [[system lifecycle]] that requires the interdisciplinary technical approach of systems engineering. Systems Engineering has Risk Management define, tailor, implement, and monitor a structured process for risk management which is integrated into the overall effort.<ref>{{cite web|url=http://www2.mitre.org/work/sepo/toolkits/risk/index.html|title=Risk Management Toolkit|publisher=MITRE, SE Process Office|access-date=8 September 2016}}</ref>

===Safety engineering===
{{Main|Safety engineering}}
The techniques of [[safety engineering]] may be applied by non-specialist engineers in designing complex systems to minimize the probability of safety-critical failures. The "System Safety Engineering" function helps to identify "safety hazards" in emerging designs and may assist with techniques to "mitigate" the effects of (potentially) hazardous conditions that cannot be designed out of systems.

===Security engineering===
{{Main|Security engineering}}
[[Security engineering]] can be viewed as an [[interdisciplinary]] field that integrates the [[community of practice]] for control systems design, reliability, safety, and systems engineering. It may involve such sub-specialties as [[authentication]] of system users, system targets, and others: people, objects, and processes.

===Software engineering===
{{Main|Software engineering}}
From its beginnings, [[software engineering]] has helped shape modern systems engineering practice. The techniques used in the handling of the complexities of large software-intensive systems have had a major effect on the shaping and reshaping of the tools, methods, and processes of Systems Engineering.