Metrics for Software-Architects

Alexander von Zitzewitz (hello2morrow)

3:50pm–4:40pm Wednesday, February 26, 2020

Location: Murray Hill

Fundamentals

Secondary topics: Best Practice, Theoretical

Average rating:

(5.00, 2 ratings)

Download slides (PPTX)

Who is this presentation for?

Software architects, lead developers, project owners

Level

Intermediate

Description

Software metrics can be used effectively to judge the maintainability and architectural quality of a code base. Even more importantly, they can be used as canaries in a coal mine to warn early about dangerous accumulations of architectural and technical debt.

I will introduces some key metrics that every architect should know (e.g., average component dependency, propagation cost, structural debt index, and more). Then he talks about the journey to create a metric to measure maintainability and introduces a new metric maintainability level. This metric is promising because its value usually matches quite well the gut feeling of developers about the maintainability of their software systems. Therefore, it can be used to monitor code maintainability and as an early warning indicator if things move in the wrong direction.

Prerequisite knowledge

Some experience with nontrivial software projects.

What you'll learn

Learn how to use metrics to judge maintainability and technical quality.

Alexander von Zitzewitz

hello2morrow

Alexander is co-founder and managing director of hello2morrow and CEO of the US subsidiary. He has more than 25 years of project and manangement experience. In 1993 he founded ootec – a company focused on project services around object oriented software technology. In March 2000 this company was sold to Valtech group, a French company, and served customers like Siemens, BMW, Thyssen-Krupp-Stahl and other well known names in German industry. From 2003 to early 2005 he worked as company Director for Central Europe for a French software vendor.

Alexander has a degree in Computer Science from Technische Universität, Munich.