Here you find an extract of the method - the most essential patterns and practices.




find problems, risks, deficiencies and technical debt within your system and your development process.
systematically improve code and structures, reduce technical debt, remove waste and optimize.
solve issues, refactor, re-architect, re-structure,
renew, migrate, cleanup
understand root-causes of problems
determine „value“ of: problems, issues and their remedies
prioritize topics and issues - identify low-hanging fruit.

  • Qualitative analysis (similar to the first phases of ATAM)

  • Stakeholder interviews to find pain-points of all kinds

  • Quantitative and structural analysis (e.g. with SonarQube or similar tools)

  • Runtime analysis, e.g. performance, memory, threads, server- and resource utilisation.

  • Software Archaeology - understand software by reading code and its version history.

  • View-based documentation to identify appropriate change candidates and determine potential consequences.

  • Determine long-term change/migration strategy.

  • Decouple data from logic..

  • Insulate changes.

  • Create change-clone

  • Differentiate symptoms and reasons

  • Estimate business value (in terms of money) of issues found during analysis

  • Propose potential remedies for issues found.

  • Estimate cost and risk of remedies.

© 2013-2014 Dr. Gernot Starke Kontakt