Definition of OpenBSW Goals

[johannes-esr]

Currently, there are no goals of OpenBSW written down in detail (supported platforms, ...). This leads to open questions, e.g. what C++ standards we should support within OpenBSW (see #136).

In our monthly call (#146) we agreed to collect these goals in this discussion and try to agree on these in our next monthly call on September 24th.

fyi: @stefanheinbockelbmw, @rolandreichweinbmw, @thomas-herrmann-1

[stefanheinbockelbmw]

Hello @johannes-esr,

we collected the goals from BMW point of view.
We can use them as a starting point for the discussions, either here or in our next monthly call.

Please feel free to comment on or ask questions about each of these points.

Goal	Details
Follow a well-described development process which keeps track of relevant work products such as requirements, architecture, test case specifications etc.	OpenBSW currently doesn't contain requirements and architecture explicitly. Intentionally contains only detailed design onwards, leaving requirements and architecture to projects integrating OpenBSW (e.g. BMW RCORE).
Enabled for safety levels up to ISO 26262 ASIL D	It shall be possible to run an application with ASIL D on top of this platform
State of the art cybersecurity software development for connected cars according to ISO21434.
Usable for Real Time Embedded Systems
Usable on Multi-Core Controllers
Support for common Automotive bus systems
Support for commonly used Automotive protocols
Use of existing OSS libraries to benefit from established solutions.
Closely track used Open Source libraries (LWIP, FreeRTOS, ETL, ...) by keeping them up-to-date in OpenBSW to enable head based development	Minimizes effort by maintaining old versions and at the same time porting effort when contributing
Official support for a limited set of toolchains (e.g. gcc + clang) and reference HW platforms (at least two, in total supporting all implemented features) by including them in the CI / standard tests
Available under Apache License
Provide a stable API for application development enabling portability, fast innovation and reuse
Implemented in modern C++ and Rust
Scalability both regarding build time and run time for both small and large teams	Large teams could have more than 500 people. Low entry barriers for new users
Openness and ease of contributions of hardware support	Enabled by good hardware abstraction; Hardware abstraction can change over time
We prefer to have one standard solution for every use case