Example: Detailed Design

Description

• component is split into two units unit1 and unit2 based on single responsibility principle.

• unit2 is injected to unit1 one via dependency injection for testability.

Static Diagrams for Unit Interactions

dd example static		status: valid security: NO safety: ASIL_B
status: valid tags: implementation safety: ASIL_B security: NO satisfies: comp_arc_sta__archdes_sub_component_1 implements: comp_req__archdes_example_req includes: sw_unit__unit1, sw_unit__unit2
dd_sta__dd_example_static		Static detailed design

Dynamic Diagrams for Unit Interactions

dd example dynamic		status: valid security: NO safety: ASIL_B
status: valid tags: implementation safety: ASIL_B security: NO satisfies: comp_arc_sta__archdes_sub_component_1 implements: comp_req__archdes_example_req
dd_dyn__dd_example_dynamic		Dynamic detailed design

Units within the Component

From here onwards the needs are defined in the source code and will be automatically generated and linked via doxygen.

SW Unit

unit1		status: valid security: NO safety: ASIL_B
status: valid tags: implementation safety: ASIL_B security: NO is included in: dd_sta__dd_example_static
Placeholder for the description that will be generated from doxygen
sw_unit__unit1		Software unit

Interface

int1		status: valid security: NO safety: ASIL_B
status: valid tags: implementation safety: ASIL_B security: NO
Placeholder for the description that will be generated from doxygen
sw_unit_int__unit1_int1		Software unit interfaces

SW Unit

unit2		status: valid security: NO safety: ASIL_B
status: valid tags: implementation safety: ASIL_B security: NO is included in: dd_sta__dd_example_static
Placeholder for the description that will be generated from doxygen
sw_unit__unit2		Software unit

Interface

int2		status: valid security: NO safety: ASIL_B
status: valid tags: implementation safety: ASIL_B security: NO
Placeholder for the description that will be generated from doxygen
sw_unit_int__unit2_int2		Software unit interfaces