S-CORE Requirements Engineering
A focused, self-paced training on the Requirements Engineering process area of the Eclipse S-CORE Process Description, covering its concepts, roles, workflows, work products, and practical application in safety- and security-critical automotive open-source software development.
| Duration | ~3.5 hours |
| Structure | 4 Modules + Checkpoint Quiz |
| Format | Self-paced |
| Standards | ISO 26262 · ASPICE SWE.1 · ISO/SAE 21434 · ISO PAS 8926 |
Modules
| Module | Title | Description | Duration |
|---|---|---|---|
| Module 1 | Why Requirements Engineering? | Role of RE in safety-critical OSS, stakeholders, roles, and how standards drive the process. | ~30 min |
| Module 2 | Requirement Levels and Types | The five requirement levels (Stakeholder, Feature, Component, AoU, Process), types, and their traceability relationships. | ~45 min |
| Module 3 | Requirement Attributes and Quality | Mandatory and auto-generated attributes, formulation rules, versioning, and reviews. | ~45 min |
| Module 4 | Workflows and Work Products | The six S-CORE workflows, work products with compliance tags, and end-to-end traceability. | ~45 min |
Checkpoint Quiz — All Modules 10 questions covering all four modules. Pass mark: 70%. Instant scoring with explanations. (~20 min)
About This Course
This training is based on the Eclipse S-CORE Process Description — specifically the Requirements Engineering process area — and the applicable standards it implements: ISO 26262 (Part 8), ASPICE PAM 4.0 (SWE.1), ISO/SAE 21434, and ISO PAS 8926.
It is intended for anyone contributing to or reviewing requirements in an S-CORE-compliant project: developers, architects, safety managers, security managers, quality managers, and testers.
Work through the modules in order. Each module ends with a short three-question check-in. After completing all four modules take the Checkpoint Quiz. Your progress is saved in your browser — no server required.
Learning Objectives
After completing this training you will be able to:
- Explain the role of structured requirements engineering in safety- and security-critical automotive software
- Name all stakeholders and identify their information needs in an S-CORE project
- Distinguish the five requirement levels and select the correct one for a given situation
- Write well-formed requirements that satisfy the mandatory attribute set
- Apply S-CORE versioning rules and identify when a version bump is required
- Trace requirements from stakeholder level through code and tests using the S-CORE workflow