36 KiB
36 KiB
| 1 | SWR_ID | Type | Status | Title | Description | SR_ID | Feature_ID | Component | Test_ID |
|---|---|---|---|---|---|---|---|---|---|
| 2 | SWR-SYS-002 | Software Requirement | Specified | FSM Transition Enforcement | The software SHALL enforce valid state transitions as defined in the System State Machine Specification. | SR-SYS-001 | F-SYS-01 | STM | T-SYS-002 |
| 3 | SWR-SYS-003 | Software Requirement | Specified | State-Based Operation Restriction | The software SHALL restrict feature operations based on the current system state according to per-state execution rules. | SR-SYS-002 | F-SYS-01 | STM | T-SYS-003 |
| 4 | SWR-SYS-004 | Software Requirement | Specified | State Transition Notification | The software SHALL notify all registered components when a state transition occurs via the Event System. | SR-SYS-003 | F-SYS-01 | STM, Event System | T-SYS-004 |
| 5 | SWR-SYS-006 | Software Requirement | Specified | Critical Data Persistence Before Teardown | The software SHALL persist all critical runtime data before completing a teardown sequence. | SR-SYS-005 | F-SYS-02 | STM, Persistence | T-SYS-006 |
| 6 | SWR-SYS-007 | Software Requirement | Specified | Data Integrity Protection During Shutdown | The software SHALL prevent data corruption during teardown and reset operations. | SR-SYS-006 | F-SYS-02 | STM, Persistence | T-SYS-007 |
| 7 | SWR-SYS-008 | Software Requirement | Specified | OLED Display Interface | The software SHALL provide a local OLED display interface using I2C communication protocol. | SR-SYS-007 | F-SYS-03 | HMI | T-SYS-008 |
| 8 | SWR-SYS-012 | Software Requirement | Specified | Diagnostic Session Support | The software SHALL support diagnostic sessions for retrieving system status and diagnostic data. | SR-SYS-011 | F-SYS-04 | Debug Session Manager | T-SYS-012 |
| 9 | SWR-SYS-013 | Software Requirement | Specified | Debug Session Support | The software SHALL support debug sessions allowing controlled engineering commands. | SR-SYS-012 | F-SYS-04 | Debug Session Manager | T-SYS-013 |
| 10 | SWR-SYS-014 | Software Requirement | Specified | Authorized Debug Access Control | The software SHALL restrict debug session actions to authorized engineering access only. | SR-SYS-013 | F-SYS-04 | Debug Session Manager, Security | T-SYS-014 |
| 11 | SWR-SYS-015 | Software Requirement | Specified | Non-Intrusive Debug Sessions | The software SHALL ensure debug sessions do not interfere with normal sensor acquisition or communication operations. | SR-SYS-013 | F-SYS-04 | Debug Session Manager | T-SYS-015 |
| 12 | SWR-DAQ-002 | Software Requirement | Specified | Dedicated Sensor Slot Mapping | The software SHALL assign each supported sensor type to a predefined and unique hardware slot. | SR-DAQ-002 | F-DAQ-01 | Sensor Manager | T-DAQ-002 |
| 13 | SWR-DAQ-003 | Software Requirement | Specified | Sensor Presence Detection | The software SHALL detect the physical presence of each sensor via a dedicated hardware detection signal prior to sensor initialization. | SR-DAQ-003 | F-DAQ-01 | Sensor Manager, Sensor Drivers | T-DAQ-003 |
| 14 | SWR-DAQ-004 | Software Requirement | Specified | Conditional Sensor Initialization | The software SHALL initialize and activate only sensors that are detected as present and enabled. | SR-DAQ-004 | F-DAQ-01 | Sensor Manager | T-DAQ-004 |
| 15 | SWR-DAQ-005 | Software Requirement | Specified | High-Frequency Sensor Sampling | The software SHALL sample each enabled sensor multiple times within a single acquisition cycle (default: 10 samples per sensor per cycle). | SR-DAQ-005 | F-DAQ-02 | Sensor Manager | T-DAQ-005 |
| 16 | SWR-DAQ-006 | Software Requirement | Specified | Local Sensor Data Filtering | The software SHALL apply a local filtering mechanism to raw sensor samples to produce a single filtered sensor value per acquisition cycle. | SR-DAQ-006 | F-DAQ-02 | Sensor Manager | T-DAQ-006 |
| 17 | SWR-DAQ-007 | Software Requirement | Specified | Deterministic Sampling Window | The software SHALL complete each sensor's sampling and filtering process within a bounded and deterministic time window (maximum 100ms per sensor). | SR-DAQ-007 | F-DAQ-02 | Sensor Manager | T-DAQ-007 |
| 18 | SWR-DAQ-008 | Software Requirement | Specified | Timestamp Generation for Sensor Data | The software SHALL generate a timestamp for each filtered sensor value upon completion of the acquisition and filtering process. | SR-DAQ-008 | F-DAQ-03 | Sensor Manager, Time Utils | T-DAQ-008 |
| 19 | SWR-DAQ-010 | Software Requirement | Specified | Availability of Latest Sensor Data | The software SHALL maintain the most recent timestamped sensor data record in memory and make it available for persistence and on-demand communication requests. | SR-DAQ-010 | F-DAQ-03 | Sensor Manager, Data Pool | T-DAQ-010 |
| 20 | SWR-DAQ-012 | Software Requirement | Specified | Non-Blocking Sensor Acquisition | The software SHALL perform sensor acquisition in a non-blocking manner. | CFC-TIME-01 | F-DAQ-02 | Sensor Manager | T-DAQ-012 |
| 21 | SWR-DAQ-013 | Software Requirement | Specified | Deterministic Memory Allocation | The software SHALL use deterministic memory allocation for sensor acquisition buffers (no dynamic allocation in acquisition path). | CFC-TIME-02 | F-DAQ-02 | Sensor Manager | T-DAQ-013 |
| 22 | SWR-DAQ-014 | Software Requirement | Specified | Sensor Data Event Publishing | The software SHALL publish sensor data updates via the Event System upon completion of each acquisition cycle. | Architecture Requirement | F-DAQ-03 | Sensor Manager, Event System | T-DAQ-014 |
| 23 | SWR-DAQ-015 | Software Requirement | Specified | Failed Sensor Exclusion | The software SHALL exclude failed sensors from acquisition cycles as defined by the failure handling model. | SR-DQC-009 | F-DAQ-01 | Sensor Manager | T-DAQ-015 |
| 24 | SWR-DQC-001 | Software Requirement | Specified | Detect Sensor Presence | The software SHALL detect the physical presence of each sensor using a dedicated hardware-based detection mechanism. | SR-DQC-001 | F-DQC-01 | Sensor Manager, Sensor Drivers | T-DQC-001 |
| 25 | SWR-DQC-002 | Software Requirement | Specified | Perform Sensor Detection During Initialization | The software SHALL perform sensor presence detection during system startup and after any reinitialization or reconfiguration event. | SR-DQC-002 | F-DQC-01 | Sensor Manager | T-DQC-002 |
| 26 | SWR-DQC-003 | Software Requirement | Specified | Conditional Sensor Initialization | The software SHALL initialize and activate only sensors that are detected as present. | SR-DQC-003 | F-DQC-01 | Sensor Manager | T-DQC-003 |
| 27 | SWR-DQC-004 | Software Requirement | Specified | Assign Fixed Sensor Slot Types | The software SHALL assign each physical sensor slot to a predefined sensor type. | SR-DQC-004 | F-DQC-02 | Sensor Manager | T-DQC-004 |
| 28 | SWR-DQC-005 | Software Requirement | Specified | Verify Sensor Type Compatibility | The software SHALL verify that a detected sensor matches the expected sensor type for its assigned slot. | SR-DQC-005 | F-DQC-02 | Sensor Manager | T-DQC-005 |
| 29 | SWR-DQC-006 | Software Requirement | Specified | Reject Invalid Sensor Configurations | The software SHALL reject and report any sensor-slot mismatch as a diagnostic event. | SR-DQC-006 | F-DQC-02 | Sensor Manager, Diagnostics | T-DQC-006 |
| 30 | SWR-DQC-007 | Software Requirement | Specified | Monitor Sensor Health | The software SHALL continuously monitor sensor responsiveness and signal validity during normal operation. | SR-DQC-007 | F-DQC-03 | Sensor Manager | T-DQC-007 |
| 31 | SWR-DQC-009 | Software Requirement | Specified | Isolate Failed Sensors | The software SHALL mark detected faulty sensors as defective and exclude them from data acquisition and reporting. | SR-DQC-009 | F-DQC-03 | Sensor Manager | T-DQC-009 |
| 32 | SWR-DQC-010 | Software Requirement | Specified | Report Sensor Failures | The software SHALL report detected sensor failures to the Main Hub with timestamps and failure classification. | SR-DQC-010 | F-DQC-03 | Sensor Manager, Communication | T-DQC-010 |
| 33 | SWR-DQC-012 | Software Requirement | Specified | Persist Machine Constants | The software SHALL store the Machine Constants dataset in non-volatile storage. | SR-DQC-012 | F-DQC-04 | Machine Constant Manager, Persistence | T-DQC-012 |
| 34 | SWR-DQC-013 | Software Requirement | Specified | Load Machine Constants at Startup | The software SHALL load and apply the Machine Constants dataset during system initialization. | SR-DQC-013 | F-DQC-04 | Machine Constant Manager | T-DQC-013 |
| 35 | SWR-DQC-014 | Software Requirement | Specified | Support Remote Machine Constants Update | The software SHALL support remote updates of the Machine Constants dataset initiated by the Main Hub. | SR-DQC-014 | F-DQC-04 | Machine Constant Manager, Communication | T-DQC-014 |
| 36 | SWR-DQC-015 | Software Requirement | Specified | Controlled Reinitialization After Update | The software SHALL apply updated Machine Constants only after executing a controlled teardown and reinitialization procedure. | SR-DQC-015 | F-DQC-04 | Machine Constant Manager, STM | T-DQC-015 |
| 37 | SWR-DQC-016 | Software Requirement | Specified | Machine Constants Integrity Validation | The software SHALL validate Machine Constants integrity before applying updates. | SR-SEC-008 | F-DQC-04 | Machine Constant Manager, Security | T-DQC-016 |
| 38 | SWR-DQC-018 | Software Requirement | Specified | Machine Constants Access via DP | The software SHALL access Machine Constants only through the DP component. | CFC-ARCH-01 | F-DQC-04 | Machine Constant Manager, Persistence | T-DQC-018 |
| 39 | SWR-COM-001 | Software Requirement | Specified | Bidirectional Main Hub Communication | The software SHALL support bidirectional communication between the Sensor Hub and the Main Hub. | SR-COM-001 | F-COM-01 | Main Hub APIs, Network Stack | T-COM-001 |
| 40 | SWR-COM-004 | Software Requirement | Specified | Monitor Communication Link Status | The software SHALL monitor the status of the communication link with the Main Hub and report link availability and failure conditions. | SR-COM-004 | F-COM-01 | Network Stack | T-COM-004 |
| 41 | SWR-COM-005 | Software Requirement | Specified | Support On-Demand Data Requests | The software SHALL support on-demand requests from the Main Hub for sensor data. | SR-COM-005 | F-COM-02 | Main Hub APIs | T-COM-005 |
| 42 | SWR-COM-006 | Software Requirement | Specified | Respond with Latest Sensor Data | The software SHALL respond to on-demand data requests with the most recent timestamped sensor data. | SR-COM-006 | F-COM-02 | Main Hub APIs, Data Pool | T-COM-006 |
| 43 | SWR-COM-007 | Software Requirement | Specified | Include Data Validity in Responses | The software SHALL include sensor status and data validity information in on-demand data responses. | SR-COM-007 | F-COM-02 | Main Hub APIs | T-COM-007 |
| 44 | SWR-COM-008 | Software Requirement | Specified | Support Peer Sensor Hub Communication | The software SHALL support limited peer-to-peer communication between Sensor Hubs for connectivity checks and time synchronization. | SR-COM-008 | F-COM-03 | Network Stack | T-COM-008 |
| 45 | SWR-COM-009 | Software Requirement | Specified | Isolate Peer Communication | The software SHALL ensure that peer Sensor Hub communication does not interfere with Main Hub communication or control operations. | SR-COM-010 | F-COM-03 | Network Stack | T-COM-009 |
| 46 | SWR-COM-010 | Software Requirement | Specified | Encrypted Main Hub Communication | The software SHALL encrypt all communication with the Main Hub using authenticated encryption. | SR-SEC-009 | F-COM-01 | Network Stack, Security | T-COM-010 |
| 47 | SWR-COM-011 | Software Requirement | Specified | Message Integrity and Authenticity | The software SHALL ensure integrity and authenticity of all transmitted and received messages. | SR-SEC-010 | F-COM-01 | Network Stack, Security | T-COM-011 |
| 48 | SWR-COM-012 | Software Requirement | Specified | State-Restricted Communication | The software SHALL limit communication operations during TEARDOWN state to session closure only. | CFC-ARCH-02 | F-COM-01 | Network Stack | T-COM-012 |
| 49 | SWR-COM-013 | Software Requirement | Specified | Non-Blocking Communication | The software SHALL perform communication operations in a non-blocking manner. | CFC-TIME-01 | F-COM-01 | Network Stack | T-COM-013 |
| 50 | SWR-COM-014 | Software Requirement | Specified | Communication Link Failure Reporting | The software SHALL report communication link failures as diagnostic events according to the failure handling model. | SR-COM-004 | F-COM-01 | Network Stack, Diagnostics | T-COM-014 |
| 51 | SWR-COM-015 | Software Requirement | Specified | Security Violation Reporting | The software SHALL detect and report communication security violations to the Main Hub. | SR-SEC-012 | F-COM-01 | Network Stack, Security | T-COM-015 |
| 52 | SWR-DIAG-002 | Software Requirement | Specified | Assign Unique Diagnostic Codes | The software SHALL assign a unique diagnostic code to each detected fault or abnormal condition. | SR-DIAG-002 | F-DIAG-01 | Diagnostics Task | T-DIAG-002 |
| 53 | SWR-DIAG-004 | Software Requirement | Specified | Timestamp and Source Diagnostics | The software SHALL associate each diagnostic event with a timestamp and the originating system component. | SR-DIAG-004 | F-DIAG-01 | Diagnostics Task | T-DIAG-004 |
| 54 | SWR-DIAG-005 | Software Requirement | Specified | Persist Diagnostic Events | The software SHALL persist diagnostic events in non-volatile storage. | SR-DIAG-005 | F-DIAG-02 | Diagnostics Task, Persistence | T-DIAG-005 |
| 55 | SWR-DIAG-006 | Software Requirement | Specified | Retain Diagnostics Across Resets | The software SHALL retain diagnostic data across system resets and power cycles. | SR-DIAG-006 | F-DIAG-02 | Diagnostics Task, Persistence | T-DIAG-006 |
| 56 | SWR-DIAG-007 | Software Requirement | Specified | Bounded Diagnostic Storage | The software SHALL implement a bounded diagnostic storage mechanism with a defined overwrite or rollover policy. | SR-DIAG-007 | F-DIAG-02 | Diagnostics Task, Persistence | T-DIAG-007 |
| 57 | SWR-DIAG-008 | Software Requirement | Specified | Provide Diagnostic Session Interface | The software SHALL provide a diagnostic session interface for accessing diagnostic and system health data. | SR-DIAG-008 | F-DIAG-03 | Diagnostics Task | T-DIAG-008 |
| 58 | SWR-DIAG-009 | Software Requirement | Specified | Retrieve Diagnostic Records | The software SHALL allow authorized diagnostic sessions to retrieve stored diagnostic events. | SR-DIAG-009 | F-DIAG-03 | Diagnostics Task | T-DIAG-009 |
| 59 | SWR-DIAG-010 | Software Requirement | Specified | Clear Diagnostic Records | The software SHALL allow authorized diagnostic sessions to clear stored diagnostic records. | SR-DIAG-010 | F-DIAG-03 | Diagnostics Task | T-DIAG-010 |
| 60 | SWR-DIAG-011 | Software Requirement | Specified | Non-Intrusive Diagnostic Sessions | The software SHALL ensure that diagnostic sessions do not interfere with normal sensor acquisition or communication operations. | SR-DIAG-011 | F-DIAG-03 | Diagnostics Task | T-DIAG-011 |
| 61 | SWR-DIAG-012 | Software Requirement | Specified | Fault-to-State Transition | The software SHALL trigger state transitions based on diagnostic severity according to the failure handling model. | Failure Handling Model | F-DIAG-01 | Diagnostics Task, Error Handler | T-DIAG-012 |
| 62 | SWR-DIAG-013 | Software Requirement | Specified | Fault Latching Behavior | The software SHALL implement fault latching behavior as defined in the failure handling model. | Failure Handling Model | F-DIAG-01 | Error Handler | T-DIAG-013 |
| 63 | SWR-DIAG-014 | Software Requirement | Specified | Fault Escalation Rules | The software SHALL implement fault escalation rules as defined in the failure handling model. | Failure Handling Model | F-DIAG-01 | Error Handler | T-DIAG-014 |
| 64 | SWR-DIAG-016 | Software Requirement | Specified | Diagnostic Information via HMI | The software SHALL provide diagnostic information through the local OLED menu interface. | SR-SYS-010 | F-DIAG-03 | Diagnostics Task, HMI | T-DIAG-016 |
| 65 | SWR-DIAG-017 | Software Requirement | Specified | Diagnostic Storage Access via DP | The software SHALL access diagnostic storage only through the DP component. | CFC-ARCH-01 | F-DIAG-02 | Diagnostics Task, Persistence | T-DIAG-017 |
| 66 | SWR-DIAG-018 | Software Requirement | Specified | State-Restricted Diagnostic Generation | The software SHALL NOT generate new diagnostic events during TEARDOWN state (except teardown-specific diagnostics). | CFC-ARCH-02 | F-DIAG-01 | Diagnostics Task | T-DIAG-018 |
| 67 | SWR-DATA-001 | Software Requirement | Specified | Persistent Timestamped Sensor Data | The software SHALL persist timestamped sensor data in non-volatile storage. | SR-DATA-001 | F-DATA-01 | Persistence | T-DATA-001 |
| 68 | SWR-DATA-003 | Software Requirement | Specified | Configurable Data Retention Policy | The software SHALL support configurable data retention and overwrite policies for persisted sensor data. | SR-DATA-003 | F-DATA-01 | Persistence | T-DATA-003 |
| 69 | SWR-DATA-004 | Software Requirement | Specified | Data Persistence Component Interface | The software SHALL provide a Data Persistence (DP) component as the sole interface for persistent data access. | SR-DATA-004 | F-DATA-02 | Persistence | T-DATA-004 |
| 70 | SWR-DATA-005 | Software Requirement | Specified | Storage Access Isolation | The software SHALL prevent application and feature modules from directly accessing storage hardware. | SR-DATA-005 | F-DATA-02 | Persistence | T-DATA-005 |
| 71 | SWR-DATA-006 | Software Requirement | Specified | Structured Data Serialization | The DP component SHALL support serialization and deserialization of structured system data. | SR-DATA-006 | F-DATA-02 | Persistence | T-DATA-006 |
| 72 | SWR-DATA-007 | Software Requirement | Specified | Data Flush Before Teardown | The software SHALL flush all critical runtime data to non-volatile storage before entering a controlled teardown or reset state. | SR-DATA-007 | F-DATA-03 | Persistence, STM | T-DATA-007 |
| 73 | SWR-DATA-008 | Software Requirement | Specified | Data Integrity During Updates | The software SHALL protect data integrity during firmware updates and machine constant updates. | SR-DATA-008 | F-DATA-03 | Persistence, OTA Manager | T-DATA-008 |
| 74 | SWR-DATA-009 | Software Requirement | Specified | Persistence Verification | The software SHALL verify successful data persistence before completing a system state transition. | SR-DATA-009 | F-DATA-03 | Persistence, STM | T-DATA-009 |
| 75 | SWR-DATA-010 | Software Requirement | Specified | State-Restricted Data Writes | The software SHALL NOT perform data write operations during TEARDOWN state unless explicitly authorized by the System Manager. | CFC-DATA-02 | F-DATA-03 | Persistence | T-DATA-010 |
| 76 | SWR-DATA-011 | Software Requirement | Specified | Persistence Completion Confirmation | The software SHALL ensure persistence completion is confirmed before state transitions. | CFC-DATA-02 | F-DATA-03 | Persistence, STM | T-DATA-011 |
| 77 | SWR-DATA-012 | Software Requirement | Specified | SD Card Failure Handling | The software SHALL handle SD card failures gracefully by entering SD_DEGRADED state and disabling persistence writes. | System State Machine Specification | F-DATA-01 | Persistence, STM | T-DATA-012 |
| 78 | SWR-DATA-013 | Software Requirement | Specified | Wear-Aware Storage Management | The software SHALL implement wear-aware storage management to prevent premature SD card failure. | Quality Requirement | F-DATA-01 | Persistence | T-DATA-013 |
| 79 | SWR-DATA-014 | Software Requirement | Specified | Single Source of Truth | The software SHALL maintain a single source of truth for runtime and persistent data through the DP component. | CFC-DATA-01 | F-DATA-02 | Data Pool, Persistence | T-DATA-014 |
| 80 | SWR-DATA-015 | Software Requirement | Specified | No Private Persistent Copies | The software SHALL NOT allow features to maintain private persistent copies of shared system data. | CFC-DATA-01 | F-DATA-02 | All Components | T-DATA-015 |
| 81 | SWR-OTA-001 | Software Requirement | Specified | OTA Negotiation Support | The software SHALL support OTA update negotiation initiated by the Main Hub. | SR-OTA-001 | F-OTA-01 | OTA Manager | T-OTA-001 |
| 82 | SWR-OTA-002 | Software Requirement | Specified | OTA Readiness Validation | The software SHALL verify internal readiness conditions before accepting an OTA update request. | SR-OTA-002 | F-OTA-01 | OTA Manager | T-OTA-002 |
| 83 | SWR-OTA-003 | Software Requirement | Specified | OTA Acknowledgement | The software SHALL explicitly acknowledge or reject OTA update requests. | SR-OTA-003 | F-OTA-01 | OTA Manager | T-OTA-003 |
| 84 | SWR-OTA-004 | Software Requirement | Specified | Firmware Reception | The software SHALL receive firmware images over the established communication interface. | SR-OTA-004 | F-OTA-02 | OTA Manager, Network Stack | T-OTA-004 |
| 85 | SWR-OTA-005 | Software Requirement | Specified | Firmware Temporary Storage | The software SHALL store received firmware images in non-volatile storage prior to validation. | SR-OTA-005 | F-OTA-02 | OTA Manager, Persistence | T-OTA-005 |
| 86 | SWR-OTA-006 | Software Requirement | Specified | Active Firmware Protection | The software SHALL prevent overwriting the active firmware during firmware reception. | SR-OTA-006 | F-OTA-02 | OTA Manager | T-OTA-006 |
| 87 | SWR-OTA-007 | Software Requirement | Specified | Firmware Integrity Verification | The software SHALL validate the integrity of received firmware images before activation. | SR-OTA-007 | F-OTA-03 | OTA Manager, Security | T-OTA-007 |
| 88 | SWR-OTA-008 | Software Requirement | Specified | Firmware Rejection Handling | The software SHALL reject firmware images that fail integrity validation. | SR-OTA-008 | F-OTA-03 | OTA Manager | T-OTA-008 |
| 89 | SWR-OTA-009 | Software Requirement | Specified | OTA Status Reporting | The software SHALL report firmware validation and OTA status to the Main Hub. | SR-OTA-009 | F-OTA-03 | OTA Manager, Communication | T-OTA-009 |
| 90 | SWR-OTA-010 | Software Requirement | Specified | OTA Teardown Execution | The software SHALL execute a controlled teardown procedure prior to firmware activation. | SR-OTA-010 | F-OTA-04 | OTA Manager, STM | T-OTA-010 |
| 91 | SWR-OTA-011 | Software Requirement | Specified | Data Persistence Before Flashing | The software SHALL persist critical runtime data and calibration data before flashing new firmware. | SR-OTA-011 | F-OTA-04 | OTA Manager, Persistence | T-OTA-011 |
| 92 | SWR-OTA-012 | Software Requirement | Specified | Controlled Firmware Activation | The software SHALL activate new firmware only after successful integrity validation. | SR-OTA-012 | F-OTA-04 | OTA Manager | T-OTA-012 |
| 93 | SWR-OTA-013 | Software Requirement | Specified | OTA Reboot Execution | The software SHALL reboot into the new firmware after successful activation. | SR-OTA-013 | F-OTA-04 | OTA Manager | T-OTA-013 |
| 94 | SWR-OTA-014 | Software Requirement | Specified | Encrypted OTA Communication | The software SHALL use encrypted and authenticated communication channels for OTA firmware updates. | SR-SEC-011 | F-OTA-02 | OTA Manager, Security | T-OTA-014 |
| 95 | SWR-OTA-015 | Software Requirement | Specified | OTA State Transition | The software SHALL transition to OTA_PREP state upon accepting an OTA request. | System State Machine Specification | F-OTA-01 | OTA Manager, STM | T-OTA-015 |
| 96 | SWR-OTA-017 | Software Requirement | Specified | OTA Duration Limit | The software SHALL complete OTA operations within a maximum duration of 10 minutes. | Quality Requirement | F-OTA-04 | OTA Manager | T-OTA-017 |
| 97 | SWR-OTA-018 | Software Requirement | Specified | OTA Failure Handling | The software SHALL handle OTA failures by transitioning to FAULT state and reporting the failure. | System State Machine Specification | F-OTA-04 | OTA Manager, STM | T-OTA-018 |
| 98 | SWR-OTA-019 | Software Requirement | Specified | Active Firmware Corruption Protection | The software SHALL protect active firmware from corruption during OTA operations. | SR-OTA-006 | F-OTA-02 | OTA Manager | T-OTA-019 |
| 99 | SWR-OTA-020 | Software Requirement | Specified | Firmware Authenticity Verification | The software SHALL verify firmware authenticity using secure boot mechanisms before execution. | SR-SEC-001 | F-OTA-04 | OTA Manager, Security | T-OTA-020 |
| 100 | SWR-SEC-001 | Software Requirement | Specified | Firmware Authenticity Verification | The software SHALL verify the authenticity of the firmware image before execution during every boot cycle. | SR-SEC-001 | F-SEC-01 | Security | T-SEC-001 |
| 101 | SWR-SEC-002 | Software Requirement | Specified | Unauthorized Firmware Blocking | The software SHALL prevent execution of firmware images that fail cryptographic verification. | SR-SEC-002 | F-SEC-01 | Security | T-SEC-002 |
| 102 | SWR-SEC-003 | Software Requirement | Specified | Secure Boot Failure Handling | The software SHALL enter BOOT_FAILURE state when secure boot verification fails. | SR-SEC-003 | F-SEC-01 | Security, STM | T-SEC-003 |
| 103 | SWR-SEC-004 | Software Requirement | Specified | Root-of-Trust Protection | The software SHALL protect the root-of-trust against unauthorized modification. | SR-SEC-004 | F-SEC-01 | Security | T-SEC-004 |
| 104 | SWR-SEC-005 | Software Requirement | Specified | Flash Data Access Protection | The software SHALL protect sensitive data stored in internal flash memory from unauthorized access. | SR-SEC-005 | F-SEC-02 | Security | T-SEC-005 |
| 105 | SWR-SEC-006 | Software Requirement | Specified | Encrypted External Storage | The software SHALL support encryption of sensitive data stored in external storage devices. | SR-SEC-006 | F-SEC-02 | Security, Persistence | T-SEC-006 |
| 106 | SWR-SEC-007 | Software Requirement | Specified | Cryptographic Key Isolation | The software SHALL restrict access to cryptographic keys to authorized system components only. | SR-SEC-007 | F-SEC-02 | Security | T-SEC-007 |
| 107 | SWR-SEC-009 | Software Requirement | Specified | Encrypted Main Hub Communication | The software SHALL encrypt all communication with the Main Hub. | SR-SEC-009 | F-SEC-03 | Network Stack, Security | T-SEC-009 |
| 108 | SWR-SEC-010 | Software Requirement | Specified | Message Integrity and Authenticity | The software SHALL ensure integrity and authenticity of all transmitted and received messages. | SR-SEC-010 | F-SEC-03 | Network Stack, Security | T-SEC-010 |
| 109 | SWR-SEC-011 | Software Requirement | Specified | Secure OTA Data Transfer | The software SHALL use encrypted and authenticated communication channels for OTA firmware updates. | SR-SEC-011 | F-SEC-03 | OTA Manager, Security | T-SEC-011 |
| 110 | SWR-SEC-012 | Software Requirement | Specified | Security Violation Reporting | The software SHALL detect and report communication and security violations to the Main Hub. | SR-SEC-012 | F-SEC-03 | Security, Communication | T-SEC-012 |
| 111 | SWR-SEC-013 | Software Requirement | Specified | Security First Initialization | The software SHALL enable secure boot and flash protection before any application-level logic executes. | CFC-SEC-01 | F-SEC-01 | Security | T-SEC-013 |
| 112 | SWR-SEC-014 | Software Requirement | Specified | Debug Session Authentication | The software SHALL authenticate debug sessions before allowing debug operations. | SR-SYS-013 | F-SEC-03 | Security, Debug Session Manager | T-SEC-014 |
| 113 | SWR-SEC-015 | Software Requirement | Specified | Debug Security Bypass Prevention | The software SHALL NOT allow debug sessions to bypass security or safety mechanisms. | CFC-DBG-01 | F-SEC-03 | Security, Debug Session Manager | T-SEC-015 |
| 114 | SWR-SEC-016 | Software Requirement | Specified | Security Violation Diagnostic Reporting | The software SHALL report security violations as FATAL diagnostic events. | Failure Handling Model | F-SEC-01 | Security, Diagnostics | T-SEC-016 |
| 115 | SWR-SEC-017 | Software Requirement | Specified | Cryptographic Key Protection | The software SHALL protect cryptographic keys during power loss and system resets. | Quality Requirement | F-SEC-02 | Security | T-SEC-017 |
| 116 | SWR-SEC-018 | Software Requirement | Specified | Secure Session Establishment | The software SHALL implement secure session establishment for all external communication. | SR-SEC-009 | F-SEC-03 | Network Stack, Security | T-SEC-018 |
| 117 | SWR-SEC-019 | Software Requirement | Specified | Message Integrity Validation | The software SHALL validate message integrity on every received message. | SR-SEC-010 | F-SEC-03 | Network Stack, Security | T-SEC-019 |
| 118 | SWR-SEC-020 | Software Requirement | Specified | Downgrade Attack Prevention | The software SHALL prevent downgrade attacks by verifying firmware version integrity. | Quality Requirement | F-SEC-01 | Security, OTA Manager | T-SEC-020 |
| 119 | SWR-IF-001 | Software Requirement | Specified | Main Hub Communication Interface | The software SHALL provide a communication interface to the Main Hub supporting bidirectional data exchange. | SR-COM-001 | F-COM-01 | Main Hub APIs, Network Stack | T-IF-001 |
| 120 | SWR-IF-003 | Software Requirement | Specified | OLED Display Interface | The software SHALL provide an I2C interface for OLED display communication. | SR-SYS-007 | F-SYS-03 | HMI | T-IF-003 |
| 121 | SWR-IF-005 | Software Requirement | Specified | Storage Interfaces | The software SHALL provide storage interfaces for SD card and NVM access. | Architecture Requirement | F-DATA-01 | SD Card Driver, NVM Driver | T-IF-005 |
| 122 | SWR-IF-006 | Software Requirement | Specified | Debug Interface | The software SHALL provide a debug interface (UART/USB) for diagnostic and debug sessions. | SR-SYS-011 | F-SYS-04 | Debug Session Manager, UART Driver | T-IF-006 |
| 123 | SWR-IF-007 | Software Requirement | Specified | Event System Interface | The software SHALL provide an Event System interface for cross-component communication. | Architecture Requirement | All Features | Event System | T-IF-007 |
| 124 | SWR-IF-008 | Software Requirement | Specified | Data Pool Interface | The software SHALL provide a Data Pool interface for runtime data access. | Architecture Requirement | All Features | Data Pool | T-IF-008 |
| 125 | SWR-IF-009 | Software Requirement | Specified | Data Persistence Interface | The software SHALL provide a Data Persistence (DP) component interface for persistent storage access. | SR-DATA-004 | F-DATA-02 | Persistence | T-IF-009 |
| 126 | SWR-IF-010 | Software Requirement | Specified | System State Manager Interface | The software SHALL provide a System State Manager interface for state queries and transitions. | SR-SYS-001 | F-SYS-01 | STM | T-IF-010 |
| 127 | SWR-IF-011 | Software Requirement | Specified | Diagnostics Interface | The software SHALL provide a Diagnostics interface for fault reporting and querying. | SR-DIAG-001 | F-DIAG-01 | Diagnostics Task | T-IF-011 |
| 128 | SWR-IF-012 | Software Requirement | Specified | Error Handler Interface | The software SHALL provide an Error Handler interface for fault classification and escalation. | Failure Handling Model | All Features | Error Handler | T-IF-012 |
| 129 | SWR-PERF-001 | Software Requirement | Specified | Sensor Acquisition Cycle Timing | The software SHALL complete sensor acquisition cycles within 100ms per sensor. | SR-DAQ-007 | Sensor Acquisition | Sensor Manager | T-PERF-001 |
| 130 | SWR-PERF-003 | Software Requirement | Specified | Data Persistence Timing | The software SHALL complete data persistence operations within 200ms. | Quality Requirement | Data Persistence | Persistence | T-PERF-003 |
| 131 | SWR-PERF-004 | Software Requirement | Specified | OTA Operation Duration | The software SHALL complete OTA operations within 10 minutes. | SWR-OTA-017 | Firmware Update | OTA Manager | T-PERF-004 |
| 132 | SWR-PERF-005 | Software Requirement | Specified | CPU Utilization Limit | The software SHALL maintain CPU utilization below 80% during normal operation. | Quality Requirement | System Performance | All Components | T-PERF-005 |
| 133 | SWR-PERF-006 | Software Requirement | Specified | RAM Usage Limit | The software SHALL maintain RAM usage below 60% of available memory. | Quality Requirement | System Performance | All Components | T-PERF-006 |
| 134 | SWR-PERF-007 | Software Requirement | Specified | Main Hub Response Time | The software SHALL respond to Main Hub data requests within 100ms. | SR-COM-005 | Communication | Main Hub APIs, Data Pool | T-PERF-007 |
| 135 | SWR-PERF-008 | Software Requirement | Specified | Communication Link Failure Detection | The software SHALL detect communication link failures within 30 seconds. | SR-COM-004 | Communication | Network Stack | T-PERF-008 |
| 136 | SWR-DESIGN-001 | Software Requirement | Specified | No Dynamic Memory in Acquisition Path | The software SHALL NOT use dynamic memory allocation in sensor acquisition paths. | CFC-TIME-02 | Sensor Acquisition | Sensor Manager | T-DESIGN-001 |
| 137 | SWR-DESIGN-002 | Software Requirement | Specified | Non-Blocking Operations | The software SHALL implement all features as non-blocking operations. | CFC-TIME-01 | All Features | All Components | T-DESIGN-002 |
| 138 | SWR-DESIGN-003 | Software Requirement | Specified | Hardware Access via Drivers | The software SHALL access hardware only through driver and OSAL layers. | CFC-ARCH-01 | All Features | All Components | T-DESIGN-003 |
| 139 | SWR-DESIGN-004 | Software Requirement | Specified | Storage Access via DP | The software SHALL access persistent storage only through the DP component. | CFC-ARCH-01 | All Features | All Components | T-DESIGN-004 |
| 140 | SWR-DESIGN-005 | Software Requirement | Specified | State-Aware Operations | The software SHALL respect system state restrictions for all operations. | CFC-ARCH-02 | All Features | All Components | T-DESIGN-005 |
| 141 | SWR-DESIGN-006 | Software Requirement | Specified | Event System Communication | The software SHALL use the Event System for all cross-component communication. | Architecture Requirement | All Features | All Components | T-DESIGN-006 |
| 142 | SWR-QUAL-001 | Software Requirement | Specified | Power Interruption Recovery | The software SHALL recover gracefully from power interruptions (< 1 second). | System Assumptions | System Reliability | All Components | T-QUAL-001 |
| 143 | SWR-QUAL-002 | Software Requirement | Specified | SD Card Failure Handling | The software SHALL handle SD card failures without system failure. | System Limitations | Data Persistence | Persistence, STM | T-QUAL-002 |
| 144 | SWR-QUAL-003 | Software Requirement | Specified | Data Integrity During Updates | The software SHALL maintain data integrity during firmware updates. | SR-DATA-008 | Data Integrity | OTA Manager, Persistence | T-QUAL-003 |
| 145 | SWR-QUAL-004 | Software Requirement | Specified | Unauthorized Firmware Prevention | The software SHALL prevent unauthorized firmware execution. | SR-SEC-001 | Security | Security, OTA Manager | T-QUAL-004 |
| 146 | SWR-QUAL-005 | Software Requirement | Specified | Deterministic Behavior | The software SHALL provide deterministic behavior under all operational conditions. | CFC-TIME-02 | System Reliability | All Components | T-QUAL-005 |