As the pace of innovation increases, IT groups are using agile approaches and short release cycles to deliver systems rapidly. As a result, IT architectures evolve quickly, and validating architectures a few times is not enough. We present a new approach for continuously validating architectures. The objective of this architecture validation technique is to ensure that the future system meets its business objectives and quality attribute requirements, without slowing down the pace of continuous delivery. This presentation describes how to use our approach to validate architectures in any type of project. First, we define what we mean by Architecture Validation. Then we focus on when to conduct Architecture Validations. We then discuss the roles required in an Architecture Validation. We finally detail how we conduct architecture validations by describing some industry-recognized techniques such as questionnaire-driven approaches, scenario-based approaches, and decision-based approaches. To illustrate the concepts introduced in this presentation, we will use a real-life example of Continuous Architecture Validation, showing how various approaches can be combined to effectively validate a project.
