Project: April 2022 – June 2025 (39 months)
Description
The existing project for transmission control software consists of the actual control software and a software library for safety-critical functions (functional safety in accordance with ISO 26262-6). The safety library is being further developed due to change requests from the OEM and as a result of stricter regulatory requirements regarding ASIL D compliance. The transmission control software runs on two different ECUs from separate manufacturers and is integrated by the OEM in five different transmission derivatives.
In close cooperation with the functional safety teams in Berlin and Gifhorn, I was responsible for the following key activities:
- SYS.2 – Technical Safety Concept: Review of updated technical safety requirements as part of structured inspections
- SWE.1 – Software Safety Requirements: Review of updated software safety requirements as part of structured inspections
- SWE.2 – Software Architecture (semi-formal): Enhancement and revision of the existing software architecture
- SWE.3 – Software Detailed Design (semi-formal): Enhancement and revision of the existing software detailed design
- SWE.3 – Implementation (handwritten code): Code implementation according to software design specifications, including static code analysis and functional evaluation (HiL or SiL)
The project was carried out in two phases, each with a binding SOP milestone.
Activities in Phase 1: SOP-Oriented Development with Fastlane Process
- Change-driven coding according to the Fastlane process for rapid availability of the firmware
- Downstream creation and revision of ASPICE-compliant documentation
- Task tracking and traceability using Enterprise Architect and JIRA
Despite a pandemic-related project delay in the early phase, the SOP milestone was reached on time.
Activities in Phase 2: Agile Further Development and Process Optimization
- Further development of the transmission software under ASPICE-compliant conditions in a change-driven environment
- Participation in 2-week sprints, with release cycles spanning 4 to 5 sprints, each preceded by an analysis sprint
- Contribution to lessons-learned workshops and process refinement measures
- Contribution to and review of the architecture, detailed design, and coding guidelines as part of the release process
- Revision of the model structure in the UML tool for process-related separation and improved navigability
- Conversion from a centralized to a distributed version control system (including migration of derivative-specific sharing structures)
At the time of my departure from the project, the safety case for the SOP had just been completed.
Summary
Project | Software for Double Clutch Transmission |
Duration | 39 months (April 2022 – June 2025) |
Customer | confidential due to nondisclosure agreement |
Industry Sector | Automotive |
Role / Responsibility | Software Safety Requirements, Software Architecture, Software Design, Implementation, Inspections |
Software / Tools / Methods | Enterprise Architect (Sparx), Eclipse CDT (Eclipse Foundation), Visual Studio Code (Microsoft), Tasking C Compiler (Tasking), ASAP2-Tools (Vector Informatik), CANape (Vector Informatik), Trace32 (Lauterbach), Helix QAC (Perforce), Silver SiL (Synopsys), StarTeam (Starbase), GitLab (Open-Source), LemonTree (LieberLieber), Confluence (Atlassian), JIRA (Atlassian) |
Hardware Environment | Infineon TriCore TC2xx/TC3xx, HiL (Hardware in the Loop) |