Architecture as a Service

On the left is a traditional layered view of how the different architectural views interact. <br/>The right-hand side extends the standard "service view" to represent the complex environment the business architecture exists in.<br/>in turn builds resilience against an ever-evolving and complex environment. The idea of variety is adapted from Ashby's "Law of Requisite Variety" and the idea here is that by developing an architecture modelling <b><i>capability</i></b> that amplifies "variety", you are better able to meet that external complexity.<br/>Perhaps the key question is: Does the "model meet your users' actual needs and goals and are the services provided sufficient or fit-for-purpose?<br/>