UML distilled (2nd ed.): a brief guide to the standard object modeling language
UML distilled (2nd ed.): a brief guide to the standard object modeling language
Understanding and improving technology transfer in software engineering
Journal of Systems and Software - Special issue on invited articles on top systems and software engineering scholars
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Agile modeling: effective practices for extreme programming and the unified process
Agile modeling: effective practices for extreme programming and the unified process
Agile Software Development with Scrum
Agile Software Development with Scrum
Explaining Software Developer Acceptance of Methodologies: A Comparison of Five Theoretical Models
IEEE Transactions on Software Engineering
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
Guest Editors' Introduction: Model-Driven Development
IEEE Software
Model-Driven Software Development: Technology, Engineering, Management
Model-Driven Software Development: Technology, Engineering, Management
EMF: Eclipse Modeling Framework 2.0
EMF: Eclipse Modeling Framework 2.0
Real-Life MDA: Solving Business Problems with Model Driven Architecture
Real-Life MDA: Solving Business Problems with Model Driven Architecture
The Impact of UML Documentation on Software Maintenance: An Experimental Evaluation
IEEE Transactions on Software Engineering
Where Is the Proof? - A Review of Experiences from Applying MDE in Industry
ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
A systematic review of quasi-experiments in software engineering
Information and Software Technology
Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit
Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit
Level of detail in UML models and its impact on model comprehension: A controlled experiment
Information and Software Technology
SEAA '09 Proceedings of the 2009 35th Euromicro Conference on Software Engineering and Advanced Applications
Towards to the validation of a usability evaluation method for model-driven web development
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
An eclipse plug-in for model-driven development of rich internet applications
ICWE'10 Proceedings of the 10th international conference on Web engineering
Model-Driven engineering of machine executable code
ECMFA'10 Proceedings of the 6th European conference on Modelling Foundations and Applications
Information Systems Frontiers
Hi-index | 0.00 |
Context: Today's project managers have a myriad of methods to choose from for the development of software applications. However, they lack empirical data about the character of these methods in terms of usefulness, ease of use or compatibility, all of these being relevant variables to assess the developer's intention to use them. Objective: To compare three methods, each following a different paradigm (Model-Driven, Model-Based and Code-Centric) with respect to their adoption potential by junior software developers engaged in the development of the business layer of a Web 2.0 application. Method: We have conducted a quasi-experiment with 26 graduate students of the University of Alicante. The application developed was a Social Network, which was organized around a fixed set of modules. Three of them, similar in complexity, were used for the experiment. Subjects were asked to use a different method for each module, and then to answer a questionnaire that gathered their perceptions during such use. Results: The results show that the Model-Driven method is regarded as the most useful, although it is also considered the least compatible with previous developers' experiences. They also show that junior software developers feel comfortable with the use of models, and that they are likely to use them if the models are accompanied by a Model-Driven development environment. Conclusions: Despite their relatively low level of compatibility, Model-Driven development methods seem to show a great potential for adoption. That said, however, further experimentation is needed to make it possible to generalize the results to a different population, different methods, other languages and tools, different domains or different application sizes.