What is the most effective way to measure technical architecture?

1 Define quality attributes

Quality attributes are the characteristics of a system that are important for its stakeholders, such as users, developers, testers, managers, or customers. They can be divided into two categories: external and internal. External quality attributes are visible to the users and affect their satisfaction and experience, such as usability, availability, responsiveness, and scalability. Internal quality attributes are visible to the developers and affect their productivity and efficiency, such as modularity, cohesion, coupling, testability, and reusability. You should define the quality attributes that are relevant for your system and prioritize them according to their importance and impact.

2 Use metrics and indicators

Metrics and indicators are quantitative or qualitative measures that can help you assess the quality attributes of your system. They can be based on code analysis, testing results, user feedback, performance monitoring, or other sources of data. For example, you can use code metrics such as cyclomatic complexity, lines of code, or code coverage to evaluate the maintainability and testability of your system. You can use indicators such as response time, throughput, or error rate to evaluate the performance and reliability of your system. You should choose metrics and indicators that are meaningful, consistent, and actionable for your system and quality attributes.

3 Apply architecture evaluation methods

Architecture evaluation methods are systematic and structured approaches that can help you identify and address the strengths and weaknesses of your architecture. They can involve different techniques, such as reviews, audits, checklists, scenarios, simulations, or experiments. For example, you can use the Architecture Trade-off Analysis Method (ATAM) to evaluate how well your architecture meets the quality attributes and trade-offs among them. You can use the Software Architecture Analysis Method (SAAM) to compare different architecture alternatives and their implications. You should apply architecture evaluation methods that are suitable for your system and context.

4 Use architecture patterns and principles

Architecture patterns and principles are proven and reusable solutions that can help you design and improve your architecture. They can provide guidance, best practices, and common vocabulary for your architecture. For example, you can use the Model-View-Controller (MVC) pattern to separate the concerns of your system into three layers: data, presentation, and logic. You can use the SOLID principles to ensure that your system is cohesive, decoupled, extensible, and adaptable. You should use architecture patterns and principles that are relevant for your system and quality attributes.

5 Seek feedback and improvement

Feedback and improvement are essential for measuring and enhancing your architecture. You should seek feedback from different sources, such as users, developers, testers, or experts, and use it to identify and resolve the issues and gaps in your architecture. You should also monitor and measure your architecture continuously and regularly, and use the results to improve your architecture. You should adopt a culture of learning and innovation, and embrace changes and challenges in your architecture.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?