Notice : In the first and the previous section of this Enterprise SOA alignment process, we have respectively shown how to structure 'Business Capabilities" and model business processes on the basis of business goals.

This section deals with the service description and realization layer of the "Business toward SOA Operating Model Framework". Thus, it focuses on the following implementation steps :


Step 4 - How to elaborate a draft backbone of the corresponding "Goal-Driven SOA" architecture ?


Steps 5 and 6 - Description of IT level use case and service component behaviours that are to be plugged into this SOA backbone.



Step 4 :  Elaborate a draft backbone of the Goal-Driven Service Oriented Architecture



This step allows us to elaborate a first draft of the architectural backbone of service and use case components at the PIM (Platform Independent Model) level of the MDA.


A draft of the Goal-Driven SOA backbone on the basis of the MDA's Computation Independent Model (business level) specifications is given in the figure below using the UML 2 component diagram notations...




Figure 6:    A draft of the Goal-Driven SOA backbone transformed at the MDA's PIM level on the basis of MDA's CIM level specifications of the business owners and analysts




Notice : All the internal structures (use cases, services, service points,...) of business capabilities previously described by the business analysts are kept "as is" with traceability !






Step 5  : Model underlying behaviours of use case and service components


In this step, we describe underlying automated actions of the processes that require actor / system interactions for their realizations.


The below activity diagram illustrates a realization scenario for the action Enter Visitor of the process Register Visitor described in figure 4.


The UC and GdS component behaviours shown at the bottom side may be automatically generated on the basis of actions specified within each of them.




Figure 7 :   Behavioral description and generation of the use case (UC_Cmp) and service (GdS_Cmp) components that realize the action Enter Visitor of the business process Register Visitor





Step 6 : Plug-in the use case and service behaviours into the backbone of the GD-SOA and test


This step focuses on the insertion of the appropriate software behaviours into the components of the architecture.


In this perspective, behaviours of the other architectural layer components such as the presentation and data storage layers have to be implemented on the basis of the previous specifications.


Finally, the previous architectural components (GUI, use case, service, entity objects) are plugged into appropriate structures of the architectural backbone of the system for their integration with other components of the architecture.


The figure below illustrates the plug-in of the previous UC and GDS components into the system architecture.





Figure 8 :  Use Case and Service components are plugged into their respective parent components within the goal-driven architectural backbone of the system 





Animated : Click to visualize how to deal with changes on the Goal-Driven Service Oriented Architecture, ...



3         Conclusion


The steps of the Goal-Driven SOA Development Process illustrated in this presentation allowed us to explain how to align IT applications on the basis of business goals, their underlying means and processes according to BMM and SOA concepts.


By bridging these concepts throughout identification of SOA services and application use cases then ensuring their separate traceability toward software implementation, the purpose of the Goal-Driven SOA process is to allow stakeholders to adapt IT applications to changes swiftly and coherently using goal structures, thus to capitalize on their business knowledge using a goal-driven service oriented architecture.


Goal-Driven Development Patterns [Patterns] that support the infrastructure of this SOA process aim to help organizations to increase their business agility without worrying about alignment issues of IT applications.  


This way, business owners and analysts focus on the enhancement of their daily business process by describing behaviours requested from supporting services and UC components, whilst end-users of the system can finaly concentrate their efforts on their interactions with the system as they should naturally do.


An MDA (Model Driven Architecture) style partitioning of a previous version of these models is proposed in [GDDP4MDA].


Additional information about relationships between BMM toward SOA Services also considering the TOGAF 9 Meta-Model with key SOA entities are provided on "From BMM and TOGAF 9 toward SOA".




[BMM] : "Business  Motivation Model - Business governance in a volatile world" of the Business Rules Group voted by the OMG in September 2005 ,

[Visibility of the Rules] :  Stan Hendryx - Business Rules - BPTrends / BPT  , October 2004

[Business-Oriented Foundation] :  Ulrich Homann - MSDN -, February 2006

[Business Capabilities View] : The OMG's Business Architecture Working Group

[Business Rules vs. Business Requirements] : Gladys S.W. Lam - Business Rules Journal, Vol. 7, No 5, May 2006), URL:

[Service Architecture - SOA : Why Sale isn't process driven] : Steve Jones -

[Becoming Strategy Driven] : Ronald G. Ross, "Becoming Strategy-Driven:  Moving Beyond the Tired Notion of 'Business Alignment'," Business Rules Journal , Vol. 9, No. 12 (Dec. 2008), URL:

[From BMM and TOGAF 9 toward SOA] : Birol Berkem

[GDDP4MDA] Birol Berkem, Goal Driven Development for MDA - OMG's Technical Meeting in Athens , April 2005

[Align-IT-with-BMM] Birol Berkem, How to align IT with the Changes using UML and according to BMM ? - Journal of Object Technology, vol. 5, no. 2, March-April 2006 ,

[Patterns] How to increase your business agility with UML and MDA? (White paper on the Goal-Driven Development Patterns and Processes)

[TOGAF] What kind of "architecture" does TOGAF deal with ?:




Creative Commons License
This work by Birol Berkem ( is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
Permissions beyond the scope of this license may be available by mail to

Birol Berkem (Ph.D), GooBiz