Lifecycle Documentation#
Portable and high-performance implementation of the Lifecycle feature for the S-CORE project, consisting of the Launch Manager and the Health Monitor.
Feature Documentation#
The Feature documentation covers the feature-level definition of Lifecycle, including architecture and safety planning artifacts.
No needs passed the filters
Module Documentation#
The Module documentation covers the module-level view, including architecture, safety management documents, and the user manual.
Title |
ID |
Safety |
Security |
Status |
|---|---|---|---|---|
Platform Verification Report |
QM |
YES |
valid |
Component Documentation#
The Components documentation provides detailed documentation for each individual component, including requirements, architecture, and design decisions:
No needs passed the filters
Release Notes#
The Release Notes document the changes, known issues and compatibility information of each module release.
Quick Start - Building and Testing#
For further platforms (e.g. QNX) see the repository’s README.
To build the entire module:
bazel build --config=x86_64-linux //score/... //examples/...
To run all tests:
bazel test --config=x86_64-linux //...
To run only the unit and component tests:
bazel test --config=x86_64-linux //score/...
To run only the integration tests:
bazel test --config=x86_64-linux //tests/integration/...
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