SW requirement engineer

SW requirement engineer

SCOPE 

To contribute and support on the requirement management activities.

The SW requirement engineer should design and define SW requirements based on defined SW architecture. He should secure the documentation, process, content of the requirement and manage the change requests while securing those requirements are properly managed in tools 5doors, Codebeamer,…). He should as well do activities such as analyzing/reviewing the system and software requirements, Software component allocation, manage/ follow up with various stakeholders to guarantee that all the software requirements are covered in proper manner

ORGANISATIONALCHART

RESPONSIBILITIES

1. Read and understand SW architecture documents, interact with SW and system architect to understand the functionalities and SW architecture
2. Design and define SW requirements to allow developers and testers to develop the right SW and be able to define the right test coverage towards the requirements
3. Understand its domain (Electrification, Hydrogen, ADAS/Radar, Lighting, platforming)
4. Organize and lead Change Control Board (CCB) and Change Request (CR) related meetings to challenge and secure requirement changes consistency and quality
5. To review the architecture and requirements documents received from system team and SW architect and make sure it complies with standards (A spice, safety, cybersecurity,…)
6. Define & use key metrics generation (safety, regulation, cybersecurity, traceability downstream)
7. To secure the use of aligned tool chain in requirement management
8. Get involved with various stakeholders (SW engineers, testers, project manager, scrum teams, scrum master, architects, ...) the issues raised in system, support resolution and adjust SW requirements if needed.
9. To provide clarification support to System, SW Architect, Development & Validation team and answering their questions
10. Organize regular review meetings for each new requirements to be understood and aligned with developers and testers
11. Define a backlog of activities in JIRA to be tracked and organize activities in agile methodologies with sprint and PI’s participation/organization

REQUIREMENTS

SKILLS AND RELEVANT EXPERIENCE

1. 5to 7 years of experience in any requirement management tools
2. Strong knowledge on requirement tools like Codebeamer (ideal), DOORS, ReqSuite® RM, Atlassian JIRA, Enterprise architect, etc.
3. Work experience in defining and analyzing specifications, requirements and use cases.
4. Work experience in any automotive domain ECU’s ADAS/Telematics/ Connectivity/Body/Chassis/FOTA and/or Electrification, Fuel cell (H2), radar, Lighting
5. Experience in SW platforming approach
6. Expertise in configuration management activities such as branching, diversity, merging/baseline, key matrices generation etc.
7. Work experience in involving several Change Control Board (CCB) and Change Request (CR) related meetings
8. Good knowledge in understanding the SW Component allocation and SW architect role
9. Good experience in Next gen tool support such as data model, prototyping, etc.
10. Good experience in Automotive communication protocol like CAN, UDS, KWP, DOIP
11. Good experience in customer and supplier interaction
12. Work experience using VB Macro, DXL and Programming skills
13. Good experience in software development life cycle
14. Expertise in Requirements Elicitation, Analysis, Specification, Documentation, Validation, and Traceability
15. Knowledge of ASPICE, ISO 26262 
16. Functional Safety, and Automotive Software Development Lifecycle (V-Model).

B.E. in Electrical/Electronics (E/E) / Electronics and Communication Engineering (E.C.E) / Electronics and Instrumentation Engineering (E.I.E) / Computer Science (CSE)

1. Good teamwork, coordination, and communication skills.
2. Good interpersonal skills to interact with diverse teams and take decisions
3. Very good analysis skills
4. Good problem-solving skills
5. Effective oral and written communication skills.