Software & System Requirements Engineer

3/2022 – 11/2024

Projects: 48V Invertor; Door handle with NFC, Battery Management System
Responsibilities:
- Identifying sources of requirements (Legacy product requirements Lastenheft from client, international standards).
- Eliciting needs, goals, desires and additional requirements from the client.
- Keeping track of open points (change requests, feature requests, unclear topics from Lastenheft).
- Gathering potential requirements from existing documents and legacy projects.
- Creating and managing requirements in DOORS & POLARION.
- Tracking the requirements in DOORS & POLARION by creating tickets in Jira for each CR or FR (one Jira ticket can be linked to multiple requirements in DOORS & POLARION).
- Creating baselines and baseline sets for each major change (after review meetings with project).
- Creating and updating Diagrams to illustrate the system/software behavior (Use case diagrams, Sequence diagrams, Timing diagrams, State machine diagrams).
- Organizing and leading requirements review meetings with other disciplines (SW team, ME team, CFT team, QA lead) to freeze newly introduced requirements for each release (proposed -> project accepted/invalid).
- Review testcases and architecture, based on requirements and process checklists.

Technologies responsible for:
- UDS, CAN, NFC, LIN, Emergency access, Kessy I/O, Voltage monitoring, Inductive sensor, Capacitive sensor.
Tools used:
- DOORS, Jira, Office, Miro, Confluence, SBM.

Requirements Engineer

1/2021 – 3/2022

Project: High Voltage Load Management, Programmable charging, HUD, Message routing for Porsche Taycan
Responsibilities:
- Identifying sources of requirements (Legacy product requirements, Lastenheft from client, international standards).
- Eliciting needs, goals, desires and additional requirements from the client.
- Keeping track of open points (change requests, feature requests, unclear topics from Lastenheft).
- Gathering potential requirements from existing documents.
- Creating and managing requirements in DOORS/CodeBeamer.
- Tracking the requirements in DOORS/CodeBeamer by creating tickets in Jira for each CR or FR (one Jira ticket can be linked to multiple requirements in DOORS/CodeBeamer).
- Creating baselines and baseline sets for each major changes (after review meetings with project).
- Creating and updating Diagrams to illustrate the system behavior (Use case diagrams, Sequence diagrams, Timing diagrams, State machine diagrams).
- Coaching external company on V-Cycle process and Requirements Engineering.
- Coaching multiple teams inside company on how to use DOORS.

Technologies responsible for:
- UDS, CAN, LIN.
Tools used:
- DOORS, Jira, Office, CodeBeamer.

Requirements Engineer

9/2019 – 1/2021

Responsibilities:
- Responsible for creating, maintaining and tracking System Requirements and deriving Software Requirements (functional and non-functional) for German OEM project after meetings with other project disciplines (SW, ME, EE).
- Identifying sources of requirements (Legacy product requirements, Lastenheft from client, International standards).
- Eliciting needs, goals, desires and additional requirements from the client.
- Keeping track of open points (change requests, feature requests, unclear topics from Lastenheft).
- Gathering potential requirements from existing documents.
- Creating and managing requirements in DOORS.
- Tracking the requirements in DOORS by creating tickets in Jira for each CR or FR (one Jira ticket can be linked to multiple requirements in DOORS).
- Creating new requirements as the project advances to enhance the product and increase robustness (ex.: network management, sleep wake-up, under/overvoltage behavior, overtemperature retry timers, etc.)
- Creating baselines and baseline sets for each major change (after review meetings with project).
- Creating and updating Diagrams to illustrate the system behavior (Use case diagrams, Sequence diagrams, Timing diagrams, State machine diagrams).
- Creating System Architecture (Rhapsody, SY-SW UML).
- Insuring compliance of the requirements with the road vehicle safety standards (ISO 26262).
- Organizing and leading requirements review meetings with other disciplines (SW team, ME team, CFT team, QA lead) to freeze newly introduced requirements for each release (proposed -> project accepted/invalid).
- Maintaining the Requirements Engineering Plan and Traceability Management Plan documents.
- CCB Meetings with the project team to prioritize change requests, feature requests and issue planned for each SW release.

Technologies responsible for:
- UDS, CAN, NFC, Qi Wireless Charging
Tools used:
- DOORS, Jira, Rhapsody, Visio, IMS, Office

Systems Engineering