Process Requirements#

Static Diagram for Unit Interactions
status: valid

The static diagram shall represent the unit and their relationships using UML notations.

Diagram Attributes#

Diagram attribute: UID
status: valid

Each diagram shall have a unique ID. It shall consist of three parts:

  • type of diagram

  • structural element

  • keyword describing the content of the diagram

Consider the project’s naming convention.

Diagram attribute: title
status: valid

The title of the diagram shall provide a short summary of the description, but is not an “additional” requirement.

This means for example that the word “shall” is not allowed in the title for all diagram.

Diagram attribute: security
status: valid
tags: manual_prio_2, attribute, mandatory, implementation

Each diagram shall have a security relevance identifier:

  • Yes

  • No

Diagram attribute: safety
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each diagram shall have a automotive safety integrity level (ASIL) identifier:

  • QM

  • ASIL_B

Diagram attribute: status
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each diagram shall have a status:

  • valid

  • invalid

Diagram attribute: description
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each diagram shall have a description. The description shall provide a needarch or image of the diagram.

Diagram Linkage#

Diagram Linkage check Component Requirement
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be linked to the corresponding component requirement via the attribute implements.

Diagram Linkage Component Requirement
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be automatically linked (inverse direction) to the corresponding component requirement via the “implemented by” linkage.

Diagram Linkage check Component Architecture
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be linked to the corresponding component architecture via the attribute satisfies.

Diagram Linkage Component Architecture
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be automatically linked (inverse direction) to the corresponding component architecture via the “satisfied by” linkage.

Diagram Linkage check Component ID
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be linked to the corresponding component id via the attribute belongs_to.

Diagram Linkage Component ID
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be automatically linked (inverse direction) to the corresponding component id via the “belongs by” linkage.

Diagram Linkage includes
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be linked to the corresponding - SW Unit - SW Unit Interface via the attribute includes.

Diagram Linkage includes
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each diagram shall be automatically linked (inverse direction) to the corresponding - SW Unit - SW Unit Interface via the “included by” linkage.

Diagram Checks#

Diagram mandatory attributes provided
status: valid
tags: prio_2_automation, attribute, check, implementation

It shall be checked if all mandatory attributes for each diagram are provided by the user. For all diagrams following attributes shall be mandatory:

Overview mandatory Diagram attributes#

Title

Diagram attribute: description

Diagram attribute: safety

Diagram attribute: security

Diagram attribute: status

Diagram attribute: UID

Interface attribute: description

Interface attribute: UID

Unit attribute: description

Unit attribute: UID

Unit Attributes#

Unit attribute: UID
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each unit shall have a unique ID. It shall consist of three parts:

  • type of unit

  • structural element

  • keyword describing the content of the unit

Consider the project’s naming convention.

Unit attribute: description
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each unit shall have a description.

Unit Linkage#

Unit Linkage check Component ID
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each unit shall be linked to the corresponding component id via the attribute belongs_to.

Unit Linkage Component ID
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each unit shall be automatically linked (inverse direction) to the corresponding component id via the “belongs by” linkage.

Interface Attributes#

Interface attribute: UID
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each interface shall have a unique ID. It shall consist of three parts:

  • type of interface

  • structural element

  • keyword describing the content of the interface

Consider the project’s naming convention.

Interface attribute: description
status: valid
tags: manual_prio_1, attribute, mandatory, implementation

Each interface shall have a description.

Interface Linkage#

Interface Linkage check SW Unit ID
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each interface shall be linked to the corresponding SW Unit id via the attribute belongs_to.

Interface Linkage SW Unit ID
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each interface shall be automatically linked (inverse direction) to the corresponding SW Unit id via the “belongs by” linkage.

Interface Linkage check Architecture
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each interface shall be linked to the corresponding architecture via the attribute implements.

Interface Linkage Architecture
status: valid
tags: prio_2_automation, attribute, automated, implementation

Each interface shall be automatically linked (inverse direction) to the corresponding architecture via the “implemented by” linkage.

Dependency Analysis#

Dependency Analysis
status: valid
tags: prio_2_automation, implementation

For each component a dependency tree view shall be created to support design inspection and Safety Analysis. It shall show the libraries used by the component (i.e. which libraries are linked to the component, defined as CI build tool target) up to the leaves of the tree.

Complexity Analyses#

Design Complexity Analysis
status: valid
tags: prio_3_automation, model, check, implementation

A complexity analysis for the components shall be performed. It shall consider appropriate code metrics like lines of code, cyclomatic complexity, number of public interfaces, number of parameters and so on. The results of the analysis shall be documented in the SW Verification Report. The project specific limits for the complexity measures shall be defined in the project guidelines.