iSAQB EMBEDDED

This course prepares participants for the iSAQB Certified Professional for Software Architecture (CPSA-Advanced Level) certification. It focuses on the EMBEDDED module, teaching participants how to design safety-critical embedded systems, manage real-time requirements, and align software with overall system architecture.

Upon completing this licensed training, participants earn 30 credit points required for admission to the CPSA-Advanced Level certification exam. The points are distributed into two categories:

• Technical Competence: 20 points

• Methodological Competence: 10 points

Participants use these points to qualify for the final certification assignment. The credential verifies that a professional can independently design complex embedded systems that meet strict dependability standards. For full certification requirements, refer to the official International Software Architecture Qualification Board (iSAQB) curriculum.

The iSAQB EMBEDDED module balances theoretical principles with practical application to train software architects in building dependable systems. While individual training providers determine the exact teaching format, such as online or in-person delivery, lectures, hands-on labs, or case studies, the core curriculum remains standardized. Participants will learn specific methodologies for managing resource constraints, real-time processing, and functional safety.

Upon completion of the course, participants will be able to:

• Analyze impact factors specific to embedded systems, including dependability, hardware constraints, and hard or soft real-time requirements.

• Design architectures for safety-critical systems that comply with domain-specific standards like IEC 61508, ISO 26262, and ISO 62304.

• Apply real-time architectural design methods by selecting time-triggered or event-triggered approaches, mapping logical tasks, and configuring Real-Time Operating Systems (RTOS).

• Evaluate system residual risk and failure modes using quantitative and qualitative methodologies such as Failure Mode and Effects Analysis (FMEA) and Fault Tree Analysis (FTA).

• Implement specialized programming paradigms, including defensive programming, design by contract, and the robustness principle.

• Manage hardware and software variability across product lines using platform architectures and specific design patterns.

• Verify system correctness and reliability by defining processes for static analysis, dynamic analysis, and architecture simulation.