Premium
Unifying Loss‐Driven Systems Engineering Activities
Author(s) -
Brtis John,
McEvilley Michael
Publication year - 2020
Publication title -
insight
Language(s) - English
Resource type - Journals
eISSN - 2156-4868
pISSN - 2156-485X
DOI - 10.1002/inst.12313
Subject(s) - unification , systems engineering , asset (computer security) , system of systems , systems development life cycle , computer science , system of systems engineering , architecture , systems design , risk analysis (engineering) , engineering , computer security , software development process , business , software development , art , software , visual arts , programming language
Systems, by definition, deliver desired capability. Not surprisingly—much of systems engineering is capability‐driven; it focuses on developing systems to deliver desired capability. There are, however, non‐capability‐driven areas of systems engineering. Loss‐driven systems engineering is an example. Loss‐driven systems engineering concerns itself with addressing the possible losses associated with system development and use. This paper explores loss‐driven systems engineering's meaning, identify the existing systems engineering specialty areas under the loss‐driven systems engineering umbrella, and discuss the potential for unifying those specialty areas along the attributes they share. We believe the attributes for possible unification include: asset types, loss types, adversity types, requirements, and architecture and design solutions. We identify the likely benefits expected from such a unification, and we explore the effect such a unification will have on systems engineering throughout the system life cycle.