Embedded Systems Architecture
summary
Uses the arc42 template, Enterprise Architect and Confluence to document a vehicle-mounted Traffic Pursuit System that combines seven hardware boards and processors with ~200k LOC C++ (20 person‑months hardware, 40 person‑months software). Architecture decisions map deployment-driven hardware partitions to software components; runtime scenarios show asynchronous messaging and an event broker. Measurements achieve higher precision than roadside radars after iterative calibration (initial deviations ~40% reduced and later certified by Swiss authorities). Emphasizes accuracy, robustness, ease of use.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:50Overview
- 5:35Requirements Overview
- 9:05Setting Context
- 13:05Deployment View
- 15:20Building Block View
- 18:27Hardware Codec
- 20:04Domain Terminology
- 21:54Runtime View
- 26:05Measurement Propagation
- 27:21UML Activity Diagram
- 29:30Sequence Diagram
- 30:36Activity Diagram
- 33:25Crosscutting Concepts
- 35:36Event Handling
- 36:25Event Sources Event Brokers
- 38:15Architectural Decision Records
- 40:01Further Resources
- 41:42Conclusion
- 43:20QA
related talks
39mSoftware development challenges in automotive projects
29mFramework Architectures
06mEmbedded Executive LIVE
20mDriving Intelligence: The Software Shift Shaping Tomorrow’s Cars
50mMoving Security Architecture from Art to Engineering
14mPANORover: Autonomous Driving System Development Platform
44mHandling Complexity in Software Development Projects
21mAPP4MC RaceCar: A Practical ADAS Demonstrator for Evaluating and Verifying Timing Behavior