Capco Blog

Architecture as a Service: Applying the EVA framework

Architecture as a Service Part 3

The Enterprise Architecture group in most financial services organizations defines some form of target state architecture. The intent is to align all local architectures to the target state architectures defined for business, data, application, security and infrastructure. To effectively ensure that an organization’s Enterprise Architecture group applies a consistent approach to its target state architecture alignment, Capco’s Architecture as a Service (AaaS) model follows the engage-validate-approve (EVA) framework.

The EVA framework (Figure 1) groups stakeholders in three categories:

  • Requestor – The team requesting the architecture review or alignment
  • Review Committee – The group of stakeholders that reviews and validates the architecture changes for alignment
  • Executive Committee – The group of stakeholders that approve the architecture changes

EVA Framework
Figure 1: Architecture as a Service – The EVA Framework

Due to the flexible nature of the AaaS model, Capco’s team of architects can work with any of the three groups. The EVA framework provides the principles and guidelines for the architects to perform their roles and support each group.

If Capco’s team of architects are working with the Requestor team, the EVA framework provides them with the appropriate methods to help the Requestor team align to the charter of the organization’s Enterprise Architecture group. The EVA framework enables the project/requestor team to standardize its processes, be consistent across teams and emphasize the architecture design, keeping in line with the overall defined target state architecture.

When working with the Review Committee/Architecture Review Board, Capco’s architects can offer their skills in governance with respect to how an architecture functions. The EVA framework provides the Review Board with various guiding principles, scoring methodologies, review checklists and architecture principles to help ensure that new architectures stay aligned with the organization’s defined target state architecture.

Finally, Capco’s team of architects can work with the Executive Committee to approve any architecture changes. The AaaS architects can facilitate the approval process and provide guidance to the Executive Committee about the status of architecture alignment. The team can also work to set the future direction of target state architectures, keeping them in line with the enterprise’s overall IT strategy.

The EVA framework forms the epicenter of AaaS and is pivotal to the success of an organization’s architecture alignment. Using the EVA model, Capco’s AaaS architects can help clients ensure that their current and future state architectures are in alignment.

What models do you rely on to align your architecture? Join the discussion.

This series of blogs discusses how Capco’s Architecture as a Service model is applying the EVA framework to help organizations align their architecture. Next week, the AaaS EVA framework blog series will focus on governance in architecture alignment.


Leave a comment

Comments are moderated and will be posted if they are on-topic and not abusive. For more information, please see our Comments FAQ
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
previous article
Rate this Article
Your rating: None Average: 1 (1 vote)
next article