'Agile Enterprise Architecture' Patterns for Business and IT Systems Alignment

Patterns for succeeding with the Business / IT System Agility using TOGAF's ADM Enterprise Architecture Methodologies

Along the enterprise architecture transformation processes such as TOGAF's ADM, in order to prevent agility issues while adapting IT to changes, business and IT structures of the Enterprise Architecture Framework are to be rendered flexible as well as traceable to guarantee a coherent evolution in face of changes of the business requirements.

Two groups of patterns help to achieve these objectives.

 

The first group of patterns confer flexibility to service specifications. These patterns ensure identification, traceability and executability of business and IT services as indicated below (click on the pattern name for details).

 

a. Pattern for Identifiable Services : Make identifiable services to support target capabilities of an architecture on the basis of changing goals then ensures a 1 to 1 traceability relationship with functional specifications of capabilities in order to adapt them swiftly to changes

b. Pattern for Evolvable Services : Ensures evolvable and traceable services that can be adapted without bringing modification to interfaces of existing (business, application, technology) systems or their building blocks.

c. Pattern for Executable Services : Early tests services in order to ensure correct understanding of requirements for building up target capabilities and inciting stakeholders to tell more about their needs.

 

Relationships between these basic patterns that contribute to the flexibility of the architecture are illustrated below.

 

Base Patterns for Succeeding on the GD-SOA PATTERN FOR IDENTIFIABLE SERVICE SPECIFICATIONS (PISS) PATTERN FOR EVOLVABLE SERVICES (PESS) PATTERN FOR EXECUTABLE SERVICES (PEXS)

Figure 1 : Relationships between basic patterns of the Goal-Driven EA/SOA approach: Click on each referenced pattern icon to visualise its detailed description

 

 

 

 

The second group patterns contribute to closing the gap between the business and IT services. They confer to the system a coherent evolution as explained in the points below. Click on the pattern name for details.

 

d. Pattern for Traceable Abstraction Layers : Ensures traceability between business and application layers in order to allow IT components to be aligned on changing business needs.

e. Pattern for Using Business Services from the Application Layer : Allows end-users of the application system to use business services and extending them considering their personalisation choices.

f. Pattern for Controled Evolution : Confers coherent evolution to system components according to changes that arise on higher level business requirements.

 

Relationships between these second group patterns are illustrated below.

 

 

SecondGroupPatternsForSOA TRACEABLE SERVICES BETWEEN ABSTRACTION LAYERS PATTERN FOR USING BUSINESS SERVICES FROM THE APPLICATION LAYER (PUBS-AL) PATTERN FOR CONTROLED EVOLUTION (PCE)

 

Figure 2 : Relationships between patterns for using services of the Goal & Capability-Driven EA/SOA : Click on the pattern icons to visualise their detailed description

 

Notice that these patterns are also ITIL (IT Infrastructure Library) compliant, in that they contribute to align IT on business requirements and allow organizations to be "customer focused " on the basis of business goals and directives.

 

 

Birol Berkem (PhD) - GooBiz - Paris (F)

Goal-Driven SOA - Synchronize IT with your Changing Environment...