Friday, 15 March 2013 16:10

Business Motivation Model MDG Technology

Written by
Rate this item
(0 votes)

What BMM is

From the OMG website: "The Business Motivation Model specification provides a scheme or structure for developing, communicating, and managing business plans in an organized manner.

Specifically, the Business Motivation Model does all of the following:

  • It identifies factors that motivate the establishing of business plans.
  • It identifies and defines the elements of business plans.
  • It indicates how all these factors and elements inter-relate.

Among these elements are those that provide governance for and guidance to the business — Business Policies and Business Rules."


What BMM is used for

As stated above, the main goal of the BMM specification is to formally and clearly describe the rules, concepts and informations that are relevant for business governance.

In other terms, a BMM model should state the rationale behind the way a given enterprise reacts to changes in its relevant business.

The changes an enterprise should be able to react to in an "explainable" way might be due, for example, to regulatory compliance evolutions, business process optimisations or Key Performance Indicators (KPIs) reaching some threshold values.

Generally speaking, BMM is useful to answer the following two questions:

  1. How do I trace the effect of changes on business processes, rules and responsibilities? (Forward Tracing);
  2. Why an Enterprise does what it does the way it does it? (Backward Tracing)

For further details on BMM, please refer to the specification, available at


A BMM MDG technology has been made freely available by Profesia in order to apply the BMM profile in Enterprise Architect. The MDG technology, beside the BMM profile, also provides the Diagram and Toolboxes profiles, along with a template model.

Profesia's MDG Technology is downloadable from

Read 7965 times

Guido Spadotto

Profesia (Software Engineer)

In the IT sector since 2005, I have always pushed for a Model Driven approach to keep the separation of concerns between business and technical requirements. As an application of this approach I implemented and maintained a set of components of a financial software suite, defining their behaviour through a set of independent DSLs. I have recently implemented an Enterprise Architect Plugin that maps model elements from/to an external ALM application, by exploiting EA's automation interface. I am currently focused on applying Agile methodologies in the context of BPMS to close the gap between the Business and IT perspectives.
Login to post comments