Description
Attending the iSAQB® CPSA-A Evolution and Improvement of Software Architectures (IMPROVE) course gives participants 20 Methodological Competence (MC) and 10 Technical Competence (TC) 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® IMPROVE - Evolution and Improvement of Software Architectures (CPSA-A) training is based on the current iSAQB® curriculum:
Part 1 - Introduction of Software Architecture
- Definition of software architecture
- Software architecture goals
- Advantages of software architecture
Part 2 - Requirements
- Interaction of quality requirements
- Functional and quality requirements
- Scenarios of quality
Part 3 - Architecture Documentation
- Estimates and potential risks
- Documentation purposes
- Black box and white box
- Architectural aspects
- Documentation template and frameworks
Part 4 - Architecture Layout
- Architectural procedures
- Tools
- Architectural principles: coupling, cohesion, S.O.L.I.D, etc.
Part 5 - Solution Strategies
- Architectural models
- Architecture analysis
- Postel's law
- Architectural decisions
Part 6 - Architectural Evaluations
- Code analysis
- Quantitative and qualitative evaluations
Target Audience
The CPSA-A Enterprise Architecture Management seminar is particularly valuable for professionals who want to address typical strategic and tactical approaches to improving existing systems.
Requirements
To join any iSAQB® CPSA - Advanced Level course, you must hold the iSAQB® Certified Professional for Software Architecture - Foundation Level (CSPA-F) certificate.
Knowledge prerequisites:
Participants should have the following prerequisite knowledge:
- Hands-on experience in design and development of small to medium-sized software systems
- Some hands-on experience in maintenance and evolution of a software system
- Some hands-on experience with the handling of source code of medium to large-scale systems, in particular analysis, assessment, quality check, refactoring, and applying metrics
Knowledge in the following areas may help understand some concepts covered in this course:
- Knowledge and hands-on experience with refactoring
- Knowledge or some hands-on experience with review and evaluation of software:
- Basic knowledge about software metrics, such as metrics to measure coupling, cohesion, dependency, and complexity
- Basic understanding of software run time analysis, such as profiling, tracing, log analysis, and data analysis
- Basic knowledge and some experience with the estimation of development efforts
- Some hands-on experience with requirements engineering and contact with various stakeholders in development projects
- Some hands-on experience with analysis of development processes
Syllabi and sample exams coming soon!
Syllabi and sample exams coming soon!
