Agile Model-Based Software Development

2 days


Date Location Language
Nov 26–27, 2020 Online
Oct 7–8, 2021 Online

More dates and in-house training classes available worldwide on request:


Model-based software development has become state of the art for automotive embedded applications. Toolchains have been established, and methods and procedures have been defined to address the strong requirements of functional safety standards. Best practices within general software development, however, propose to overcome strict waterfall process models and promote agile methods in order to address real-world challenges, such as late changes or vague requirements. These real-world scenarios exist in automotive software development, and agile methods will also be beneficial here. This training class introduces the basic principles of agile methods and elaborate on their instantiation in model-based development. The class assists participants in gaining first-hand experience in agile methods, and participants will apply some of these methods in live sessions.

Target Audience

This training class is targeted at modelers, developers, testers, quality managers, project managers, and team leaders, who want to familiarize themselves with agile methods and how agile methods comply with model-based development of embedded software based on MATLAB/Simulink and similar.


  • Principles of model-based development with Simulink/Stateflow
  • Core concepts of agile methods like Kanban or Scrum
  • Foundations of agility in model-based development
  • Elements of continuous quality assurance
  • Approaches to continuous integration
  • Agility as viewed by either: ISO 26262 or ASPICE
  • Interactive parts that properly reflect real team situations

Fees, Terms & Conditions

Agenda - Day 1

10 a.m. Welcome and introduction round
  • Expectations and background of participants
  • Overview of the different slots
  • 10:30 a.m. Introduction: Agile approaches to model-based software development
  • Motivation for model-based software development
  • Why agile? Agile Manifesto and principles
  • Myths and more (interactive)
  • Typical approaches to agility: Kanban, Scrum, etc.
  • 12 p.m. Lunch break and open dialog
    1 p.m. Core elements of Scrum
  • Development objectives: Backlog, epic, user story, task
  • Timing: Sprint and the related events
  • Roles: Product Owner, Scrum Master, Team
  • Quality Gates: Definition of Ready (DoR), Definition of Done (DoD)
  • Alignment with Kanban
  • 2:30 p.m. Short break
    2:45 p.m. Overview: Model-based development and quality assurance with Simulink
  • Basic concepts of model-based development
  • Overview of development and safeguarding activities
  • Boundary conditions for safety-critical systems
  • Samples of quality assurance methods such as static and dynamic model analysis
  • 4:15 p.m.Short break
    4:30 p.m. Scrum in a nutshell (interactive)
  • Introduction
  • Sprint 1
  • Sprint 2
  • Assessment
  • 6 p.m. End of day

    Agenda - Day 2

    9 a.m. Model decomposition and integration
  • Distributed modeling
  • Implementing software architectures in models
  • Analysis and evaluation of model structure

  • Hands-on: Analysis of model structure
    10:30 a.m.Short break
    10:45 a.m. Refactoring Simulink models and their structure
  • Modeling styles facilitating refactoring
  • Basic refactoring operations for Simulink
  • Complex refactoring operations

  • Hands-on: Using a model refactoring tool
    12:15 p.m. Lunch break and open dialog
    1:15 p.m. Core elements of continuous integration
  • Basics concepts of continuous integration
  • Definition of integration jobs
  • Jenkins as state-of-the-art platform
  • MES tool plugins for Jenkins, including the use of MES Quality Commander as quality dashboard
  • Challenges regarding a continuous integration for model-based development
  • Experience report: Validation suite for the MES Model Examiner
  • 2:45 p.m. Short break
    3 p.m. Optional topics
  • Ensuring model quality with modeling guidelines (incl. hands-on)
  • Ensuring model quality with model testing
  • Definition of Done in model-based software development
  • Automotive standards (ISO 26262 and ASPICE 3.x) on agility
  • 4:30 p.m. Wrap up of the event
    5 p.m. End of training class