Short, focused videos taking a real thermostat unit from requirements to ISO 26262-ready verification — flow charts, graphical functions and finite state machines, with interactive EverView reviews along the way.
⬇ Download Free TrialFree Trial · All Features · No Credit Card
Follow one running example — a thermostat unit (TMS) — from requirements to ISO 26262-ready verification with EverTest. You’ll model flow charts and graphical functions, manage interfaces and data in the Model Explorer, and grow the design into a hierarchical state machine, then compare both modeling styles side by side in interactive EverView reviews. New to the tools? Start with MATLAB and Simulink; afterwards, ISO 26262 for Simulink is the natural next step.
How to use Flow Charts in Stateflow for production projects, including which features are recommended and which to avoid. Covers junctions and transitions, conditions and actions, handling interfaces and data, predefined flow patterns, and graphical functions — the building blocks you reuse across every model.
Software development in production projects starts from a clear set of unit requirements. Here we specify a thermostat (TMS) for a heating device — what it must sense, decide and actuate — and turn that into testable requirements. This running example carries through the rest of the course, from Simulink and Stateflow implementation to verification.
From the requirements we build a Simulink model for the thermostat. We set up the test harness and the test unit, separate the model under test from its environment, and prepare the infrastructure for test-driven development — the foundation the later verification and Stateflow videos build directly on.
We develop requirements-based tests and verify the thermostat unit in line with ISO 26262 Part 6 and Part 8. Working through several test cases, we exercise each requirement, achieve full structural coverage including MCDC, and produce the verification evidence — showing dynamic model analysis applied to a real unit rather than in the abstract.
With the requirements and Simulink implementation in place, we build the equivalent Stateflow model for the thermostat. We work through Stateflow Patterns, manage interfaces and data in the Model Explorer, and check model coverage during an equivalence comparison against the Simulink version — the same behavior, expressed as a state machine.
Not a video — a live EverView export of the thermostat (TMS) flow-chart harness built 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 unit in any browser, with no MATLAB installation or license required.
How to use Finite State Machines in Stateflow for production projects, with the recommended and prohibited features called out. Covers state transition rules, transition search order, the Stateflow action language and action rules, inner flow graphs, and events with temporal logic — everything needed to write state machines that stay maintainable.
Building a state machine in Stateflow looks straightforward — until the edge cases appear. Starting from a “perfect” model with full structural coverage, MCDC and green tests, we refactor a flow-chart design into a clean state machine step by step, keeping the exact same functional behavior while improving visual clarity and execution animation.
The state-machine counterpart to the review above — a live EverView export of the harness for the state-machine unit from the SF 14 chapters. Compare it with the flow-chart version: same interfaces, same requirements, different modeling style. Navigate the chart hierarchy, search the model and leave comments on specific areas, directly in the browser. This side-by-side review workflow is what the ISO 26262 course later formalises as independent model inspection.
Ready for the next step? Continue with the ISO 26262 functional-safety course.
Stateflow is the right tool when the behavior is driven by modes, events or decision logic: operating states, fault handling, task scheduling, protocol logic. Continuous signal processing and mathematical relationships stay in Simulink blocks. A common pattern is a Stateflow chart supervising the modes of a system whose dynamics are modeled in Simulink — the thermostat unit in this course is built exactly that way.
A flow chart has no memory: it evaluates its decision logic completely within one time step and always starts from the beginning. A state machine keeps an active state between time steps, so its output depends on history, not only on current inputs. The course models the same thermostat unit both ways — same interfaces, same requirements, different modeling style — and you can compare the two designs side by side in the interactive EverView reviews above.
The same way as any software unit: generate a test harness around the chart so it can be verified in isolation, derive test cases from the unit requirements, and measure model coverage — states, transitions and decisions, up to MCDC — to find untested logic. A tool like EverTest automates the harness generation, test execution and the verification report. The SF 13d chapter shows this workflow applied to the thermostat unit.
Yes — Stateflow is widely used in production safety projects. Modeling guidelines restrict the chart constructs to an analyzable subset, static checks enforce those guidelines, and dynamic verification with coverage provides the evidence. The ISO 26262 course covers the processes and work products; this course builds the modeling and verification skills they rely on.
Yes, the videos are free to watch and require no registration. The course is made for function developers who model decision logic and state-driven behavior for production projects. Working knowledge of Simulink is assumed — the MATLAB and Simulink courses are the recommended preparation.
Working through Stateflow on a real project and stuck on how a pattern applies? 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