Comparative Analysis Between Model-Driven Architecture and Classical Software Development Methodologies
Comparative Analysis Between Model-Driven Architecture and Classical Software Development Methodologies
DOI:
https://doi.org/10.51473/rcmos.v1i2.2025.1741Keywords:
Model Driven Architecture; Traditional Methodologies; Software EngineeringAbstract
This work presents a theoretical comparative analysis between Model Driven Architecture (MDA) and traditional software development methodologies, investigating technical foundations, benefits, limitations, and contextual applicability of each approach. The general objective consists of conducting a systematic comparison based on criteria established by scientific literature, identifying scenarios where each approach demonstrates superiority. The adopted methodology is characterized as qualitative descriptive-analytical theoretical research, based on bibliographic review of verifiable scientific publications. A comparative framework was established structured in technical dimensions: abstraction and model levels, documentation, software quality, traceability, maintainability, communication, automation, productivity, cost, organizational maturity, and risks. The literature review examined foundations of Waterfall, V-Model, Spiral, and RUP, as well as MDA architecture including concepts of CIM/PIM/PSM, MOF, QVT, XMI, and UML. Empirical studies revealed contradictory evidence regarding MDA productivity benefits, with effectiveness demonstrating high dependence on context, tool maturity, and domain characteristics. Traditional methodologies maintain applicability in projects with stable requirements and experienced teams. Results indicate that MDA offers advantages in separation between business logic and technology, artifact automation, and multi-platform portability, while facing challenges in learning curve, tool maturity, and representation of non-functional requirements. It is concluded that approaches do not constitute mutually exclusive alternatives, being able to coexist in hybrid strategies adapted to specific organizational contexts.
Downloads
References
BOEHM, B. A spiral model of software development and enhancement. Computer, v. 21, n. 5, p. 61–72, 1988. DOI: https://doi.org/10.1109/2.59
BOEHM, B.; HANSEN, W. J. Understanding the Spiral Model as a Tool for Evolutionary Acquisition. CrossTalk: The Journal of Defense Software Engineering, v. 13, n. 5, p. 4–9, 2000.
BRAMBILLA, M.; CABOT, J.; WIMMER, M. Model-Driven Software Engineering in Practice. 2. ed. Morgan & Claypool, 2017. DOI: https://doi.org/10.1007/978-3-031-02549-5
BROY, M.; KRÜGER, I. H.; MEISINGER, M. A Model-Based Approach to Systems Engineering in the Automotive Domain. Software & Systems Modeling, v. 11, n. 4, p. 483–504, 2012.
FORSBERG, K.; MOOZ, H. The relationship of system engineering to the project cycle. INCOSE International Symposium, v. 6, n. 1, p. 57–65, 1996. DOI: https://doi.org/10.1002/j.2334-5837.1991.tb01484.x
FRANCE, R.; RUMPE, B. Model-driven development of complex software. IEEE International Conference on Software Engineering, p. 37–54, 2007. DOI: https://doi.org/10.1109/FOSE.2007.14
HUTCHINSON, J.; WHITTLE, J.; ROUNCEFIELD, M. Model-driven engineering practices in industry. Proceedings of ICSE, p. 633–642, 2011. DOI: https://doi.org/10.1145/1985793.1985882
KLEPPE, A.; WARMER, J.; BAST, W. MDA Explained: The Model Driven Architecture – Practice and Promise. Addison-Wesley, 2003.
KRUCHTEN, P. The Rational Unified Process: An Introduction. Addison-Wesley, 2004.
KURTEV, I. The MDE vision revisited. Journal of Object Technology, v. 19, n. 1, 2020.
MEYER, B. Agile! The Good, the Hype and the Ugly — A critical analysis comparing agile, MDE and classic engineering. Springer, 2014. DOI: https://doi.org/10.1007/978-3-319-05155-0
MOHAGHEGHI, P.; DEHLEN, V. Experiences from applying MDE in industry: A survey. Model-Driven Architecture – Foundations and Applications, p. 256–272, 2008.
MOHAGHEGHI, P.; DEHLEN, V.; NEPLE, T. Definitions and approaches in model-based system engineering. ECMFA 2009, 2009.
OBJECT MANAGEMENT GROUP (OMG). MDA Guide Version 2.0. OMG Document formal/2014-06-01, 2014.
OBJECT MANAGEMENT GROUP (OMG). Meta Object Facility (MOF) 2.5.1 Core Specification, 2016. DOI: https://doi.org/10.1007/978-1-4899-7993-3_914-2
PEREIRA, C.; SILVA, T.; MEIRA, S. A Systematic Review on Model-Driven Development and Traditional Software Engineering. Journal of Systems and Software, v. 167, 110611, 2020.
PRESSMAN, R.; MAXIM, B. Software Engineering: A Practitioner’s Approach. 9. ed. McGraw-Hill, 2019.
ROYCE, W. W. Managing the development of large software systems. Proceedings of IEEE WESCON, 1970.
SELIC, B. The pragmatics of model-driven development. IEEE Software, v. 20, n. 5, p. 19–25, 2003. DOI: https://doi.org/10.1109/MS.2003.1231146
SENDALL, S.; KOZACZYNSKI, W. Model transformation: The heart and soul of model-driven software development. IEEE Software, v. 20, n. 5, p. 42–45, 2003. DOI: https://doi.org/10.1109/MS.2003.1231150
SOMMERVILLE, I. Software Engineering. 10. ed. Pearson, 2016.
STAHL, T.; VÖLTER, M. Model-Driven Software Development: Technology, Engineering, Management. Wiley, 2006.
Downloads
Published
Issue
Section
Categories
License
Copyright (c) 2025 Paulo Vinicius Alves Melo, Mauro José Araújo de Melo (Autor)
This work is licensed under a Creative Commons Attribution 4.0 International License.
This work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). This means you are free to:
- Share — copy and redistribute the material in any medium or format.
- Adapt — remix, transform, and build upon the material for any purpose, even commercially.
The use of this material is conditioned upon proper attribution to the original author(s), providing a link to the license, and indicating if changes were made. The license does not require permission from the author or the publisher as long as these conditions are met.
The Creative Commons license logo is displayed permanently in the footer of the journal.
The copyright of the manuscript can be retained by the authors without restrictions and can be requested at any time, even after publication in the journal.
