1.0: System Engineering Processes
Key Terms
Before diving into the content, here are key acronyms used throughout this chapter:
- SYS: System Engineering process group
- SWE: Software Engineering process group
- HWE: Hardware Engineering process group
- ASPICE: Automotive SPICE (Software Process Improvement and Capability dEtermination)
- V-Model: Verification and validation lifecycle model
- HITL: Human-in-the-Loop (human oversight pattern)
- L0-L3: Automation levels (Manual to Full Automation)
- WP: Work Product
- TCL: Tool Confidence Level
- ASIL: Automotive Safety Integrity Level
- SIL: Safety Integrity Level
- MC/DC: Modified Condition/Decision Coverage
- TARA: Threat Analysis and Risk Assessment
- STRIDE: Security threat modeling framework (Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege)
Learning Objectives
After reading this chapter, you will be able to:
- Describe the five SYS processes and their relationships
- Implement system engineering with AI augmentation
- Produce ASPICE-compliant system work products
- Map SYS processes to V-Model phases
Chapter Overview
The System Engineering (SYS) process group addresses the complete system lifecycle from stakeholder needs to qualified system. The V-Model diagram below positions each SYS process on the left (development) or right (verification) side, showing how requirements flow down and verification flows up.
SYS Process Summary
| Process | Purpose | AI Automation Level | V-Model Phase |
|---|---|---|---|
| SYS.1 | Gather stakeholder requirements | L0-L1 | V-Model Left |
| SYS.2 | Transform to system requirements | L1-L2 | V-Model Left |
| SYS.3 | Establish system architecture | L1 | V-Model Left |
| SYS.4 | System integration and integration verification | L2 | V-Model Right |
| SYS.5 | System verification | L1-L2 | V-Model Right |
What This Means: The SYS process group covers the complete system lifecycle from stakeholder needs to validation. Notice that AI automation increases from left to right in the V-model, with higher automation in verification activities (SYS.4) compared to requirements activities (SYS.1). This reflects the increased complexity of requirements work that requires human judgment.
Process Relationships
The following diagram shows how the five SYS processes interact, illustrating the flow of work products from requirements elicitation through qualification testing.
Key Work Products
Note: ASPICE 4.0 uses generic work product types (e.g., 17-00 "Requirement", 08-60 "Verification Measure", 15-52 "Verification Results"). The process context determines the specific requirements type (stakeholder, system, software, hardware) or verification scope (integration, system).
| WP ID | Work Product | Producer Process |
|---|---|---|
| 17-00 | Requirement (stakeholder requirements) | SYS.1 |
| 17-00 | Requirement (system requirements specification) | SYS.2 |
| 04-06 | System architecture description | SYS.3 |
| 08-60 | Verification Measure (integration) | SYS.4 |
| 15-52 | Verification Results (integration) | SYS.4 |
| 08-60 | Verification Measure (system) | SYS.5 |
| 15-52 | Verification Results (system) | SYS.5 |
What This Means: These work products represent the tangible outputs of the SYS process group. Each work product has a specific ID that follows the ASPICE 4.0 standard, ensuring consistency across projects. The progression from stakeholder requirements to qualification test results shows the complete system development lifecycle.
AI Integration Overview
Per-Process AI Opportunities
| Process | AI Capability | HITL Pattern |
|---|---|---|
| SYS.1 | Document analysis, need extraction | Collaborator |
| SYS.2 | Consistency checking, completeness analysis | Reviewer |
| SYS.3 | Pattern matching, allocation suggestions | Reviewer |
| SYS.4 | Test case generation, result analysis | Reviewer |
| SYS.5 | Traceability verification, coverage analysis | Monitor |
What This Means: AI integration varies significantly across the SYS processes. Early processes (SYS.1) require more human collaboration due to stakeholder interaction, while later processes (SYS.4-5) allow for higher automation in test generation and analysis. The HITL patterns indicate how humans should interact with AI in each process.
Automation Level Rationale
| Level | Process | Rationale |
|---|---|---|
| L0-L1 | SYS.1 | Human stakeholder interaction essential |
| L1-L2 | SYS.2 | AI analysis + human judgment |
| L1 | SYS.3 | Architecture requires human decisions |
| L2 | SYS.4 | AI can generate/execute tests |
| L1-L2 | SYS.5 | AI analysis + human validation |
What This Means: The automation level rationale explains why certain processes have higher or lower AI automation. Requirements and architecture processes (SYS.1-3) require more human judgment, while verification processes (SYS.4-5) can leverage more AI automation for repetitive tasks like test execution and analysis.
Chapter Sections
| Section | Topic | Focus |
|---|---|---|
| 05.01 | SYS.1 Requirements Elicitation | Stakeholder needs capture |
| 05.02 | SYS.2 System Requirements Analysis | Requirements specification |
| 05.03 | SYS.3 System Architectural Design | Architecture development |
| 05.04 | SYS.4 System Integration and Integration Verification | System element integration and verification |
| 05.05 | SYS.5 System Verification | System verification against system requirements |
| 05.06 | AI Tools for System Engineering | Tool recommendations |
Prerequisites
Before reading this chapter, ensure familiarity with:
| Prerequisite | Covered In |
|---|---|
| ASPICE framework | 01.02, 02.00-02.04 |
| V-Model structure | 01.03 |
| Automation levels | 03.01 |
| HITL patterns | 03.02 |
AI Impact by Process
| Process | AI Impact | Primary AI Use Cases |
|---|---|---|
| SYS.1 | Low | Document analysis, interview preparation |
| SYS.2 | Medium-High | Consistency analysis, completeness checking, conflict detection |
| SYS.3 | Medium | Pattern matching, allocation suggestions, design space exploration |
| SYS.4 | High | Test case generation, execution automation, result analysis |
| SYS.5 | Medium-High | Traceability verification, coverage analysis, report generation |
What This Means: The AI impact varies across the system engineering processes, with the highest impact in verification activities (SYS.4) where AI can automate test generation and execution. Requirements and analysis processes (SYS.1-2) benefit from AI for consistency checking, while architectural processes (SYS.3) see moderate AI impact for design exploration.
Cross-References
| Topic | See Also |
|---|---|
| AI Tools for Requirements | Part III - Chapter 13 |
| AI Tools for Testing | Part III - Chapter 15 |
| Practical SYS Implementation | Part IV - Chapter 17 |
| ISO 26262 Integration | Part IV - Chapter 18 |