Skip to content
Matthias Bohlen

iSAQB® CPSA Advanced Level Workshop

Evaluating software architecture

Reflect on your software architecture, find risks, make decisions easier. A two-day intensive workshop with Matthias Bohlen (20 CP for iSAQB® CPSA-A).

days
2
credit points
20
people max.
12
language
DE / EN
Book your seat ↓

Architecture evaluation: find chances to improve, track down risks, and gain confidence in your architecture decisions.

How you get started

In this seminar you learn basic techniques and methods to examine the solution approaches in your software system's architecture. With them you make decisive improvements, add extensions, or drop approaches for good reasons.

First you meet qualitative evaluation methods that you can use early in a project. They give you a quick start and encourage communication and transparency.

Then we discuss quantitative methods. They deliver measurements and give your teams up-to-date indicators of the quality of their work. That keeps architecture work on course, even in the sometimes hectic day-to-day of development.

In the workshop you learn how to reconstruct your existing solution approaches and reflect on the resulting architecture in in-house workshops. You gain insight into the trade-offs you made, the risks that remain, and the places where your architecture is sensitive to change.

iSAQB accredited training

Accredited training for the iSAQB® Certified Professional for Software Architecture, Advanced Level (CPSA-A). It counts for 20 credit points (20 methodical).

Content

  1. 01

    Basic conceptsthe basic concepts of software architecture evaluation

  2. 02

    Quality requirementsexamine, refine and describe them. How would you evaluate an architecture if you don't know what "good enough" means?

  3. 03

    Evaluation workshopsprepare and run them, with thorough methods such as ATAM and with lightweight, low-effort methods that suit an agile approach

  4. 04

    Follow-up and using the resultsturn what the workshops produce into something you can act on, instead of leaving it in a drawer

  5. 05

    Evaluating existing systemstools and approaches you should know for existing systems and parts of systems. Who still gets to work on a completely new system these days?

Who it's for

Software architects and developers who design or evolve systems. You should have experience in IT projects or product development. You don't need to know any particular technology or programming language to follow along. UML helps, but isn't required.

Prerequisites

Experience in IT projects or product development. No particular technology or programming language. UML helps, but isn't required.

What architecture evaluation does

Architecture evaluation is a shared look back at what your teams have built as the architecture of your software system:

  • Agile projects: use this practice to keep architecture work lean, iterative and focused on the quality goals.
  • Large and long-running projects: use it to direct the effort for reworking and maintaining the architecture to the right places in the system, where the costly problems are.

With architecture evaluation you uncover risks and bring more clarity to how you work and how you decide. You gain confidence in your architecture design and avoid setbacks.

Delivery

A balanced mix of talks and hands-on exercises. With my guidance, you learn in the group how to reflect on your software architecture, discover risks and prepare future decisions well.

Online

Since 2020 I've also taught ARCEVAL online, with Zoom (or Microsoft Teams if need be) as the video platform and Miro as an online whiteboard. I've set up a fully equipped video studio with professional broadcast hardware for it.

Book your seat

In-house for your company? Call +49 170 772 8545 or email mbohlen@mbohlen.de.