Architecture Governance Audit Examples

Objectives

Establish areas that the current guidelines

Display the areas that need to be right to help drive the Common Capability Model CCM and Enterprise capability Delivery ECD forward.

Why do this? The current progress and observations in a few projects indicate that the design work is not being linked together to achieve the deployment of the strategic vision and artefacts from the Enterprise Vision design,

• Lack of use of the CCM and ECDs in project vocabulary

• Drive for 90 days missing the use of reuse models based on CCM and ECD principles

• Currently project deliverables don’t have the CCM and ECD models in place

• Currently no IDE roll out to enable the enforcement or even access to these models

• Currently historical evidence

• Need to be more proactive in driving projects to work to these standards. The use of principles and themes in the current Integration Design Delivery guidelines don’t not equate to a governance approach i.e. the guidelines are a policies document and not a governance management structure. Best practice

In short, need to “take the gloves off” to push the deployment governance stronger.

Areas that reference a SOA based guideline

What Enteprise need to adopt

The areas that represent a SOA guidance structure – specific deliverables and artefacts that represent best practice in policy and guidelines

The following is a list or key best practice deliverables of what should be in an SOA orientated organisation.

May organisations define artefacts such as meta models but do not embed these into working practices of projects : case studies :

Meta Models

• work has defined meta abstractions at the Business service and Information Model layers (ECDs and CCM) but not the other areas, namelyu the APIs , messaging and Process areas. This has various impacts of not linking and promoting reuse of services

• Current project documentations don’t capture logical (or event conceptual designs of the SOA concepts)

Technology patterns

• The drive for hub centric patterns has highlighted the NFR performance model deficits in meeting point to point and high volume distributed network demands.

• There needs to be a separation between what are design patterns and those that are run-time patterns (ESB, EDA). There is currently a confusion over defining the ESB as a design pattern when it’s a run-time solution to meet a specific SOA design pattern. SOA is a design strategy. ESB is a technology pattern.

Patterns

Governance

- Structure

Gaps in current Guidelines

The current guidelines developed for the Integration and data Design groups covers a number of elements

#ArchitectureGovernance #SOAAudit #SOA