S. Abrahão, Andy J. Nolan, P. Clements, J. McGregor
The objective of this workshop is to bring together researchers and practitioners to report and discuss the challenges and opportunities for integrating quantitative methods in product line engineering with the objective of achieving both technical and business goals. In particular, we are seeking contributions that, on the one hand, deal with product line estimation and metrics for the effective management of product line projects, and on the other hand, provide some insight into new trends in value-based product line engineering.
{"title":"First International Workshop on Quantitative Methods in Software Product Line Engineering","authors":"S. Abrahão, Andy J. Nolan, P. Clements, J. McGregor","doi":"10.1109/SPLC.2011.12","DOIUrl":"https://doi.org/10.1109/SPLC.2011.12","url":null,"abstract":"The objective of this workshop is to bring together researchers and practitioners to report and discuss the challenges and opportunities for integrating quantitative methods in product line engineering with the objective of achieving both technical and business goals. In particular, we are seeking contributions that, on the one hand, deal with product line estimation and metrics for the effective management of product line projects, and on the other hand, provide some insight into new trends in value-based product line engineering.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128217269","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}
Andy J. Nolan, S. Abrahão, P. Clements, A. Pickard
A complex system's requirements almost always remain uncertain late into its software development. In gas turbine engine control systems at Rolls-Royce, for a traditional project (non-product line) typically 50% of requirements will change between Critical Design Review and Entry into Service. Requirements uncertainty is particularly relevant when defining the scope of a Software Product Line. If the core asset team fails to recognise or accommodate requirements uncertainty, changes will manifest later in the product line. If the core asset team over-compensates by adding too much functionality or variability to account for a wide range of uncertainty, they will invest effort that may never be required. The optimal balance can be found through an application of requirements uncertainty analysis and understanding the balance between the impact of risk and mitigation effort. This paper first describes the use of the requirements uncertainty analysis technique at Rolls-Royce for traditional (non-product line) software development and then explains how this technique works in the context of a software product line.
{"title":"Requirements Uncertainty in a Software Product Line","authors":"Andy J. Nolan, S. Abrahão, P. Clements, A. Pickard","doi":"10.1109/SPLC.2011.13","DOIUrl":"https://doi.org/10.1109/SPLC.2011.13","url":null,"abstract":"A complex system's requirements almost always remain uncertain late into its software development. In gas turbine engine control systems at Rolls-Royce, for a traditional project (non-product line) typically 50% of requirements will change between Critical Design Review and Entry into Service. Requirements uncertainty is particularly relevant when defining the scope of a Software Product Line. If the core asset team fails to recognise or accommodate requirements uncertainty, changes will manifest later in the product line. If the core asset team over-compensates by adding too much functionality or variability to account for a wide range of uncertainty, they will invest effort that may never be required. The optimal balance can be found through an application of requirements uncertainty analysis and understanding the balance between the impact of risk and mitigation effort. This paper first describes the use of the requirements uncertainty analysis technique at Rolls-Royce for traditional (non-product line) software development and then explains how this technique works in the context of a software product line.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128960711","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}
In this paper we present a practical way for managing software product lines with respect to its feature interactions and illustrate how it works with the results from the real products in our previous experience. In front of this work, we have applied a software product line engineering and model driven development to our product line development, in which we have ever developed more than 30 products by assembling software components without hand coding. In this previous experience, we found that product developers tended to make excessive effort on verification and testing because of the fear of feature interaction problems. This prevented improving the productivity of software development. In order to address this issue, we propose accumulating the results of feature interactions that have ever appeared in the past products so that the product developers can focus their testing effort on interactions that first appear in their product without worrying about the implementation details. Then they will have confidence in their product configuration. We believe that the variation management with respect to the feature interactions will encourage the developers and promote the introduction of software product line engineering.
{"title":"Variation Management for Software Product Lines with Cumulative Coverage of Feature Interactions","authors":"S. Kato, Nobuhito Yamaguchi","doi":"10.1109/SPLC.2011.51","DOIUrl":"https://doi.org/10.1109/SPLC.2011.51","url":null,"abstract":"In this paper we present a practical way for managing software product lines with respect to its feature interactions and illustrate how it works with the results from the real products in our previous experience. In front of this work, we have applied a software product line engineering and model driven development to our product line development, in which we have ever developed more than 30 products by assembling software components without hand coding. In this previous experience, we found that product developers tended to make excessive effort on verification and testing because of the fear of feature interaction problems. This prevented improving the productivity of software development. In order to address this issue, we propose accumulating the results of feature interactions that have ever appeared in the past products so that the product developers can focus their testing effort on interactions that first appear in their product without worrying about the implementation details. Then they will have confidence in their product configuration. We believe that the variation management with respect to the feature interactions will encourage the developers and promote the introduction of software product line engineering.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129897144","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}
Andy J. Nolan, S. Abrahão, P. Clements, J. McGregor, Sholom G. Cohen
A good estimation tool offers a "model" of a project and is usually used to estimate cost and schedule, but it can also be used to help make trade decisions that affect cost and schedule as well as to estimate risks and opportunities. It was evident that Rolls-Royce needed a cost model to underpin decisions when they launched a Software Product Line initiative. The first generation cost model was based on COCOMO II, which represents the software product as a single size measure (Source Lines of Code) but makes limited use of the architecture or any characteristics of the product being developed. The next generation of the cost model, currently under development, is intended to account for the quality attributes of the core assets and the resulting products in order to estimate their impact on cost and net-benefit to the business. The objective of this paper is to describe our current efforts to integrate key quality attributes into the SPL cost model. We describe the quality attributes selected, the reason for their selection and the benefits we expect to obtain after integrating them into the model.
{"title":"Towards the Integration of Quality Attributes into a Software Product Line Cost Model","authors":"Andy J. Nolan, S. Abrahão, P. Clements, J. McGregor, Sholom G. Cohen","doi":"10.1109/SPLC.2011.44","DOIUrl":"https://doi.org/10.1109/SPLC.2011.44","url":null,"abstract":"A good estimation tool offers a \"model\" of a project and is usually used to estimate cost and schedule, but it can also be used to help make trade decisions that affect cost and schedule as well as to estimate risks and opportunities. It was evident that Rolls-Royce needed a cost model to underpin decisions when they launched a Software Product Line initiative. The first generation cost model was based on COCOMO II, which represents the software product as a single size measure (Source Lines of Code) but makes limited use of the architecture or any characteristics of the product being developed. The next generation of the cost model, currently under development, is intended to account for the quality attributes of the core assets and the resulting products in order to estimate their impact on cost and net-benefit to the business. The objective of this paper is to describe our current efforts to integrate key quality attributes into the SPL cost model. We describe the quality attributes selected, the reason for their selection and the benefits we expect to obtain after integrating them into the model.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"270 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131692961","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}
Software Product Lines are a mean to improve the economic performance of firms that offer several products to a market by systematically reusing software artifacts. In most cases the definitive company goal is profit maximization. That can be reached by increasing revenue or by reducing cost. Revenue is increased by offering products with a wide variety of features to an audience willing to pay. However, the fewer features are realized the fewer cost incur. Hence, a firm may ask what features are most important to realize. We approach this question by introducing Value-Based Portfolio Optimization as an addition to common Product Portfolio Scoping approaches that helps deciding on this question.
{"title":"Value-Based Portfolio Optimization for Software Product Lines","authors":"Johannes Müller","doi":"10.1109/SPLC.2011.18","DOIUrl":"https://doi.org/10.1109/SPLC.2011.18","url":null,"abstract":"Software Product Lines are a mean to improve the economic performance of firms that offer several products to a market by systematically reusing software artifacts. In most cases the definitive company goal is profit maximization. That can be reached by increasing revenue or by reducing cost. Revenue is increased by offering products with a wide variety of features to an audience willing to pay. However, the fewer features are realized the fewer cost incur. Hence, a firm may ask what features are most important to realize. We approach this question by introducing Value-Based Portfolio Optimization as an addition to common Product Portfolio Scoping approaches that helps deciding on this question.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133805084","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}
Deepak Dhungana, Dominik Seichter, Goetz Botterweck, Rick Rabiser, P. Grünbacher, David Benavides, J. Galindo
In industrial settings, products are rarely developed by one organization alone. Software vendors and suppliers typically maintain their own product lines, which can contribute to a larger (multi) product line. The teams involved often use different approaches and tools to manage the variability of their systems. It is unrealistic to assume that all participating units can use a standardized and prescribed variability modeling technique. The configuration of products based on several models in different notations and with different semantics is not well supported by existing approaches. In this paper we present an integrative approach that provides a unified perspective to users configuring products in multi product line environments, regardless of the different modeling methods and tools used internally. We also present a technical infrastructure and a prototypic implementation based on Web Services. We show the feasibility of the approach and its implementation by using it with two different variability modeling approaches (one feature-based and one decision-oriented approach) on an example derived from industrial experience.
{"title":"Configuration of Multi Product Lines by Bridging Heterogeneous Variability Modeling Approaches","authors":"Deepak Dhungana, Dominik Seichter, Goetz Botterweck, Rick Rabiser, P. Grünbacher, David Benavides, J. Galindo","doi":"10.1109/SPLC.2011.22","DOIUrl":"https://doi.org/10.1109/SPLC.2011.22","url":null,"abstract":"In industrial settings, products are rarely developed by one organization alone. Software vendors and suppliers typically maintain their own product lines, which can contribute to a larger (multi) product line. The teams involved often use different approaches and tools to manage the variability of their systems. It is unrealistic to assume that all participating units can use a standardized and prescribed variability modeling technique. The configuration of products based on several models in different notations and with different semantics is not well supported by existing approaches. In this paper we present an integrative approach that provides a unified perspective to users configuring products in multi product line environments, regardless of the different modeling methods and tools used internally. We also present a technical infrastructure and a prototypic implementation based on Web Services. We show the feasibility of the approach and its implementation by using it with two different variability modeling approaches (one feature-based and one decision-oriented approach) on an example derived from industrial experience.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"119 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116391241","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}
Generative programming and model transformation techniques are becoming widely used for the development of software components for product lines. The ability to develop components with identified common and variable parts, and rapidly instantiate product-specific versions is key to many software product line approaches. However if this approach is to be truly cost effective for high assurance applications, the instantiation process must be property-preserving, any verification evidence acquired on the product-line component must be demonstrably applicable to the instantiated component. In this paper we outline an approach that uses static analysis techniques and the SPARK language that can potentially demonstrate the correctness of model transformations.
{"title":"Towards Cost-Effective High-Assurance Software Product Lines: The Need for Property-Preserving Transformations","authors":"S. Hutchesson, J. Mcdermid","doi":"10.1109/SPLC.2011.32","DOIUrl":"https://doi.org/10.1109/SPLC.2011.32","url":null,"abstract":"Generative programming and model transformation techniques are becoming widely used for the development of software components for product lines. The ability to develop components with identified common and variable parts, and rapidly instantiate product-specific versions is key to many software product line approaches. However if this approach is to be truly cost effective for high assurance applications, the instantiation process must be property-preserving, any verification evidence acquired on the product-line component must be demonstrably applicable to the instantiated component. In this paper we outline an approach that uses static analysis techniques and the SPARK language that can potentially demonstrate the correctness of model transformations.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131546249","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}
Software product line companies increasingly expand their platform outside their organizational boundaries, in effect transitioning to a software ecosystem approach. In this tutorial, we discuss the emerging trend of software ecosystems and provide a overview of the key concepts and implications of adopting a software ecosystem approach. We define the notion of software ecosystems and introduce a taxonomy. Finally, we explore the implications of software ecosystems to the way companies build software.
{"title":"Software Ecosystems -- Implications for Strategy, Business Model and Architecture","authors":"J. Bosch","doi":"10.1109/SPLC.2011.10","DOIUrl":"https://doi.org/10.1109/SPLC.2011.10","url":null,"abstract":"Software product line companies increasingly expand their platform outside their organizational boundaries, in effect transitioning to a software ecosystem approach. In this tutorial, we discuss the emerging trend of software ecosystems and provide a overview of the key concepts and implications of adopting a software ecosystem approach. We define the notion of software ecosystems and introduce a taxonomy. Finally, we explore the implications of software ecosystems to the way companies build software.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116094180","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 configuration of a product from a product line is a decision-making process that requires humans to answer questions. However, questions and their choices tend to affect one another (e. g., one feature depending on another) and decisions on how questions are answered may render other questions obsolete or reduce their choices. There is thus an ideal order in which questions should be answered to minimize the number of questions that need answering to completely configure a product. Unfortunately, this ideal order differs depending on the product -- which cannot be known a priori. Decision-making is thus characterized by either imposing a predefined order on how questions must be answered (usually done manually by product line engineers) or not imposing any order. Both situations have downsides and this paper thus proposes an alternative: an incremental algorithm and tool-support for automatically optimizing the order of questions with every answer. We evaluated our approach on six models, the largest with over 280 questions, and found that the approach is 78-99% optimal and significantly reduces the number of questions that need to be answered manually. For the creators of product line models, this implies savings in not having to predefine the optimal order which is exponentially complex. For the configurator (decision maker) this implies more freedom in the order in which to answer questions while still benefiting from guidance.
{"title":"Optimizing User Guidance during Decision-Making","authors":"Alexander Nöhrer, Alexander Egyed","doi":"10.1109/SPLC.2011.45","DOIUrl":"https://doi.org/10.1109/SPLC.2011.45","url":null,"abstract":"The configuration of a product from a product line is a decision-making process that requires humans to answer questions. However, questions and their choices tend to affect one another (e. g., one feature depending on another) and decisions on how questions are answered may render other questions obsolete or reduce their choices. There is thus an ideal order in which questions should be answered to minimize the number of questions that need answering to completely configure a product. Unfortunately, this ideal order differs depending on the product -- which cannot be known a priori. Decision-making is thus characterized by either imposing a predefined order on how questions must be answered (usually done manually by product line engineers) or not imposing any order. Both situations have downsides and this paper thus proposes an alternative: an incremental algorithm and tool-support for automatically optimizing the order of questions with every answer. We evaluated our approach on six models, the largest with over 280 questions, and found that the approach is 78-99% optimal and significantly reduces the number of questions that need to be answered manually. For the creators of product line models, this implies savings in not having to predefine the optimal order which is exponentially complex. For the configurator (decision maker) this implies more freedom in the order in which to answer questions while still benefiting from guidance.","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124938160","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 tutorial provides practical guidance for project managers and architects facing the "PLE challenge". It demonstrates practices and concrete activities we use to make a product line an economical and technical success
{"title":"Successful Product Line Engineering: Experiences from the Real World","authors":"F. Buschmann, Christa Schwanninger","doi":"10.1109/SPLC.2011.57","DOIUrl":"https://doi.org/10.1109/SPLC.2011.57","url":null,"abstract":"The tutorial provides practical guidance for project managers and architects facing the \"PLE challenge\". It demonstrates practices and concrete activities we use to make a product line an economical and technical success","PeriodicalId":278787,"journal":{"name":"2011 15th International Software Product Line Conference","volume":"201 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122570439","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
扫码关注我们
求助内容：
应助结果提醒方式：