Article

Violatility analysis framework for product lines

Authors:

Juha Savolainen,

Juha KuuselaAuthors Info & Claims

SSR '01: Proceedings of the 2001 symposium on Software reusability: putting software reuse in context

Pages 133 - 141

https://doi.org/10.1145/375212.375277

Published: 01 May 2001 Publication History

Abstract

Evolution of a software intensive system is unavoidable. In fact, evolution can be seen as a part of reuse process. During the evolution of the software asset, the major part of the system functionality is normally reused. So the key issue is to identify the volatile parts of the domain requirements. Additionally, there is promise that tailored tool support may help supporting evolution in software intensive systems. In this paper, we describe the volatility analysis method for product lines. This highly practical method has been used in multiple domains and is able to express and estimate common types of evolutional characteristics. The method is able to represent volatility in multiple levels and has capacity to tie the volatility estimation to one product line member specification. We also briefly describe current tool support for the method. The main contribution of this paper is a volatility analysis framework that can be used to describe how requirements are estimated to evolve in the future. The method is based on the definition hierarchy framework.

References

[1]

Lehman, M., Software's Future: Managing Evolution, IEEE Software, January-February, IEEE, 1998, pp.40-44.]]

Digital Library

[2]

Lehman, M., Software Engineering the Software Process and their Support, IEEE Software Engineering Journal, IEEE Computer Society Press, 1991, pp.243-258.]]

Digital Library

[3]

Perry D., Dimensions of Software Evolution, International Conf. of Software Maintenance, IEEE, 1994, pp.296-303.]]

Digital Library

[4]

Kuusela, J., Savolainen, J., Requirements Engineering for Product Lines, in International Conference on Software Engineering (ICSE2000), IEEE, 2000, pp.61-69.]]

Digital Library

[5]

Kang, K., Cohen, S., Hess, J., Novak, W., Peterson, S., Feature-Oriented Domain Analysis (FODA) Feasibility Study, Technical Report, CMU/SEI-90-TR-021, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, November 1990.]]

[6]

Software Productivity Consortium, Reuse-Driven Software Processes Guidebook, Version 02.00.03, November 1993.]]

[7]

Software Productivity Consortium, Reuse Adoption Guidebook, Version 02.00.05, November 1993.]]

[8]

Software Technology for Adaptable, Reliable Systems (STARS). Organization Domain Modeling (ODM) Guidebook, V. 2.0. Tech Rep STARS-VC-A025/001/00]]

[9]

Ardis, M., Weiss, D., Defining Families: The Commonality Analysis, in International Conference on Software Engineering ICSE1997, IEEE, 1997, pp.649-650.]]

Digital Library

[10]

Griss, M., Favaro, J., d'Alessandro, M., Integrating feature modeling with the RSEB, Proceedings of Fifth International Conference on Software Reuse, IEEE, 1998, pp. 76-85.]]

Digital Library

[11]

Coplien, J., Multi-Paradigm Design for C++, Addison Wesley, 1998.]]

Digital Library

[12]

Weiss, D., Lai, R., Software Product-Line Engineering - A Family-Based Software Development Process, Addison Wesley, 1999.]]

Digital Library

[13]

Kuusela, J., Savolainen, J., How to Use Requirements and Properties of Existing Products as a Guide in Implementing a Product Family, OOSA'98 In Proc. of the ECOOP'98 on Object-Oriented SW Architectures, Report of Univ. Karlskrona/Ronneby, ISRN HK/R-RES-98/13-SE, 1998,]]

[14]

ESAPS System-family Engineering Glossary, 2000.]]

[15]

Nuseibeh, N., Kramer, J., Finkelstein, A., A Framework for Expressing the Relationships Between Multiple Views in Requirement Specification, IEEE Transactions on Software Engineering, October 1994, IEEE, 1994, pp.760-773.]]

Digital Library

[16]

Ecklund, E., Delcambre, L., Freiling, M., Change Cases: Use Cases that Identify Future Requirements, in conference of Object Oriented Languages, Systems and Languages (OOPSLA'96), ACM, 1996, pp.342-358.]]

Digital Library

[17]

Karhinen, A., Kuusela, J., "Structuring Design Decisions for Evolution," in Development and Evolution of Software Architectures for Product Families, Springer-Verlag, February 1998, pp. 223-234.]]

Digital Library

[18]

Cohen, S., Stanley, J., Peterson, W., Krut, R., Application of Feature-Oriented Domain Analysis to the Army Movement Control Domain, Technical Report, CMU/SEI-91-TR-028, SEI, Carnegie Mellon University, Pittsburgh, June1992.]]

[19]

Vici, A. D. Argentieri, N. Mansour, A. d'Alessandro, M. Favaro, J., FODAcom: An Experience with Domain Analysis in the Italian Telecom Industry, in Proc. of 5th Int. Conf. on Software Reuse, IEEE Comp. Soc. Press, 1998, pp. 166-175.]]

Digital Library

[20]

Keepance, B., Mannion, M., Using Patterns to Model Variability in Product Families, IEEE Software, IEEE, July/August 1999, pp.102-108.]]

Digital Library

[21]

Bayer, J., Flege, O., Knauber, P., Laqua, R., Methig, D., Schmid, K., Widen, T., DeBaud, J., PuLSE: A Methodology to Develop Software Product Lines, in Symposium on Software Reusability (SSR'99), 1999, pp. 122-131.]]

Digital Library

[22]

Batory, D. Goglianese, L. Goodwin, M., Creating Reference Architectures: An Example for Avionics, in Proceedings of the Symposium of Software Reuse, ACM, 1995, pp. 27-37.]]

Digital Library

[23]

Clements, P., Northrop, L., A Framework for Software Product Line Practice - Version 2.0, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, July 1999.]]

[24]

Klein, M., Kazman, R., Bass, L., Carriere, J., Barbacci, M., Lipson, H., Attribute-Based Architecture Styles, in Software Architecture, P. Donohoe (Ed.), Kluwer Academic Publishers, 1999, pp. 225-243.]]

[25]

Kazman, R., Klein, M., Clements, P., ATAM: Method for Architecture Evaluation, Technical Report, CMU/SEI-2000- TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, August 2000.]]

Cited By

Thurimella ABruegge B(2018)Issue-based variability managementInformation and Software Technology10.1016/j.infsof.2012.02.00554:9(933-950)Online publication date: 29-Dec-2018
https://dl.acm.org/doi/10.1016/j.infsof.2012.02.005
Berger TLettner DRubin JGrünbacher PSilva ABecker MChechik MCzarnecki KSchmidt D(2015)What is a feature?Proceedings of the 19th International Conference on Software Product Line10.1145/2791060.2791108(16-25)Online publication date: 20-Jul-2015
https://dl.acm.org/doi/10.1145/2791060.2791108
Thurimella A(2011)On the communication problem between domain engineering and application engineeringACM SIGSOFT Software Engineering Notes10.1145/1988997.200364536:4(1-5)Online publication date: 4-Aug-2011
https://dl.acm.org/doi/10.1145/1988997.2003645
Show More Cited By

Index Terms

Violatility analysis framework for product lines
1. Software and its engineering

Recommendations

Violatility analysis framework for product lines

Evolution of a software intensive system is unavoidable. In fact, evolution can be seen as a part of reuse process. During the evolution of the software asset, the major part of the system functionality is normally reused. So the key issue is to ...
An Approach to Developing Domain Requirements as a Core Asset Based on Commonality and Variability Analysis in a Product Line

The methodologies of product line engineering emphasize proactive reuse to construct high-quality products more quickly that are less costly. Requirements engineering for software product families differs significantly from requirements engineering for ...
Analyzing evolution of variability in a software product line: From contexts and requirements to features

Context: In the long run, features of a software product line (SPL) evolve with respect to changes in stakeholder requirements and system contexts. Neither domain engineering nor requirements engineering handles such co-evolution of requirements and ...

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences

SSR '01: Proceedings of the 2001 symposium on Software reusability: putting software reuse in context

May 2001

177 pages

ISBN:1581133588

DOI:10.1145/375212

Chairman:
Paul G. Bassett
Netron Inc., Canada

ACM SIGSOFT Software Engineering Notes Volume 26, Issue 3
May 2001
172 pages
ISSN:0163-5948
DOI:10.1145/379377
Chairman:
David Notkin
Univ. of Washington, Seattle
Issue’s Table of Contents

Copyright © 2001 ACM.

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

SIGSOFT: ACM Special Interest Group on Software Engineering

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 May 2001

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Article

Conference

SSR01

Sponsor:

SIGSOFT

SSR01: Symposium on Software Reusability 2001

Ontario, Toronto, Canada

Acceptance Rates

Overall Acceptance Rate 33 of 76 submissions, 43%

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

14
Total Citations
View Citations
874
Total Downloads

Downloads (Last 12 months)1
Downloads (Last 6 weeks)0

Reflects downloads up to 30 Nov 2024

Other Metrics

View Author Metrics

Citations

Cited By

Thurimella ABruegge B(2018)Issue-based variability managementInformation and Software Technology10.1016/j.infsof.2012.02.00554:9(933-950)Online publication date: 29-Dec-2018
https://dl.acm.org/doi/10.1016/j.infsof.2012.02.005
Berger TLettner DRubin JGrünbacher PSilva ABecker MChechik MCzarnecki KSchmidt D(2015)What is a feature?Proceedings of the 19th International Conference on Software Product Line10.1145/2791060.2791108(16-25)Online publication date: 20-Jul-2015
https://dl.acm.org/doi/10.1145/2791060.2791108
Thurimella A(2011)On the communication problem between domain engineering and application engineeringACM SIGSOFT Software Engineering Notes10.1145/1988997.200364536:4(1-5)Online publication date: 4-Aug-2011
https://dl.acm.org/doi/10.1145/1988997.2003645
Thurimella ABruegge BCreighton O(2008)Identifying and Exploiting the Similarities between Rationale Management and Variability ManagementProceedings of the 2008 12th International Software Product Line Conference10.1109/SPLC.2008.14(99-108)Online publication date: 8-Sep-2008
https://dl.acm.org/doi/10.1109/SPLC.2008.14
Villela KDoerr JGross A(2008)Proactively Managing the Evolution of Embedded System RequirementsProceedings of the 2008 16th IEEE International Requirements Engineering Conference10.1109/RE.2008.57(13-22)Online publication date: 8-Sep-2008
https://dl.acm.org/doi/10.1109/RE.2008.57
Thurimella ABruegge B(2007)Evolution in Product Line Requirements Engineering: A Rationale Management Approach15th IEEE International Requirements Engineering Conference (RE 2007)10.1109/RE.2007.11(254-257)Online publication date: Oct-2007
https://doi.org/10.1109/RE.2007.11
Savolainen JKauppinen MMannisto T(2007)Identifying Key Requirements for a New Product Line14th Asia-Pacific Software Engineering Conference (APSEC'07)10.1109/ASPEC.2007.67(478-485)Online publication date: Dec-2007
https://doi.org/10.1109/ASPEC.2007.67
Montalvillo LDíaz O(2016)Requirement-driven evolution in software product linesJournal of Systems and Software10.5555/3044222.3051232122:C(110-143)Online publication date: 1-Dec-2016
https://dl.acm.org/doi/10.5555/3044222.3051232
Fogdal TScherrebeck HKuusela JBecker MZhang BMei H(2016)Ten years of product line engineering at DanfossProceedings of the 20th International Systems and Software Product Line Conference10.1145/2934466.2934491(252-261)Online publication date: 16-Sep-2016
https://dl.acm.org/doi/10.1145/2934466.2934491
Montalvillo LDíaz O(2016)Requirement-driven evolution in software product lines: A systematic mapping studyJournal of Systems and Software10.1016/j.jss.2016.08.053122(110-143)Online publication date: Dec-2016
https://doi.org/10.1016/j.jss.2016.08.053
Show More Cited By

View Options

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents