Architecture#
Persistency KVS Module Architecture
|
status: valid
security: NO
safety: ASIL_B
|
||||
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
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).
Component Name (Static View)
|
status: invalid
security: YES
safety: ASIL_B
|
||||
|
|||||
Dynamic Architecture#
Dynamic View
|
status: invalid
security: YES
safety: ASIL_B
|
||||
put here a 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
Lower Level Components#
Component Name 2
|
status: invalid
security: YES
safety: ASIL_B
|
||||
no architecture but detailed design |
|||||
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