An Aspect-Oriented Approach for Use Case Based Modeling of Software Product Lines
- 1
- 2
Abstract
Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects” to increase modularity, reusability, maintainability and ease of evolution. In this paper, we apply an as-pect-oriented use case modeling approach to product line system modeling. A use case specification captures stake-holders concerns as interactions between a system and its actors. We adapt our previous work with the introduction of a “variability” relationship for the expression of variabilities. This relationship is used to model variable and common behaviours across a family of products as use cases. A variability composition mechanism enables building of executa-ble behaviour models for each member of a product line family by integrating common elements with the applicable variable elements.
- P. Clements and L. Northrop, “Software product lines: Practices and patterns,” Addison-Wesley Longman Pub-lishing Co., Inc., Boston, MA, USA, 2001.
- E. Ecklund, L. Delcambre, and M. Freiling, “Change cases-Use cases that identify future requirements,” Pro-ceedings of OOPSLA 96, San Jose, Ca, pp. 342?358, October 1996.
- I. Jacobson, M. Griss, and P. Jonsson, “Software re-use–Architecture,” Process and Organization for Business success, Addison-Wesley, 1997.
- H. Gomaa, “Designing software product lines with UML–From use cases to pattern-based software architec-tures,” Addison-Wesley, 2004.
- I. John, and D. Muthig, “Product line modeling with ge-neric use cases,” SPLC-2 Workshop on Techniques for Exploiting Commonality Through Variability Manage-ment, Second Software Product Line Conference, San Diego, USA, August 2002.
- S. Somé, “Supporting use cases based requirements en-gineering,” Information and Software Technology, Vol. 48(1), pp. 43–58, 2006.
- Use Case Editor (UCEd) toolset, http://www.site.uott-awa.ca/~ssome/UseCaseEditorUCEd.html.
- S. S. Somé and P. Anthonysamy, “An approach for as-pect-oriented use case modeling,” Workshop on Early Aspects at ICSE 2008: Aspect-Oriented Requirements Engineering and Architecture Design, May 2008.
- N. Loughran, A. Sampaio, and A. Rashid, “From re-quirements documents to feature models for aspect ori-ented product line implementation,” Workshop on MDD in Product Lines at MODELS, 2005.
- M. Saleh and H. Gomaa, “Separation of concerns in software product line engineering,” In Proceedings of the 2005 Workshop on Modeling and Analysis of concerns in Software. St. Louis, Missouri, 2005.
- H. Siy, P. Aryal, V. Winter, and M. Zand, “Aspectual support for specifying requirements in software product Lines,” Workshop on Early Aspects at ICSE. Minneapolis, USA, May 2007.
- OMG: UML 2.1.2 Superstructure Object Management Group, 2007.
- S. S. Somé, “Petri nets based formalization of textual use cases,” Technical Report TR-2007-11, SITE, University of Ottawa, 2007.
- C. A. Petri, “Communication with Automata,” PhD thesis, Technische Universitat Darmstadt, 1962.
- I. Jacobson and P. W. Ng, “Aspect-oriented software development with use cases,” Addison Wesley, 2005.