Risk Mitigation
A formal architecture evaluation illuminates areas of risk in both new and existing architectures. Armed with this knowledge, architects can redesign portions of the solution accordingly, or isolate risky components in order to protect other system components. Additionally, the evaluation process forces system utility requirements to be explicitly defined up front, reducing the risk of potential stability, performance, and security issues during construction and in production.
Improved Architecture Understanding
Often times the architecture for a solution is created in an ad-hoc fashion or is inherited from a third-party systems integrator. In these cases, the documentation is frequently out-of-date or non-existent. An architecture review will document the primary features, risks, and sensitivity points of your architecture.
Greater Cross-Project Reuse
Experience has shown that the best approach for increasing the number of opportunities for code reuse is by explicitly identifying recurring business requirements and architectural commonalities, both within a project and between projects. Since both the business and technical stakeholders are active in a formal architectural evaluation process, an environment is created where these common requirements and architectural patterns can easily be discovered.
Bridging the Communications Gap
By putting business stakeholders and engineers in the same room, a formal architecture evaluation process forces the prioritization of conflicting goals, creating an understanding and agreement on the quality requirements of the architecture under review.
|