Article

Metodologies de Desenvolupament Dirigides per Models

Authors:
To read the full-text of this research, you can request a copy directly from the author.

Abstract

En aquest treball, s'introduiran dos de les metodologies de desenvolupament dirigides per models més significatives: Model Driven Architecture (MDA) i Domain Specific Modeling (DSM). Així mateix, es presentarà un estudi comparatiu d'algunes de les diferents eines existents actualment al mercat que els hi donen suport. En este trabajo, se introducirán dos de las metodologías de desarrollo dirigidas por modelos más significativas: Modelo Driven Architecture (MDA) y Domain Specific Modeling (DSM). Asimismo, se presentará un estudio comparativo de algunas de las diferentes herramientas existentes actualmente al mercado que se les dan apoyo. This study will introduce two of the development methodologies driven by more significant models: Model Driven Architecture (MDA) and Domain Specific Modeling (DSM). In addition, a comparative study will be presented of the various tools currently on the market that support them.

No full-text available

Request Full-text Paper PDF

To read the full-text of this research,
you can request a copy directly from the author.

ResearchGate has not been able to resolve any citations for this publication.
Article
Full-text available
Resumen El lenguaje de modelado UML es el estándar más utilizado para especificar y documentar cualquier sistema de forma precisa. Sin embargo, el hecho de que UML sea una notación de propósito muy general obliga a que muchas veces sea deseable poder contar con algún lenguaje más específico para modelar y representar los conceptos de ciertos dominios particulares. Los Perfiles UML constituyen el mecanismo que proporciona el propio UML para extender su sintaxis y su semántica para expresar los conceptos específicos de un determinado dominio de aplicación. En este artículo analizaremos los mecanismos de extensión que se utilizan para definir un Perfil UML. También discutiremos la utilidad y relevancia de estos Perfiles UML en el contexto del modelado guiado por arquitecturas (MDA).
Article
Full-text available
We survey the literature available on the topic of domain-specific languages as used for the construction and maintenance of software systems. We list a selection of 75 key publications in the area, and provide a summary for each of the papers. Moreover, we discuss terminology, risks and benefits, example domain-specific languages, design methodologies, and implementation techniques.
Article
Model transformations are touted to play a key role in Model Driven Development (TM). Although well-established standards for creating metamodels such as the Meta-Object Facility exist, there is currently no mature foundation for specifying transformations among models. We propose a framework for the classification of several existing and proposed model transformation approaches. The classification framework is given as a feature model that makes explicit the different design choices for model transformations. Based on our analysis of model transformation approaches, we propose a few major categories in which most approaches fit.
Article
In the realm of OO methodologies there are two major schools of thought. Both schools claim to define mechanisms whereby software applications can be created that are reusable, maintainable, and robust. Moreover, both schools claim to use abstraction as a key mechanism for achieving these benefits. At issue is whether or not these two schools are fundamentally different, or just variations on an object-oriented theme. Shlaer and Mellor have dubbed one of these schools ''Translational''. In the translational approach, two models are created. One is an abstract model of the application domain which is devoid of any design dependencies. The other model is an abstract model of the design which is devoid of any application dependencies. These two models are composed automatically to yield the code for the system. The other school - supported by Booch, Rumbaugh, Jacobson, and Martin - views the architecture of a system from several different perspectives of abstraction, e.g. logical, physical. These abstractions typically form a layer; abstractions in the logical sense manifest themselves as individual classes as well as collaborations of classes. There may be one layered model, at different layers of abstraction, or, especially given the Objectory view point, there may be multiple models, with an analysis model that's nearly independent from the design model. The panel will explore: Is there a seamless transition between analysis and design? Should there be a single model or should there be two - one for the analysis and one for the design? If there are two models, how are they ''bridged''? What, if any, are the differences in process between the two schools? How does architecture manifest itself? Is there, in fact, a real difference between the two schools of thought? As a result of this exploration, we hope to answer the question: Is translation a myth or is it a reality?
Article
The realisation of domain-specific languages (dsls) differs in fundamental ways from that of traditional programming languages. We describe eight recurring patterns that we have identified as being used for dsl design and implementation. Existing languages can be extended, restricted, partially used, or become hosts for dsls. Simple dsls can be implemented by lexical processing. In addition, dsls can be used to create front-ends to existing systems or to express complicated data structures. Finally, dsls can be combined using process pipelines. The patterns described form a pattern language that can be used as a building block for a systematic view of the software development process involving dsls.
Conference Paper
Domain-Specific Modeling (DSM) raises the level of abstraction beyond programming by specifying the solution directly using domain concepts. In many cases, the final products can be generated from these high-level specifications. This automation is possible because both the language and generators need fit the requirements of only one company and domain. This demonstration illustrates DSM by showing real world cases from various fields of software development. These cases describe how DSM, giving first class support for modeling, can prevent incorrect or unwanted designs at the early stages of development, and how full code can be generated from the modeler's point of view. Second part of the demonstration will show in an interactive manner both the design side and the use side of DSM languages and generators. Using MetaEdit+ tool for metamodeling, we define a DSM for a given domain and apply it to generate full code from high-level models.
How to get started with DSM
  • Dsm Forum
DSM Forum. How to get started with DSM. (http://www.dsmforum.org/how.html)
Unified or Domain-Specific Modeling Languages? Software Development Agile Modeling Newsletter
  • S Ambler
S. Ambler. Unified or Domain-Specific Modeling Languages?. Software Development Agile Modeling Newsletter, March 2006. (http://www.metacase.com/news/AgileModelingMarch2006.html)
  • G Booch
  • A Brown
  • S Iyengar
  • J Rumbaugh
  • B Selic
G. Booch, A. Brown, S. Iyengar, J. Rumbaugh, B. Selic. An MDA Manifesto. MDA Journal, May 2004.
Architectural Manifesto: Choosing MDA tools
  • M Kontio
M. Kontio. Architectural Manifesto: Choosing MDA tools. IBM developerWorks (http://www-128.ibm.com/developerworks/wireless/library/wi-arch18.html)
Domain-Specific Modeling for Generative Software Development
  • Itarchitect
ITarchitect. Domain-Specific Modeling for Generative Software Development. (http://www.itarchitect.co.uk/articles/display.asp?id=161)
MDA Tools Classification Approach: An Evaluation Template
  • Sd Asia
SD Asia. MDA Tools Classification Approach: An Evaluation Template. (http://architecture.sdaasia.com/sda/specialcolumn/psecom,id,2,nodeid,39,_language,Singapore.html)
Desarrollo basado en modelos y UML 2.0: ¿el fin de la programación tal como la conocemos
  • M Björkander
M. Björkander. Desarrollo basado en modelos y UML 2.0: ¿el fin de la programación tal como la conocemos?. Novatica, Nº 168, Marzo-Abril 2006, p.21-24.
From Front End To Code – MDSD in Practice
  • M Voelter
  • B Kolb
  • S Efftinge
  • A Hasse
M. Voelter, B. Kolb, S. Efftinge, A. Hasse. From Front End To Code – MDSD in Practice. June 15, 2006. (
Comparision of Model Driven Architecture (MDA) based tools (A Thesis document)
  • Ahsan Tariq
  • N Akhter
Ahsan Tariq, N. Akhter. Comparision of Model Driven Architecture (MDA) based tools (A Thesis document). Department of Computer and Systems Sciences, Royal Institute of Technology (KTH), 2005.
A Guided Tool Adoption Roadmap for MDA Adopters
  • Sd Asia
  • Mda Tools Comparison
  • Matrix
SD Asia. MDA Tools Comparison Matrix: A Guided Tool Adoption Roadmap for MDA Adopters. (http://www.sdaasia.com/sda/specialcolumn/psecom,id,7,_language,Singapore,w,4,nodeid,1,xv_query,mda,xv_ numresults,35,xv_sortvalue,0.html)
podrem executar-la mitjançant el motor de transformació, que ens generarà el codi final
  • La Quan Completem
  • Plantilla
Quan completem la plantilla, podrem executar-la mitjançant el motor de transformació, que ens generarà el codi final:
Next-generation model-driven development. Rational Software White Paper
  • G Cernosek
G. Cernosek. Next-generation model-driven development. Rational Software White Paper, December 2004. (ftp://ftp.software.ibm.com/software/rational/web/whitepapers/rsa-cernosek-wp.pdf)
  • Borland Together
Borland Together 2006 Data Sheet. (http://www.borland.com/resources/en/pdf/products/together/together_datasheet.pdf)
MDA Guide Version 1.0.1. Object Management Group
  • J Miller
  • J Mukerji
J. Miller, J. Mukerji. MDA Guide Version 1.0.1. Object Management Group (OMG), 2003.
The OMG Model Driven Architecture and BPM. Business Process Trends Newsletter
  • P Harmon
P. Harmon. The OMG Model Driven Architecture and BPM. Business Process Trends Newsletter, May 2004, Volume 2, No. 5.