3. Software Design Description
Defines the software architecture and low level requirements, that will satisfy high level requirements.
3.1. Overview
Detailed description of how the software requirements are allocated to processors and tasks
3.2. Architecture
Defines the software structure to achieve the high level requirements
3.3. Interface
Describes input and output interfaces
3.3.1. ARINC 429 label format
UID: |
REQ-A429 |
The IMU_AZ data is read from the data field in the Arinc word defined by:
Comment: Refer to Arinc 429 definition
3.3.2. Low level requirements
3.3.2.1. LLR title example
UID: |
LLR-001 |
The software component imu shall ….
Parents:
[HLR-001]HLR title example
3.3.3. Detailed design
3.4. Dataflow and Control flow
Describes dataflow and control flow between software components.
3.5. Resource limitations
For instance time and memory.
3.6. Scheduling
Describes threads attributes and synchronization.
3.7. Partitioning concerns
Describes partitioning design concerns.
3.8. Software components
Detailed description of software components defined in the architecture.
3.9. Derived requirements
To be analysed by safety analysis process.
3.9.1. Derived LLR example
UID: |
LLR-002 |
Derived LLR statement example.
Parents:
[DERIVED]Derived Requirement Placeholder
3.10. Deactivated code
Description of the means to deactivate some peace of the code.