Log Bridge Component Architecture#

log_bridge Architecture
status: draft
security: NO
safety: ASIL_B
tags: template
realizes: wp__component_arch
doc__log_bridge_architecture
Generic Document

Attention

The above directive must be updated according to your needs.

  • Modify Your Component Name to be your Component Name

  • Modify id to be your Component 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>

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 internal 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).

log_bridge
status: invalid
security: YES
safety: ASIL_B
forms part of: feat__logging
implements: logic_arc_int__log_rust__score_logger
uses: logic_arc_int__log_cpp__recorder
included by: mod__logging

comp__log_bridge
Component

Dynamic Architecture#

Interfaces#

Internal Components#

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