<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Levendovszky, Tihamer</style></author><author><style face="normal" font="default" size="100%">Bernhard Rumpe</style></author><author><style face="normal" font="default" size="100%">Bernhard Schaetz</style></author><author><style face="normal" font="default" size="100%">Sprinkle, Jonathan</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Holger Giese,</style></author><author><style face="normal" font="default" size="100%">Karsai, Gabor</style></author><author><style face="normal" font="default" size="100%">Edward Lee,</style></author><author><style face="normal" font="default" size="100%">Bernhard Rumpe</style></author><author><style face="normal" font="default" size="100%">Bernhard Schatz</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Model Evolution and Management</style></title><secondary-title><style face="normal" font="default" size="100%">Model-Based Engineering of Embedded Real-Time Systems, Lecture Notes in Computer Science 6100</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.springerlink.com/content/888565g01l1m6630/fulltext.pdf</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">241-270</style></pages><abstract><style face="normal" font="default" size="100%">As complex software and systems development projects need models as an important planning, structuring and development technique, models now face issues resolved for software earlier: models need to be versioned, differences captured, syntactic and semantic correctness checked as early as possible, documented, presented in easily accessible forms, etc. Quality management needs to be established for models as well as their relationship to other models, to code and to requirement documents precisely clarified and tracked. Business and product requirements, product technologies as well as development tools evolve. This also means we need evolutionary technologies both for models within a language and if the language evolves also for an upgrade of the models. This chapter discusses the state of the art in model management and evolution and sketches what is still necessary for models to become as usable and used as software.</style></abstract></record></records></xml>