Model-Driven Development Using UML 2.0: Promises and Pitfalls
- 21 February 2006
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in Computer
- Vol. 39 (2) , 59-66
- https://doi.org/10.1109/mc.2006.65
Abstract
Experience indicates that effective complexity management mechanisms automate mundane development tasks and provide strong support for separation of concerns. For example, current high-level programming languages and integrated development environments provide abstractions that shield developers from intricate lower-level details and offer automated support for transforming abstract representations of source code into faithful machine-executable forms. The Object Management Group initiated the Unified Modeling Language 2.0 effort to address significant problems in earlier versions. While UML 2.0 improves over earlier versions in some aspects, its size and complexity can present a problem to users, tool developers, and OMG working groups charged with evolving the standard.Keywords
This publication has 5 references indexed in Scilit:
- Directives for Composing Aspect-Oriented Design Class ModelsPublished by Springer Nature ,2006
- A Tool-Supported Approach to Testing UML Design ModelsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2005
- UML – the Good, the Bad or the Ugly? Perspectives from a panel of expertsSoftware and Systems Modeling, 2005
- Aspect-oriented approach to early design modellingIEE Proceedings - Software, 2004
- Test adequacy criteria for UML design modelsSoftware Testing, Verification and Reliability, 2003