Abstract
Model Driven Software Development (MDD) is a vision of software development where models play a core role as primary development artifacts. Its industrial adoption depends on several factors, including possibilities of increasing productivity and quality by using models. In this paper we present a case study of two companies willing to adopt the principles of MDD. One of the companies is in the process of adopting MDD while the other withdrew from its initial intentions. The results provide insights into the differences in requirements for MDD in these organizations, factors determining the decision upon adoption and the potentially suitable modeling notation for the purpose of each of the companies. The analysis of the results from this case study, supported by the conclusions from a previous case study of a successful MDD adoption, show also which conditions should be fulfilled in order to increase the chances of succeeding in adopting MDD.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
