- Analyse System Requirements together with the stakeholders.
- Update/create SW Architecture concepts based on the System Requirements (focus areas: Diagnose, DTC Handling, Re-flashing, Power Management, Communication, Reset handling, Startup und Security).
- Documentation of concepts and SW design from static and dynamic view based on the analysis of the use cases.
- Definition of the performance concept and the implementation guidelines for the SW components.
- Carrying out reviews with relevant representatives from other disciplines and roles (system, architecture, development, possibly test) and incorporation of the review comments.

• Implementation of monitoring for ASIL and QM ECU-received signals (E2E check, validity, timeout supervision)
• Defects management
• Requirements analysis and clarification with customer
• Ethernet stack configuration review and bug-fixing (based on BMW Ethernet-TestCheckList for SP2021 specification and OPEN Alliance Automotive Ethernet ECU Test Specification).

HW & Tools

• ASIL B Autonomous Driving project
• Microcontrollers: Renesas R-Car V3H system-on-chip,
  Renesas RH850F1L
• Configuration and change management tool: Integrity lifecycle manager 11, GIT
• Coding: ECLIPSE, Visual Studio Code
• AUTOSAR Release 4.3 based 
• BAC (BMW Autosar Core) Modules
• Flash Absicherung Tool (FAT)
• EDIABAS
• E-Sys Flashing Tool
• Vector DaVinci Developer 
• Vector DaVinci Configurator 
• Lauterbach Trace32 
• Vector CANoe 
• Wireshark
• MISRA 
• QAC

• Review and extend the functionality of the FBS4 (Fahrberechtigungssystem – Driving Authorization System - version 4) - confidential part, based on Daimler specification updates.
• Design document creation for the FBS4 functionality (337 functions, 11072 ELOC).
• Module tests development for FBS4 functionality (337 functions, 11072 ELOC).
• Implementation and integration of a complex device driver dedicated to a Daimler specific Transport Protocol related to the FBS4/Authentication Control functionality.
• Solve issues reported by System Tests and Daimler related to FBS4 Confidential/ Authentication Control functionalities.

HW & Tools

• Microcontrollers: Castor4 - Daimler security microprocessor: Freescale Calypso 3M, Chorus - ST Chorus CH04M/CH10M - SPC58EGx, SPC58NGx 
• Configuration and change management tool: Integrity lifecycle manager 11 (IMS BS)
• Requirements engineering: DOORS (v9.3)
• Coding: IDEAS (Continental Automotive GmbH specific integrated development environment, ECLIPSE-based)
• Compiler: Wind River Diab (v5.9.4.2)
• SW design and code generation: MathWorks: MATLAB (R2017b)/ Simulink (9.0)/ Stateflow (9.0) / Embedded Coder (6.13) with AUTOSAR Support Package (17.2.3)
• Debugger: I-System IC5000 / IC5500 / IC6000 / winIdea (9.12.288 64-bit)
• Vector CANoe

• Requirements analysis and clarification with Requirements Manager and with the customer.
• Integration and configuration of Diagnostics stack (Vector SLP) and development of the CDD Diag (complex device driver for Diagnostics Handler - implementation of the diagnostic services). (ODX import)
• Update and maintenance of the Memory Stack modules (NvM configuration).
• Support for test and integration of the FBL (Flash Boot Loader).
• Support the System Tests team to develop tests for Diagnosis stack and review the System Test Specification.
• Team member, from Continental Automotive GmbH side, of the assessment team who reviewed the MLBevo Vector Microsar Standard Software configuration (together with Vector, Audi and BFFT).

HW & Tools

• Microcontroller: Renesas RH850, R7F7010153AFP
• Configuration and change management tool: Integrity lifecycle manager 11 (IMS BS)
• Requirements engineering: DOORS (v9.3)
• Coding: IDEAS (Continental Automotive GmbH specific integrated development environment, ECLIPSE-based)
• Compiler: Green Hills Software, vGHS 850.2013.5.5p2 
• AUTOSAR 3.2 - MLBevo Vector Microsar SIP
• Debugger: I-System IC5000 / IC5500 / IC6000 / winIdea, TRACE32 (Lauterbach GmbH), WinIdea (iSystem)
• Vector CANoe
• ODIS Engineering 6.2

• Analyze and clarify Software-Requirements with the customer and with the project team.
• Integrate, configure and test AUTOSAR, non-AUTOSAR and 3rd party software modules according to the customer requirements and specific HW needs, based on the company’s guidelines, processes and methods with respect to the planned milestones and deliveries.
• Analyze, debug and fix MCAL and AUTOSAR BSW modules integration issues which occurred during FAT, DM, DS execution and HIL tests.
• Analyze and provide solutions to project and customer reported bugs.
• Provide technical expertise and support for the project management team and for the customer by phone, email or on-site.
• Part of the critical escalations/"red-alert" teams for analysis and solving critical issues.

HW & Tools

• Infineon AURIX TC275 multi-core microcontroller
• ASIL B project
• AUTOSAR Release 4.0.3 based
• BAC (BMW Autosar Core) Modules 
• Flash Absicherung Tool (FAT)
• ECUTEST RUNTIME BMW
• EDIABAS
• Esys Flashing Tool
• Diagnostic Master Test
• Diagnostic System Test 
• CESSAR-CT
• Tresos Studio
• Understand for C
• Lauterbach Trace32
• iSYSTEM winIDEA 
• Vector CANoe
• CAN/Flex Ray bus systems

• Analyze and clarify Software-Requirements with the customer and with the project team.
• Integrate, configure and test AUTOSAR MEM Stack software modules according to the customer requirements and specific HW needs, based on the company's guidelines, processes and methods with respect to the planned milestones and deliveries.
• Analyze and provide solutions to project and customer reported bugs.
• Provide technical expertise and support for the project management team and for the customer by phone, email or on-site.
• Part of the critical escalations/"red-alert" teams to analyze and provide solutions to solve the critical issues.

HW & Tools

• Infineon AURIX TC2791 multi-core microcontroller 
• ASIL D project 
• AUTOSAR Release 3.2 based
• IBM Rational Rhapsody
• CESSAR-CT
• Vector DaVinci Configurator
• Vector GENy
• Understand for C
• Lauterbach Trace32
• Vector CANoe
• Vector CANalyzer 
• CAN/Flex Ray bus systems

• Part of the project core team from the start of the project until the SOP.
• Analyze and clarify Software-Requirements with the customer and with the project team.
• Integrate, configure and test AUTOSAR, non-AUTOSAR and 3rd party software modules according to the customer requirements and specific HW needs, based on the company’s guidelines, processes and methods with respect to the planned milestones and deliveries.
• Analyze, debug and fix MCAL and AUTOSAR BSW modules integration issues which occurred during FAT, DM, DS execution and HIL tests.
• Actively took part to the AUTOSAR BSW modules implementation improvement and to the integration and test automation process definition and implementation within AUTOSAR Center.
• Analyze and provide solutions to project and customer reported bugs.
• Provide technical expertise and support to the project management team and to the customer by phone, email or on-site.
• Part of the critical escalations/"red-alert" teams to analyze and provide solutions for solving the critical issues.

HW & Tools

• Infineon AURIX TC277 and TC275 multi-core microcontrollers 
• ASIL B projects
• AUTOSAR Release 4.0.3 based
• BAC (BMW Autosar Core) Modules 
• Flash Absicherung Tool (FAT)
• ECU-TEST RUNTIME BMW
• EDIABAS
• Esys Flashing Tool
• Diagnostic Master Test 
• Diagnostic System Test
• CESSAR-CT
• Tresos Studio
• Understand for C
• Lauterbach Trace32
• iSYSTEM winIDEA
• Vector CANoe
• CAN/Flex Ray bus systems

• Responsible for the realization of the “System” subset of product functionalities: Diagnosis, Self-test, Error Management and AUTOSAR Communication Stack (CAN).
• Lead a team of 5 people spread over two locations.
• Responsible for the complete function chain (planning, requirements engineering, design, implementation, test, integration and test of 3rd party software and the related documentation) according to the company guidelines, processes and methods. The whole project has been assessed as Automotive SPICE Level 3 conformant.
• Define and clarify product requirements with the customer for the mentioned functionalities and, based on those, create and maintain Software Requirements Specification documents
• The software developed and / or integrated (e.g. Vector SLP10) was based on AUTOSAR Standard 3.0, Conformance Class 1 (ICC1).

HW & Tools

• Renesas 32-bit microcontroller μPD70F3523 with V850 core
• Microsoft Visual Studio 2005
• Green Hills MULTI 2000 debugger + MINICUBE QB-V850 MINI
• BSKD
• FHostSp
• Vector CANoe
• Vector Geny AUTOSAR Framework
• Vector MICROSAR SIP
• Vector CANdela Studio
• Modification Request Database (MR-DB)
• PVCS, XML Trace System
• DOORS.