How to align IT with the changes using UML and according to BMM? Applying the 'Goal Driven Development' Process on a case study using UML 2 and the BMM

In the previous articles that I wrote for JOT in 2005 and 2003, I presented the 'Goal-Driven Development Process' and its patterns that aim at increasing the business reactivity of the companies in face of changes. In this article, this methodology is presented using a case study and according to BMM (The Business Motivation Model-voted by the OMG in September 2005). As you know, use case driven and object-oriented development processes are widely used in organisations for building their IT systems. This practice allows stakeholders to concentrate their requirements management efforts as well as analysis and design efforts on the usage choices of the systems. However, IT systems developed only with use-case driven and object-oriented development methodologies do not provide their organisations with good levels of reactivity in face of changes. This is because these systems are not structured on the basis of business goals and underlying rules & policies that support the achievement of these goals, so they are unable to capture changes on the business needs and propagate them coherently toward IT applications [Align-IT]. In order to show in practice how to develop IT applications on the basis of company's goals then align these applications with the changing business rules and policies, we present below steps of the Goal-Driven Development Process on a case study using the Enterprise Architect (EA), a UML 2 compliant case tool.