There Is Only One Time in Software (Language) Engineering!
summary
Claim: development and operation collapse into one continuous engineering time, so languages and toolchains must adapt at runtime. Implements ASOS (adaptive MSOS) compiled into the Seal framework to run MAP-K feedback loops, with formal checks for determinism/termination but noted limits. Prototypes adapt semantics for miniJava (loop perforation), a declarative HTML variant (image quality vs energy), and Robolang (time vs battery), and drives an engineering forge with TwinIt and an Airbus/Safran pilot toward digital twin-driven, feedback‑based optimization.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:26Defining time in software
- 3:12Development and operation time continuum
- 5:26Runtime as cross-cutting
- 7:37Application vs domain engineering
- 10:04Subcommunities and Conway's law
- 13:14Hyper agility and evolving reqs
- 16:42Continuous software vision
- 19:52Software language engineering role
- 21:58Self-adaptable languages and ASOS
- 24:03Adaptive semantics with ASOS
- 27:17ASOS meta model and Seal
- 30:07Case studies: MiniJava, HTML, Roblong
- 32:16Engineering abstractions
- 33:21Abstraction challenges
- 36:58Hybrid and adaptive modeling
- 38:42Deep variability spaces
- 41:58Continuous dev environments
- 44:04Integrated dev environments
- 45:50Engineering forge for CSE
- 47:13Digital twins in dev
- 50:06Future of IDEs as twins
- 51:32Conclusion
related talks
58mSoftware Engineering Languages
35mCraft, Engineering, and the Essence of Programming
01h 00mEngineering Software
35mSoftware Engineering - Development in 100 Years Time
58mIs Software Engineering Still an Oxymoron?
12mTowards Self-Adaptable Languages
53mSoftware Design: Beyond Boxes & Lines
50mSoftware Is Details