Short, focused videos taking real software units from requirements to verified models — algebraic, logical, continuous and discrete systems, with static checks and requirements-based testing along the way.
⬇ Download Free TrialFree Trial · All Features · No Credit Card
You’ll build a complete thermodynamic system in Simulink, unit by unit: an algebraic temperature converter, logical and continuous units, and a discrete PI controller, integrated into one closed-loop simulation. Each unit is checked with EverCheck, tested against its requirements with EverTest and reviewed in EverView — and custom blocks and libraries make the design reusable. Warm up with the MATLAB training, then continue with Stateflow and ISO 26262 for Simulink.
Before starting, make sure MATLAB, Simulink and Simulink Coverage are installed on your own machine so you can follow the exercises hands-on, and that you have a stable internet connection to stream the videos — a second monitor helps keep the model and the video side by side. The chapter previews the full agenda: algebraic and logical systems, continuous and discrete systems, static checks, structural coverage, boundary values and verification reports. It closes with what the course builds toward — integrating all the units into a complete system and creating custom blocks and libraries for reuse.
Simulink lets you model the time-dependent mathematical relationships between systems, inputs, states and outputs. It supplies both discrete and continuous solvers, verification support such as structural coverage, and automatic C code generation for the production toolchain. This chapter sets out the path the course follows: designing algebraic and logical systems, then continuous and discrete ones, testing each software unit individually, and finally integrating them into a closed-loop simulation so you can develop complete systems rather than isolated blocks.
This chapter models and simulates different types of algebraic systems in Simulink, starting with the most common cases — linear and quadratic equations. Since the smallest unit of a Simulink block diagram is a single block, you implement the formula by adding, connecting and calibrating blocks drawn from the Simulink Library Browser. Mathematical expressions come first, then lookup tables as an alternative way to implement functions and linear equations. The chapter closes with algebraic loops: how they arise and how to avoid them.
In a production project, software unit development starts from a requirement, not from a model. This chapter defines the unit specification for a temperature converter (CNV) from Centigrade to Fahrenheit — a small unit implementing a single algebraic equation, which makes it an ideal running example for the rest of the course. You review the interfaces, the use case written in natural language and the requirement expressed in semi-formal notation, then set up the project folder structure that the later modeling, static analysis and verification chapters build on.
With the requirement in place, this chapter starts requirements-based modeling of the Temperature Converter (CNV) in Simulink, beginning with an orientation in the Simulink Library Browser. Gain, Add and Constant blocks implement the algebraic equation, and the result is wrapped in a Subsystem so the functionality can be tested as a unit. For simulation, a Ramp block generates a sweeping input signal and a Scope block displays the calculated output, giving you an immediate visual check that the converter behaves as the requirement specifies.
Static checks catch modeling errors early, before any simulation is run, which is where they are cheapest to fix. EverCheck provides the checks for static analysis in Simulink. After a run, you get detailed results with direct links to the non-compliant blocks or settings, and each finding must then be either fixed or justified. Most violations can be corrected automatically; for the remainder you review the violation and decide how to resolve or justify it. The resulting EverCheck reports serve as documentation evidence.
Where static analysis inspects the model at rest, dynamic analysis verifies it by running it. EverTest generates a test harness around the subsystem so it can be verified in isolation. Test cases are written manually or generated automatically from the predefined design ranges of the interface signals. You then debug the CNV model and analyze its dynamic behavior, with Simulink Viewers displaying the relevant signals graphically. Unique requirement IDs feed a requirements traceability matrix, and once expected results are defined, the verification report becomes the evidence artefact.
Lookup tables are a practical way to implement both linear and non-linear functions in Simulink. The breakpoints are mapped to the table values and can be ordinary MATLAB vectors, which keeps calibration data separate from the algorithm. Because results differ depending on the interpolation algorithm you choose, exact comparison is rarely the right test criterion: global settings in EverTest handle tolerances so a test passes when values fall inside the tolerance band. The chapter also shows how validating metamorphic relationships between inputs and outputs simplifies the test cases considerably.
Not a video — a live EverView export of the CNV test harness, the same model built and verified in the previous chapters. Open it full-page and navigate the hierarchy exactly as in Simulink: descend into subsystems, inspect look-up graphs, search the model and comment on selected areas. Because the export is a single self-contained HTML file, reviewers, suppliers and assessors can inspect the model in any browser, with no MATLAB installation or license. This is the review workflow the ISO 26262 course later formalises as independent model inspection.
Beyond the short concept videos, the course continues with longer, structured chapters — logical systems and execution order, continuous-time dynamics and solver choice, discrete and hybrid systems, and finally custom blocks and libraries for reuse across projects. Some chapters are password-protected; write to support@everbits.com to request access.
Ready for the next step? Continue with the training in Stateflow or ISO 26262 for Simulink.
Modeling a function for a production project and stuck on a solver, a subsystem boundary or a test harness? Write to us — you’ll reach an engineer, not a sales desk.
⬇ Download Free TrialFree Trial · All Features · No Credit Card
Or write to us at support@everbits.com