{"title":"基于跟踪的模型转换的保留模式的正式框架","authors":"Thomas Goldschmidt, A. Uhl","doi":"10.1109/SEAA.2011.23","DOIUrl":null,"url":null,"abstract":"Model-to-model (M2M) transformations play an important role within model-driven development. Modern M2Mapproaches support incremental updates to the target model according to changes in the source model(s). Bidirectional transformation approaches even allow to incrementally translate target model changes back to the source model. However, in some cases, e.g., if the target model should be refined either manually or automatically, it is important that target model changes are not overwritten if the original transformation is re-executed. There is currently only weak support for this kind of retainment by transformation engines. However, in many transformation engines a transformation trace is available which keeps record of a transformation's actions. In this paper, we exploit this information and define patterns which allow transformation engineers to trim transformations to facilitate the handling of target model changes. We describe a formal framework which serves as basis for implementing these retainment patterns.","PeriodicalId":107972,"journal":{"name":"2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications","volume":"44 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"A Formal Framework for Retainment Patterns for Trace-Based Model Transformations\",\"authors\":\"Thomas Goldschmidt, A. Uhl\",\"doi\":\"10.1109/SEAA.2011.23\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Model-to-model (M2M) transformations play an important role within model-driven development. Modern M2Mapproaches support incremental updates to the target model according to changes in the source model(s). Bidirectional transformation approaches even allow to incrementally translate target model changes back to the source model. However, in some cases, e.g., if the target model should be refined either manually or automatically, it is important that target model changes are not overwritten if the original transformation is re-executed. There is currently only weak support for this kind of retainment by transformation engines. However, in many transformation engines a transformation trace is available which keeps record of a transformation's actions. In this paper, we exploit this information and define patterns which allow transformation engineers to trim transformations to facilitate the handling of target model changes. We describe a formal framework which serves as basis for implementing these retainment patterns.\",\"PeriodicalId\":107972,\"journal\":{\"name\":\"2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications\",\"volume\":\"44 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2011-08-30\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SEAA.2011.23\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SEAA.2011.23","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A Formal Framework for Retainment Patterns for Trace-Based Model Transformations
Model-to-model (M2M) transformations play an important role within model-driven development. Modern M2Mapproaches support incremental updates to the target model according to changes in the source model(s). Bidirectional transformation approaches even allow to incrementally translate target model changes back to the source model. However, in some cases, e.g., if the target model should be refined either manually or automatically, it is important that target model changes are not overwritten if the original transformation is re-executed. There is currently only weak support for this kind of retainment by transformation engines. However, in many transformation engines a transformation trace is available which keeps record of a transformation's actions. In this paper, we exploit this information and define patterns which allow transformation engineers to trim transformations to facilitate the handling of target model changes. We describe a formal framework which serves as basis for implementing these retainment patterns.