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#
Feature 1
|
status: valid
security: YES
safety: QM
|
||||
|
|||||
Logical Interface 2
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Logical Interface 3
|
status: valid
security: YES
safety: ASIL_B
|
||||
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 Viewpoint#
Module 1
|
|||||
|
|||||
Module 2
|
|||||
|
|||||
Component Architecure File(s)#
Component 1
|
status: valid
security: NO
safety: ASIL_B
|
||||
|
|||||
Component 3
|
status: valid
security: NO
safety: QM
|
||||
|
|||||
Lower Level Component 1
|
status: valid
security: NO
safety: ASIL_B
|
||||
Lower Level Component 2
|
status: valid
security: NO
safety: ASIL_B
|
||||
Lower Level Component 3
|
status: valid
security: NO
safety: QM
|
||||
Example Stkh Req
|
status: valid
security: YES
safety: ASIL_B
|
||||
The platform shall provide the feature …. |
|||||
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 .. |
|||||