Feature Architecture

Lifecycle Module Architecture		status: valid security: YES safety: ASIL_B
version: 1 realizes: wp__feature_arch
doc__lifecycle_module_architecture		Generic Document

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

<Design Decisions - For the documentation of the decision the Decision Record Template (gd_temp__change_decision_record) can be used.>

<Design Constraints>

Rationale Behind Architecture Decomposition

Mandatory: A motivation for the decomposition

Note

Common decisions across features / cross cutting concepts is at the high level.

Static Architecture

Lifecycle Static View		status: valid security: YES safety: ASIL_B
version: 1 belongs to: feat__lifecycle fulfils: feat_req__lifecycle__launch_support, feat_req__lifecycle__logging_support includes: logic_arc_int__lifecycle__alive_if, logic_arc_int__lifecycle__controlif, logic_arc_int__lifecycle__deadline_monitor_if, logic_arc_int__lifecycle__lifecycle_if, logic_arc_int__lifecycle__logical_monitor_if
feat_arc_sta__lifecycle__static_view_arch		Feature & Feature Package Diagram

Configuration parameters static architecture		status: valid security: YES safety: ASIL_B
version: 1 belongs to: feat__lifecycle fulfils: feat_req__lifecycle__component_group_config, feat_req__lifecycle__config_file_support, feat_req__lifecycle__run_target_support includes: logic_arc_int__lifecycle__alive_if, logic_arc_int__lifecycle__controlif, logic_arc_int__lifecycle__deadline_monitor_if, logic_arc_int__lifecycle__lifecycle_if, logic_arc_int__lifecycle__logical_monitor_if
feat_arc_sta__lifecycle__cfg_params_static		Feature & Feature Package Diagram

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

Interactions between the Launch Manager and a User application (through it’s interfaces):

• Control Client

• Lifecycle Client

• Alive

• Launch manager

• External Monitoring

Interaction between the Health Monitor and Launch Manager:

• Health Monitor

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)