Architecting an IoT Product Line: Part 1 - Scoping
summary
Argument: apply the ISO product-line model to IoT and Zephyr and show concrete mappings and decisions. Uses ISO/IEC/IEEE 26550 as the scoping model, identifies common vs variable features, and maps domain assets to Zephyr pieces like the build system, Kconfig and Twister, example app repos and manifests. Cites an HP printer product line that evolves four generations and a reference to 200 firmware images as a classifier. Calls out a missing controlled shutdown facility and shows reuse succeded after refactoring.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:50Agenda
- 7:23Product Line Terminology
- 8:30Terminology
- 19:24Scope of the Problem
- 20:47Defining the Problem Space
- 22:02How the System Is Going To Get Decomposed
- 22:46Product Line Does Not Mean that It Has To Cover Everything
related talks
53mField Report: Setting up a Software Product Line (SPL) Architecture based on Zephyr
40mHow I Fell in Love with Zephyr – a System Architect’s Tale
16mKeynote: The Rise of Frameworks in Zephyr: From Devices to Subsystems to Frameworks
53mBridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded...
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
15mLightning Talk: A Reusable Zbus Based Architecture, Abstracting Core Application Components
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded De...