Skip to content

The systematic improver [How-to guide for software architects]

Demands for an improvement of software often are the result of the excessive cost of changes or exten­sions – as our client (motivated by technical or business matters) often shows only little interest in the innate quality of systems. That is why changing software for the better proves to be a laborious process in most instances, which you will have to tackle system­at­i­cally and step by step.

by Gernot Starke and Peter Hruschka

Read the article here .

Share this article:

Stay Up-to-Date with the iSAQB® Newsletter!

Scroll To Top