Empirical Investigations of Model Size, Complexity and Effort in a Large Scale, Distributed Model Driven Development Process

Author(s):  
Werner Heijstek ◽  
Michel R.V. Chaudron
2015 ◽  
Vol 12 (2) ◽  
pp. 683-705 ◽  
Author(s):  
Jaroslav Porubän ◽  
Michaela Bacíková ◽  
Sergej Chodarev ◽  
Milan Nosál’

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.


Author(s):  
Yucong Duan ◽  
Jiaxuan Li ◽  
Qiang Duan ◽  
Lixin Luo ◽  
Liang Huang

Author(s):  
Yeshica Isela Ormeño ◽  
Jose Ignacio Panach ◽  
Nelly Condori-Fernández ◽  
Óscar Pastor

Nowadays there are sound Model-Driven Development (MDD) methods that deal with functional requirements, but in general, usability is not considered from the early stages of the development. Analysts that work with MDD implement usability features manually once the code has been generated. This manual implementation contradicts the MDD paradigm and it may involve much rework. This paper proposes a method to elicit usability requirements at early stages of the software development process such a way non-experts at usability can use it. The approach consists of organizing several interface design guidelines and usability guidelines in a tree structure. These guidelines are shown to the analyst through questions that she/he must ask to the end-user. Answers to these questions mark the path throughout the tree structure. At the end of the process, the paper gathers all the answers of the end-user to obtain the set of usability requirements. If it represents usability requirements according to the conceptual models that compose the framework of a MDD method, these requirements can be the input for next steps of the software development process. The approach is validated with a laboratory demonstration.


Author(s):  
Harald Kühn ◽  
Marion Murzek ◽  
Gerhard Specht ◽  
Srdjan Zivkovic

Public and private organisations have a high rate of interaction, i.e. all their external business processes are de-facto inter-organisational. Besides traditional non-functional aspects, inter-organisational processes demand a high rate of interoperability. The authors present a model-driven development process explicitly considering interoperability levels as development process phases. Applying this development process has shown that it substantially raises the interoperability awareness for all associated actors. To further improve “common sense” between the involved actors, we use an integrated modelling language approach. For this, the metamodels of the used modelling languages are integrated using metamodel integration based on metamodel mappings and integration rules. The approach is demonstrated by integrating BPMN-based business process modelling and CCTS-based data modelling into a consolidated modelling language. Considering the integrated metamodel, the authors apply model transformation to re-use model information along the described development phases, e.g. business process definitions are used to generate skeletons for executable workflows and business document definitions are used to generate data model definitions and associated data schemata. The application of the model-driven development process, the metamodel integration as well as the model transformation is illustrated by a case study of electronic VAT statement transaction.


Author(s):  
Rita Suzana Pitangueira Maciel ◽  
Bruno Carreiro da Silva ◽  
Ana Patrícia Fontes Magalhães ◽  
Nelson Souto Rosa

2014 ◽  
Vol 89 ◽  
pp. 320-349 ◽  
Author(s):  
Ana I. Molina ◽  
William J. Giraldo ◽  
Manuel Ortega ◽  
Miguel A. Redondo ◽  
César A. Collazos

Sign in / Sign up

Export Citation Format

Share Document