Feature Architecture#
Lifecycle Module Architecture
|
status: valid
security: YES
safety: ASIL_B
|
||||
Overview#
A brief overview of Lifecycle is described Lifecycle (doc__lifecycle).
Description#
The concept is based on 2 major components:
Launch Manager: Responsible for starting and stopping components based on the defined Run States and alive supervision of the started components
Health Monitor: Provides process local monitoring functionalities such as deadline monitoring and logical program flow monitoring
Rationale Behind Architecture Decomposition#
The decomposition of the monitoring functionality between the Launch Manager and the Health Monitor is documented in In-Process Health Monitor (dec_rec__lifecycle__in_process_health_monitor).
Static Architecture#
Feature Decomposition#
Lifecycle Static View
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Configuration Structure#
Configuration parameters static architecture
|
status: valid
security: YES
safety: ASIL_B
|
||||
The Launch Manager configuration is structured around Run Target and Component configurations. Each Component configuration specifies how the Component is started, monitored, and recovered during system operation. Components can have dependencies on other Components, collectively forming a dependency graph. Run Targets are configured through Run Target configurations, which define dependencies on Components and other Run Targets. These dependencies determine which Components are activated when a Run Target is activated. The Launch Manager is configured with an Initial Run Target and Fallback Run Target. The Initial Run Target is activated when the Launch Manager is first started. The Fallback Run Target specifies the Run Target that is activated if a failure occurs that cannot be recovered. |
|||||
Dynamic Architecture#
Logical Interfaces#
The logical interfaces of the feature are defined in the interfaces section of the feature documentation in the project repository: Lifecycle Architecture (doc__lifecycle_architecture)