Setting Up a Software Product Line Architecture Based on Zephyr

Setting Up a Software Product Line Architecture Based on Zephyr

Linux Foundation via YouTube Direct link

Proposals: Embrace Life REUSE Live REUSE includes topologies where the Zephyr repository is just another module in the workspace • Proposal The Zephyr document generation tools support workspace-leve…

17 of 24

17 of 24

Proposals: Embrace Life REUSE Live REUSE includes topologies where the Zephyr repository is just another module in the workspace • Proposal The Zephyr document generation tools support workspace-leve…

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Setting Up a Software Product Line Architecture Based on Zephyr

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Preface
  3. 3 What is a Software Product Line (SPL) Architecture?
  4. 4 A Software Product Line is NOT
  5. 5 Product Line Adoption and Institutionalization
  6. 6 Speaking from Experience
  7. 7 How Zephyr is being used as an SPL
  8. 8 Costs of a Software Product Line
  9. 9 SPL Core Asset Support: Architecture
  10. 10 SPL Core Asset Support: Software Components Must be designed to be general without a loss of performance must build in support for variation points
  11. 11 SPL Core Asset Support: Test Plans/Cases/Data Must consider variation points and multiple instances of the product line
  12. 12 SPL Core Asset Support: Tools and Processes Must be more robustan required for single product development
  13. 13 SPL Core Asset Support: Project Plans Must be generic or be made extensible to accommodate product variations
  14. 14 SPL Core Asset Support: People, Skills, and Training Must involve training and expertisecentered around the assets and procedures associated with the product line
  15. 15 Assessment: What is needed for SPL Best Practice? Starting with Zephyr v2.6.0 functionality • Embrace Extensibility . How is each aspect of the ecosystem impacted by module
  16. 16 Proposals: Embrace Extensibility (cont) MISRA Dir 3.1 (Required), states
  17. 17 Proposals: Embrace Life REUSE Live REUSE includes topologies where the Zephyr repository is just another module in the workspace • Proposal The Zephyr document generation tools support workspace-leve…
  18. 18 Proposals: Embrace Composability Composability means managing boards, drivers, and subsystems so that they can be assembled into a working device without requiring crafting or tuning
  19. 19 Multi-Project Integration Issues: Documentation
  20. 20 Multi-Project Integration Issues: Verification
  21. 21 Multi-Project Integration Issues: Implementation
  22. 22 Multi-Project Integration Issues: Design
  23. 23 Multi-Project Integration Issues: Requirements
  24. 24 Engineering, the Path Forward Software Product Line is the current best practice model for what we are trying to achieve with rouse of Copen source software in embedded systems.

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.