Software Development Process for OpenBSW

[johannes-esr]

Due to OpenBSW being an Eclipse project, the Eclipse Foundation Development Process applies. In addition, we want to enable the possibility of safety certifying (parts of) OpenBSW. This leads to the discussion, whether (in addition) another process will be applied to OpenBSW. Possible options could be

• Eclipse S-CORE development process, see https://eclipse-score.github.io/process_description/main/
• Trustable Software Framework, see https://codethinklabs.gitlab.io/trustable/trustable/ & https://www.eclipse.org/lists/openbsw-dev/msg00009.html

Goal of this discussion should be to have an open exchange regarding the pros/cons of different solutions and to find a general approach of how we deal with this topic.

[drpnsystems]

The software development process for OpenBSW (Open Basic Software) generally follows a structured approach similar to the V-model used in automotive and embedded systems. It begins with requirement analysis, where functional and non-functional needs are defined. Next comes software architecture and module design, ensuring compatibility with AUTOSAR standards. Development involves implementing reusable, modular components, followed by unit testing, integration testing, and validation against requirements. Continuous integration, version control, and automated testing help maintain quality. Finally, the process emphasizes documentation, compliance, and adaptability, making OpenBSW suitable for safety-critical automotive applications.