A New Methodology to Automate the Transformation of GIS Models in an Iterative Development Process

  • André Miralles
  • Thérèse Libourel
Part of the Springer Optimization and Its Applications book series (SOIA, volume 25)


In the majority of research today in areas such as evaluation of flood risks, management of organic waste as it applies to plants, and mapping ecological conditions of rivers, scientific advances are often aimed toward the development of new software or the modification of existing software. One of the particulars for software developed for agricultural or environmental fields is that this software manages geographic information. The amount of geographic information has greatly increased over the past 20 years. Geographic Information Systems (GISs ) have been designed to store this information and use it to calculate indicators and to create maps to facilitate the presentation and the appropriation of the information. Often, the development of these GISs is a long and very hard process. Since the early 1970 s, in order to help project managers, software development processes have been designed and applied. These development processes have also been used for GIS developments. In this chapter, the authors present a new methodology to realize GIS more easily and more interactively. This methodology is based on model transformations, a concept introduced by the Object Management Group (OMG) in its approach called model driven architecture (MDA ). When software is developed, models are often used to improve the communication between users, stakeholders, and designers. The changes of a model can be seen as a process where each action (capture of user concepts, modification of concepts, removal of concepts, etc.) transforms the model. In the MDA approach, the OMG recommends automation of these actions using model transformations. The authors have developed a complete set of model transformations that enable one to ensure the evolution of a GIS model from the analysis phase to the implementation phase.


Geographic Information System Unify Modeling Language Rapid Prototype Design Pattern Software Development Process 
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.


  1. 1.
    Beck K. 2000. eXtreme Programming Explained – Embrace Change. Addison-Wesley. 190 pp.Google Scholar
  2. 2.
    Bédard Y, Larrivée S, Proulx M-J, Nadeau M. 2004. Modeling Geospatial Databases with Plug-ins for Visual Languages: A Pragmatic Approach and the Impacts of 16 Years of Research and Experimentations on Perceptory. Presented at ER Workshops 2004 CoMoGIS, Shanghai, China.Google Scholar
  3. 3.
    Bénard J-L. 2001. Méthodes agiles (1) – Panorama. Développeur Référence. Last access: September 2004.
  4. 4.
    Bénard J-L, Bossavit L, Médina R, Williams D. 2002. Gestion de projet eXtreme Programming. Eyrolles. 298 pp.Google Scholar
  5. 5.
    Booch G, Rumbaugh J, Jacobson I. 2000. Guide de l'utilisateur UML. Eyrolles. 500 pp.Google Scholar
  6. 6.
    Cros T. 2001. La conception dans l'eXtreme Programming. Développeur Référence. Last access: September 2004.
  7. 7.
    Desfray P. 1994. Object Engineering – The Fourth Dimension. Addison-Wesley. 342 pp.Google Scholar
  8. 8.
    Fayet E. 2002. Forum Utilisateurs Rational – Le discours de la méthode. Développeur Référence. Last access: September 2004.
  9. 9.
    Gamma E, Helm R, Johnson R, Vlissides J. 2001. Design patterns – Elements of Reusable Object-Oriented Software. Addison-Wesley Professional. 416 pp.Google Scholar
  10. 10.
    Guimond L-E. 2005. Conception d'un environnement de découverte des besoins pour le développement de solutions SOLAP. Thèse. Université Laval, Québec. 124 pp.Google Scholar
  11. 11.
    Jacobson I. 2003. Use Cases – Yesterday, Today, and Tomorrow.; http://www.ivarjacob Last access: August 2005.
  12. 12.
    Jacobson I, Booch G, Rumbaugh J. 1999. The Unified Software Development Process. Addison-Wesley. 463 pp.Google Scholar
  13. 13.
    Kleppe A. 2004. Interview with Anneke Kleppe. Code Generation Network. articleId=21. Last access: August 2006.
  14. 14.
    Kleppe A, Warmer J, Bast W. 2003. MDA Explained: The Model Driven Architecture—Practice and Promise. Addison-Wesley Professional. 170 pp.Google Scholar
  15. 15.
    Kruchten PB. 1999. The Rational Unified Process: An Introduction. Addison-Wesley Professional. 336 pp.Google Scholar
  16. 16.
    Larman C. 2002. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process. Prentice Hall PTR. 627 pp.Google Scholar
  17. 17.
    Larman C. 2002. UML et les Design Patterns. CampusPress. 672 pp.Google Scholar
  18. 18.
    Miller J, Mukerji J. 2001. Model Driven Architecture (MDA). OMG. 07-01.pdf. Last access: September 2004.
  19. 19.
    Miller J, Mukerji J. 2003. MDA Guide Version 1.0.1. OMG. -01. Last access: May 2006.
  20. 20.
    Miralles A. 2006. Ingénierie des modèles pour les applications environnementales. Thèse de doctorat. Université Montpellier II, Montpellier. 322 pp.
  21. 21.
    Muller P-A, Gaertner N. 2000. Modélisation objet avec UML. Eyrolles. 520 pp.Google Scholar
  22. 22.
    OMG. 2001. Common Warehouse Metamodel – Version 1.0. OMG. ?ad/2001-02-01. Last access: June 2004.
  23. 23.
    OMG. 2003. Unified Modeling Language – Specification – Version 1.5. formal/03-03-01.pdf. 736 pp.
  24. 24.
    Région Wallonne. 2004. Le prototypage: Définition et objectifs. Portail Wallonie.Google Scholar
  25. 25.
    Roques P, Vallée F. 2002. UML en Action – De l'analyse des besoins à la conception en Java. Eyrolles. 388 pp.Google Scholar
  26. 26.
    Royce WW. 1970. Managing the Development of Large Software Systems. Presented atIEEE Westcon, Monterey, CA.Google Scholar
  27. 27.
    Schramm WL. 1954. How communication works. In: The Process and Effects of Communication. University of Illinois Press. pp. 3–26.Google Scholar
  28. 28.
    Softeam. 2005. Formation sur les Modèles Objet et UML.Google Scholar
  29. 29.
    The Middleware Company. 2003. Model Driven Development for J2EE Utilizing a Model Driven Architecture (MDA) Approach – Productivity Analysis.Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2009

Authors and Affiliations

  1. 1.Centre for Agricultural and Environmental Engineering ResearchEarth Observation and GeoInformation for Environment and Land Development UnitMontpellierFrance

Personalised recommendations