In one line: The discipline of designing the whole rather than the parts. It means defining what the system must do, dividing it wisely, managing interfaces and trade-offs, and making sure the integrated result meets the need over its whole life.
Core idea
A system is a set of interacting elements organized to achieve a purpose that none of them achieves alone. Systems engineering is the interdisciplinary approach that makes such systems succeed. It starts from stakeholder needs and the operational concept, turns them into requirements, allocates functions to subsystems, keeps the interfaces under control, and verifies and validates the integrated result. The major handbooks (INCOSE’s and NASA’s [1], [2]) describe it as both a technical process and a management discipline.
How it works
- Begin with the need and the concept of operations: who uses the system, how, and in what environment.
- Think in life cycles: concept, development, production, operations, support and retirement all impose requirements.
- Decompose and integrate. Break the system into manageable pieces, then put it back together and prove it works. This pattern is often drawn as a “V.”
- Own the interfaces, because that is where most failures hide.
- Make trade-offs explicit across disciplines (see Trade-off Analysis).
- Manage risk, configuration and technical reviews throughout (see Systems Engineering Process).
In practice
Two quick exercises from the program show the systems lens in action:
- Write a few sentences on What is systems engineering? before studying it. Most engineers find their first answer is about one discipline’s view of the system.
- Read a state decarbonization roadmap [3]. It treats reaching net-zero emissions by 2050 as a multi-variable system problem: buildings, transportation, electricity supply, land use and costs all interact. Each pathway is evaluated against the whole, because optimizing one sector alone can raise demand in another.
The systems engineer is often the T-Shaped Professional in its clearest form: deep enough to be credible, and broad enough to see where the disciplines collide.
Questions to ask yourself
- Can I describe the system my work belongs to, including its users and its whole life cycle?
- Which interface on my project is least well defined?
- Where might optimizing my subsystem make the whole system worse?
Connections
- The process: Systems Engineering Process. The mindset: Thinking in Systems, Complexity.
- Core skill: Trade-off Analysis. The person: T-Shaped Professional.
- Capabilities exercised: Connecting Across Disciplines, Vision, Realizing the Vision.
Sources
- INCOSE - Systems Engineering Handbook [1]
- NASA (2007) Systems Engineering Handbook [2]
- Commonwealth of Massachusetts (2020) MA 2050 Decarbonization Roadmap [3]