Feature Architecture#

[Your Feature Name] Architecture
status: draft
security: NO
safety: ASIL_B
tags: template, feature_name

Attention

The above directive must be updated according to your Feature.

  • Modify Your Feature Name to be your Feature Name

  • Modify id to be your Feature Name in upper snake case preceded by doc__ and followed by _architecture

  • Adjust status to be valid

  • Adjust safety and tags according to your needs

Overview#

Brief summary

Description#

General Description

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

Design Constraints

Requirements#

.. needtable:: Overview of Feature Requirements
   :style: table
   :columns: title;id
   :filter: search("feat_arch_sta__archdes$", "fulfils_back")
   :colwidths: 70,30

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#

Static View
status: invalid
security: YES
safety: ASIL_B

Dynamic Architecture#

Dynamic View
status: invalid
security: YES
safety: ASIL_B
tags: feature_name

put here a sequence diagram

Logical Interfaces#

Interface Name
status: invalid
security: YES
safety: ASIL_B

Operation
status: invalid
security: YES
safety: ASIL_B
tags: feature_name

Module Viewpoint#

The following modules are needed to be defined to be able to draw the static feature view. They will be replaced by linking the proper module definitions in the used module’s repositories as soon as those exist.

Module Name
tags: feature_name

Used Components#

The following components are needed to be defined to be able to draw the static feature view. They will be replaced by linking the proper SW component definitions in the used module’s repositories as soon as those exist.

Component Name
status: invalid
security: YES
safety: ASIL_B

Note

Architecture can be split into multiple files, it is an High level architecture_design which can be shown without actual c++/rust interfaces and data types and there will be link to lower level architecture till code to get actual api descriptions.

Attention

The above directives must be updated according to your feature architecture.