Framework Architectures
summary
Framework architectures target tiny, battery‑constrained devices by trading off hardware cost for software complexity and by designing tight, reusable abstractions. The example family named base is five frameworks and four libraries totaling 437,000 lines of C++, with a 36,000‑line COM framework for local/remote ports and a 19,000‑line DMD data‑mirroring framework. Documentation uses arc42 and Q42 (160+ quality attributes) and emphasizes cross‑cutting concept chapters that capture domain abstractions; deployed examples include police‑car units with seven processors and distributed power‑station networks.
AI-written summary · about
chapters (14)
- 0:00Introduction by host
- 0:52Frameworks in embedded systems
- 3:05Libraries vs frameworks
- 6:22Why build custom frameworks
- 9:01Hardware constraints and costs
- 11:13Documenting frameworks with Arc42
- 14:50Example framework goals and stakeholders
- 17:28Framework quality and abstraction
- 19:41Building block view of Base framework
- 21:49Cross-cutting concepts in frameworks
- 23:59Communication abstraction in Com framework
- 25:09Data management with DMD framework
- 26:40Real-world applications using Base
- 28:11Summary and recommendations
related talks
47mEmbedded Systems Architecture
51mMicroProcess Architectures: Planning for Change, & Retaining Flexibility
11mBuilding an Architecture Documentation Framework from Scratch
31mScaleable Service Frameworks
13mTo Framework or Not to Framework? That is the Question
01h 01mClean Architecture
43mApplying architectural principles, processes, and tools
42mC4 — A Lightweight Approach to Documenting Architecture