What Is Systems Engineering? Definition, Process and Roles
The Essential Guide to Requirements Management and Traceability
Chapters
- 1. Requirements Management
- Overview
- 1 What is Requirements Management? A Complete Guide
- 2 Why Do You Need Requirements Management?
- 3 Four Stages of Requirements Management Processes
- 4 Adopting Agile Requirements Management Tools
- 5 Status Request Changes
- 6 Conquering the 5 Biggest Challenges of Requirements Management
- 7 Three Reasons You Need a Requirements Management Solution
- 8 Guide to Poor Requirements: Identify Causes, Repercussions, and How to Fix Them
- 9 What Is a Requirements Management Plan? A Practical Guide
- 10 Enterprise Requirements Management: Keeping Traceability Current
- 11 8 Requirements Management Best Practices
- 2. Writing Requirements
- Overview
- 1 Functional Requirements Examples and Templates
- 2 Product Requirements Document (PRD): A Complete Guide
- 3 What Is a User Requirement Specification (URS)? How to Write and Manage One
- 4 Identifying and Measuring Requirements Quality
- 5 How to Write a System Requirements Specification (SRS) Document
- 6 The Fundamentals of Business Requirements: Examples of Business Requirements and the Importance of Excellence
- 7 Adopting the EARS Notation to Improve Requirements Engineering
- 8 What Is a Compliance Risk Assessment? Steps, Framework, and Examples
- 9 Introducing Jama Intelligence: AI for Requirements Management
- 10 How to Write an Effective Product Requirements Document (PRD)
- 11 Functional vs. Non-Functional Requirements
- 12 What Are Nonfunctional Requirements and How Do They Impact Product Development?
- 13 What Is a Software Design Specification? Key Components + Template
- 14 Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS)
- 15 8 Do’s and Don’ts for Writing Requirements
- 16 Project Requirements: Types, Process, and Best Practices
- 17 INCOSE Guide to Writing Requirements
- 18 How to Write Technical Requirements That Survive Verification
- 19 Types of Requirements in Engineering: A Complete Guide
- 3. Requirements Gathering and Management Processes
- Overview
- 1 Requirements Engineering
- 2 Requirements Analysis
- 3 A Guide to Requirements Elicitation for Product Teams
- 4 Requirements Gathering Techniques for Agile Product Teams
- 5 What Is Requirements Gathering? Process, Techniques and Best Practices
- 6 Defining and Implementing a Requirements Baseline
- 7 Managing Project Scope — Why It Matters and Best Practices
- 8 Requirements Decomposition and How AI Supports It
- 9 How Long Do Requirements Take?
- 10 How to Reuse Requirements Across Multiple Products
- 11 Requirements Prioritization Techniques: 7 Methods for Engineers
- 12 How to Run a Requirements Gathering Workshop
- 13 Customer Requirements Management From Need to Verified Evidence
- 4. Requirements Traceability
- Overview
- 1 What Is Traceability? A Guide for Regulated Product Teams
- 2 Tracing Your Way to Success: The Crucial Role of Traceability in Modern Product and Systems Development
- 3 Bidirectional Traceability: What It Is and How to Implement It
- 4 Change Impact Analysis (CIA): A Short Guide for Effective Implementation
- 5 What is Engineering Change Management (ECM)? A Complete Guide
- 6 What is Meant by Version Control?
- 7 Key Traceability Challenges and Tips for Ensuring Accountability and Efficiency
- 8 The Role of a Data Thread in Product and Software Development
- 9 What is a Traceability Matrix? A Guide to Requirements Traceability
- 10 How to Create and Use a Requirements Traceability Matrix (RTM)
- 11 Requirements Traceability Matrix Pros and Cons: A Practical Guide
- 12 Live Traceability vs. After-the-Fact Traceability
- 13 Requirements Traceability, What Are You Missing?
- 14 Requirements Traceability: Links in the Chain
- 15 What Are the Benefits of End-to-End Traceability During Product Development?
- 16 Requirements Volatility: 7 Essential Management Strategies
- 17 FAQs About Requirements Traceability
- 18 What Is AI Traceability? How to Implement It
- 19 Product Traceability for Regulated Industries: A Complete Guide to Audit-Ready Compliance
- 20 What Is the Traceability Information Model?
- 21 Supply Chain Traceability: What to Send Suppliers and What to Get Back
- 22 Component Traceability: Linking Parts to Requirements and Tests
- 23 What Is an Engineering Change Order (ECO)?
- 5. Solutions for Capturing and Tracking Requirements
- Overview
- 1 Selecting the Right Requirements Management Tools
- 2 Why Investing in Requirements Management Software Makes Business Sense During an Economic Downturn
- 3 Why Word and Excel Alone is Not Enough for Product, Software, and Systems Development
- 4 Can You Track Requirements in Excel?
- 5 What Is Application Lifecycle Management (ALM)?
- 6 Requirements Management Tools Jira
- 7 Requirements Management Checklist: Selecting the Right Tool
- 8 How to Choose Defense Requirements Management Software
- 6. Requirements Validation and Verification
- 7. Meeting Regulatory Compliance and Industry Standards
- Overview
- 1 Understanding ISO Standards
- 2 Understanding ISO/IEC 27001: A Guide to Information Security Management
- 3 What is DevSecOps? A Guide to Building Secure Software
- 4 Compliance Management
- 5 What Is Functional Safety (FuSa)? Standards, Lifecycle, and Where Programs Fail
- 6 Failure Mode and Effects Analysis (FMEA) Explained
- 7 TÜV SÜD: Ensuring Safety, Quality, and Sustainability Worldwide
- 8 What Is IEC 62443? A Complete Guide to Industrial Cybersecurity
- 9 DFARS Compliance: A Guide for Defense Contractors
- 10 CMMC vs FedRAMP: What’s Different and Which One Applies to You
- 11 Automotive SPICE (ASPICE) 4.0: A Complete Guide
- 12 Restriction of Hazardous Substances (RoHS) Compliance Guide
- 13 MISRA C and MISRA C++ Explained: Rules for Safer Embedded Code
- 14 REACH Compliance for Product Engineering Teams
- 15 Radio Equipment Directive (RED) Cybersecurity Requirements
- 16 What Is a Software Bill of Materials?
- 8. Systems Engineering
- Overview
- 1 What Is Systems Engineering? Definition, Process and Roles
- 2 How Do Engineers Collaborate? A Guide to Streamlined Teamwork and Innovation
- 3 The Systems Engineering Body of Knowledge (SEBoK)
- 4 What Is MBSE? Model-Based Systems Engineering Explained
- 5 Digital Engineering Between Government and Contractors
- 6 Digital Engineering Tools: The Key to Driving Innovation and Efficiency in Complex Systems
- 7 What Is Bill of Materials (BOM) Management? A Guide to Controlling Product Data
- 8 What Is SysML? A Guide to the Systems Modeling Language
- 9. Automotive Development
- Overview
- 1 Understanding IATF 16949: A Quick Guide to Automotive Quality Management
- 2 What Is ISO 21434? Automotive Cybersecurity Engineering Explained
- 3 What Is ISO 26262? A Guide to Functional Safety in Automotive
- 4 What Is an Automotive Safety Integrity Level (ASIL)?
- 5 What Is SOTIF? A Guide to ISO 21448 for ADAS Safety
- 10. Medical Device & Life Sciences Development
- Overview
- 1 The Importance of Benefit-Risk Analysis in Medical Device Development
- 2 Software as a Medical Device: Revolutionizing Healthcare
- 3 Navigating the Risks of Software of Unknown Pedigree (SOUP) in the Medical Device & Life Sciences Industry
- 4 What’s a Design History File, and How Are DHFs Used by Product Teams?
- 5 What Is ISO 13485? A Guide to Medical Device Quality Management Systems
- 6 What Is IEC 62304? A Guide to Medical Device Software
- 7 What Is a Device Master Record (DMR)? Definition and FDA Requirements
- 8 Failure Modes, Effects, and Diagnostic Analysis (FMEDA) for Medical Devices: What You Need to Know
- 9 Embracing the Future of Healthcare: Exploring the Internet of Medical Things (IoMT)
- 10 What Is General Safety and Performance Requirements (GSPR)? What You Need To Know
- 11 What Is IEC 62366? Usability Engineering for Medical Devices
- 12 What Is the Quality Management System Regulation (QMSR)?
- 13 510(k) vs PMA: Differences in FDA Device Approval and Clearance
- 14 EU MDR Compliance Requirements and Timeline
- 15 Essential Performance Requirements and How to Identify Them
- 16 DHF vs DMR vs DHR: What Changed Under the FDA QMSR
- 17 Computer Software Assurance for Production and Quality Systems
- 18 IVDR Compliance: What Manufacturers Need to Know
- 19 IVDR Compliance: What Manufacturers Need to Know (copy)
- 20 IEC 60601-1 Guide for Medical Devices
- 21 A Guide to Medical Device Requirements Management
- 22 What Are Design Controls? A Guide to the Process and Its Elements
- 11. Aerospace & Defense Development
- Overview
- 1 What is ITAR Compliance? What Engineering Teams Need to Know
- 2 What Is DO-278A? A Guide for Compliance Teams
- 3 ARP4754B Explained: Changes, Recognition, and Compliance
- 4 What Is a Safety Integrity Level (SIL)? How to Calculate and Apply It
- 5 A Guide to Aerospace Requirements Management
- 6 MIL-STD-882E: System Safety Standard for Defense Programs
- 7 What Is ARP4754A? A Complete Guide to Civil Aircraft and Systems Development Assurance
- 8 Understanding ARP4761A: Guidelines for System Safety Assessment in Aerospace
- 9 What Is DO-254? A Complete Guide to Airborne Hardware Design Assurance
- 10 What Is DO-178C? A Guide to Airborne Software Certification
- 11 Aerospace Requirements Management System: What to Look For
- 12. Architecture, Engineering, and Construction (AEC industry) Development
- 13. Industrial Manufacturing & Machinery, Automation & Robotics, Consumer Electronics, and Energy
- 14. Semiconductor Development
- 15. AI in Product Development
- Overview
- 1 What Is AI in Product Development? A Complete 2026 Guide
- 2 AI Test Case Generation: A Complete Guide for Regulated QA Teams
- 3 Using AI to Write Software Requirements: What Works and What Doesn’t
- 4 What Is the Model Context Protocol (MCP) for Requirements Management?
- 5 AI for Systems Engineering: Benefits, Risks, and Adoption
- 6 How to Automate Requirements Management
- 7 AI Requirements Quality Scoring for Automated Reviews
- 8 Artificial Intelligence in Requirements Management
- 16. Risk Management
- 17. Product Development Terms and Definitions
Chapter 8: What Is Systems Engineering? Definition, Process and Roles
Chapters
- 1. Requirements Management
- Overview
- 1 What is Requirements Management? A Complete Guide
- 2 Why Do You Need Requirements Management?
- 3 Four Stages of Requirements Management Processes
- 4 Adopting Agile Requirements Management Tools
- 5 Status Request Changes
- 6 Conquering the 5 Biggest Challenges of Requirements Management
- 7 Three Reasons You Need a Requirements Management Solution
- 8 Guide to Poor Requirements: Identify Causes, Repercussions, and How to Fix Them
- 9 What Is a Requirements Management Plan? A Practical Guide
- 10 Enterprise Requirements Management: Keeping Traceability Current
- 11 8 Requirements Management Best Practices
- 2. Writing Requirements
- Overview
- 1 Functional Requirements Examples and Templates
- 2 Product Requirements Document (PRD): A Complete Guide
- 3 What Is a User Requirement Specification (URS)? How to Write and Manage One
- 4 Identifying and Measuring Requirements Quality
- 5 How to Write a System Requirements Specification (SRS) Document
- 6 The Fundamentals of Business Requirements: Examples of Business Requirements and the Importance of Excellence
- 7 Adopting the EARS Notation to Improve Requirements Engineering
- 8 What Is a Compliance Risk Assessment? Steps, Framework, and Examples
- 9 Introducing Jama Intelligence: AI for Requirements Management
- 10 How to Write an Effective Product Requirements Document (PRD)
- 11 Functional vs. Non-Functional Requirements
- 12 What Are Nonfunctional Requirements and How Do They Impact Product Development?
- 13 What Is a Software Design Specification? Key Components + Template
- 14 Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS)
- 15 8 Do’s and Don’ts for Writing Requirements
- 16 Project Requirements: Types, Process, and Best Practices
- 17 INCOSE Guide to Writing Requirements
- 18 How to Write Technical Requirements That Survive Verification
- 19 Types of Requirements in Engineering: A Complete Guide
- 3. Requirements Gathering and Management Processes
- Overview
- 1 Requirements Engineering
- 2 Requirements Analysis
- 3 A Guide to Requirements Elicitation for Product Teams
- 4 Requirements Gathering Techniques for Agile Product Teams
- 5 What Is Requirements Gathering? Process, Techniques and Best Practices
- 6 Defining and Implementing a Requirements Baseline
- 7 Managing Project Scope — Why It Matters and Best Practices
- 8 Requirements Decomposition and How AI Supports It
- 9 How Long Do Requirements Take?
- 10 How to Reuse Requirements Across Multiple Products
- 11 Requirements Prioritization Techniques: 7 Methods for Engineers
- 12 How to Run a Requirements Gathering Workshop
- 13 Customer Requirements Management From Need to Verified Evidence
- 4. Requirements Traceability
- Overview
- 1 What Is Traceability? A Guide for Regulated Product Teams
- 2 Tracing Your Way to Success: The Crucial Role of Traceability in Modern Product and Systems Development
- 3 Bidirectional Traceability: What It Is and How to Implement It
- 4 Change Impact Analysis (CIA): A Short Guide for Effective Implementation
- 5 What is Engineering Change Management (ECM)? A Complete Guide
- 6 What is Meant by Version Control?
- 7 Key Traceability Challenges and Tips for Ensuring Accountability and Efficiency
- 8 The Role of a Data Thread in Product and Software Development
- 9 What is a Traceability Matrix? A Guide to Requirements Traceability
- 10 How to Create and Use a Requirements Traceability Matrix (RTM)
- 11 Requirements Traceability Matrix Pros and Cons: A Practical Guide
- 12 Live Traceability vs. After-the-Fact Traceability
- 13 Requirements Traceability, What Are You Missing?
- 14 Requirements Traceability: Links in the Chain
- 15 What Are the Benefits of End-to-End Traceability During Product Development?
- 16 Requirements Volatility: 7 Essential Management Strategies
- 17 FAQs About Requirements Traceability
- 18 What Is AI Traceability? How to Implement It
- 19 Product Traceability for Regulated Industries: A Complete Guide to Audit-Ready Compliance
- 20 What Is the Traceability Information Model?
- 21 Supply Chain Traceability: What to Send Suppliers and What to Get Back
- 22 Component Traceability: Linking Parts to Requirements and Tests
- 23 What Is an Engineering Change Order (ECO)?
- 5. Solutions for Capturing and Tracking Requirements
- Overview
- 1 Selecting the Right Requirements Management Tools
- 2 Why Investing in Requirements Management Software Makes Business Sense During an Economic Downturn
- 3 Why Word and Excel Alone is Not Enough for Product, Software, and Systems Development
- 4 Can You Track Requirements in Excel?
- 5 What Is Application Lifecycle Management (ALM)?
- 6 Requirements Management Tools Jira
- 7 Requirements Management Checklist: Selecting the Right Tool
- 8 How to Choose Defense Requirements Management Software
- 6. Requirements Validation and Verification
- 7. Meeting Regulatory Compliance and Industry Standards
- Overview
- 1 Understanding ISO Standards
- 2 Understanding ISO/IEC 27001: A Guide to Information Security Management
- 3 What is DevSecOps? A Guide to Building Secure Software
- 4 Compliance Management
- 5 What Is Functional Safety (FuSa)? Standards, Lifecycle, and Where Programs Fail
- 6 Failure Mode and Effects Analysis (FMEA) Explained
- 7 TÜV SÜD: Ensuring Safety, Quality, and Sustainability Worldwide
- 8 What Is IEC 62443? A Complete Guide to Industrial Cybersecurity
- 9 DFARS Compliance: A Guide for Defense Contractors
- 10 CMMC vs FedRAMP: What’s Different and Which One Applies to You
- 11 Automotive SPICE (ASPICE) 4.0: A Complete Guide
- 12 Restriction of Hazardous Substances (RoHS) Compliance Guide
- 13 MISRA C and MISRA C++ Explained: Rules for Safer Embedded Code
- 14 REACH Compliance for Product Engineering Teams
- 15 Radio Equipment Directive (RED) Cybersecurity Requirements
- 16 What Is a Software Bill of Materials?
- 8. Systems Engineering
- Overview
- 1 What Is Systems Engineering? Definition, Process and Roles
- 2 How Do Engineers Collaborate? A Guide to Streamlined Teamwork and Innovation
- 3 The Systems Engineering Body of Knowledge (SEBoK)
- 4 What Is MBSE? Model-Based Systems Engineering Explained
- 5 Digital Engineering Between Government and Contractors
- 6 Digital Engineering Tools: The Key to Driving Innovation and Efficiency in Complex Systems
- 7 What Is Bill of Materials (BOM) Management? A Guide to Controlling Product Data
- 8 What Is SysML? A Guide to the Systems Modeling Language
- 9. Automotive Development
- Overview
- 1 Understanding IATF 16949: A Quick Guide to Automotive Quality Management
- 2 What Is ISO 21434? Automotive Cybersecurity Engineering Explained
- 3 What Is ISO 26262? A Guide to Functional Safety in Automotive
- 4 What Is an Automotive Safety Integrity Level (ASIL)?
- 5 What Is SOTIF? A Guide to ISO 21448 for ADAS Safety
- 10. Medical Device & Life Sciences Development
- Overview
- 1 The Importance of Benefit-Risk Analysis in Medical Device Development
- 2 Software as a Medical Device: Revolutionizing Healthcare
- 3 Navigating the Risks of Software of Unknown Pedigree (SOUP) in the Medical Device & Life Sciences Industry
- 4 What’s a Design History File, and How Are DHFs Used by Product Teams?
- 5 What Is ISO 13485? A Guide to Medical Device Quality Management Systems
- 6 What Is IEC 62304? A Guide to Medical Device Software
- 7 What Is a Device Master Record (DMR)? Definition and FDA Requirements
- 8 Failure Modes, Effects, and Diagnostic Analysis (FMEDA) for Medical Devices: What You Need to Know
- 9 Embracing the Future of Healthcare: Exploring the Internet of Medical Things (IoMT)
- 10 What Is General Safety and Performance Requirements (GSPR)? What You Need To Know
- 11 What Is IEC 62366? Usability Engineering for Medical Devices
- 12 What Is the Quality Management System Regulation (QMSR)?
- 13 510(k) vs PMA: Differences in FDA Device Approval and Clearance
- 14 EU MDR Compliance Requirements and Timeline
- 15 Essential Performance Requirements and How to Identify Them
- 16 DHF vs DMR vs DHR: What Changed Under the FDA QMSR
- 17 Computer Software Assurance for Production and Quality Systems
- 18 IVDR Compliance: What Manufacturers Need to Know
- 19 IVDR Compliance: What Manufacturers Need to Know (copy)
- 20 IEC 60601-1 Guide for Medical Devices
- 21 A Guide to Medical Device Requirements Management
- 22 What Are Design Controls? A Guide to the Process and Its Elements
- 11. Aerospace & Defense Development
- Overview
- 1 What is ITAR Compliance? What Engineering Teams Need to Know
- 2 What Is DO-278A? A Guide for Compliance Teams
- 3 ARP4754B Explained: Changes, Recognition, and Compliance
- 4 What Is a Safety Integrity Level (SIL)? How to Calculate and Apply It
- 5 A Guide to Aerospace Requirements Management
- 6 MIL-STD-882E: System Safety Standard for Defense Programs
- 7 What Is ARP4754A? A Complete Guide to Civil Aircraft and Systems Development Assurance
- 8 Understanding ARP4761A: Guidelines for System Safety Assessment in Aerospace
- 9 What Is DO-254? A Complete Guide to Airborne Hardware Design Assurance
- 10 What Is DO-178C? A Guide to Airborne Software Certification
- 11 Aerospace Requirements Management System: What to Look For
- 12. Architecture, Engineering, and Construction (AEC industry) Development
- 13. Industrial Manufacturing & Machinery, Automation & Robotics, Consumer Electronics, and Energy
- 14. Semiconductor Development
- 15. AI in Product Development
- Overview
- 1 What Is AI in Product Development? A Complete 2026 Guide
- 2 AI Test Case Generation: A Complete Guide for Regulated QA Teams
- 3 Using AI to Write Software Requirements: What Works and What Doesn’t
- 4 What Is the Model Context Protocol (MCP) for Requirements Management?
- 5 AI for Systems Engineering: Benefits, Risks, and Adoption
- 6 How to Automate Requirements Management
- 7 AI Requirements Quality Scoring for Automated Reviews
- 8 Artificial Intelligence in Requirements Management
- 16. Risk Management
- 17. Product Development Terms and Definitions
What Is Systems Engineering? Definition, Process and Roles
Systems engineering is the engineering discipline that plans, designs and verifies a complex product as one whole system, so that its hardware, software and other parts work together and meet its users’ needs from concept to retirement. Systems engineers define what the whole system must do, divide that into requirements for each part and each team, and verify that the integrated parts meet those requirements.
When one team’s choice constrains another team’s work, systems engineering is how the teams coordinate that decision. On a program with separate hardware, software and test groups, teams often find a mismatch between two subsystems at integration, months after the decision that caused it, when fixing it means reopening design and test work that depended on that decision.
What Does Systems Engineering Cover?
Systems engineering covers a system’s whole life cycle and the work of every engineering discipline that contributes to it. It is a transdisciplinary and integrative approach to realizing, using and retiring engineered systems with systems principles and with scientific, technological and management methods. In practice, that means developing an operable system that meets its requirements within constraints that often pull against each other.
Responsibilities Through Production and Operation
Systems engineers stay with a project from the initial idea through development, operation and retirement. During operation, they address upgrades, obsolescence management, maintenance and repair, manufacturing changes and user training. Running production itself is not part of the discipline.
Manufacturing engineers run production, while systems engineers assess how production changes affect the system.
Coordination and Management Across Disciplines
Systems engineering integrates the other engineering disciplines and doesn’t replace them. Systems engineers weigh the contributions of structural, electrical, mechanism, power and human factors engineers against one another, so the result is a coherent whole that no single discipline’s perspective dominates.
How much management comes with the role varies by project. On some projects, systems engineering includes strong governance, technical management and resource management, and on others it is an almost entirely technical, advisory and coordinating role where management structures already exist.
What Does a Systems Engineer Do Day to Day?
A systems engineer spends much of the working day documenting decisions as requirements and checking that the teams downstream can build and verify them. On NASA programs, the role has six responsibilities:
- Concept of operations and architecture: The systems engineer usually leads the development of the concept of operations (ConOps) and the system architecture that results from it. A team that captures that architecture in a Systems Modeling Language (SysML) model is practicing model-based systems engineering (MBSE).
- Requirements definition and allocation: Systems engineers turn the expectations of customers and users into a complete set of validated technical requirements written as “shall” statements. The systems engineer then allocates those requirements to subsystems and the teams that own them.
- Trade studies: Trade studies are performed before decisions are made, so the chosen design can be baselined with confidence. Systems engineers archive the supporting studies for later reference.
- Interface management: The systems engineer defines and assesses interfaces, usually through interface control documents (ICDs), and confirms that each ICD has been validated with the parties on both sides of the interface.
- Technical reviews: System requirements reviews (SRRs), preliminary design reviews (PDRs) and critical design reviews (CDRs) have entrance criteria that should not be waived.
- Verification and validation oversight: The systems engineer oversees verification and validation, which check whether the built system meets its requirements and whether it meets users’ needs in operation. The systems engineer tracks verification in a matrix that lists each “shall” requirement, the document it comes from and how each one is verified.
The balance between those tasks shifts as a program matures. Concept work, requirements and trade studies take most of the time early on. Systems engineers spend more time on integration issues, verification closure and change requests later.
What Are the Stages of the Systems Engineering Process?
ISO/IEC/IEEE 15288:2023 covers the whole system life cycle, including the “conception, development, production, utilization, support and retirement of systems.” The generic life cycle model in the Systems Engineering Body of Knowledge (SEBoK) has six stages, each with its own activities.
| Stage | What happens |
| Concept | Identify user needs, explore concepts and propose viable designs |
| Development | Refine system requirements, create the system description, build the system, and verify and validate it |
| Production | Produce the system, then inspect and test it |
| Utilization | Operate the system to deliver its intended capability |
| Support | Sustain that capability through maintenance and logistics |
| Retirement | Store, archive or dispose of the system |
Each stage ends at a decision gate where decision makers choose to proceed, remain in the current stage, or terminate or re-scope the work. Once you identify your program’s current stage, you can check what decision makers at the next gate will require. NASA runs its own version, with phases from Pre-Phase A concept studies through Phase F closeout and Key Decision Points (KDPs) marking each transition.
Under ISO/IEC/IEEE 15288, teams choose their own life cycle model and can apply its processes iteratively and concurrently to a system and recursively to its elements. With that flexibility, one team can follow a V-model while another manages incremental releases against the same six stages. For the activities inside development, use our guide to the systems engineering process for complex programs.
Which Standards and Handbooks Define Systems Engineering?
ISO/IEC/IEEE 15288:2023 is the process standard that the International Council on Systems Engineering (INCOSE) handbook and the ISO/IEC/IEEE companion standards build on. It defines four sets of life cycle processes, named agreement processes, organizational project-enabling processes, technical management processes and technical processes.
Systems engineers spend most of their time in the last two groups. The technical management processes are project planning, project assessment and control, decision management, risk management, configuration management, information management, measurement and quality assurance.
Engineers begin the technical processes with business or mission analysis and the definition of needs and system requirements. The technical processes then run through architecture and design, system analysis, implementation, integration, verification, transition, validation, operation, maintenance and disposal. Alongside 15288, systems engineers use companion documents for requirements engineering, management planning and practice guidance.
| Document | Edition and date | What it gives a systems engineer |
| ISO/IEC/IEEE 15288:2023 | Edition 2, May 2023 | The process framework and vocabulary for the full system life cycle |
| ISO/IEC/IEEE 29148:2018 | Edition 2, November 2018, with a draft revision under development | Processes and required information items for requirements engineering |
| ISO/IEC/IEEE 24748-4:2026 | Edition 2, February 2026 | Requirements and guidance for the content of a systems engineering management plan (SEMP) |
| INCOSE Systems Engineering Handbook | Fifth edition, July 2023 | Practice guidance that elaborates the 15288:2023 processes |
| NASA Systems Engineering Handbook, NASA/SP-2016-6105 Rev 2 | Publication record dated February 17, 2017 | NASA’s practice companion to its NASA Procedural Requirements (NPR) 7123.1 |
| SEBoK | Version 2.14, May 2026 | A guide to the systems engineering literature, stewarded by INCOSE, the IEEE Systems Council and Stevens Institute of Technology |
| INCOSE Systems Engineering Vision 2035 | 2021 | The strategic direction INCOSE sets for the discipline |
You’ll use 15288 for the process names that contracts and audits refer to, and the INCOSE handbook for how to perform those processes. When a contract cites 29148 for requirements engineering, confirm the edition, because ISO is developing a revision to replace the 2018 edition.
How Do Requirements Hold a Systems Engineering Program Together?
Engineers use requirements to communicate agreed decisions between disciplines. A systems engineer communicates architecture and trade decisions to hardware, software and test teams through allocated and derived requirements. The program then shows that each requirement is met by tracing it to the design that satisfies it and the test that verifies it.
What Allocated and Derived Requirements Are
An allocated requirement is a higher-level requirement assigned to a subsystem, function or configuration item. The approved set of allocated requirements is the allocated baseline, which documents the functional, performance and interface characteristics allocated from a higher-level requirements document. A derived requirement is one the team adds because of an architecture choice, a design decision or a constraint the parent implies without stating.
Systems engineers repeat that allocation and derivation at every level. Once baselined, the derived and allocated requirements become the high-level requirements for the decomposed elements, and the process begins again.
What Bidirectional Traceability Has to Connect
Bidirectional traceability is the ability to trace any requirement to its parent requirement and to the child requirements allocated from it. Engineers also link requirements to verification, so each requirement’s record holds a trace to its parent and its system verification method.
You can identify different problems by tracing upward and downward. When a requirement has no parent and isn’t an acceptable self-derived requirement, either the traceability process is flawed and should be redone, or the requirement is gold plating and should be eliminated. For link types and matrices, use our requirements traceability chapter.
What Breaks When Traceability Is Maintained by Hand
When you store requirements in documents and links in a spreadsheet, someone has to update the trace after each change. Without those updates, you have to assess change impact from memory. Managing requirements changes well takes a process that assesses the impact of each proposed change before anyone approves or implements it. Poor requirement traceability can compromise technical products and disrupt milestone reviews such as the SRR and the System Design Review (SDR).
For interface changes, integration with the launch vehicle is too late in the development cycle to discover that a spacecraft has an issue with its umbilical interface. Engineers can also miss change impacts when reusing software, as the first flight of Ariane 5 shows.
Ariane 5 reused inertial reference software from Ariane 4, including an alignment function whose timing was based on an Ariane 4 requirement and wasn’t required for Ariane 5. After lift-off the function stayed active, and the maiden flight ended in failure on 4 June 1996. The European Space Agency (ESA) Inquiry Board found that the alignment function “was not taken into account in the simulations and that the equipment and system tests were not sufficiently representative.” To check whether a reused function has a reason to run in the new system, engineers can trace it to a parent requirement.
What a Requirements Record Has to Hold
Each requirement needs enough metadata for someone other than its author to check its source and verification evidence. Four fields make that check possible:
- Owner: The owner is the person or group responsible for writing, managing or approving changes to the requirement. Without one, a change request has nobody to approve it.
- Version and baseline: Each requirement has a version number for maintenance and belongs to a baseline, an agreed set of requirements, designs or documents whose changes are controlled through formal approval and monitoring.
- Links: You record links to a parent, to any interface definition and to the design and tests below it. A “Traced from” field records the relationship between a derived requirement and its parent.
- Verification method and status: The method is test, inspection, analysis or demonstration, and the status lets engineers identify open items before a review.
The four fields are useful only when they stay current together, and keeping requirements, design and tests linked in one place reduces the manual reconciliation work systems engineers do. Dexcom, which focused on improving traceability and cross-functional collaboration, achieved a 60% productivity boost for their systems engineering team. On regulated programs, auditors also use the same record to trace a requirement back to its source and forward to its verification evidence.
How Is Systems Engineering Applied in Regulated Industries?
Regulated industries run the same process and add a demand for evidence that every requirement was allocated, implemented and verified. Systems engineers in aerospace and defense, medical device and automotive programs use industry-specific standards to organize that evidence.
Aerospace and Defense
ARP4754B gives recommended practices for developing civil aircraft and systems, and its current revision dates from 19 December 2023. Its practices include validation of requirements and verification of the design implementation. Under ARP4754B, software development is addressed through DO-178C and airborne electronic hardware through DO-254.
RTCA published DO-178C in 2011. The Federal Aviation Administration (FAA) references it in Advisory Circular (AC) 20-115D.
DO-178C and DO-254 are civil airworthiness documents that some defense programs also adopt by contract. Because a system-level change can affect both software and hardware, it has to be traced into the software and hardware analyses it affects.
Medical Devices
FDA’s Quality Management System Regulation (QMSR) has been in effect since 2 February 2026. The QMSR incorporates ISO 13485:2016 by reference.
Manufacturers of class II, class III and certain class I devices must meet the design and development requirements in Clause 7.3 of ISO 13485 (21 CFR 820.10(c)). The former design section, 21 CFR 820.30, is now marked Reserved. Manufacturers address the elements formerly called “Design Controls” and “Design History File (DHF)” through those same design and development requirements.
Manufacturers must address planning, inputs, outputs, review, verification, validation, transfer and changes (Clause 7.3). Design inputs must be complete, unambiguous, able to be verified or validated, and not in conflict with each other. During planning, manufacturers record roles and responsibilities, traceability methods and the resources needed. Manufacturers also evaluate each design change for its impact on constituent parts and the product. For the move from the old regulation, read our overview of FDA and ISO 13485 harmonization.
Automotive
ISO 26262:2018 sets the functional safety requirements for road vehicles, and a draft third edition is under development. Engineers perform product development at the system level, including technical safety requirements, the technical safety concept, system architectural design, item integration and testing, and safety validation (Part 4). System-level work builds on the item definition and the Hazard Analysis and Risk Assessment (HARA) that the concept phase produces.
Automotive SPICE (ASPICE) assesses the process around that work. The Quality Management Center of the German Association of the Automotive Industry (VDA QMC) released version 4.1 in August 2026, with five system engineering processes named SYS.1 Requirements Elicitation, SYS.2 System Requirements Analysis, SYS.3 System Architectural Design, SYS.4 System Integration and Integration Verification, and SYS.5 System Verification.
Assessors look for consistency and bidirectional traceability between the elements of the system architecture and the system requirements (SYS.3). The existence of links doesn’t by itself mean the information is consistent, so an assessor checks what the links connect, not only that they exist.
Will AI Change the Systems Engineer’s Job?
AI is changing the tools systems engineers use faster than it changes what they’re accountable for. INCOSE expects AI to substantially change systems engineering methods and tools as algorithms are developed to help systems engineers deliver results more efficiently and effectively. SEBoK’s editors expect the next evolution of systems engineering practice to come mainly from AI technologies that assist systems engineers in development life cycle activities.
AI tools can check requirements against INCOSE’s Guide to Writing Requirements V4, which INCOSE released in June 2023. Engineers can find it difficult to apply all 42 rules consistently while writing. Researchers from MITRE assessed how far natural language processing (NLP) techniques can automate those checks, in work presented at INCOSE’s 2025 International Symposium. They reported that 78% of the rules they assessed can be checked at least partially with NLP techniques.
Large language models (LLMs) may hallucinate information, so engineers need to review their output during requirements work. A well-formed requirement can still be wrong or infeasible, and only an engineer who knows the system can judge that.
On a regulated program, an AI-proposed requirement, trace link or test case should count only after an engineer reviews and accepts it, with the record showing who accepted it and when. A general-purpose AI tool used on its own has no product context, no governance and no audit trail, so its suggestions lack the relationships and history the requirement depends on.
Learn About Model-Based Systems Engineering
How Jama Connect Supports Systems Engineering
Jama Connect® is a web-based requirements management and traceability platform for complex, regulated product development. For systems engineers coordinating allocated and derived requirements across teams, it stores each requirement as an item with its own version history, status and trace links. The Traceability Information Model (TIM) defines the expected chain from needs through system and subsystem requirements to design elements and test cases, and it flags a requirement that’s missing its verification. When a systems engineer changes a requirement, suspect links flag linked downstream test cases and design elements for review, and engineers use impact analysis to identify what a proposed change would affect before anyone approves it. Traceable MBSE™ links requirements to the SysML model elements that satisfy them through Jama Connect’s pre-built MBSE integrations.
We ship pre-built frameworks for airborne systems, medical devices and automotive programs, with out-of-the-box exports for traceability matrices and audit documentation. For AI-assisted work, Jama Intelligence is an add-on for Jama Connect Cloud that evaluates requirements against 30 of the 40 INCOSE rules and the six Easy Approach to Requirements Syntax (EARS) patterns, and its drafted test cases are linked to a requirement only when an engineer accepts them. Self-hosted customers can access Jama Intelligence Gateway, which contains only the Intelligence Assistant. Anything performed with AI inside Jama Connect is versioned and documented as AI-generated.
Setting Up Systems Engineering Around a Traceable Requirements Record
At the concept stage, before the first allocation, set up a traceable requirements record, because architecture diagrams and trade studies get superseded as a program evolves. The set of allocated requirements, with their owners, rationale and links, is what a successor engineer, a supplier or an auditor can still follow years later.
Jama Connect supports that setup with baselines you can compare later to see what changed in the record and when. To check how readily another engineer can follow that record, you can start a free 30-day trial with one of your own subsystems.
Frequently Asked Questions About Systems Engineering
Is systems engineer a job title or a set of activities?
Systems engineer is both a job title and a description of activities. People with these skills are usually called systems engineers, but they may also hold titles such as lead systems engineer, technical manager or chief engineer. Every engineer and discipline that contributes to a system’s design and development also practices systems engineering.
How is systems engineering different from project management?
A project manager balances schedule, budget and resources to deliver an acceptable product on its delivery date, while the systems engineer is responsible for the product’s content and the technical decisions behind it. The two roles meet at trade-offs over cost and schedule, which the systems engineer works through with the project manager.
What certifications does INCOSE offer for systems engineers?
INCOSE certifies systems engineers at three levels. The Associate Systems Engineering Professional (ASEP) recognizes systems engineering knowledge without requiring work experience, and the Certified Systems Engineering Professional (CSEP) requires at least five years of direct systems engineering work experience. For the Expert Systems Engineering Professional (ESEP), INCOSE requires at least twenty years of experience, with leadership in the practice of systems engineering. Since March 2025, the knowledge exam has tested only the fifth edition of the INCOSE handbook.
Is systems engineering only used in aerospace?
No, systems engineering also applies to biomedical, defense, healthcare, power and energy, telecommunications and transportation programs. ISO/IEC/IEEE 15288 applies to one-of-a-kind systems, mass-produced systems and customised, adaptable systems, so the same process vocabulary works for a satellite and a consumer device.
If I want to learn more about systems engineering, what else should I read?
Use our chapter on the Systems Engineering Body of Knowledge to understand how SEBoK is organized and find each knowledge area. For links between requirements and their verification tests, follow the guide to building a traceability matrix. To keep requirements and SysML models connected, read about Jama Connect’s MBSE software.
This article was authored by Mario Maldari and published on November 7, 2026.
Book a Demo
See Jama Connect in Action!
Our Jama Connect experts are ready to guide you through a personalized demo, answer your questions, and show you how Jama Connect can help you identify risks, improve cross-team collaboration, and drive faster time to market.