Module Template Documentation#
<Brief description of the module and the implemented feature(s).>
<Further documentation of the module and the implemented feature(s) should be added in the respective sections of the documentation (e.g., feature architecture, safety analysis, security analysis, manuals, etc.) following the provided templates and guidelines.>
Feature Documentation#
The Feature documentation covers the feature-level definition of <module name>, including architecture and safety planning artifacts.
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
[Feature Name] Architecture |
ASIL_B |
NO |
draft |
|
[Feature Name] Architecture Inspection |
ASIL_B |
YES |
draft |
|
[Feature Name] DFA |
ASIL_B |
NO |
draft |
|
[Feature Name] Feature AoU |
ASIL_B |
NO |
draft |
|
[Feature Name] Feature Security AoU |
QM |
YES |
draft |
|
[Feature Name] FMEA |
ASIL_B |
NO |
draft |
|
[Feature Name] Safety WPs |
ASIL_B |
NO |
draft |
|
[Feature Name] Security WPs |
ASIL_B |
YES |
draft |
Module Documentation#
The Module documentation covers the module-level view, including architecture, safety management documents, and the user manual.
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
[Module Name] Release Note |
ASIL_B |
NO |
draft |
|
[Module Name] Safety Analysis Checklist |
ASIL_B |
YES |
draft |
|
[Module Name] Safety Manual |
ASIL_B |
NO |
draft |
|
[Module Name] Safety Package Formal Review |
ASIL_B |
NO |
draft |
|
[Module Name] Safety Plan |
ASIL_B |
NO |
draft |
|
[Module Name] Safety Plan Formal Review |
ASIL_B |
NO |
draft |
|
[Module Name] Security Manual |
ASIL_B |
YES |
draft |
|
[Module Name] Security Package Formal Review |
ASIL_B |
YES |
draft |
|
[Module Name] Security Plan |
ASIL_B |
YES |
draft |
|
[Module Name] Security Plan Formal Review |
ASIL_B |
YES |
draft |
|
[Module Name] User Manual |
QM |
NO |
draft |
|
[Module Name] Verification Report |
ASIL_B |
NO |
draft |
Component Documentation#
The Components documentation provides detailed documentation for each individual library component, including requirements, architecture, and design decisions:
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
[Component Name] Architecture |
ASIL_B |
NO |
draft |
|
[Component Name] Architecture Inspection |
ASIL_B |
YES |
draft |
|
[Component Name] Component AoU |
ASIL_B |
NO |
draft |
|
[Component Name] Component AoU |
QM |
YES |
draft |
|
[Component Name] Component Classification |
ASIL_B |
NO |
draft |
|
[Component Name] Detailed Design |
ASIL_B |
NO |
draft |
|
[Component Name] DFA |
ASIL_B |
NO |
draft |
|
[Component Name] FMEA |
ASIL_B |
NO |
draft |
|
[Component Name] Implementation Inspection Checklist |
ASIL_B |
YES |
draft |
|
[Component Name] Requirements |
ASIL_B |
YES |
draft |
|
[Component Name] Requirements Inspection Checklist |
ASIL_B |
YES |
draft |
|
[Your Component Name] |
ASIL_B |
NO |
draft |
Architecture Modeling Example#
An example of modeling architecture in Sphinx Needs can be found in
Please note, that is not a template for architecture documentation, but an example of how to use Sphinx Needs for architecture modeling. The architecture documentation of the components and features of the module should follow the provided templates and guidelines.
Quick Start - Building and Testing#
Attention
This could also contain just a link to the repository’s README
To build the entire module:
bazel build //src/...
To run all tests:
bazel test //...
To run only unit tests:
bazel test //src/...
To run only component or feature integration tests:
bazel test //tests/...
Module Build Configuration#
The project_config.bzl file at the root of the module defines metadata used by Bazel macros.
This file controls build behavior and project-specific settings. It should follow the S-CORE definition.
See S-CORE user guide for project_config.bzl for details.
The configuration enables conditional build behavior:
Language-specific tools: For C++ code, tools like
clang-tidyare used; for Rust code,clippyis usedSafety level: The ASIL level affects safety-related build settings and validation
Source code languages: The build system optimizes for the configured languages
Release Notes#
The Module documentation covers the module-level view, including architecture, safety management documents, and the user manual.