Software unit test coverage and adequacy
ACM Computing Surveys (CSUR)
Domain-Driven Design: Tacking Complexity In the Heart of Software
Domain-Driven Design: Tacking Complexity In the Heart of Software
Design and code inspections to reduce errors in program development
Software pioneers
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
The Art of Software Testing
Model-Driven Software Development: Technology, Engineering, Management
Model-Driven Software Development: Technology, Engineering, Management
WebDSL: A Case Study in Domain-Specific Language Engineering
Generative and Transformational Techniques in Software Engineering II
Software Language Engineering: Creating Domain-Specific Languages Using Metamodels
Software Language Engineering: Creating Domain-Specific Languages Using Metamodels
A model driven software factory using domain specific languages
ECMDA-FA'07 Proceedings of the 3rd European conference on Model driven architecture-foundations and applications
Adopting model driven software development in industry: a case study at two companies
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Model-Driven engineering in a large industrial context — motorola case study
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
A case study in evidence-based DSL evolution
ECMFA'13 Proceedings of the 9th European conference on Modelling Foundations and Applications
| Hi-index | 0.00 |
Model-driven software development (MDSD) has been on the rise over the past few years and is becoming more and more mature. However, evaluation in real-life industrial context is still scarce. In this paper, we present a case-study evaluating the applicability of a state-of-the-art MDSD tool, MOD4J, a suite of domain specific languages (DSLs) for developing administrative enterprise applications. MOD4J was used to partially rebuild an industrially representative application. This implementation was then compared to a base implementation based on elicited success criteria. Our evaluation leads to a number of recommendations to improve MOD4J. We conclude that having extension points for hand-written code is a good feature for a model driven software development environment.