GooBiz

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 in order to guarantee a coherent evolution in face of changes of the business requirements.

Two groups of engineering patterns help to achieve these objectives.

 

The first group 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 : Identifies services on the basis of business goals, capabilities, functions and ensures traceability from functional specifications to their object-oriented representations.

b. Pattern for Evolvable Services : Make evolvable and traceable service components in order to adapt them without any modification to the interfaces of legacy systems or other system components.

c. Pattern for Executable Services : Early tests services in order to ensure correct understanding of requirements by inciting business owners to tell more on their needs.

 

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

 

Figure 1 : Relationships between basic patterns of the Goal-Driven 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, also by considering their personalisation constraints.

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

 

Relationships between these second group patterns are illustrated below.

 

 

 

Figure 2 : Relationships between patterns for using services of the Goal-Driven 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...