An Aspect-Oriented Approach for Use Case Based Modeling of Software Product Lines
Stéphane S. SOMé, Pauline ANTHONYSAMY
.
DOI: 10.4236/jsea.2009.24032   PDF   HTML     5,214 Downloads   9,325 Views   Citations

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.

Share and Cite:

S. SOMé and P. ANTHONYSAMY, "An Aspect-Oriented Approach for Use Case Based Modeling of Software Product Lines," Journal of Software Engineering and Applications, Vol. 2 No. 4, 2009, pp. 248-258. doi: 10.4236/jsea.2009.24032.

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1] P. Clements and L. Northrop, “Software product lines: Practices and patterns,” Addison-Wesley Longman Pub-lishing Co., Inc., Boston, MA, USA, 2001.
[2] 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.
[3] I. Jacobson, M. Griss, and P. Jonsson, “Software re-use–Architecture,” Process and Organization for Business success, Addison-Wesley, 1997.
[4] H. Gomaa, “Designing software product lines with UML–From use cases to pattern-based software architec-tures,” Addison-Wesley, 2004.
[5] 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.
[6] S. Somé, “Supporting use cases based requirements en-gineering,” Information and Software Technology, Vol. 48(1), pp. 43–58, 2006.
[7] Use Case Editor (UCEd) toolset, http://www.site.uott-awa.ca/~ssome/UseCaseEditorUCEd.html.
[8] 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.
[9] 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.
[10] 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.
[11] 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.
[12] OMG: UML 2.1.2 Superstructure Object Management Group, 2007.
[13] S. S. Somé, “Petri nets based formalization of textual use cases,” Technical Report TR-2007-11, SITE, University of Ottawa, 2007.
[14] C. A. Petri, “Communication with Automata,” PhD thesis, Technische Universitat Darmstadt, 1962.
[15] I. Jacobson and P. W. Ng, “Aspect-oriented software development with use cases,” Addison Wesley, 2005.
[16] J. Araújo and A. M. D. Moreira, “An aspectual use case driven approach,” In VIII Jornadas Ingeniería del Soft-ware y Bases deDatos (JISBD 2003), pp. 463?468, 2003.
[17] R. Chitchyan, A. Rashid, P. Rayson, and R. Waters, “Se-mantics-based composition for aspect-oriented require-ments engineering,” In: AOSD ’07: Proceedings of the 6th International conference on Aspect-oriented software de-velopment, ACM, pp. 36–48, 2007.
[18] AspectJ Project, http://www.eclipse.org/aspectj/.
[19] R. Stoiber, S. Meier, and M. Glinz, “Visualizing product line domain variability by aspect-oriented modeling,” Proceedings of the 2nd International Workshop on Re-quirements Engineering Visualization (REV'07), in con-junction with RE'07. New Delhi, India.
[20] M. Griss, J. Favaro, and M. d’Alessandro, “Integrating feature modeling with the RSEB,” Proceedings of Fifth International Conference on Software Reuse, Victoria, B.C., 1998.
[21] Aspects and Software Product Lines (EA-SPLC), http://trese.cs.utwente.nl/workshops/early-aspects-SPLC2005/.
[22] A. Rashid, A. Moreira, and J. Araújo, “Modularization and composition of aspectual requirements,” In Proc. of the 2nd International Conference on Aspect-Oriented Software Development (AOSD’03), Boston, MA, pp. 11–20, March 2003.

Copyright © 2022 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.