16
®
Systems Engineering and System Denitions
INCOSE-TP-| 22 July 2019
APPENDIX: TYPICAL FEATURES OF SYSTEMS ENGINEERING
Systems Engineering considers and balances the business, technical, personal and societal needs of the
system’s stakeholders, including customers, beneciaries, users, owners, and relevant third parties, with the
goal of providing a quality solution that is t for its intended purpose in real-world operation. The scope is the
total or “whole system” solution, not just the engineered artifacts that may be key elements of the solution.
Business needs deal with the factors that justify expenditure of time and resources on the activities that occur
during the various stages of a system.
Systems Engineering (SE) focuses on ten key activities:
1. establishing stakeholders’ success criteria and concerns, and dening actual or anticipated customer
needs and required functionality, early in the development cycle, and revising them as new information is
gained and lessons are learned;
2. investigating the solution space, proposing alternative solution and operational concepts, weighing their
value (viability, utility, benet at cost) and selecting the optimal or most appropriate concept(s);
3. architecting a solution or set of solutions based on the selected concept(s) while considering potential
concepts of employment and usage;
4. modelling (or otherwise evaluating) the solution at each relevant phase of the endeavor, considering both
normal and exceptional scenarios, and an appropriate diversity of viewpoints, in order to:
a. establish required capability and performance;
b. increase condence that the solution will work as expected and required, while avoiding or
minimizing undesirable unintended consequences;
c. ensure the solution is resilient and can evolve if required to adapt to anticipated or possible changes
in the user needs and operational environments;
d. provide ongoing prediction and assessment of system effectiveness and value;
5. dening and managing the interfaces, both within the system and between the system and the rest of the
world (noting that increasingly, systems engineering is conducted in a brown-eld rather than a green-
eld environment, so legacy systems may be a major or key part of the overall solution);
6. establishing appropriate process and life cycle models that consider complexity, uncertainty, change and
variety, and implementing system management and governance processes for both development and
through-life use and disposal;
7. proceeding with detailed design synthesis, integration, and solution verication and validation (ensuring
the solution is t for the intended purpose) while considering the complete problem (including aspects of
dependability such as safety, security, reliability, availability, logistic support, and disaster recovery), all
necessary enabling systems and services, and end-of-life processes (e.g.. transition to a replacement
system, recycling of the retired one, nuclear decommissioning and waste disposal…);
8. providing the SE knowledge and information required by all stakeholder groups to ensure coherence
of the whole endeavor – typically including a vision statement, operational concepts, business drivers,
analyses and recommendations for decision support and the business case, architecture denition,
organizational policies and processes, required properties and interfaces of the system and its elements
(including common standards to ensure interoperability), verication and validation criteria, analysis
and interpretation of test and evaluation results, anticipated operational usage, and appropriate system
congurations for different scenarios;
9. supporting transition to use, considering all aspects including people, processes, information and
technology;
10. periodically re-evaluating status, risks and opportunities, stakeholder feedback, observed or anticipated
unintended consequences, and anticipated system effectiveness and value, and recommending any