Peter Ebraert, Andreas Classen, P. Heymans, T. D'Hondt
{"title":"面向变更编程的特征图","authors":"Peter Ebraert, Andreas Classen, P. Heymans, T. D'Hondt","doi":"10.3233/978-1-60750-014-8-107","DOIUrl":null,"url":null,"abstract":"Abstract. The idea of feature-oriented programming is to map requirements to fea-tures, concepts that can be composed to form a software product. Change-orientedprogramming (ChOP), in which features are seen as sets of changes that can beapplied to a base program, has recently been proposed as an approach to FOP.Changes are recorded as the programmer works and can encapsulate any developeraction, including the removing of code.Before changes can be combined to form a product, it has to be verified that thereare no harmful interactions between selected changes. There exists, however, noformal model of the current approach that may serve as a reference specificationfor ChOP implementations. In an effort to fill this gap, we propose a formal modelof ChOP, which, as we will show, maps to the well-understood notion of feature di-agram. Thanks to this, we can reuse a number of results in feature diagram researchand apply them to ChOP.Keywords. Formal Methods, Feature-Oriented Programming, Feature Diagrams,Software Product Lines","PeriodicalId":382411,"journal":{"name":"International Conference on Feature Interactions in Software and Communication Systems","volume":"14 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"12","resultStr":"{\"title\":\"Feature Diagrams for Change-Oriented Programming\",\"authors\":\"Peter Ebraert, Andreas Classen, P. Heymans, T. D'Hondt\",\"doi\":\"10.3233/978-1-60750-014-8-107\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Abstract. The idea of feature-oriented programming is to map requirements to fea-tures, concepts that can be composed to form a software product. Change-orientedprogramming (ChOP), in which features are seen as sets of changes that can beapplied to a base program, has recently been proposed as an approach to FOP.Changes are recorded as the programmer works and can encapsulate any developeraction, including the removing of code.Before changes can be combined to form a product, it has to be verified that thereare no harmful interactions between selected changes. There exists, however, noformal model of the current approach that may serve as a reference specificationfor ChOP implementations. In an effort to fill this gap, we propose a formal modelof ChOP, which, as we will show, maps to the well-understood notion of feature di-agram. Thanks to this, we can reuse a number of results in feature diagram researchand apply them to ChOP.Keywords. Formal Methods, Feature-Oriented Programming, Feature Diagrams,Software Product Lines\",\"PeriodicalId\":382411,\"journal\":{\"name\":\"International Conference on Feature Interactions in Software and Communication Systems\",\"volume\":\"14 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1900-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"12\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"International Conference on Feature Interactions in Software and Communication Systems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.3233/978-1-60750-014-8-107\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"International Conference on Feature Interactions in Software and Communication Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.3233/978-1-60750-014-8-107","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Abstract. The idea of feature-oriented programming is to map requirements to fea-tures, concepts that can be composed to form a software product. Change-orientedprogramming (ChOP), in which features are seen as sets of changes that can beapplied to a base program, has recently been proposed as an approach to FOP.Changes are recorded as the programmer works and can encapsulate any developeraction, including the removing of code.Before changes can be combined to form a product, it has to be verified that thereare no harmful interactions between selected changes. There exists, however, noformal model of the current approach that may serve as a reference specificationfor ChOP implementations. In an effort to fill this gap, we propose a formal modelof ChOP, which, as we will show, maps to the well-understood notion of feature di-agram. Thanks to this, we can reuse a number of results in feature diagram researchand apply them to ChOP.Keywords. Formal Methods, Feature-Oriented Programming, Feature Diagrams,Software Product Lines