The calculations of NPV (net present value) and cash flows provide useful means when organizations come to decide whether they should transit from one-off development to software product line (SPL) based development, how much investment should be made for the development of SPL, whether their investments are being successfully returned from the on-going SPL adoption programs, or whether they should modify their on-going programs. The paper first summarizes experiences that were gathered from the Toshiba Software Factory in which a series of product lines for the domain of electric power generation, called EPG-SPL, has been developed and practically applied since 1962. At present, the 4 generation of EPG-SPL is being applied. The purpose of this paper is to present how NPV and cash flow calculations can be used if it is applied to the management and controls of SPL adoption, and to propose a guide for monitoring the shortage of return-on- investment every year, which is necessary to achieve successful SPL adoptions.
{"title":"A Guide for Management and Financial Controls of Product Lines","authors":"Y. Matsumoto","doi":"10.1109/SPLINE.2007.26","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.26","url":null,"abstract":"The calculations of NPV (net present value) and cash flows provide useful means when organizations come to decide whether they should transit from one-off development to software product line (SPL) based development, how much investment should be made for the development of SPL, whether their investments are being successfully returned from the on-going SPL adoption programs, or whether they should modify their on-going programs. The paper first summarizes experiences that were gathered from the Toshiba Software Factory in which a series of product lines for the domain of electric power generation, called EPG-SPL, has been developed and practically applied since 1962. At present, the 4 generation of EPG-SPL is being applied. The purpose of this paper is to present how NPV and cash flow calculations can be used if it is applied to the management and controls of SPL adoption, and to propose a guide for monitoring the shortage of return-on- investment every year, which is necessary to achieve successful SPL adoptions.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"22 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":"116125644","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}
D. Ganesan, J. Knodel, R. Kolb, Uwe Haury, G. Meier
Quality assurance in general and testing in particular remains as an unsolved problem in product line engineering. It is unclear, from an economic point of view, whether one should test each product line member separately or test just product-specific parts and compose them with tested core assets from family engineering. While the former strategy introduces redundancy in testing, the latter strategy is also more difficult because of genericity. Ideally, we need to carefully calculate cost-benefits of both cases and define a test strategy accordingly. Currently, there is no economic model for testing in the context of product lines. Thus, we introduce an initial economic model, and then perform Monte-Carlo simulations to calculate cost-benefit of the two test strategies. For the Testo product line of climate and flue gas measurement devices, the results showed that, using an infrastructure-focused test strategy, on average a cost saving of 13% can be expected with 87% certainty.
{"title":"Comparing Costs and Benefits of Different Test Strategies for a Software Product Line: A Study from Testo AG","authors":"D. Ganesan, J. Knodel, R. Kolb, Uwe Haury, G. Meier","doi":"10.1109/SPLINE.2007.21","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.21","url":null,"abstract":"Quality assurance in general and testing in particular remains as an unsolved problem in product line engineering. It is unclear, from an economic point of view, whether one should test each product line member separately or test just product-specific parts and compose them with tested core assets from family engineering. While the former strategy introduces redundancy in testing, the latter strategy is also more difficult because of genericity. Ideally, we need to carefully calculate cost-benefits of both cases and define a test strategy accordingly. Currently, there is no economic model for testing in the context of product lines. Thus, we introduce an initial economic model, and then perform Monte-Carlo simulations to calculate cost-benefit of the two test strategies. For the Testo product line of climate and flue gas measurement devices, the results showed that, using an infrastructure-focused test strategy, on average a cost saving of 13% can be expected with 87% certainty.","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":"116299304","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}
Publish-discover-compose paradigm of service-oriented computing (SOC) presents a challenge on service applicability. Services are not just for predefined clients, rather for potentially many unknown clients. Hence, published services should be highly adaptable to various service clients and contexts. For that, service variability must carefully be modeled by considering the unique computing paradigm and requirements of SOC such as dynamic discovery and composition of services. Current SOC approaches to modeling services largely focus on defining business processes and service components without considering service variability in sufficient details. In this paper, we first compare the variability on conventional applications and the variability on SOC. Then, we identify four types of variability on services. For the types of service variability, we present a method to model service variability and design adaptable services. Using our proposed framework, we believe the applicability and reusability of such services can be greatly increased.
{"title":"A Variability Modeling Method for Adaptable Services in Service-Oriented Computing","authors":"Soo-Ho Chang, Soo Dong Kim","doi":"10.1109/SPLINE.2007.10","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.10","url":null,"abstract":"Publish-discover-compose paradigm of service-oriented computing (SOC) presents a challenge on service applicability. Services are not just for predefined clients, rather for potentially many unknown clients. Hence, published services should be highly adaptable to various service clients and contexts. For that, service variability must carefully be modeled by considering the unique computing paradigm and requirements of SOC such as dynamic discovery and composition of services. Current SOC approaches to modeling services largely focus on defining business processes and service components without considering service variability in sufficient details. In this paper, we first compare the variability on conventional applications and the variability on SOC. Then, we identify four types of variability on services. For the types of service variability, we present a method to model service variability and design adaptable services. Using our proposed framework, we believe the applicability and reusability of such services can be greatly increased.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"21 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":"123577845","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}
The widespread use of the product line approach allows companies to realize significant improvements in time-to- market, cost, productivity, and quality. However, a fundamental problem in software product line engineering is that a product line of industrial size can easily incorporate several thousand variable features. The complexity caused by this amount of variability makes variability management and product derivation tasks extremely difficult. To address this problem, we present a new method to optimize the variability provided in a software product line. Our method constructs a visualization that provides a classification of the usage of variable features in real products derived from the product line. We show how this classification can be used to derive restructuring strategies for simplifying the variability. The effectiveness of our work is demonstrated by presenting a case study of optimizing the variability in a large industrial software product line.
{"title":"Optimization of Variability in Software Product Lines","authors":"Felix Lösch, E. Plödereder","doi":"10.1109/SPLINE.2007.31","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.31","url":null,"abstract":"The widespread use of the product line approach allows companies to realize significant improvements in time-to- market, cost, productivity, and quality. However, a fundamental problem in software product line engineering is that a product line of industrial size can easily incorporate several thousand variable features. The complexity caused by this amount of variability makes variability management and product derivation tasks extremely difficult. To address this problem, we present a new method to optimize the variability provided in a software product line. Our method constructs a visualization that provides a classification of the usage of variable features in real products derived from the product line. We show how this classification can be used to derive restructuring strategies for simplifying the variability. The effectiveness of our work is demonstrated by presenting a case study of optimizing the variability in a large industrial software product line.","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":"129612910","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}
The introduction of a software product line may pose a great organizational challenge in the domain of high- integrity systems. Project and technical managers within an organization need to be assured that the reusable assets of a product line are reliable and trustworthy, particularly when project teams do not have full control over the development of these assets. In this paper we report on our experience with the establishment of a software product line for an aerospace Engine Monitoring Unit (EMU). Specifically, we report on challenges encountered with the configuration management and certification of EMU products derived from the product line. These two areas are still to be addressed adequately by the product line community as they are central for the management of product line assets across different projects within an organization.
{"title":"Challenges of Establishing a Software Product Line for an Aerospace Engine Monitoring System","authors":"I. Habli, T. Kelly","doi":"10.1109/SPLINE.2007.37","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.37","url":null,"abstract":"The introduction of a software product line may pose a great organizational challenge in the domain of high- integrity systems. Project and technical managers within an organization need to be assured that the reusable assets of a product line are reliable and trustworthy, particularly when project teams do not have full control over the development of these assets. In this paper we report on our experience with the establishment of a software product line for an aerospace Engine Monitoring Unit (EMU). Specifically, we report on challenges encountered with the configuration management and certification of EMU products derived from the product line. These two areas are still to be addressed adequately by the product line community as they are central for the management of product line assets across different projects within an organization.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"121 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":"126648247","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}
Features have been widely used by the product line community to model variability. They represent the common and variable characteristics of the members of a product line. They are very well suited for the configuration of product line members. Outside the product line community, use cases are also widely used to model the functionality of systems at a similar level of abstraction but from a user perspective. Significant work has been done by several authors regarding the possible relationship between these two perspectives of a system. Nonetheless, this has been done in an informal way. In this paper we explore the relationships between these two perspectives and describe a possible approach to automate the transformation from UML use case to feature models.
{"title":"Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines","authors":"A. Bragança, R. J. Machado","doi":"10.1109/SPLINE.2007.17","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.17","url":null,"abstract":"Features have been widely used by the product line community to model variability. They represent the common and variable characteristics of the members of a product line. They are very well suited for the configuration of product line members. Outside the product line community, use cases are also widely used to model the functionality of systems at a similar level of abstraction but from a user perspective. Significant work has been done by several authors regarding the possible relationship between these two perspectives of a system. Nonetheless, this has been done in an informal way. In this paper we explore the relationships between these two perspectives and describe a possible approach to automate the transformation from UML use case to feature models.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"20 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":"129773504","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}
Cost reduction, time to market, product quality improvement, and the support of technological evolution are all critical issues that software companies must face to be competitive in today's market. Software product line engineering (SPLE) is one approach to address these issues. This paper presents the experiences of Mondragon Sistemas de Informacion, a small-to-medium company, of introducing software product line engineering. The paper describes reports the benefits generated by deploying a software product line for developing programmable logic controllers' programs for metal processing lines as well as lessons learned.
降低成本、缩短上市时间、提高产品质量以及支持技术发展都是软件公司在当今市场中必须面对的关键问题。软件产品线工程(SPLE)是解决这些问题的一种方法。本文介绍了蒙德拉贡信息系统公司(Mondragon Sistemas de information)引入软件产品线工程的经验。本文介绍了通过为金属加工生产线开发可编程逻辑控制器程序部署软件产品线所产生的好处以及所吸取的经验教训。
{"title":"Introducing Software Product Line Engineering for Metal Processing Lines in a Small to Medium Enterprise","authors":"D. Sellier, Gorka Benguria, G. Urchegui","doi":"10.1109/SPLINE.2007.14","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.14","url":null,"abstract":"Cost reduction, time to market, product quality improvement, and the support of technological evolution are all critical issues that software companies must face to be competitive in today's market. Software product line engineering (SPLE) is one approach to address these issues. This paper presents the experiences of Mondragon Sistemas de Informacion, a small-to-medium company, of introducing software product line engineering. The paper describes reports the benefits generated by deploying a software product line for developing programmable logic controllers' programs for metal processing lines as well as lessons learned.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"17 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":"122414343","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}
A mechanically formalized feature modeling meta-model is presented. This theory is a generic higher-order formalization of a mathematical model synthesizing several feature modeling approaches found in the literature. This meta-model supports not only a better understanding of the various approaches to feature modeling, but also supports reasoning about and within feature model approaches, feature models, and on feature trees and their configurations.
{"title":"Reasoning about Feature Models in Higher-Order Logic","authors":"Mikoláš Janota, J. Kiniry","doi":"10.1109/SPLINE.2007.36","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.36","url":null,"abstract":"A mechanically formalized feature modeling meta-model is presented. This theory is a generic higher-order formalization of a mathematical model synthesizing several feature modeling approaches found in the literature. This meta-model supports not only a better understanding of the various approaches to feature modeling, but also supports reasoning about and within feature model approaches, feature models, and on feature trees and their configurations.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"104 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":"133628688","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}
Besides ordinary applications, also infrastructure software such as operating systems or database management systems is being developed as a software product line. With proper tool support these systems can be configured easily by selecting features in a feature model. However, in the future multi-level architectures of layered product lines will be common practice. For humans the feature-based configuration will become increasingly complex, as the number of configurable features will be tremendous. Our goal is to reduce this complexity. The approach is based on the observation that many configuration decisions could be automated by statically analyzing the code of layers on top of an infrastructure product line. Motivated by use cases the paper presents the concepts behind our analysis tool, which is able to automate the configuration in many cases. First results in the context of a feature-oriented version of the Berkeley DB illustrate the potential of this novel approach.
{"title":"Tailoring Infrastructure Software Product Lines by Static Application Analysis","authors":"Horst Schirmeier, O. Spinczyk","doi":"10.1109/SPLINE.2007.33","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.33","url":null,"abstract":"Besides ordinary applications, also infrastructure software such as operating systems or database management systems is being developed as a software product line. With proper tool support these systems can be configured easily by selecting features in a feature model. However, in the future multi-level architectures of layered product lines will be common practice. For humans the feature-based configuration will become increasingly complex, as the number of configurable features will be tremendous. Our goal is to reduce this complexity. The approach is based on the observation that many configuration decisions could be automated by statically analyzing the code of layers on top of an infrastructure product line. Motivated by use cases the paper presents the concepts behind our analysis tool, which is able to automate the configuration in many cases. First results in the context of a feature-oriented version of the Berkeley DB illustrate the potential of this novel approach.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"46 17 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":"124669980","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}
Jules White, D. Schmidt, Egon Wuchner, A. Nechypurenko
Product-line architectures (PLAs) designed for mobile devices create a unique challenge for automated product variant selection engines since variants must be derived on-the-fly as devices are discovered. Current automation techniques do not incorporate device resource consumption constraints into variant selection and do not address how a PLA can be designed to improve automated variant selection speed. This paper presents a tool called Scatter whose input is (1) the requirements of PLA construction and (2) the resources available on a discovered mobile device and whose output is the optimal variant that can be deployed to the device. Scatter provides automatic variant selection based on configuration and resource constraints and also ensures that variant selection is optimal with regard to a configurable cost function. The paper presents our results from experiments with Scatter and how PLA design decisions affect a constraint-based variant selection engine's solving speed.
{"title":"Automating Product-Line Variant Selection for Mobile Devices","authors":"Jules White, D. Schmidt, Egon Wuchner, A. Nechypurenko","doi":"10.1109/SPLINE.2007.19","DOIUrl":"https://doi.org/10.1109/SPLINE.2007.19","url":null,"abstract":"Product-line architectures (PLAs) designed for mobile devices create a unique challenge for automated product variant selection engines since variants must be derived on-the-fly as devices are discovered. Current automation techniques do not incorporate device resource consumption constraints into variant selection and do not address how a PLA can be designed to improve automated variant selection speed. This paper presents a tool called Scatter whose input is (1) the requirements of PLA construction and (2) the resources available on a discovered mobile device and whose output is the optimal variant that can be deployed to the device. Scatter provides automatic variant selection based on configuration and resource constraints and also ensures that variant selection is optimal with regard to a configurable cost function. The paper presents our results from experiments with Scatter and how PLA design decisions affect a constraint-based variant selection engine's solving speed.","PeriodicalId":202515,"journal":{"name":"11th International Software Product Line Conference (SPLC 2007)","volume":"10 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":"125634869","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
扫码关注我们
求助内容：
应助结果提醒方式：