Trainings#

S-CORE offers hands-on trainings, which you work through in a GitHub repository, and self-paced interactive training portals.

Hands-on Trainings#

Unlike the training portals below, a hands-on training is a GitHub repository: you copy it into your own account and work through task issues, defect branches and prepared pull requests in a fictive S-CORE module.

Contributor Training

Build, review, fix and rebase in a module made from the S-CORE module template, with tracks for the quality, safety and security roles. Self-organised, without a tutor; the solutions are open. Ends with a certificate of completion, which is no Eclipse Foundation certification. Further tracks are planned.

Duration: about five working days
Stages: 7 (environment to formal review)
Tracks: quality · safety · security
Open Training Repository →

Training Portals#

Caution

THE CONTENT IS CREATED BY AI AND MAY CONTAIN ERRORS. THE CONTENT PURPOSE IS ONLY PROVIDED FOR VISUALIZATION AND DEMONSTRATION OF THE TRAINING PORTAL. PLEASE VERIFY THE INFORMATION BEFORE USE.

Human verification has NOT been performed to ensure the accuracy of the content, and the content may not be suitable for actual training purposes.

Self-paced interactive training portals for the Eclipse S-CORE process areas. Each portal is built from editable Markdown source files and rendered as a standalone HTML site with progress tracking and embedded quizzes.

Note

The portals open as self-contained HTML applications. Progress is saved locally in your browser — no server or login required.

Available Trainings (VISUALIZATION AND DEMONSTRATION PURPOSE ONLY)#

Requirements Engineering (VISUALIZATION AND DEMONSTRATION PURPOSE ONLY)

A focused 4-module training covering the S-CORE requirements engineering process: concepts, requirement levels, attributes, and workflows.

Duration: ~3.5 hours
Modules: 4 + Checkpoint Quiz
Standards: ISO 26262 · ASPICE SWE.1 · ISO/SAE 21434
Open Training Portal →

Training Source and Build#

Each training is maintained under process/trainings/<training_name>/source/ as editable Markdown files and rebuilt automatically whenever the documentation is built via bazel run //:docs.

To rebuild a specific training manually:

cd process/trainings/trainings_requirements_engineering/source
python build.py

Adding a new training#

  1. Copy the template from process/trainings/trainings_templates/content/ into a new trainings_<area>/source/content/ directory.

  2. Copy build.py, template.html, requirements.txt, and assets/ from an existing training source folder.

  3. Update the MODULES array in assets/app.js and the OUT path in build.py.

  4. Add a grid card above pointing to the generated portal.