CPRE-FL v3 — Automotive Edition
A requirement can look reasonable on paper and still hide ambiguity, an unvalidated assumption, an undefined operational design domain or a silent conflict between an OEM's system requirement and a Tier 1 supplier's implementation. In automotive software, that gap does not surface as a support ticke
Course Overview
The most important single part of building vehicle software is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, and no other part so cripples the resulting system — or endangers a driver — if done wrong. The inability to produce complete, correct and unambiguous requirements remains the major cause of software failure today, and in a modern, software-defined vehicle that failure does not stay technical. This course gives requirements engineers, systems engineers, software engineers and test engineers working across OEMs and Tier 1 suppliers the practical tools and techniques to deliver high-quality, traceable requirements specifications — and prepares you for the IREB CPRE Foundation Level (CPRE-FL) certification.
Is This Course Right For You?
This course is ideal for:
If you're new to this area, our Foundation-level courses are a better starting point than this Advanced-level course.
What You'll Be Able To Do
The IREB CPRE Foundation Level body of knowledge is standard-agnostic by design — it is the same discipline whether you build a mobile app or an ECU. What changes in an automotive organization is the context the requirements engineer must work within: the standards that shape what a requirement must demonstrate, and the stakeholders — often spanning an OEM and at least one Tier 1 supplier — who must agree it is correct before it can move forward.
- Understand the impact of requirement errors on project failure — and on vehicle and road-user safety.
- Learn the rationale for Requirements Engineering as a formal and systematic discipline.
- Learn various sources of requirements and techniques to capture the required information.
- Learn how to remove ambiguity in language.
- Understand how to record requirements.
- Examine the quality assurance aspects of the requirements and requirements documentation.
- Learn how to deal with disagreement on requirements and conflict resolution across OEM and supplier teams.
- Learn how to effectively manage the requirements, including traceability to safety goals and verification evidence.
How You'll Use This At Work
Common requirements engineering terminology across systems, software, safety, cybersecurity and program teams. Common quality criteria and review practices aligned to ISO 26262 and Automotive SPICE. Stronger OEM / Tier 1 requirements alignment and review discipline. Requirements validation and traceability practices that hold up under an ASPICE assessment or safety audit. Change and requirements governance appropriate to a V-model / safety lifecycle environment. Experience with AI-assisted Requirements Engineering, applied responsibly across a multi-supplier toolchain.
Curriculum
- What / Why / Where and How of Requirements Engineering
- The Role and Tasks of a Requirements Engineer
- The impact of requirement errors on project failure — and on vehicle and road-user safety
- Where Requirements Engineering fits within Automotive SPICE (ASPICE) and the ISO 26262 safety lifecycle
- The 9 Principles of Requirements Engineering
- Value-orientation while doing requirements engineering work
- Stakeholder centricity — including Functional Safety / Cybersecurity / Systems Engineering and the Tier 1 supplier
- Shared understanding across OEM / supplier / safety and regulatory teams
- Developing a solid understanding of context - including the Operational Design Domain (ODD)
- The intertwined triple Problem – Requirements – Solution
- Validation of Requirements
- Requirements evolution is reality — and what that means across vehicle platform variants
- Innovation — more of the same is not enough
- Systematic and disciplined work
- Sources for Requirements — HARA and safety goals / field data / regulatory requirements / prior-platform requirements
- The Practice of Elicitation of Requirements
- Requirements Elicitation Techniques
- Requirements Negotiation and Conflict Resolution — across OEM / supplier / safety / cost and schedule priorities
- Validation of Requirements
- Characteristics of Work Products
- Level of Detail — appropriate to the ISO 26262 Automotive Safety Integrity Level (ASIL)
- Aspects to be Considered in Work Products
- Documentation Guidelines
- Planning the Work Products to be produced
- Natural-Language-Based Work Products
- Template-Based Work Products
- Model-Based Work Products
- Making context / structure / flow and behaviour visible for an ADAS features
- Modeling Context — including the Operational Design Domain and system boundary
- Modeling Structure and Data — including sensor fusion data models
- Modeling Function and Flow — including decision logic flow
- Modeling State and Behaviour — critical for degraded modes / fail-safe and fail-operational states
- Importance of Glossaries in Requirements Engineering — and alignment across OEM / supplier and regulatory terminology
- Requirements Documentation Structures
- Prototypes in Requirements Engineering including Software-in-the-Loop (SIL) and Hardware-in-the-Loop (HIL) simulation
- Quality Criteria for Work Products and Requirements
- Influencing Factors while Selecting a Requirements Engineering Process and Working Structure
- Requirements Engineering Process Facets
- Configuring a Requirements Engineering Process — to align with Automotive SPICE (SYS.2 SWE.1) and the ISO 26262 safety lifecycle
- Purpose and Tasks of Requirements Management
- Life Cycle Management
- Version Control
- Configurations and Baselines — including variant management across vehicle platforms and trims
- Attributes and Views
- Traceability — from stakeholder requirement through safety goal to verification evidence
- Handling Change — including impact analysis on the safety case and supplier interface
- Prioritization
- Criterion for Selecting a Requirements Engineering Tool
- Introducing Tools — including integration across OEM and Tier 1 toolchains
How You'll Learn
Live Online • Classroom • Corporate / On-site Instructor-led sessions • automotive case studies • individual and group exercises • ReqDrive labs • exam preparation
Before You Start
- There are no prerequisites for this course, but some experience defining requirements — in automotive or another regulated, safety-critical environment — will be useful.
What You'll Get With Baseline Skills
- Certificate of Training Completion and verified insignia
- Comprehensive training material
- Exam preparation reference material with mock exams
- Complementary trial access to ReqDrive
Your Trainer
Surendra Saxena
Founder, ReqDrive, Baseline Skills
Surendra holds an MBA degree from FMS Delhi University and a Masters degree in Computer Science from IIT Roorkee. He brings over 40 years of experience in handling variety of assignments from software architecture design…
View Full ProfileLearner Experiences
No reviews yet.
Where Do You Go Next?
IREB CPRE Foundation Level (CPRE-FL)
From CPRE Knowledge to Requirements Engineering Capability. Learn the standard. Practise the skill. Apply it at work.
Learn MoreIREB CPRE Advanced Level — Requirements Elicitation
Deepen your elicitation practice — advanced stakeholder analysis, negotiation, and conflict resolution.
Learn MoreIREB CPRE Advanced Level — Requirements Modeling
Model requirements with precision using UML, BPMN, and goal-oriented notations.
Learn MoreChoose how you'd like to learn
| Delivery | Schedule | Price | |
|---|---|---|---|
| Corporate On-site | Custom | Pricing available on request | Request Corporate Training |
| Private Cohort | Custom | Pricing available on request | Request a Private Cohort |