2,573 $
excl. VATWhat this module delivers.
How the training runs
- Method
- Current-state analysis, cost calculation and rebuild planning on a real example system
- Basis
- Official iSAQB curriculum 1.6.1, English only
- Outcome
- 30 credit points: 20 methodical, 10 technical, no course exam
Dates & booking
Choose a date that fits
6 dates
Sessions with this symbol offer up to 25% group discount. Click “Details & Registration” to learn more.
2,866 $−287 $2,579 $
2,866 $−287 $2,579 $
2,866 $−287 $2,579 $
2,573 $−257 $2,316 $
2,866 $−287 $2,579 $
No dates match this selection.
Dates are still available. Reset the filters to see them.
Fit
Who this module is designed for
Typical roles
- You own a system that has been running for years and still has to grow.
- You have to justify a rebuild to the people who hold the budget.
- You decide between improving step by step and rebuilding from scratch.
Prerequisites
No prerequisites
You can start right away. Helpful: hands-on experience maintaining and evolving existing systems, working with the source code of medium to large systems, some experience with refactorings and code metrics.
Consider instead ARCEVAL Runs evaluation procedures such as ATAM, CBAM and DCAR across 570 minutes and stops at the findings, without planning what they cost or how they get implemented.
Curriculum
CPSA® IMPROVE Course in Detail
Curriculum 1.6.1 splits IMPROVE into six parts across 1080 teaching minutes. It starts at technical debt, runs through current-state analysis and economic assessment to long-term planning and the rebuild techniques themselves, and closes on a real example system. The official document is published in English only.
01Foundations of Improvement and Evolution
The first part settles what the rest of the training is talking about.
- Change, evolution and maintenance as distinct jobs
- Recognising technical debt and classifying it by cause
- Reasons for change: features, quality requirements, context shifts, cost pressure
- Ad-hoc change, refactoring, re-architecting and rewriting compared
02Analyse Current State
This part keeps finding problems strictly apart from solving them.
- Stakeholder analysis and interviews as a source of weaknesses
- Contextual analysis: system boundaries and external interfaces
- Qualitative procedures including ATAM
- Quantitative procedures: code, organisational and runtime metrics
03Estimate and Assess Problems and Solutions
Here every finding gets a price and every solution a counter-value.
- Direct costs, capital expenditure (CAPEX) and operating expenditure (OPEX)
- Run-the-company against develop-the-company
- Return on investment, break-even and depreciation
- Estimating as an interval rather than a single figure: best, average, worst case
04Long-Term Planning of Improvements
Individual measures become a strategy spanning several releases.
- Documenting assessed problems and solutions explicitly
- Clusters, dependencies and m:n relations between problems and approaches
- Application strangling and encapsulating risk as a black box
- Weighing a rewrite against continuous improvement
05Typical Approaches to Improvement
At 360 minutes this is the largest part of the curriculum: the work itself.
- Semantics-preserving refactorings and how they relate to technical debt
- Reducing coupling: modularisation, dependency injection, adapter, wrapper, gateway
- Clean-code principles for comprehensible source code
- Automated testing, continuous integration and continuous delivery
06Examples of Improvement
To close, one real system runs through the whole cycle once.
- System scope, quality goals and usage scenarios of the example
- The problems found in it and how they were assessed
- Short, mid and long-term planning on the concrete case
- Stated by the curriculum to be not examinable
Outcome
What you will be able to do afterwards
- 01
You classify technical debt and separate it from new functional requirements.
- 02
You establish the current state from stakeholder interviews, documentation and runtime measurements.
- 03
You read structural weaknesses out of metrics for coupling, complexity and cohesion.
- 04
You put a figure on problems and solutions in CAPEX, OPEX and return on investment.
- 05
You estimate effort as an interval with best, average and worst case instead of a single figure.
- 06
You group individual findings into an improvement strategy spanning several releases.
- 07
You retire legacy systems through application strangling and encapsulate risks as a black box.
- 08
You reduce coupling through refactoring, dependency injection, adapters and gateways.
Credit points toward CPSA-A
- Methodical competence
- 20
- Technical competence
- 10
- Communicative competence
- 0
30 of 70 points toward CPSA-A admission
Certificate of participation
The tecnovy certificate of participation records your attendance of the IMPROVE training, not a passed examination.
Open the Certificate Showroom tecnovy →≥80%attendance
Why tecnovy
What you get on top with us
01
iSAQB® Accredited Provider
We are an officially accredited Training Provider of the International Software Architecture Qualification Board.
02
Certificate Showroom
Get your certificate of participation and, if you have one, add your exam certificate from E-Learning. Fully automated, beautifully designed. Just for you, only at tecnovy.
03
No Slideshow, Hands-On!
Promised: no PowerPoint marathon. We work in groups, tie theory to practice, and you get real project examples from our experienced trainers plus the exchange with like-minded people.
04
Attend Twice, Pay Once
You are welcome to attend the training online again within a year as a refresher.
05
Learn from Authors
Your instructors are not just trainers, but the authors of the preparatory literature for the iSAQB CPSA-F certification exam and at the same time an active member of the iSAQB Foundation group.
06
Flexible Date Change
If you are not able to attend the course, you can rebook your training free of charge up to one week before the start of the training.
Experiences
What participants say
I took the iSAQB IMPROVE course because in most larger companies there is not only new development; the greater part of the software already exists. On top of that, the course was taught by Dr. Gernot Starke, a leading authority in the field. The course itself was very interesting, instructive and a long way from death by PowerPoint
FAQs
