scholarly journals Propuesta para generar artefactos basados en modelos [Proposal for generation of software model-based artifacts]

2012 ◽  
Author(s):  
Vicente García Díaz ◽  
Edward Rolando Núñez Valdez ◽  
B. Cristina Pelayo García-Bustelo ◽  
Jordan Pascual Espada ◽  
Carlos Enrique Montenegro Marín
Keyword(s):  
Software Development ◽  
Source Code ◽  
Automatic Generation ◽  
Model Driven Engineering ◽  
New Paradigm ◽  
Natural Evolution ◽  
Model Driven ◽  
Software Model ◽  
Development Approach ◽  
The Impact

ResumenLa ingeniería Dirigida por Modelos es una aproximación de desarrollo en continua evolución. Prueba de ello sin los numerosos estándares que están surgiendo y la reciente aparición de herramientas que facilitan el trabajo con este reciente paradigma de la ingeniería del software. Al trabajar con modelos, un aspecto clave esla generación automática de código de menor nivel de abstracción. Sin embargo, la forma de llevar a cabo dicha generación no tiene en cuenta la evolución de los sistemas, y esa es la razón por la que el proceso es lento y repetitivo. En este trabajo se presenta una propuesta para generar código incrementalmente a partir de modelos, de forma que se minimice el impacto sobre aplicaciones que ya podrían estar en funcionamiento y se permita obtener la evolución exacta que han tenido los sistemas desde su origen.Palabras ClaveEvolución, matamodelos, modelo, generación de artefactos.Abstract The Model-Driven Engineering is a software development approach that continues evolving. In fact, there are some emerging standards and tools that facilitate working with this new paradigm of software engineering. Working with models, a key point is the automatic generation of source code of lower level of abstraction. However, the natural evolution of systems is not taken into account and that is the reason for which the process is usually slow and repetitive. In this work, we are going to show a proposal for incremental generation of source code from models. That way, we will minimize the impact on deployed applications and we will make the traceability of the evolution of systems. KeywordsArtifacts generation, evolution, metamodel, model. 

scholarly journals Measuring Models

2009 ◽  
pp. 147-169 ◽  
Author(s):  
Martin Monperrus ◽  
Jean-Marc Jézéquel ◽  
Joël Champeau ◽  
Brigitte Hoeltzener
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Point Of View ◽  
Specific Information ◽  
Model Driven Engineering ◽  
Text Documents ◽  
Model Driven ◽  
Domain Specific ◽  
Wide Range

Model-Driven Engineering (MDE) is an approach to software development that uses models as primary artifacts, from which code, documentation and tests are derived. One way of assessing quality assurance in a given domain is to define domain metrics. We show that some of these metrics are supported by models. As text documents, models can be considered from a syntactic point of view i.e., thought of as graphs. We can readily apply graph-based metrics to them, such as the number of nodes, the number of edges or the fan-in/fan-out distributions. However, these metrics cannot leverage the semantic structuring enforced by each specific metamodel to give domain specific information. Contrary to graph-based metrics, more specific metrics do exist for given domains (such as LOC for programs), but they lack genericity. Our contribution is to propose one metric, called s, that is generic over metamodels and allows the easy specification of an open-ended wide range of model metrics.

scholarly journals Dependability Modeling and Assessment in UML-Based Software Development

2012 ◽  
Vol 2012 ◽  
pp. 1-11 ◽  
Author(s):  
Simona Bernardi ◽  
José Merseguer ◽  
Dorina C. Petriu
Keyword(s):  
Software Development ◽  
Formal Model ◽  
General Purpose ◽  
Software Modeling ◽  
Model Driven ◽  
Domain Specific ◽  
Software Model ◽  
Software Models ◽  
Assessment Approach ◽  
System Properties

Assessment of software nonfunctional properties (NFP) is an important problem in software development. In the context of model-driven development, an emerging approach for the analysis of different NFPs consists of the following steps: (a) to extend the software models with annotations describing the NFP of interest; (b) to transform automatically the annotated software model to the formalism chosen for NFP analysis; (c) to analyze the formal model using existing solvers; (d) to assess the software based on the results and give feedback to designers. Such a modeling→analysis→assessment approach can be applied to any software modeling language, be it general purpose or domain specific. In this paper, we focus on UML-based development and on the dependability NFP, which encompasses reliability, availability, safety, integrity, and maintainability. The paper presents the profile used to extend UML with dependability information, the model transformation to generate a DSPN formal model, and the assessment of the system properties based on the DSPN results.

MoDSEL

2012 ◽  
pp. 572-594
Author(s):  
Ersin Er ◽  
Bedir Tekinerdogan
Keyword(s):  
Software Development ◽  
Impact Analysis ◽  
Software Evolution ◽  
Academic Research ◽  
Model Driven ◽  
Model Driven Software Development ◽  
Basic Concepts ◽  
The Impact ◽  
Development And Evolution

Model-Driven Software Development (MDSD) aims to support the development and evolution of software intensive systems using the basic concepts of model, metamodel, and model transformation. In parallel with the ongoing academic research, MDSD is more and more applied in industrial practices. Like conventional non-MDSD practices, MDSD systems are also subject to changing requirements and have to cope with evolution. In this chapter, the authors provide a scenario-based approach for documenting and analyzing the impact of changes that apply to model-driven development systems. To model the composition and evolution of an MDSD system, they developed the so-called Model-Driven Software Evolution Language (MoDSEL) which is based on a megamodel for MDSD. MoDSEL includes explicit language abstractions to specify both the model elements of an MDSD system and the evolution scenarios that might apply to model elements. Based on MoDSEL specifications, an impact analysis is performed to assess the impact of evolution scenarios and the sensitivity of model elements. A case study is provided to show different kind of evolution scenarios and the required adaptations to model elements.

Automate Model Transformation From CIM to PIM up to PSM in Model-Driven Architecture

2020 ◽  
pp. 262-283
Author(s):  
Yassine Rhazali ◽  
Asma El Hachimi ◽  
Idriss Chana ◽  
Mohammed Lahmer ◽  
Abdallah Rhattoy
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Business Process ◽  
Model Transformation ◽  
Source Code ◽  
Elementary Transformation ◽  
Multiple Points ◽  
Model Driven ◽  
Computer Scientists ◽  
Synthesis Methodology

The CIM, PIM, and PSM models are the main levels of the MDA approach. Model transformation is an important step in the MDA process. Indeed, in MDA there are two elementary transformation kinds: CIM to PIM transformation and PIM to PSM transformation. However, most searches propose approaches transforming PIM to PSM, since there are multiple points in common between PIM and PSM. Nevertheless, transforming CIM to PIM is rarely addressed in research because these two levels are mainly different. However, there is not a synthesis work that makes it possible to carry out a model transformation from CIM to PIM towards PSM until obtaining the code. This synthesis methodology allows controlling models transformation from CIM to PIM to PSM, indeed, up to obtaining code according the MDA. This approach makes it possible to limit the intervention of computer scientists in the life cycle of software development. Indeed, this methodology allows modeling only CIM, the business process, and then obtains the source code through successive semi-automatic transformations.

SeaLion: An eclipse-based IDE for answer-set programming with advanced debugging support

2013 ◽  
Vol 13 (4-5) ◽  
pp. 657-673 ◽  
Author(s):  
PAULA-ANDRA BUSONIU ◽  
JOHANNES OETSCH ◽  
JÖRG PÜHRER ◽  
PETER SKOČOVSKÝ ◽  
HANS TOMPITS
Keyword(s):  
Source Code ◽  
Answer Set Programming ◽  
Model Driven Engineering ◽  
Development Environment ◽  
Integrated Development ◽  
Model Driven ◽  
Class Diagrams ◽  
The Rich ◽  
Answer Sets ◽  
Answer Set

AbstractIn this paper, we present SeaLion, an integrated development environment (IDE) for answer-set programming (ASP).SeaLionprovides source-code editors for the languages ofGringoandDLVand offers popular amenities like syntax highlighting, syntax checking, code completion, visual program outline, and refactoring functionality. The tool has been realised in the context of a research project whose goal is the development of techniques to support the practical coding process of answer-set programs. In this respect,SeaLionis the first IDE for ASP that provides debugging features that work for real-world answer-set programs and supports the rich languages of modern answer-set solvers. Indeed,SeaLionimplements a stepping-based debugging approach that allows the developer to quickly track down programming errors by simply following his or her intuitions on the intended semantics. Besides that,SeaLionsupports ASP development using model-driven engineering techniques including domain modelling with extended UML class diagrams and visualisation of answer sets in corresponding instance diagrams. Moreover, customised visualisation as well as visual editing of answer sets is realised by the Kara plugin ofSeaLion. Further implemented features are a documentation generator based on the Lana annotation language, support for external solvers, and interoperability with external tools.SeaLioncomes as a plugin of the popular Eclipse platform and provides interfaces for future extensions of the IDE.

Towards Measuring the Change Impact in ATL Model Transformations

2016 ◽  
Vol 26 (02) ◽  
pp. 153-181 ◽  
Author(s):  
Andreza Vieira ◽  
Franklin Ramalho
Keyword(s):  
Software Development ◽  
Static Analysis ◽  
Development Time ◽  
Development Process ◽  
Model Transformations ◽  
Software Development Process ◽  
Model Driven ◽  
Change Impact ◽  
The Impact

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.

scholarly journals XRTSDIC: model transformation from PIM to PSM

2018 ◽  
Vol 7 (1.8) ◽  
pp. 92
Author(s):  
G Ramesh
Keyword(s):  
Software Design ◽  
Model Transformation ◽  
Source Code ◽  
Object Oriented ◽  
Proof Of Concept ◽  
Model Driven Engineering ◽  
Model Driven ◽  
Relationship Analysis ◽  
Uml Class Diagram ◽  
Computer Aided Software Engineering

Computer Aided Software Engineering (CASE) has been growing faster in software industry. As part of it Model Driven Engineering (MDE) has been around for focusing on models and transforming them from one model to other model. The tool named Extensible Real Time Software Design Inconsistency Checker (XRTSDIC) proposed by us in previous paper supports UML modelling, design inconsistency checking and model transformation from UML to ERD to SQL. In this paper it is extended further to facilitate model transformation from PIM (UML class diagram) to PSM (source code). We proposed an algorithm and defined model transformation and consistency rules. The extended framework has provision for class relationship analysis and support for choosing different object oriented languages like C#, C++ and Java. While transforming the model, we used the concept of dialects. Dialect is the class with transformation functionality which has ability to adapt to syntax and semantics of chosen language. Different dialects are made available for different languages. Thus the proposed system is capable of transforming models and the prototype application we built and extended demonstrates the proof of concept. The empirical results revealed that the model transformation is consistent and accurate.

Sign in / Sign up

Export Citation Format

Share Document