MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
Tracing Evolution Changes of Software Artifacts through Model Synchronization
ICSM '04 Proceedings of the 20th IEEE International Conference on Software Maintenance
ICEBE '05 Proceedings of the IEEE International Conference on e-Business Engineering
Automated impact analysis of UML models
Journal of Systems and Software
Service-Oriented Modeling and Architecture for Realization of an SOA
SCC '06 Proceedings of the IEEE International Conference on Services Computing
Morpheus: Semantics-based Incremental Change Propagation in SOA-based Solutions
SCC '08 Proceedings of the 2008 IEEE International Conference on Services Computing - Volume 1
SOMA-ME: a platform for the model-driven design of SOA solutions
IBM Systems Journal
Evolution and change management of XML-based systems
Journal of Systems and Software
DaemonX: Design, Adaptation, Evolution, and Management of Native XML (and More Other) Formats
Proceedings of International Conference on Information Integration and Web-based Applications & Services
Hi-index | 0.00 |
Existing tools for model-driven development support automated change management across predefined models with precisely known dependencies. These tools cannot be easily applied to scenarios where we have a diverse set of models and relationships, and where human judgment and impact analysis are critical to introducing and managing changes. Such scenarios arise in model-based development of service oriented architectures (SOA), where a plethora of high-level models representing different aspects of the business (requirements, processes, data) need to be translated into service models, and changes across these models need to be carefully analyzed and propagated. To support the process of model evolution, we present an extensible framework that can automatically identify possible changes in any MOF-compliant model. Changes across different model types can be easily related through a user interface and via rules that are programmed at specified plug-in points. At runtime, when an instance of a model is changed, the framework performs fine-grained analysis to identify impacted models and elements therein. It also allows analysts to selectively apply or reject changes based on the specific context and summarizes the incremental impact on downstream elements as choices are made. We share our experience in using our framework during the design of a SOA-based system that underwent several changes in business models, necessitating changes in the associated service design.