SW Platform Assumptions#
SW Platform Assumptions
|
status: draft
security: YES
safety: ASIL_B
|
||||
Assumptions on Environment#
In this section assumptions are described which need to be fulfilled by the architecture level below the SW platform, i.e. by the elements outside of S-CORE, but used by S-CORE platform components. These include elements like the operating system, programming language libraries, hypervisor or processing hardware.
To fulfill these assumptions is the responsibility of the integrator.
OS safety features
|
status: valid
security: YES
safety: ASIL_B
|
||||
The Integrator shall integrate the SW platform with an OS providing safety functions, if the system using the SW platform has safety goals. Note: A list of OS safety functions needed is compiled by the S-CORE project here (TBD). |
|||||
Assumptions on the OS integration - Community Level#
This is the lowest level of integration, the higher levels will build on this. It also contains expectations towards an OS supplier which can be used as criteria for OS selection by the integrator. Building and running of OS is enabled, but no pro-active support from S-CORE is provided for e.g. build or test problems. No guarantees that S-CORE builds or runs on the OS.
OS integration assistance
|
status: valid
security: YES
safety: QM
|
||||
The OS supplier shall provide a contact point for integration assistance. |
|||||
OS integration manual
|
status: valid
security: YES
safety: QM
|
||||
The OS supplier shall provide an integration manual. |
|||||
OS bug interface
|
status: valid
security: YES
safety: QM
|
||||
The OS supplier shall provide a bug reporting interface. Note: There is no guarantee provided to fix these bugs. |
|||||
TBD: AoUs on the S-CORE SW Platform integrator with respect to OS integration on this level.
Assumptions on the OS integration - Functional Level#
This is the middle level of integraton, the higher level will build on this. It is the level where the S-CORE SW platform will functionally “work” on the supplied OS.
OS bazel tooling
|
status: valid
security: YES
safety: QM
|
||||
The OS supplier shall provide tools for Bazel to be able to build the S-CORE SW platform on the supplier OS and support the run and test of the S-CORE SW platform on the supplier OS. |
|||||
OS bug fixing
|
status: valid
security: YES
safety: QM
|
||||
The OS supplier shall fix bugs reported in a predictable manner. Note: For OSS community providing an OS this requirement could be covered by analyzing how bugs were treated in the past. For companies by the definition of a service level process. |
|||||
TBD: AoUs on the S-CORE SW Platform integrator with respect to OS integration on this level.
Assumptions on the OS integration - Certifiable Level#
This is the highest level of integraton. This is the level where the S-CORE SW platform will be certifiable on the supplied OS.
OS integration levels
|
status: valid
security: YES
safety: ASIL_B
|
||||
The OS supplier shall provide all the levels AoUs in a safe way (i.e. the “safety” attribute will be raised to the level in this AoU). Note: This includes for example OS bazel tooling (aou_req__platform__os_bazel_tooling), OS bug fixing (aou_req__platform__os_bug_fixing) |
|||||
OS safety AoU
|
status: valid
security: YES
safety: ASIL_B
|
||||
The OS supplier shall provide Assumptions of (safe) Use. |
|||||
OS safety functions
|
status: valid
security: YES
safety: ASIL_B
|
||||
The OS supplier shall provide a list of safe OS functions. |
|||||
OS safety anomaly reporting
|
status: valid
security: YES
safety: ASIL_B
|
||||
The OS supplier shall perform safety anomaly reporting. Note: This could be fulfilled by listing per release version all known and user reported bugs which affect the safe OS functions. |
|||||
TBD: AoUs on the S-CORE SW Platform integrator with respect to OS integration on this level.
Assumptions of Use#
In this section assumptions are described which need to be fulfilled by the applications running on top of the SW platform.
TBD