Practical Experiences in the Application of MDA

  • Miguel de Miguel
  • Jean Jourdan
  • Serge Salicki
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2460)


During the last ten years a lot of concepts have emerged from software engineering. Most of them try to formalize and organize software engineering knowledge at a higher level of abstraction, giving code a secondary role. Model Driven Architecture (MDA), putting the concept of the model on the critical path of software development, is about to change this situation, turning the role of models from contemplative to productive. This paper introduces some problems detected in the process of adoption of MDA methods. The application of MDA for a specific domain, technique, or technology requires the Description of Specialized Modeling Language. Two main techniques provide support for the description of UML extensions, MOF meta-models and UML profiles. The Process of Mapping Description requires good support to identify the elements of the source modeling language that are mapped and the model elements of the destination modeling language that correspond to the source elements. This process require specific solutions.


Model Transformation Object Management Group Model Drive Architecture Model Drive Architecture Model Drive Engineering 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 2.
    Architecture Board ORMSC “Model Driven Architecture”, OMG document number ormsc/2001-07-01. (July 2001)
  2. 3.
    J. Bézivin. “From Object Composition to Model Transformation with the MDA”. In Proceedings of TOOLS’2001. IEEE. (August 2001).Google Scholar
  3. 4.
    T. Clark, A. Evans and S. Kent. “Engineering Modelling Languages: A Precise Meta-Modelling Approach”.
  4. 5.
    P. Desfray “MDA-When a major software industry trend meets our toolset, implemented since 1994”. (October 2001)
  5. 6.
    D. DSouza. “Model-Driven Architecture and Integration: Opportunities, and Challenges”, version 1.1,
  6. 7.
    D. Flater. “Impact of Model-Driven Architecture”. In Proceedings of the 35th Hawaii International Conference on System Sciences, (January 2002)Google Scholar
  7. 8.
    R. Hubert. “Convergent Architecture: Building Model-Driven J2EE Systems with UML” J. Wiley (November 2001)Google Scholar
  8. 9.
  9. 10.
    Kennedy Carter: “iUML—The executable UML modelling environment”.
  10. 11.
    B. Nordmoen “Beyond CORBA Model Driven Development”.
  11. 12.
    Object Management Group. “MOF 1.3 Specification”, OMG document number formal00-04-03, (March 2000)
  12. 13.
    Object Management Group. “UML Profile for EDOC”. OMG document number ptc01-12-04 (December 2002)
  13. 14.
    Object Management Group. “UML Profile for CORBA 1.1 Specification”, OMG document number ad/99-03-11 (March 1999)
  14. 15.
    Object Management Group. “UML Profile for Schedulability, Performance, and Time”, OMG document number ptc02-03-02 (March 2002)
  15. 16.
    Object Management Group. “UML Profile for Modeling Quality of Service and Fault Tolerance Characteristics and Mechanisms”, (Request for Proposal). OMG document number ad02-01-07 (January 2002)
  16. 17.
    Object Management Group. “Actions Semantic for the UML”, OMG document number ptc02-01-09 (January 2002)
  17. 18.
    Object Management Group. “MOF 2.0 Query / views / transformation”, (Request for Proposal). OMG document number ad02-04-10 (April 2002)
  18. 19.
    D. Poole. “Model-Driven Architecture: Vision, Standards And Emerging Technologies”. Workshop on Metamodeling and Adaptive Object Models. ECOOP 2001.Google Scholar
  19. 20.
    M. Richters and M. Gogolla. “Validating UML Models and OCL Constraints” In Proceedings of UML 2000. Springer. (October 2000)Google Scholar
  20. 21.
    J. Siegel and the OMG Staff Strategy Group. “Developing in OMGś Model-Driven Architecture”. Object Management Group White Paper (November, 2001)
  21. 22.
    R. Soley and OMG Staff Strategy Group. “Model Driven Architecture”, Object Management Group White paper, (November 2000)
  22. 23.
    Softeam. “Objecteering/UML CASE tool”.
  23. 24.
    Sun Java Community Process JSR-26. “UML/EJB Mapping Specification”.
  24. 25.
    Thales-TRT. “Model Based Engineering of Software Products”. In proceedings of OCM 2002 (March 2002)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Miguel de Miguel
    • 2
  • Jean Jourdan
    • 1
  • Serge Salicki
    • 1
  1. 1.Thales-TRTOrsayFrance
  2. 2.E.T.S.I. TelecomaunicaciónCiudad UniversitariaMadridSpain

Personalised recommendations