iSAQB CPSA-A ADOC

Beschrijving

Attending the iSAQB® CPSA-A Architecture Documentation (ADOC) course gives participants 20 Methodological Competence (MC) points towards the 70 points required for eligibility to take the iSAQB CPSA-A exam with Brightest. It is important to remember that as part of the 70 points required to take the iSAQB CPSA-A exam with Brightest, you will need at least ten competence points in each of the following areas: 

• Technical Competence (TC)
• Methodological Competence (MC)
• Communicative Competence (CC)

Accredited iSAQB® ADOC - Architecture Documentation (CPSA-A) training is based on the current iSAQB® curriculum:

Part 1 - Basic concepts of software architecture documentation

• Description and convincing representation of the architectural documentation
• Explanation of the importance of architectural documentation for different stakeholders
• Be able to name typical records for architectural documentation
• Be able to designate concrete process models regarding architecture documentation

Part 2 - Documentation and procedure

• Determine the purpose of groups and the purposes of documentation
• Building new systems
• Progress of existing systems with existing documentation
• Documentation of existing systems without existing documentation
• Documentation in exceptional situations (little time, little budget, little available information, sources, etc.)
• Discuss the benefits of fixed divisions and structures for documentation

Part 3 - Components of architectural documentation

• Further development of existing architecture documentation
• Identify and appropriately document factors that influence software architecture (boundary conditions, quality purposes, technical risks)
• Capture architectural decisions in an understandable way
• Generate technical or general concepts appropriate to the target group
• Structure components in documents

Part 4 - Tools

• Choosing the right tools for the respective activities
• Use analogue and digital documentation tools

Part 5 - Rate documentation

• Distinguish between the content of an architectural document and a formal assessment
• Separating the review of a document from the assessment of the architecture
• Select, plan, and execute for appropriate review steps

Part 6 - Examples for the documentation of software architectures

• Explanation of how the systematic documentation was changed
• In the example, your strengths and weaknesses from the model presented