CDO-LM: A Module System for Models
summary
A module system built on CDO and EMF that uses P2 to resolve version ranges at checkout and produces an assembly (P2 profile) that maps each module name to a concrete CDO view and timestamp. Each module lives in its own CDO repository with a required module manifest file, the system repo records modules, streams, changes, deliveries and fixed or floating baselines. Demo shows creating modules, tagging a baseline, bumping a version, automatic live update of dependent models, conflict detection by P2, and practical scale of thousands to tens of thousands of EMF objects.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:22AMS Tool Context
- 8:48Motivations - Use Case
- 12:40Module Repository
- 13:27Module Definition
- 14:04System Repository
- 17:54Repository Management
- 18:58Putting It All Together
related talks
53mCrafting a self-documenting Modular Monolith with DDD principles (theory not included)
28mLooking Backwards and Forwards at CDM:...
44mOpenMDM - Data Management for SDV
41mA Modular Compositional Approach to Engineering Complex Systems
45mDomain Driven Modular Architecture
15mEuroCDP: the open branch
47mGetting modules right with Domain-driven Design
43mMonoliths to Modular: Navigating the Transition