Postgraduate DiplomaAutomotive & Motorsport Applications open

Postgraduate Diploma in Versioning, Testing and Security of Toolchains

Online 800 h Postgraduate Diploma in Versioning, Testing and Security of Toolchains. 8 modules covering ISO 26262-8, ISO/SAE 21434 and Git. Assigned tutor and enrolment open.

Duration800 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Virtual lab · try it before you enrol

Take the controls.

Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.

SIM · LIVE ●
Learning outcomes

What you will be able to do

01

Analyse engineering toolchains in competition.

02

Apply version control to code, data and models.

03

Design testing strategies for engineering software.

04

Implement continuous integration and continuous delivery.

05

Protect the software supply chain.

06

Apply cybersecurity in the racing environment.

07

Govern and improve development processes.

Profile

Who it's for

  • Engineering software engineer seeking to specialise in Versioning, Testing and Security of Toolchains.
  • DevOps engineer seeking to specialise in Versioning, Testing and Security of Toolchains.
  • Cybersecurity manager seeking to specialise in Versioning, Testing and Security of Toolchains.
  • Software quality engineer seeking to specialise in Versioning, Testing and Security of Toolchains.
  • Tools engineer seeking to specialise in Versioning, Testing and Security of Toolchains.
  • Systems engineer seeking to specialise in Versioning, Testing and Security of Toolchains.
  • Graduates in engineering or sciences seeking to enter motorsport.
Standards & tools

What you'll work with

  • ISO 26262-8
  • ISO/SAE 21434
  • ISO/IEC 27001:2022
  • IEC 62443-4-1
  • ISO/IEC/IEEE 29119-1
  • ISO/IEC/IEEE 12207
  • NIST SP 800-218
  • MISRA C:2012
Syllabus

8 modules · 800 h

  1. 1.1Simulation, data and calibration tools
  2. 1.2Engineering software lifecycle
  3. 1.3Risks of uncontrolled tools
  4. 1.4Tool qualification under ISO 26262
  5. 1.5Tool inventory
  6. 1.6Dependencies and versions
  7. 1.7Development environments
  8. 1.8Team responsibilities
  9. 1.9Software engineering good practice
  10. 1.10Case study: a team's toolchain inventory
  1. 2.1Commit model and Git repositories
  2. 2.2Branching strategies
  3. 2.3Code review and pull requests
  4. 2.4Versioning of data and models
  5. 2.5Git LFS for large files
  6. 2.6Semantic versioning of tools
  7. 2.7Release tagging
  8. 2.8Conflict management
  9. 2.9Change traceability
  10. 2.10Laboratory: branching workflow with Git
  1. 3.1Unit testing of calculation functions
  2. 3.2Integration testing
  3. 3.3Numerical regression testing
  4. 3.4Tests with reference data
  5. 3.5Code coverage
  6. 3.6Performance testing
  7. 3.7pytest and unittest frameworks
  8. 3.8Testing simulation models
  9. 3.9Testing calibrations
  10. 3.10Practice: test suite with pytest
  1. 4.1CI pipelines
  2. 4.2Build automation
  3. 4.3Containers with Docker
  4. 4.4Continuous deployment of internal tools
  5. 4.5Test environments
  6. 4.6Artefact management
  7. 4.7Code quality with SonarQube
  8. 4.8Static analysis of Python code
  9. 4.9Quality metrics
  10. 4.10Workshop: CI pipeline with GitLab
  1. 5.1Threats in the software supply chain
  2. 5.2Management of vulnerable dependencies
  3. 5.3SBOM and transparency
  4. 5.4Code and artefact signing
  5. 5.5Secrets management
  6. 5.6Access control
  7. 5.7Security in vehicle cybersecurity
  8. 5.8Protection of intellectual property
  9. 5.9Incident response
  10. 5.10Case study: compromised dependency
  1. 6.1Garage and factory networks
  2. 6.2Telemetry security
  3. 6.3Device security
  4. 6.4Identity management
  5. 6.5Network segmentation
  6. 6.6Security monitoring
  7. 6.7Staff awareness
  8. 6.8Regulatory and contractual compliance
  9. 6.9Security audits
  10. 6.10Practice: garage network risk assessment
  1. 7.1Development policies and code review
  2. 7.2Technical documentation of tools
  3. 7.3Change management for critical tools
  4. 7.4Software process audits
  5. 7.5DORA delivery indicators
  6. 7.6Software engineering training
  7. 7.7Software supplier management
  8. 7.8Maturity models such as Automotive SPICE
  9. 7.9Continuous improvement roadmap
  10. 7.10Case study: process maturity assessment
  1. 8.1Tool inventory
  2. 8.2Versioning strategy
  3. 8.3Test suite
  4. 8.4CI/CD pipeline implementation
  5. 8.5Security measures
  6. 8.6Risk analysis
  7. 8.7Governance plan
  8. 8.8Final system evaluation
  9. 8.9Report and presentation
  10. 8.10Final review with the tutor
Methodology, software & labs

How you'll learn

Fully 100% online training on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. There are no fixed timetables: students progress at their own pace within the intake, which makes it possible to combine study with work.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is Git, GitLab CI, Docker, SonarQube, pytest, in free, academic or evaluation versions. Case studies are based on real procedures for implementing CI pipelines in engineering tools, security audits of the supply chain and numerical regression testing. Assessment is continuous by module, plus the final integrating project.

Accreditable laboratories(EN ISO/IEC 17025) with rotor rig, EMC/Lightning pre-compliance, HIL/SIL, vibration/acoustics.
Evidence-oriented final project:safety case, test plan, compliance dossier and operational limits.
Industry mentoring:faculty with track records in training, , eVTOL/UAM and flight test.
Flexible format(hybrid/online), international cohorts and support from SEIUM Career Services.
Ethics and safety:a safety-by-design approach, with ciber-OT, DIH and compliance as its pillars.
Capstone project

Build it end to end

Your final project follows the real engineering workflow, step by step, reviewed by your tutor.

Tool inventory

Analyse engineering toolchains in competition.

Versioning strategy

Apply version control to code, data and models.

Test suite

Design testing strategies for engineering software.

CI/CD pipeline implementation

Implement continuous integration and continuous delivery.

Security measures

Protect the software supply chain.

Career opportunities

Where this takes you

Engineering software engineerDevOps engineerCybersecurity managerSoftware quality engineerTools engineerSystems engineer
Admissions & scholarships

Requirements

  • Prior technical training or professional experience in the sector. A university degree is not required.
  • Internet connection and a computer capable of running the programme's software.
  • Sufficient Spanish to follow technical standards documentation.

Ready to start?

Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.

FAQ

Frequently asked questions

The programme consists of 800 hours in total, spread over 6 to 8 months. That is an average of 10 to 15 hours per week, compatible with a full-time job.

You work with Git, GitLab CI, Docker, SonarQube and pytest. Free, academic or evaluation versions are used, and the tutor indicates the free alternative when one exists.

An own diploma from SEIUM upon passing the continuous assessment and the integrating project. This is in-house training, not an official qualification from the Ministry.

Yes. Modules passed in a course or postgraduate diploma in the same area can be credited towards the higher programme. Check the credit recognition policy when you enrol.

Postgraduate Diploma in Versioning, Testing and Security of ToolchainsEnrol
Scroll to Top
SEIUM – Institute of Advanced Engineering
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.