Architecture#

KVS Module Architecture
status: valid
security: NO
safety: ASIL_B
realizes: wp__component_arch
doc__kvs_architecture
Generic Document

Overview#

Brief summary

Requirements Linked to Component Architecture#

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

Description#

<General Description>

<Design Decisions - For the documentation of the decision the gd_temp__change_decision_record can be used.>

<Design Constraints>

Rationale Behind Architecture Decomposition#

mandatory: a motivation for the decomposition or reason for not further splitting it into sub components.

Note

Common decisions across components / cross cutting concepts is at the higher level.

Static Architecture#

The components are designed to cover the expectations from the feature architecture (i.e. if already exists a definition it should be taken over and enriched).

A component can optional also consist of subcomponents to further structure the architecture. The component and its static views can also optionally use interfaces provided by other components.

The live component architecture template is maintained in the module template documentation.

Component Name (Static View)
status: invalid
security: YES
safety: ASIL_B
belongs to: comp__persistency_kvs
fulfils: comp_req__kvs__key_naming

comp_arc_sta__kvs__static_view
Component Package Diagram

Dynamic Architecture#

Dynamic View
status: invalid
security: YES
safety: ASIL_B
belongs to: comp__persistency_kvs
fulfils: comp_req__kvs__key_naming

put here a sequence diagram
comp_arc_dyn__kvs__dynamic_view
Component Sequence Diagram

Interfaces#

.. real_arc_int:: <Title>
   :id: real_arc_int__<component>__<Title>
   :security: <YES|NO>
   :safety: <QM|ASIL_B|ASIL_B>
   :fulfils: <link to component requirement id>
   :language: cpp

Internal Components#

Component Name 2
status: invalid
security: YES
safety: ASIL_B
belongs to: comp__persistency_kvs
fulfils: comp_req__kvs__key_naming

no architecture but detailed design
comp_arc_sta__kvs__2
Component Package Diagram

Note

Architecture can be split into multiple files. At component level the public interfaces to be used by the user and tester to be shown.

Attention

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

  • Replace the example content by the real content (according to gd_guidl__arch_design)

  • Set the status to valid and start the review/merge process