Feature Dependency Analysis for Product Line Component Design
Analyzing commonalities and variabilities among products of a product line is an essential activity for product line asset development. A feature-oriented approach to commonality and variability analysis (called feature modeling) has been used extensively for product line engineering. Feature modeling mainly focuses on identifying commonalities and variabilities among products of a product line and organizing them in terms of structural relationships (e.g., aggregation and generalization) and configuration dependencies (e.g., required and excluded). Although the structural relationships and configuration dependencies are essential inputs to product line asset development, they are not sufficient to develop reusable and adaptable product line assets. Other types of dependencies among features also have significant influences on the design of product line assets. In this paper, we extend the feature modeling to analyze feature dependencies that are useful in the design of reusable and adaptable product line components, and present design guidelines based on the extended model. An elevator control software example is used to illustrate the concept of the proposed method.
KeywordsProduct Line Software Product Line Fire Fighter Feature Dependency Call Request
Unable to display preview. Download preview PDF.
- 1.Clements, P., Northrop, L.: Software Product Lines: Practices and Patterns. Addison- Wesley, Upper Saddle River (2002)Google Scholar
- 2.Czarnecki, K., Eisenecker, U.: Generative Programming: Methods, Tools, and Applications. Addison-Wesley, Reading (2000)Google Scholar
- 5.Griss, M.: Implementing Product-Line Features by Composing Aspects. In: Donohoe, P. (ed.) Software Product Lines: Experience and Research Directions, Kluwer Academic Publishers, Boston (2000)Google Scholar
- 6.Griss, M., Favaro, J., d’Alessandro, M.: Integrating Feature Modeling with the RSEB. In: Proceedings of Fifth International Conference on Software Reuse, pp. 76–85 (1998)Google Scholar
- 8.Jacobson, I., Griss, M., Jonsson, P.: Software Reuse: Architecture, Process and Organization for Business Success. Addison Wesley Longman, New York (1997)Google Scholar
- 9.Kang, K.C., Cohen, S., Hess, J., Nowak, W., Peterson, S.: Feature-Oriented Domain Analysis (FODA) Feasibility Study. Technical Report CMU/SEI-90-TR-21. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA (1990)Google Scholar
- 11.Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C.V., Loingtier, J., Irwin, J.: Aspect-Oriented Programming. LNCS, vol. 1241, pp. 220–242 (1997)Google Scholar
- 12.Kimbler, K., Bouma, L.G.: Feature Interactions in Telecommunication and Software Systems V. IOS Press, Amsterdam (1998)Google Scholar
- 15.van Hilst, M., Notkin, D.: Using C++ Templates to Implement Role-Based Designs. In: Proceedings of the 2nd JSSST International Symposium on Object Technologies for Advanced Software, pp. 22–37 (1996)Google Scholar
- 16.Vici, A.D., Argentieri, N.: FODAcom: An Experience with Domain Analysis in the Italian Telecom Industry. In: Proceedings of Fifth International Conference on Software Reuse, pp. 166–175 (1998)Google Scholar
- 17.Zalman, N.S.: Making the Method Fit: An Industrial Experience in Adopting FODA. In: Proceedings of Fourth International Conference on Software Reuse, pp. 233–235 (1996)Google Scholar