Software product lines aim to create highly configurable programs from a set of features. Common belief and recent studies suggest that aspects are well-suited for implementing features. We evaluate the suitability of AspectJ with respect to this task by a case study that refactors the embedded database system Berkeley DB into 38 features. Contrary to our initial expectations, the results were not encouraging. As the number of aspects in a feature grows, there is a noticeable decrease in code readability and maintainability. Most of the unique and powerful features of AspectJ were not needed. We document where AspectJ is unsuitable for implementing features of refactored legacy applications and explain why.
{"title":"A Case Study Implementing Features Using AspectJ","authors":"Christian Kästner, S. Apel, D. Batory","doi":"10.1109/SPLINE.2007.12","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.12","url":null,"abstract":"Software product lines aim to create highly configurable programs from a set of features. Common belief and recent studies suggest that aspects are well-suited for implementing features. We evaluate the suitability of AspectJ with respect to this task by a case study that refactors the embedded database system Berkeley DB into 38 features. Contrary to our initial expectations, the results were not encouraging. As the number of aspects in a feature grows, there is a noticeable decrease in code readability and maintainability. Most of the unique and powerful features of AspectJ were not needed. We document where AspectJ is unsuitable for implementing features of refactored legacy applications and explain why.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"181 5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133073379","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Most embedded software in the consumer electronics is generally developed through derivation from legacy software. Many new projects are derived from preexisting ones, through modification of functionality, optimization of performance and application new features. Particularly in the digital AV (audio & video) domain, the rise of 'digital convergence' has lead to a need for the functionality of products to be integrated and unified across different products. In this situation, a product line approach might be more efficient and effective rather than a product-oriented approach. The characteristics of this environment make the product line approach ideal for the digital AV domain. In this paper, we present our experience of designing product line architecture as a common, reference architecture in the digital AV domain. We describe our development process with application on a case project. We also show concrete principles and guidelines to design and build a software product line in consideration of the characteristics of the digital AV domain. We developed guidelines with our experience and domain knowledge in the digital AV domain mainly focused on reusability, maintainability and flexibility. We believe that concrete design principles and guidelines can significantly enhance those attributes in the productization. As a case study, we describe how to find, extract and develop core assets of the product family against our process and guidelines. We found candidates of architecture and core assets, and then extracted target architecture via re-engineering. With the analysis information and domain knowledge of legacy system, we developed a reference architecture with commonality and variability of the target domain. We used the term 'software platform' for the reference architecture and set of core assets as an implementation of software product line. We evaluated the platform against the guidelines as a design guideline itself and quality attribute as well.
{"title":"Building Software Product Line from the Legacy Systems \"Experience in the Digital Audio and Video Domain\"","authors":"Kangtae Kim, Hyungrok Kim, Woomok Kim","doi":"10.1109/SPLINE.2007.27","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.27","url":null,"abstract":"Most embedded software in the consumer electronics is generally developed through derivation from legacy software. Many new projects are derived from preexisting ones, through modification of functionality, optimization of performance and application new features. Particularly in the digital AV (audio & video) domain, the rise of 'digital convergence' has lead to a need for the functionality of products to be integrated and unified across different products. In this situation, a product line approach might be more efficient and effective rather than a product-oriented approach. The characteristics of this environment make the product line approach ideal for the digital AV domain. In this paper, we present our experience of designing product line architecture as a common, reference architecture in the digital AV domain. We describe our development process with application on a case project. We also show concrete principles and guidelines to design and build a software product line in consideration of the characteristics of the digital AV domain. We developed guidelines with our experience and domain knowledge in the digital AV domain mainly focused on reusability, maintainability and flexibility. We believe that concrete design principles and guidelines can significantly enhance those attributes in the productization. As a case study, we describe how to find, extract and develop core assets of the product family against our process and guidelines. We found candidates of architecture and core assets, and then extracted target architecture via re-engineering. With the analysis information and domain knowledge of legacy system, we developed a reference architecture with commonality and variability of the target domain. We used the term 'software platform' for the reference architecture and set of core assets as an implementation of software product line. We evaluated the platform against the guidelines as a design guideline itself and quality attribute as well.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123659175","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
An aspect-based extension to a text transformation language provides higher-order transformations that can be used to represent variability in generative product line engineering. We show by example how these higher-order transformations compare with first order transformations. We also detail how the approach has been implemented as an extension of MOFScript, an existing model-to-text transformation language.
{"title":"Higher-Order Transformations for Product Lines","authors":"Jon Oldevik, Øystein Haugen","doi":"10.1109/SPLINE.2007.11","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.11","url":null,"abstract":"An aspect-based extension to a text transformation language provides higher-order transformations that can be used to represent variability in generative product line engineering. We show by example how these higher-order transformations compare with first order transformations. We also detail how the approach has been implemented as an extension of MOFScript, an existing model-to-text transformation language.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134236032","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Enterprise software is an untapped area for software product lines (SPL) approach. Our current understanding of enterprise SPL is as follows. The enterprise SPL is based upon an application centric architecture, which manages variability of platform and non-functional requirements, and achieves variability management for functional requirements in an application layer. NRI has been executing this approach through two projects, (I) development of semi made-to-order package software for the retail chains and (II) restructuring of enterprise systems owned by Seven & i Holdings, the biggest conglomerate of retail industry in Japan. This paper mainly describes what application centric architecture is and how this approach differs from others with lessons learned for the last five years.
企业软件是软件产品线(SPL)方法尚未开发的领域。我们目前对企业SPL的理解如下。企业SPL基于以应用程序为中心的体系结构，管理平台和非功能需求的可变性，并在应用层实现功能需求的可变性管理。NRI一直在通过两个项目来执行这种方法，(I)为零售连锁店开发半定制套装软件，(II)重组日本最大的零售企业集团Seven & I Holdings拥有的企业系统。本文主要描述了什么是以应用程序为中心的体系结构，以及这种方法与过去五年的经验教训有何不同。
{"title":"Software Product Lines Approach in Enterprise System Development","authors":"Y. Ishida","doi":"10.1109/SPLINE.2007.18","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.18","url":null,"abstract":"Enterprise software is an untapped area for software product lines (SPL) approach. Our current understanding of enterprise SPL is as follows. The enterprise SPL is based upon an application centric architecture, which manages variability of platform and non-functional requirements, and achieves variability management for functional requirements in an application layer. NRI has been executing this approach through two projects, (I) development of semi made-to-order package software for the retail chains and (II) restructuring of enterprise systems owned by Seven & i Holdings, the biggest conglomerate of retail industry in Japan. This paper mainly describes what application centric architecture is and how this approach differs from others with lessons learned for the last five years.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134373610","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Danfoss drives - one of the largest producers of frequency converters in the world - is in a situation like many others: it has to produce a number of product series with an increasing number of variants, while at the same time decreasing time-to-market and keeping development costs low. As part of the strategy to master this challenge, Danfoss Drives decided to reduce software development efforts by migrating to a product line approach. This paper describes the approach Danfoss Drives took to successfully introduce software product line principles into its organization.
{"title":"Minimally Invasive Migration to Software Product Lines","authors":"H. Jepsen, Jan Gaardsted Dall, Danilo Beuche","doi":"10.1109/SPLINE.2007.30","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.30","url":null,"abstract":"Danfoss drives - one of the largest producers of frequency converters in the world - is in a situation like many others: it has to produce a number of product series with an increasing number of variants, while at the same time decreasing time-to-market and keeping development costs low. As part of the strategy to master this challenge, Danfoss Drives decided to reduce software development efforts by migrating to a product line approach. This paper describes the approach Danfoss Drives took to successfully introduce software product line principles into its organization.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116603546","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
This report explains the challenges experienced as Overwatch Textron Systems transitioned to a software product line approach. Overwatch Textron Systems provides both software products and custom software development in the domain of intelligence planning, collection and analysis to the U.S. Government and its allies. This report: a) Describes the approach taken to transition Overwatch Textron Systems to a product line organization. b) Provides an overview of the Overwatch Textron Systems software product line; the Overwatch Intelligence Center. c) Describes the product line architecture that is key to the Overwatch Intelligence Center software product line. d) Provides a summary of the lessons learned during the transition.
{"title":"Experiences with Product Line Development of Multi-Discipline Analysis Software at Overwatch Textron Systems","authors":"P. Jensen","doi":"10.1109/SPLINE.2007.25","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.25","url":null,"abstract":"This report explains the challenges experienced as Overwatch Textron Systems transitioned to a software product line approach. Overwatch Textron Systems provides both software products and custom software development in the domain of intelligence planning, collection and analysis to the U.S. Government and its allies. This report: a) Describes the approach taken to transition Overwatch Textron Systems to a product line organization. b) Provides an overview of the Overwatch Textron Systems software product line; the Overwatch Intelligence Center. c) Describes the product line architecture that is key to the Overwatch Intelligence Center software product line. d) Provides a summary of the lessons learned during the transition.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"108 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125488111","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Companies such as Toyota have achieved significant competitive advantage by treating product production as a system that can be planned and optimized. Software product line organizations can achieve similar advantage when they explicitly coordinate the actions of core asset and product developers. We describe a technique for planning the production system for a software product line organization. The technique encompasses a production strategy, which relates the production goals of the product line to the method of core asset and product development; and a production method, which coordinates the development of core assets with the production of products. The results of the technique are documented in a production plan, which guides the product developers through the steps of production. Data gathered from representatives of SPLC Product Line Hall of Fame members and our experience working with product line organizations are used to illustrate problems and specify solutions.
{"title":"A Production System for Software Product Lines","authors":"Gary J. Chastek, P. Donohoe, J. McGregor","doi":"10.1109/SPLINE.2007.29","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.29","url":null,"abstract":"Companies such as Toyota have achieved significant competitive advantage by treating product production as a system that can be planned and optimized. Software product line organizations can achieve similar advantage when they explicitly coordinate the actions of core asset and product developers. We describe a technique for planning the production system for a software product line organization. The technique encompasses a production strategy, which relates the production goals of the product line to the method of core asset and product development; and a production method, which coordinates the development of core assets with the production of products. The results of the technique are documented in a production plan, which guides the product developers through the steps of production. Data gathered from representatives of SPLC Product Line Hall of Fame members and our experience working with product line organizations are used to illustrate problems and specify solutions.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115009533","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：