Salion, Inc.: A Software Product Line Case Study

Clements, Paul; Northrop, Linda

doi:10.21236/ada412311

Cited by 85 publications

(106 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As compared to the many experience papers published in the literature (e.g. [3,7,12,19]), one could claim that our product family is rather small in size. Still we believe it is representative as some type of "boundary example": in spite of its relative small scale, its evolution became unmanageable.…”

Section: Starting Pointmentioning

confidence: 95%

Observations from the Recovery of a Software Product Family

Lago

Vliet

2004

Software Product Lines

View full text Add to dashboard Cite

Abstract. The problem of managing the evolution of complex and large software systems is well known. Evolution implies reuse and modification of existing software artifacts, and this means that the related knowledge must be documented and maintained. This paper focuses on the evolution of software product families, although the same principles apply in other software development environments as well. We describe our experience gained in a case study recovering a family of six software products. We give an overview of the case study, and report a list of lessons learned, a list of implicit assumptions reconstructed during the case study, and some rules that we think are generally applicable. Our experience indicates that organizing architectural knowledge is a difficult issue. To properly serve the various uses of this knowledge, it needs to be organized along different dimensions. For effective use, tools are required. Our experience also indicates that, next to variability explicitly designed into the product family, there is a "variation creep", caused by different, and evolving, technical and organizational environments of the products. We propose to explicitly model invariabilities, next to variabilities, in software product lines to get a better grip on this variation creep.

show abstract

Section: Starting Pointmentioning

confidence: 95%

Observations from the Recovery of a Software Product Family

Lago

Vliet

2004

Software Product Lines

View full text Add to dashboard Cite

show abstract

“…In [4][6] the authors located the common and variable parts within a product using clones. We used clone detection tools to derive the merge strategy by analyzing clones across products using software architecture decomposition.…”

Section: Related Workmentioning

confidence: 99%

Assessing merge potential of existing engine control systems into a product line

Yoshimura

Ganesan

Muthig

2006

Proceedings of the 2006 International Workshop on Software Engineering for Automotive Systems

View full text Add to dashboard Cite

Engine Control Systems (ECS) for automobiles have many variants for many manufactures and several markets. To improve their development efficiency, exploiting ECS commonalities and predicting their variability are mandatory. The concept of software product line engineering meets this ECS business background. However, we should carefully investigate the expected technical, economical, and organizational effects of introducing the strategy into existing products. Thereafter, a strategy will be derived systematically and realize the desired benefits. This paper reports an experience with the up-front investigation performed for Hitachi's ECS. We focus on the approach to plan the migration of the existing family of individual systems into a future product line. The approach assesses potential ways of merging software from existing variants and eventually defines a procedure for performing the migration. To get a high quality strategy, we integrate the approach of software measurement, the expertise of software architects, and reverse engineering techniques

show abstract

“…Software Product Lines (SPL) refer to a set of software intensive systems developed for a specific aim or market from common software assets [2].…”

Section: Introductionmentioning

confidence: 99%

Verification Tool for Feature Models and Configurations using Semantic Web Technologies

Choi¹

2011

Journal of the Korea society of IT services

View full text Add to dashboard Cite

논문투고일：2011년 07월 15일논문수정완료일：2011년 08월 16일 논문게재확정일：2011년 09월 14일 * 본 연구는 덕성여자대학교 2010년도 교내연구비 지원에 의해 수행되었음. ** 덕성여자대학교 컴퓨터학과 부교수 Feature models are widely used to model commonalities and variabilities among products during software product line development. Feature configurations are generated by selecting the features to be included in individual products.Automated tools to identify errors or inconsistencies in the feature models and configurations are essential to successful software product line engineering. This paper proposes a verification technique and tool based on semantic web technologies such as OWL, SWRL and Protege API. This approach checks the feature model and configuration based on predefined rules and provides information on existence of errors as well as the kinds of those errors. This approach is extensible due to ease of rule modification and may be easily applied to other environments because semantic web technologies can be easily integrated with other programming environments. This paper demonstrates how various semantic web-related technologies can support automatic verification of one kind of software development artifact, the feature model.

show abstract

Salion, Inc.: A Software Product Line Case Study

Abstract: The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange.

Cited by 85 publications

References 3 publications

Observations from the Recovery of a Software Product Family

Observations from the Recovery of a Software Product Family

Assessing merge potential of existing engine control systems into a product line

Verification Tool for Feature Models and Configurations using Semantic Web Technologies

Contact Info

Product

Resources

About