Systems Engineering (SE) is the engineering discipline that focuses on integrating all the key elements of a system into one overall system and managing it throughout its lifecycle from cradle to grave. It’s focuses on the overall development process of a system that is based on established processes, documented needs and traceable communications or interaction among the customers, users, engineers, and other stakeholders. The overall goal of SE is to develop and design a system that meets a specific set of requirements (needs) in the guidelines established by the Program Manager (PM). A systems engineer in the DoD will develop, design, allocate, and manage user and system level requirements (see Requirements Development), lead the development of the system architecture, evaluate design tradeoffs, balance technical risk between systems, define and assess interfaces, provide oversight of verification and validation activities, as well as many other tasks throughout the course of a program. In short, SE is the technical discipline that glues all the pieces together to make the end product.
“Systems engineering is an interdisciplinary engineering management process that evolves and verifies an integrated, life-cycle balanced set of system solutions that satisfy customer needs.”
Disciplined SE is accomplished by integrating three (3) major activities. These activities are:
- Development phasing that controls the design process and provides baselines that coordinate design efforts,
- Establishing a Systems Engineering Process that provides a structure for solving design problems and tracking requirements flow through the design effort, and
- Life-cycle integration that involves customers in the design process and ensures that the system developed is viable throughout its life.
SE is focused on many tasks and products throughout the typical DoD acquisition programs. Below is a list of the main task/products that are expected of SE in the DoD acquisition process. For a more detailed list of tasks and products, check out the Systems Engineering Activity Map.
- Requirements Development, Management and Control (ICD, CDD, JCIDS Process, KPP, CONOPS)
- Develop Systems Engineering Plan
- Develop and Establish SE Tools and Resources (Modeling & Simulation)
- Verification and Validation
- Technical Planning
- Configuration Management
- Configuration Baselines
- Life-Cycle Integration
- Functional and Physical Architectures
- Milestone & Program Reviews (Milestones, Milestone Requirements Matrix, Major Reviews, SRR, SVR)
- Interface Management
- Risk Management
- System Safety Engineering
- Trade Studies
- Quality Assurance
- Communication with Program Management
Systems Engineering Process
The Systems Engineering Process is a comprehensive, iterative and recursive problem solving process, applied sequentially top-down by integrated teams. It transforms needs and requirements into a set of system product and process descriptions, generate information for decision makers, and provides input for the next level of development. The process is applied sequentially, one level at a time, adding additional detail and definition with each level of development.
- There is no one standard definition or systems engineering process. It’s a collection of ways and means across many disciplines. Best practices, guidebooks and lessons learned are a great source of systems engineering knowledge.
- Each program is different so there is no one process that perfectly fits. It’s the job of the systems engineer to modify the process to meets their programs needs the most .
AcqLinks and References:
- Defense Acquisition Guidebook (DAG) – Chapter 4
- DAU Systems Engineering Fundamentals Guide – Jan 2001
- Space and Missile Systems Center (SMC) “Systems Engineering Primer & Handbook” – 29 April 2005
- NASA Systems Engineering Handbook (large 9 Mb file)
- Mil-Standard 499 Rev B “Systems Engineering Management” – 1 May 1974
- Iterations in the Systems Engineering Process Guide – 14 Sept 2009
- Website: International Council on Systems Engineering (INCOSE)