GooBiz

IT systems developed only with use-case driven and object-oriented methodologies do not provide their organisations with good levels of agility in face of changes. This is because such methodologies structure systems only focusing on actor/system interactions that hide business rules and assigning business responsibilities to domain objects.

The resulting use case driven and traditional object based systems fail to capture changes on the business needs and to propagate them coherently toward IT application layer in order to align IT components to changes as required by the GD-SOA.

Along the above adaptation process, in order to prevent reactivity issues caused by traditional use case driven and object approachs, services of the SOA are to be rendered flexible as well as traceable for closing the gap between business and application layers. Two groups of engineering patterns can help us to achieve these objectives.

 

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

 

a. Pattern for Identifiable Services : Finds out services on the basis of business goals and ensures traceability toward their object-oriented representations.

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

c. Pattern for Executable Services : Early tests services in order to assure correct understanding of requirements as well as to incite business experts to tell more on their needs.

 

Relationships between these basic patterns that allow flexibility to services are illustrated below.

 

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

 

 

 

 

The second group patterns contribute to closing the gap between the business and application services in order to 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 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 as by aligning IT on the business, they allow companies to be "customer aligned" using services.

 

 

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

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