Applying model driven to software development: A university library case study

2011 ◽  
Author(s):  
Li Dan ◽  
Li Danning
Keyword(s):  
Software Development ◽  
Model Driven ◽  
University Library

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.

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 Teaching pragmatic model-driven software development

2015 ◽  
Vol 12 (2) ◽  
pp. 683-705 ◽  
Author(s):  
Jaroslav Porubän ◽  
Michaela Bacíková ◽  
Sergej Chodarev ◽  
Milan Nosál’
Keyword(s):  
Software Development ◽  
Development Process ◽  
Model Driven Development ◽  
Model Driven ◽  
Visualisation Tool ◽  
Big Picture ◽  
Model Driven Software Development ◽  
Positive Results

Model-driven software development is surrounded by numerous myths and misunderstandings that hamper its adoption. For long, our students were victims of these myths and considered MDSD impractical and only applied in academy. In this paper we discuss these myths and present our experience with devising an MDSD course that challenges them and motivates students to understand MDSD principles. The main contribution of this work is a set of MDSD teaching guidelines that can make the course pragmatic in the eyes of students - programmers. These guidelines introduce MDSD from the viewpoint of a programmer as a pragmatic tool for solving concrete problems in the development process. In our MDSD course we implemented the presented guidelines. The course shows several techniques and principles of model-driven development in multiple incremental iterations instead of concentrating on a single tool. At the same time we unite these techniques by using a dynamic visualisation tool that shows to the students the whole infrastructure in the big picture. The course is implemented as an iterative incremental MDSD case study. The paper concludes with a survey performed with our students that indicates positive results of the approach.

A Case Study of Ontology-Driven Development of Intelligent Educational Systems

2011 ◽  
pp. 79-94
Author(s):  
Gordon Deline ◽  
Fuhua Lin ◽  
Dunwei Wen ◽  
Dragan Gaševic ◽  
Kinshuk N/A
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Ontology Development ◽  
Educational Systems ◽  
Software Components ◽  
Review Of Literature ◽  
Driven Systems ◽  
Model Driven ◽  
Development Methodology

This article presents a case study of ontology-driven development of intelligent educational systems. Following a review of literature related to ontology development, ontology-driven software development, and traditional software engineering, we developed an ontology-driven software development methodology appropriate for intelligent ontology-driven systems which have ontologies as key execution components, such as e-Advisor, and which is biased toward an integration of incremental and iterative ontology development and downstream Model Driven Architecture for development of software components.

A Model-Driven Approach for the Design and Implementation of Software Development Methods

2012 ◽  
Vol 3 (4) ◽  
pp. 86-103 ◽  
Author(s):  
Mario Cervera ◽  
Manoli Albert ◽  
Victoria Torres ◽  
Vicente Pelechano
Keyword(s):  
Software Development ◽  
Method Engineering ◽  
Model Driven ◽  
Design And Implementation ◽  
Two Phases ◽  
Definition Of ◽  
Model Driven Approach ◽  
Development Methods ◽  
Software Development Methods

The Situational Method Engineering (SME) discipline emerged two decades ago to address the challenge of the in-house definition of software development methods and the construction of the corresponding supporting tools. Unfortunately, current SME approaches still have limitations that are hindering their adoption by industry. One of these limitations is that most approaches do not properly encompass two phases of the SME lifecycle, which refer to the method design and the method implementation. To address this limitation, this paper demonstrates how Model-Driven Development (MDD) techniques can contribute to successfully cover both phases. The proposal is illustrated by a real case study that is currently being used at the Valencian Regional Ministry of Infrastructure, Territory and Environment.

Sign in / Sign up

Export Citation Format

Share Document