An Interdisciplinary View on Prototypes - Towards Executable Models That Can Be...
summary
Argues that executable statecharts become the single source of truth by generating visual diagrams from code and vice versa, and shows a working editor that live-updates ASTs to keep flowcharts, docs and implementation in sync. Describes a pharma clean‑room VR training project where statechart simulations replace brittle flowcharts and reduced miscommunication. References XState/Stately, SCXML and a custom StateML experiment, and proposes hole-driven models so stakeholders can collaboratively fill behavior gaps while the model remains executable and verifiable.
AI-written summary · about
chapters (13)
- 0:00Introduction to talk
- 1:12Explaining state machines
- 2:17Orienteering as software analogy
- 11:24What are prototypes?
- 13:27Problems with evolutionary prototyping
- 17:43Understanding models
- 19:28Executable models in practice
- 23:01State charts as single source of truth
- 27:12Collectively building systems
- 31:47Views and stakeholder communication
- 34:36Future of interactive prototypes
- 37:24Summary and closing
- 38:48Q&A: Modeling for prototypes
related talks
27mOperationalizing the Integration of User Interaction Specifications in Modeling Editor Synthesis
29mQ: A Sound Verification Framework for Statecharts and Their Implementations
39mDiagrams as Code 2.0
35mThe holy war of modeling notations - what fits best and why?
34mDiagram as Code - Decoding Architectural Diagrams
01h 09mSCCharts Twelve Years Later: A Reflection on Sequential Constructiveness and(…)
29mTaming the Circus: The Future of Power System Planning Model Interoperability
02mMike Wojtynac at DDD Europe 2025