MDA® Implementers’ Workshop Succeeding with Model Driven Systems

By now, we’ve all heard of MDA and seen the logos, but what does it all mean and how does it fit? This tutorial will provide an understanding of the basic concepts of MDA; separation of concerns, PIM’s, PSM’s, and transformations. We expand on this to discuss the full-lifecycle of MDA based development processes and understand the role of profiles and meta-models in the process. Then, we put this into context of the MDA Core technologies; MOF, UML, CWM, XMI and explain the underlying architecture of MDA, the interrelationship between the technologies, and the benefits this brings. We examine how tools fit into the total picture and how to evaluate tools against particular enterprise requirements. Finally, we finish the tutorial by going through a complete development example including a sample profile and meta-model, business model, PIM, PSM, finally generating code. All of this is presented in an objective, vendor neutral fashion, to provide a complete and unbiased understanding of MDA.

OMG Management GroupModel Driven Architecture

Understanding MDA – Mike Rosen, CTO, M2VP
MDA® Implementers’ Workshop
Succeeding with Model Driven Systems
December 2-5, 2003
Burlingame, CA USA

MDA Methodologies and Processes

Models are an important part of software development and architecture. MDA provide standards for the definition and processing of models, but doesn”t venture into how it fits with development methodologies and processes.

This session presents three views on the topic, starting with the issues of integrating MDA into the development process and a formal method for describing the resultant process; then insight into how MDA can help with the management and specification of requirements, and finally a process for creating high level, executable models.

MDA Tools: Realizing the Vision

The MDA vision will only be realized with tool support. Tools that will provide modeling support of complex, enterprise-level and embedded systems, assist in automated model transformation and code generation, support flexible and dynamic configuration, provide adequate documentation and offer design verification and system validation capabilities.

The panel of tool vendors and systems integrators assessed current MDA tool capabilities and provided insight into future plans in meeting this vision.

Using MDA to Implement Enterprise Architecture

IT systems can no longer be developed in isolation, but must fit into a larger context that meets the goals of the overall business. EA defines that context and the rules and guidelines for conformance. Unfortunately, many development projects and organizations are unaccustomed to following the rules, stressing the new IT Architectural models being developed. But wait, here’s MDA to the rescue! MDA provides a standards based approach to defining enterprise architecture. Additionally, MDA tools can provide a mechanism to automatically incorporate the architecture into the development process.

This presentation will describe the concepts and process of defining Enterprise Architecture using MDA.

MDA in the Federal Government

In 2001, the federal government introduced its e-Government initiative to improved and streamline government services. A major portion is focused on IT, as described by the Federal Enterprise Architecture (FEA). Starting in FY2003 the OMB announced that funding would be given only to projects that explicitly conform to the FEA. This presentation shows how one project used MDA to meet those requirements.

The project team used MDA to codify standards and constraints of the FEA into their frameworks and processes using UML profiles. We will discuss the project”s requirements, framework, UML profiles and progress to date.

Incorporating MDA into the Development Process

MDA defines certain types of models to be created (PIM/PSM), but doesn’t explain how to fit them into a development process nor how to partition business information between the models. Other industry standards, such as RUP, define a detailed development process, while RM-ODP provides guidance on separation of concerns in enterprise systems.

This session will present a framework, following RM-ODP viewpoints, for fitting MDA’s Platform Independent Models into the RUP development process to reduce duplication of effort within the various RUP models and verify requirements through traceability across the models. An example will illustrate the framework using Rational Rose.

What MDA Tools are Right for You?

As MDA gains momentum, tool vendors are getting in line to claim support. Many tools offer full compliance with MDA and substantial generation capabilities, while others are just jumping on the marketing bandwagon. At the same time, different tools support different approaches and methodologies but few tools cover the entire gamut from business requirements to executable code.

This session will explore the issues of methodology, model translation, traceability, generation capabilities, etc. to build a framework for evaluating MDA tools against your particular needs. It will also show how some of the leading tools stack up against these metrics.