Stakeholder Requirements Specification

Document ID	Rev	Date	Classification
SYS.1-001	1.0	2026-03-21	Confidential

Revision History

Rev	Date	Author	Reviewer	Description
1.0	2026-03-21	An Dao	--	Initial release

1. Purpose

This document captures the stakeholder requirements for the foxBMS 2 POSIX vECU project in accordance with ASPICE SYS.1 (Stakeholder Requirements Analysis). It identifies the key stakeholders, elicits their needs, and formalizes them into traceable requirements that drive the system and software specifications.

2. Scope

All stakeholder requirements for the POSIX SIL adaptation of foxBMS 2 v1.10.0, covering the vECU, plant model, test infrastructure, and documentation.

3. References

ID	Title
[SYS.2-001]	System Requirements Specification
[ASMT-SCOPE-001]	ASPICE CL2 Assessment Scope
[GAP-ANALYSIS]	foxBMS POSIX vECU Gap Analysis

4. Stakeholder Identification

4.1 Stakeholder 1: HIL Test Engineer

Role: Primary end-user of the SIL system. Uses the vECU to pre-validate BMS test cases before executing them on the physical HIL bench.

Context: HIL bench time is expensive and limited. Test setup on real hardware requires physical battery simulators, power supplies, and contactor assemblies. Many BMS logic tests (state transitions, diagnostic thresholds, CAN message content) can be validated in software first.

Needs: - Run BMS logic on a standard Linux workstation without hardware dependencies - Execute the same diagnostic and state machine logic as the production ECU - Validate CAN message content and timing before HIL bench sessions - Automate regression testing in CI pipelines

4.2 Stakeholder 2: Functional Safety Engineer

Role: Responsible for demonstrating that the BMS meets ASIL-D safety requirements per ISO 26262. Uses fault injection to validate that diagnostic paths correctly detect anomalies and transition the BMS to a safe state.

Context: Inducing real faults on hardware (overvoltage, overcurrent, sensor failure) is dangerous and destructive. A SIL environment enables exhaustive fault injection without risk to equipment or personnel.

Needs: - Inject faults into cell voltages, currents, and temperatures programmatically - Verify that DIAG_Handler correctly classifies and escalates each fault - Trace safety requirements through to test evidence - Validate FTTI (Fault Tolerant Time Interval) behavior in software

4.3 Stakeholder 3: Student / New Developer

Role: Newcomer to the foxBMS codebase who needs to understand, build, and experiment with the BMS without access to target hardware.

Context: The foxBMS project is complex (170+ source files, FreeRTOS, TMS570-specific HAL). A new developer cannot easily set up the full toolchain (Code Composer Studio, HALCoGen, TMS570 LaunchPad). The POSIX port provides an accessible entry point.

Needs: - Clone and build with a single command on standard Ubuntu - Observe BMS behavior through CAN messages and log output - Understand the architecture through clear documentation - Modify and experiment without risk of bricking hardware

5. Stakeholder Requirements

5.1 Build and Setup

ID	Requirement	Stakeholder	Priority	Traces To
STKH-REQ-001 ↓ Traces Down SW-REQ-062 SW-REQ-129 SYS-REQ-001 SYS-REQ-150	The system shall build from source on Ubuntu 24.04 LTS using only standard packages (GCC, Make, Python 3, SocketCAN).	S3: Student	MUST	SYS-REQ-001 ↑ Traces Up STKH-REQ-001 ↓ Traces Down IT-010 QT-001 SW-REQ-062 UT-042
STKH-REQ-002 ↓ Traces Down SW-REQ-062 SW-REQ-129 SYS-REQ-002 SYS-REQ-150	A single setup command shall clone the repository, apply all patches, build the vECU, configure the CAN interface, and run a smoke test.	S3: Student	MUST	SYS-REQ-002 ↑ Traces Up STKH-REQ-002 ↓ Traces Down IT-010 QT-001 SW-REQ-062 UT-042
STKH-REQ-003 ↓ Traces Down SW-REQ-062 SW-REQ-063 SW-REQ-066 SW-REQ-080 SW-REQ-129 SYS-REQ-003 SYS-REQ-150 UT-080	The build shall complete in under 60 seconds on a standard workstation.	S1: HIL Eng	SHOULD	SYS-REQ-003 ↑ Traces Up STKH-REQ-003 ↓ Traces Down IT-010 QT-001 SW-REQ-062 SW-REQ-063 SW-REQ-066 SW-REQ-080 UT-042
STKH-REQ-004 ↓ Traces Down SW-REQ-062 SW-REQ-063 SW-REQ-129 SYS-REQ-004 SYS-REQ-150	The system shall use foxBMS v1.10.0 as a pinned, version-checked dependency to ensure reproducible builds.	S1: HIL Eng	MUST	SYS-REQ-004 ↑ Traces Up STKH-REQ-004 ↓ Traces Down IT-010 QT-001 SW-REQ-062 SW-REQ-063 UT-042

5.2 BMS Functional Behavior

ID	Requirement	Stakeholder	Priority	Traces To
STKH-REQ-005 ↓ Traces Down IT-001 IT-011 SW-REQ-040 SW-REQ-050 SW-REQ-051 SW-REQ-062 SW-REQ-065 SW-REQ-070 +6 more	The vECU shall execute the same BMS state machine logic as the production foxBMS (SYS/BMS/CONT/BAL state machines).	S1: HIL Eng	MUST	SYS-REQ-010 ↑ Traces Up STKH-REQ-005 ↓ Traces Down IT-011 QT-001 SW-REQ-062 SW-REQ-065 SW-REQ-070
STKH-REQ-006 ↓ Traces Down IT-001 SSR-020 SSR-051 SW-REQ-040 SW-REQ-041 SW-REQ-042 SW-REQ-043 SW-REQ-050 +16 more	The BMS shall reach the NORMAL operating state through the legitimate transition sequence (UNINIT, INIT, IDLE, STANDBY, PRECHARGE, NORMAL).	S1: HIL Eng	MUST	SYS-REQ-011 ↑ Traces Up STKH-REQ-006 ↓ Traces Down IT-011 QT-001 SW-REQ-062 SW-REQ-065 SW-REQ-071 SW-REQ-075
STKH-REQ-007 ↓ Traces Down IT-002 IT-010 IT-036 SSR-001 SSR-040 SSR-041 SW-REQ-001 SW-REQ-003 +28 more	The vECU shall transmit at least 15 CAN message types on the virtual CAN bus, matching the foxBMS DBC message IDs.	S1: HIL Eng	MUST	SYS-REQ-020 ↑ Traces Up STKH-REQ-007 ↓ Traces Down IT-030 QT-002 QT-008 SSR-001 SW-REQ-001 SW-REQ-003 UT-010 UT-011 +1 more
STKH-REQ-008 ↓ Traces Down IT-011 IT-036 SSR-003 SW-REQ-010 SW-REQ-070 SW-REQ-071 SW-REQ-072 SW-REQ-073 +9 more	The SOC algorithm shall reflect changes in battery state of charge when current flows (discharge or charge).	S1: HIL Eng	MUST	SYS-REQ-030 ↑ Traces Up STKH-REQ-008 ↓ Traces Down IT-036 QT-004 SSR-003 SW-REQ-010 UT-016

5.3 Safety and Diagnostics

ID	Requirement	Stakeholder	Priority	Traces To
STKH-REQ-009 ↓ Traces Down IT-036 SSR-005 SSR-020 SSR-030 SSR-031 SSR-032 SSR-033 SSR-042 +12 more	The vECU shall execute the DIAG_Handler for all software-checkable diagnostic IDs (overvoltage, undervoltage, overcurrent, overtemperature, plausibility).	S2: Safety Eng	MUST	SYS-REQ-040 ↑ Traces Up STKH-REQ-009 ↓ Traces Down IT-032 QT-005 SSR-005 SW-REQ-020 UT-018
STKH-REQ-010 ↓ Traces Down SSR-006 SW-REQ-021 SW-REQ-034 SW-REQ-035 SYS-REQ-041 SYS-REQ-153 SYS-REQ-154 UT-024 +1 more	Hardware-absent diagnostic IDs (AFE SPI, SBC, I2C, IMD, interlock) shall be explicitly suppressed with documented rationale.	S2: Safety Eng	MUST	SYS-REQ-041 ↑ Traces Up STKH-REQ-010 ↓ Traces Down IT-033 QT-005 SSR-006 SW-REQ-021 UT-019
STKH-REQ-011 ↓ Traces Down IT-050 SSR-020 SSR-021 SSR-030 SSR-032 SSR-033 SSR-042 SSR-050 +12 more	The system shall provide a fault injection interface that allows test scripts to override cell voltages, currents, and temperatures at runtime.	S2: Safety Eng	MUST	SYS-REQ-050 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-040 IT-060 QT-007 QT-010 QT-011 QT-012 QT-014 SSR-030 +3 more
STKH-REQ-012 ↓ Traces Down SSR-020 SSR-030 SSR-032 SSR-033 SSR-042 SW-REQ-030 SW-REQ-031 SW-REQ-032 +4 more	Injected faults shall trigger the same DIAG_Handler response as genuine sensor readings (same DIAG ID, same severity classification).	S2: Safety Eng	MUST	SYS-REQ-051 ↑ Traces Up STKH-REQ-009 STKH-REQ-012 ↓ Traces Down IT-040 IT-042 QT-004 SSR-032 SW-REQ-030 SW-REQ-031 UT-001 UT-003
STKH-REQ-013 ↓ Traces Down IT-050 SSR-007 SSR-021 SSR-022 SSR-023 SSR-024 SSR-050 SSR-052 +12 more	FAS_ASSERT violations shall terminate the vECU with a visible error message including file and line number.	S2: Safety Eng	MUST	SYS-REQ-042 ↑ Traces Up STKH-REQ-013 ↓ Traces Down IT-034 QT-005 SSR-007 SW-REQ-022 UT-020

5.4 Test Automation

ID	Requirement	Stakeholder	Priority	Traces To
STKH-REQ-014 ↓ Traces Down IT-002 IT-010 SW-REQ-060 SW-REQ-061 SW-REQ-068 SW-REQ-069 SW-REQ-090 SW-REQ-093 +10 more	An automated smoke test shall verify that the BMS reaches NORMAL state, contactors close, and SOC is non-zero.	S1: HIL Eng	MUST	SYS-REQ-060 ↑ Traces Up STKH-REQ-007 STKH-REQ-014 ↓ Traces Down IT-001 IT-007 IT-010 QT-001 SW-REQ-060 SW-REQ-061 SW-REQ-068 SW-REQ-069 +11 more
STKH-REQ-015 ↓ Traces Down IT-002 SW-REQ-091 SW-REQ-100 SW-REQ-129 SYS-REQ-061 SYS-REQ-150 UT-052	The vECU shall support a timeout flag (--timeout N) for CI pipeline integration, exiting cleanly after N seconds.	S1: HIL Eng	MUST	SYS-REQ-061 ↑ Traces Up STKH-REQ-007 STKH-REQ-015 ↓ Traces Down IT-001 IT-013 QT-001 SW-REQ-091 SW-REQ-100 UT-051
STKH-REQ-016 ↓ Traces Down SSR-041 SW-REQ-095 SW-REQ-101 SW-REQ-111 SW-REQ-129 SYS-REQ-062 SYS-REQ-150	Integration tests shall verify end-to-end CAN communication between plant model and vECU.	S1: HIL Eng	SHOULD	SYS-REQ-062 ↑ Traces Up STKH-REQ-007 STKH-REQ-016 ↓ Traces Down IT-002 IT-004 QT-001 QT-006 SSR-041 SW-REQ-095 SW-REQ-09B SW-REQ-101 +2 more
STKH-REQ-017 ↓ Traces Down SSR-020 SSR-030 SSR-032 SSR-033 SSR-040 SSR-042 SW-REQ-030 SW-REQ-031 +7 more	ASIL-D fault injection tests shall cover all safety-relevant diagnostic paths with pass/fail verdict.	S2: Safety Eng	MUST	SYS-REQ-063 ↑ Traces Up STKH-REQ-007 STKH-REQ-017 ↓ Traces Down IT-001 IT-007 QT-006 SSR-040 SW-REQ-095 SW-REQ-09B SW-REQ-110

5.5 Documentation and Usability

ID	Requirement	Stakeholder	Priority	Traces To
STKH-REQ-018 ↓ Traces Down IT-002 SW-REQ-050 SW-REQ-053 SW-REQ-100 SW-REQ-129 SYS-REQ-070 SYS-REQ-150 UT-052	The project shall include a troubleshooting guide covering common failure modes with diagnosis and resolution steps.	S3: Student	SHOULD	SYS-REQ-070 ↑ Traces Up STKH-REQ-018 ↓ Traces Down IT-020 QT-001 SW-REQ-050 SW-REQ-053 SW-REQ-100
STKH-REQ-019 ↓ Traces Down IT-001 SW-REQ-040 SW-REQ-108 SW-REQ-129 SW-REQ-203 SYS-REQ-071 SYS-REQ-150 UT-030	The architecture shall be documented with block diagrams showing layer decomposition and data flow.	S3: Student	SHOULD	SYS-REQ-071 ↑ Traces Up STKH-REQ-019 ↓ Traces Down IT-021 IT-024 IT-060 QT-001 SSR-020 SSR-021 SW-REQ-040 SW-REQ-108 +2 more
STKH-REQ-020 ↓ Traces Down SSR-051 SW-REQ-041 SW-REQ-109 SW-REQ-129 SYS-REQ-072 SYS-REQ-150 UT-030	A feature coverage matrix shall identify which foxBMS features work on POSIX, which are suppressed, and which are not implemented.	S1: HIL Eng	MUST	SYS-REQ-072 ↑ Traces Up STKH-REQ-020 ↓ Traces Down IT-021 QT-001 SSR-051 SW-REQ-041 SW-REQ-109 UT-031

6. Requirements Analysis

6.1 Prioritization

Priority	Count	Description
MUST	15	Essential for SIL validation purpose
SHOULD	5	Important for usability and completeness

6.2 Conflicts and Trade-offs

Conflict	Resolution
STKH-REQ-005 ↓ Traces Down IT-001 IT-011 SW-REQ-040 SW-REQ-050 SW-REQ-051 SW-REQ-062 SW-REQ-065 SW-REQ-070 +6 more (same logic) vs. single-threaded execution	ACCEPTED: cooperative loop preserves logic correctness; concurrency testing deferred to HIL (GA-02)
STKH-REQ-010 ↓ Traces Down SSR-006 SW-REQ-021 SW-REQ-034 SW-REQ-035 SYS-REQ-041 SYS-REQ-153 SYS-REQ-154 UT-024 +1 more (suppress HW diag) vs. STKH-REQ-009 ↓ Traces Down IT-036 SSR-005 SSR-020 SSR-030 SSR-031 SSR-032 SSR-033 SSR-042 +12 more (execute SW diag)	Selective DIAG_Handler: 24 HW IDs suppressed, 61 SW IDs enabled
STKH-REQ-003 ↓ Traces Down SW-REQ-062 SW-REQ-063 SW-REQ-066 SW-REQ-080 SW-REQ-129 SYS-REQ-003 SYS-REQ-150 UT-080 (build speed) vs. STKH-REQ-004 ↓ Traces Down SW-REQ-062 SW-REQ-063 SW-REQ-129 SYS-REQ-004 SYS-REQ-150 (reproducibility)	setup.sh caches submodule; incremental builds take <10s

6.3 Traceability

All STKH-REQ-xxx requirements trace forward to SYS-REQ-xxx in the System Requirements Specification (SYS.2-001). The bidirectional traceability matrix in ISO26262-part8-traceability.md provides the complete mapping chain from stakeholder requirements through system requirements, software requirements, detailed design, and test cases.

5.7 Traceability: STKH-REQ → SYS-REQ

STKH-REQ	Traces Down To
STKH-REQ-001 ↓ Traces Down SW-REQ-062 SW-REQ-129 SYS-REQ-001 SYS-REQ-150	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-002 ↓ Traces Down SW-REQ-062 SW-REQ-129 SYS-REQ-002 SYS-REQ-150	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-003 ↓ Traces Down SW-REQ-062 SW-REQ-063 SW-REQ-066 SW-REQ-080 SW-REQ-129 SYS-REQ-003 SYS-REQ-150 UT-080	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-004 ↓ Traces Down SW-REQ-062 SW-REQ-063 SW-REQ-129 SYS-REQ-004 SYS-REQ-150	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-005 ↓ Traces Down IT-001 IT-011 SW-REQ-040 SW-REQ-050 SW-REQ-051 SW-REQ-062 SW-REQ-065 SW-REQ-070 +6 more	SYS-REQ-080 ↑ Traces Up STKH-REQ-005 STKH-REQ-006 ↓ Traces Down QT-001 QT-008 SW-REQ-050 SW-REQ-051 SW-REQ-123 UT-100 , SYS-REQ-090 ↑ Traces Up STKH-REQ-005 STKH-REQ-006 ↓ Traces Down SW-REQ-040
STKH-REQ-006 ↓ Traces Down IT-001 SSR-020 SSR-051 SW-REQ-040 SW-REQ-041 SW-REQ-042 SW-REQ-043 SW-REQ-050 +16 more	SYS-REQ-080 ↑ Traces Up STKH-REQ-005 STKH-REQ-006 ↓ Traces Down QT-001 QT-008 SW-REQ-050 SW-REQ-051 SW-REQ-123 UT-100 , SYS-REQ-081 ↑ Traces Up STKH-REQ-006 ↓ Traces Down IT-020 QT-001 SW-REQ-050 SW-REQ-051 SW-REQ-052 SW-REQ-120 UT-100 UT-101 , SYS-REQ-090 ↑ Traces Up STKH-REQ-005 STKH-REQ-006 ↓ Traces Down SW-REQ-040 , SYS-REQ-091 ↑ Traces Up STKH-REQ-006 ↓ Traces Down SW-REQ-041 , SYS-REQ-092 ↑ Traces Up STKH-REQ-006 ↓ Traces Down SW-REQ-042 , SYS-REQ-093 ↑ Traces Up STKH-REQ-006 ↓ Traces Down SW-REQ-043
STKH-REQ-007 ↓ Traces Down IT-002 IT-010 IT-036 SSR-001 SSR-040 SSR-041 SW-REQ-001 SW-REQ-003 +28 more	SYS-REQ-060 ↑ Traces Up STKH-REQ-007 STKH-REQ-014 ↓ Traces Down IT-001 IT-007 IT-010 QT-001 SW-REQ-060 SW-REQ-061 SW-REQ-068 SW-REQ-069 +11 more , SYS-REQ-061 ↑ Traces Up STKH-REQ-007 STKH-REQ-015 ↓ Traces Down IT-001 IT-013 QT-001 SW-REQ-091 SW-REQ-100 UT-051 , SYS-REQ-062 ↑ Traces Up STKH-REQ-007 STKH-REQ-016 ↓ Traces Down IT-002 IT-004 QT-001 QT-006 SSR-041 SW-REQ-095 SW-REQ-09B SW-REQ-101 +2 more , SYS-REQ-063 ↑ Traces Up STKH-REQ-007 STKH-REQ-017 ↓ Traces Down IT-001 IT-007 QT-006 SSR-040 SW-REQ-095 SW-REQ-09B SW-REQ-110 , SYS-REQ-064 ↑ Traces Up STKH-REQ-007 ↓ Traces Down SW-REQ-095 , SYS-REQ-066 ↑ Traces Up STKH-REQ-007 ↓ Traces Down SW-REQ-074 SW-REQ-095
STKH-REQ-008 ↓ Traces Down IT-011 IT-036 SSR-003 SW-REQ-010 SW-REQ-070 SW-REQ-071 SW-REQ-072 SW-REQ-073 +9 more	SYS-REQ-130 ↑ Traces Up STKH-REQ-008 ↓ Traces Down SW-REQ-070 , SYS-REQ-131 ↑ Traces Up STKH-REQ-008 ↓ Traces Down SW-REQ-071 , SYS-REQ-132 ↑ Traces Up STKH-REQ-008 ↓ Traces Down SW-REQ-074 , SYS-REQ-133 ↑ Traces Up STKH-REQ-008 ↓ Traces Down SW-REQ-073 , SYS-REQ-134 ↑ Traces Up STKH-REQ-008 ↓ Traces Down SW-REQ-072
STKH-REQ-009 ↓ Traces Down IT-036 SSR-005 SSR-020 SSR-030 SSR-031 SSR-032 SSR-033 SSR-042 +12 more	SYS-REQ-050 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-040 IT-060 QT-007 QT-010 QT-011 QT-012 QT-014 SSR-030 +3 more , SYS-REQ-051 ↑ Traces Up STKH-REQ-009 STKH-REQ-012 ↓ Traces Down IT-040 IT-042 QT-004 SSR-032 SW-REQ-030 SW-REQ-031 UT-001 UT-003 , SYS-REQ-052 ↑ Traces Up STKH-REQ-009 ↓ Traces Down IT-040 IT-041 QT-005 SSR-031 SW-REQ-030 SW-REQ-033 UT-004 , SYS-REQ-053 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-030 IT-039 QT-002 QT-003 QT-004 QT-005 QT-006 QT-007 +5 more
STKH-REQ-010 ↓ Traces Down SSR-006 SW-REQ-021 SW-REQ-034 SW-REQ-035 SYS-REQ-041 SYS-REQ-153 SYS-REQ-154 UT-024 +1 more	SYS-REQ-153 ↑ Traces Up STKH-REQ-010 ↓ Traces Down SW-REQ-034 , SYS-REQ-154 ↑ Traces Up STKH-REQ-010 ↓ Traces Down SW-REQ-035
STKH-REQ-011 ↓ Traces Down IT-050 SSR-020 SSR-021 SSR-030 SSR-032 SSR-033 SSR-042 SSR-050 +12 more	SYS-REQ-050 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-040 IT-060 QT-007 QT-010 QT-011 QT-012 QT-014 SSR-030 +3 more , SYS-REQ-053 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-030 IT-039 QT-002 QT-003 QT-004 QT-005 QT-006 QT-007 +5 more , SYS-REQ-054 ↑ Traces Up STKH-REQ-011 STKH-REQ-013 ↓ Traces Down IT-030 IT-050 IT-051 QT-002 QT-004 SSR-021 SW-REQ-044 SW-REQ-067 +2 more
STKH-REQ-012 ↓ Traces Down SSR-020 SSR-030 SSR-032 SSR-033 SSR-042 SW-REQ-030 SW-REQ-031 SW-REQ-032 +4 more	SYS-REQ-050 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-040 IT-060 QT-007 QT-010 QT-011 QT-012 QT-014 SSR-030 +3 more , SYS-REQ-053 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-030 IT-039 QT-002 QT-003 QT-004 QT-005 QT-006 QT-007 +5 more
STKH-REQ-013 ↓ Traces Down IT-050 SSR-007 SSR-021 SSR-022 SSR-023 SSR-024 SSR-050 SSR-052 +12 more	SYS-REQ-054 ↑ Traces Up STKH-REQ-011 STKH-REQ-013 ↓ Traces Down IT-030 IT-050 IT-051 QT-002 QT-004 SSR-021 SW-REQ-044 SW-REQ-067 +2 more , SYS-REQ-055 ↑ Traces Up STKH-REQ-013 ↓ Traces Down IT-025 QT-002 QT-003 QT-007 SSR-022 SSR-023 SSR-024 SW-REQ-045 +3 more
STKH-REQ-014 ↓ Traces Down IT-002 IT-010 SW-REQ-060 SW-REQ-061 SW-REQ-068 SW-REQ-069 SW-REQ-090 SW-REQ-093 +10 more	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-015 ↓ Traces Down IT-002 SW-REQ-091 SW-REQ-100 SW-REQ-129 SYS-REQ-061 SYS-REQ-150 UT-052	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-016 ↓ Traces Down SSR-041 SW-REQ-095 SW-REQ-101 SW-REQ-111 SW-REQ-129 SYS-REQ-062 SYS-REQ-150	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-017 ↓ Traces Down SSR-020 SSR-030 SSR-032 SSR-033 SSR-040 SSR-042 SW-REQ-030 SW-REQ-031 +7 more	SYS-REQ-050 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-040 IT-060 QT-007 QT-010 QT-011 QT-012 QT-014 SSR-030 +3 more , SYS-REQ-053 ↑ Traces Up STKH-REQ-009 STKH-REQ-011 STKH-REQ-012 STKH-REQ-017 ↓ Traces Down IT-030 IT-039 QT-002 QT-003 QT-004 QT-005 QT-006 QT-007 +5 more
STKH-REQ-018 ↓ Traces Down IT-002 SW-REQ-050 SW-REQ-053 SW-REQ-100 SW-REQ-129 SYS-REQ-070 SYS-REQ-150 UT-052	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-019 ↓ Traces Down IT-001 SW-REQ-040 SW-REQ-108 SW-REQ-129 SW-REQ-203 SYS-REQ-071 SYS-REQ-150 UT-030	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A
STKH-REQ-020 ↓ Traces Down SSR-051 SW-REQ-041 SW-REQ-109 SW-REQ-129 SYS-REQ-072 SYS-REQ-150 UT-030	SYS-REQ-150 ↑ Traces Up STKH-REQ-001 STKH-REQ-002 STKH-REQ-003 STKH-REQ-004 STKH-REQ-014 STKH-REQ-015 STKH-REQ-016 STKH-REQ-018 +2 more ↓ Traces Down SW-REQ-129 SW-REQ-12A

7. Acceptance Criteria

Each stakeholder requirement is considered fulfilled when:

The corresponding system requirement(s) are implemented
Test evidence demonstrates the requirement is met (test_smoke.py, test_integration.py, or test_asil.py)
The GAP-ANALYSIS.md entry (if any) is marked FIXED or ACCEPTED with documented rationale

← SUP.10 Change Request SYS.2 System Reqs →