Example model of architectural design#

This chapter only serves as an example how an architecture could be modeled in Sphinx Needs. All the needs are required to print the views which are displayed in the Static- and Interface Views. In the actual process this files would be split into multiple different files:

Feature Architecture File#

Note

The feature and the logical interfaces are normally defined in the platform repo (features folder) and imported from there as sphinx needs objects. In this example it is defined here only, to hold the example consistent.

Feature 1 Static View
status: valid
security: YES
safety: QM

Logical Operation 1
status: valid
security: YES
safety: ASIL_B
Logical Operation 2
status: valid
security: YES
safety: ASIL_B
Logical Operation 3
status: valid
security: YES
safety: ASIL_B
Logical Operation 4
status: valid
security: YES
safety: ASIL_B
Logical Operation 5
status: valid
security: YES
safety: ASIL_B
Logical Operation 6
status: valid
security: YES
safety: ASIL_B
Logical Operation 7
status: valid
security: YES
safety: ASIL_B
Logical Operation 8
status: valid
security: YES
safety: ASIL_B

Module View File#

Module 1
status: valid
security: YES
safety: ASIL_B

This is Module 1.

Module 1 Static View

Module 2
status: valid
security: YES
safety: ASIL_B

This is Module 2.

Module 2 Static View

Feature or Component Architecture File(s)#

Component 2
status: invalid
security: YES
safety: ASIL_B

Example Component 2 description.

Component 3
status: invalid
security: YES
safety: QM

Example Component 3 description.

Component 1 Static View
status: valid
security: NO
safety: ASIL_B

Component 1_3
status: valid
security: NO
safety: ASIL_B

Requirements for the Example#

Note

The stakeholder requirements shall be defined in the platform repo (stakeholder requirements folder) and imported as sphinx needs objects. Here it is defined only to hold the example together and prevent errors because the sphinx needs meta model have mandatory links to it.

Example Stkh Req
status: valid
security: YES
safety: ASIL_B
rationale: needed for archdes example
reqtype: Functional

The platform shall provide the feature ….

Note

The feature requirements shall be defined in the platform repo (in the requirements folder of the (features)) and imported as sphinx needs objects. Here it is defined only to hold the example together and prevent errors because the sphinx needs meta model have mandatory links to it.

Example Feature Req
status: valid
security: YES
safety: ASIL_B

The feature shall provide the functionality to ….

Example Component Req
status: valid
security: YES
safety: ASIL_B

The component shall provide the Logical Operation 4 to get the ..