How to Increase your Business Reactivity using a Goal-Driven Service Oriented Architecture (GD-SOA) ?

Six Steps for succeeding with your Goal-Driven SOA using the OMG's UML, MDA and BMM standards

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 assign 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.

Read more 9.05.2007


Six Patterns for Aligning IT to Changes on the GD-SOA

Patterns for succeeding with the Goal-Driven Service Oriented Architecture (GD-SOA)

Along the above adaptation process, in order to prevent reactivity issues caused by traditional use case driven and O.O approachs, services of the SOA are to be rendered flexible as well as traceable for a swift and coherent evolution in face of changes. Two groups of engineering patterns help us to achieve these objectives.


The first group patterns confer flexibility to service specifications. They ensure identification, traceability and executability of services.


The second group patterns configure services to closing the gap between the business and application layers in order to confer to the system a coherent evolution in face of changes.



Recent White Papers