Taha ABDENNABI

The TECU (Target Embedded Systems) Technical Lead is responsible of the functionality FOTA (Firmware Over The Air) on one or several TECUs in their scope. – Master the FOTA Full System Architecture / FOTA requirements / Vehicle specificities – Master the bug review and analysis – Provide and request to SWPL/Supplier all necessary information to secure the FOTA functionality on the ECUs in their scope (Always share the context and importance of the need and keep a trace of all requests/MoM, always request a date of delivery/visibility) – Support technically the SWPL and Supplier on the FOTA specificities (For S400 REN ECU: Support on FUTE tests results, after Supplier results analysis) – Request and monitor SW release (SW release roadmap update and clear visibility) and check the SW package sent – Monitor the ECU and harness needs (Provide quote and all information to use them) – Provide to the validation team the SW information/documentation and follow up closely the progress of this validation – Support technically the vehicle, bench, production validation teams – Monitor bugs progress from opening to closure – Propose bugs to derogations – Provide the Go/NoGo document for each official SW release of the ECUs in their scope – Monitor the technical specifications coherence et the right deployment of the new functionalities in collaboration with the architects – Report weekly/daily to the project manager the ECUs progress – Report the blockers (HW, SW, issues, ...) quickly – Organize Integration and/or Debug session and participate – Update and monitor the compliance matrix – Tools: JIRA, SILK, Confluence, Sharepoint, Suite Office, Comet, VNext, FUTE, Artifactory, Gitlab, CANalyser/TCS/ Canoe

Projects: RSA-NISSAN Functionalities: PASE/Immo (Passive Access and Start Engine/Immobilizer) Role: Developing software for BCM (Body Control Module) and HFM (Hands-Free Model) following V-Model. – Participate in the implementation of new behaviours in vehicles (Renault, Nissan): Remote Engine Start, Passive Access, Remote Keyless Entry. – Code implementing in C according to AUTOSAR architecture, respecting LINT/MISRA rules, real-time constraints and scheduling. – Contributing to the architecture, design and development of the project Auto-Test which aims to validation tests automation via CAPL.(keyword ; CAPL, CANOE, TestBensh,Wireless Box, CAN). – Analyze and understand final customer requirements (CRS) Update Software Requirement Specification (SRS) under Doors. – Analyze/confirm a reported problem then fix the wrong behavior. Perform validation and Integration tests following specification documents (VTS: Validation Tests Specification, ITS: Integration Tests Specification) on manual and automatic test bench. – Writing unit tests via SWATT tool and ensure total code testing and coverage.

– Test Engineer in project " Body Domain Controller" BDC2018 (BMW Group) – Analyze SW requirements – Implementation of Automated Test Cases Using AUTOSAR interface – Functional and non Functional testing (Black box Testing) – Test Execution and Results analysis – Finding Defects related to Software Version – Reporting SW defect in Jira – Review – Key Words: BMW, IBM Rational DOORs, Jira, Jenkins, Eclipse, Carmen, SVN, LIN/CAN Communication, TCF, Automotive Test

– Command of a stepper motor by a Beagle Bone card using a LabWindows communication interface (H/M)

– ADSL management and maintenance service in Tunisia Telecom (Technical Group)

– Engineer Internship of production of electronic cards, thermostats and testing of control systems and tests.