Model-Driven Derivation of Domain Functional Requirements from Use Cases

Jianmei Guo, Zheying Zhang, Yinglin Wang
DOI: 10.4236/jsea.2010.39102                

Abstract

Domain analysis is essential to core assets development in software product line engineering. Most existing approaches, however, depend on domain experts’ experience to analyze the commonality and variability of systems in a domain, which remains a manual and intensive process. This paper addresses the issue by proposing a model-driven approach to automating the domain requirements derivation process. The paper focuses on the match between the use cases of existing individual products and the domain functional requirements of a product line. By introducing a set of linguistic description dimensions to differentiate the sub-variations in a use case, the use case template is extended to model variability. To this end, a transformation process is formulated to sustain and deduce the information in use cases, and to match it to domain functional requirements. This paper also presents a prototype which implements the derivation as a model transformation described in a graphical model transformation language MOLA. This approach complements existing domain analysis techniques with less manual operation cost and more efficiency by automating the domain functional requirements development.

Keywords

Software Product Lines, Domain Analysis, Model Transformation, Use Cases, Functional Requirements

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, Boston, 2001.
[2]	K. Pohl, G. Bockle and F. van der Linden, “Software Product Line Engineering: Foundations, Principles and Techniques,” Springer Verlag, Heidelberg, 2005.
[3]	C. W. Krueger, “Easing the Transition to Software Mass Customization,” Proceedings International Workshop on Product Family Engineering, Bilbao, 2001, pp. 282-293.
[4]	N. Niu and S. Easterbrook, “Extracting and Modeling Product Line Functional Requirements,” Proceedings RE’08, Barcelona, 2008, pp. 155-164.
[5]	R. Prieto-Diaz, “Domain Analysis for Reusability,” Proceedings 11th Annual International Computer Software and Applications Conference, Tokyo, 1987, pp. 23-29.
[6]	K. C. Kang, S. G. Cohen, J. A. Hess, W. E. Novak and A. S. Peterson, “Feature-Oriented Domain Analysis (FODA) Feasibility Study,” Technical Report CMU/SEI-90-TR-021, Software Engineering Institute, Canadian Mennonite University, 1990.
[7]	K. C. Kang, S. Kim, J. Lee, K. Kim, E. Shin and M. Huh, “FORM: A Feature-Oriented Reuse Method with Domain-Specific Reference Architectures,” Annals of Software Engineering, Vol. 5, No. 1, 1998, pp. 143-168.
[8]	I. Jacobson, M. Griss and P. Jonsson, “Software Reuse: Architecture Process and Organization for Business Success,” Association for Computing Machinery Press, 1997.
[9]	M. L. Griss, J. Favaro and M. D. Alessandro, “Integrating Feature Modeling with the RSEB,” Proceedings of Inter- national Conference on Steel Rolling’98, Victoria, 1998, pp. 76-85.
[10]	J. Coplien, D. Hoffman and D. Weiss, “Commonality and Variability in Software Engineering,” IEEE Software, Vol. 15, No. 6, 1998, pp. 37-45.
[11]	M. Moon, H. S. Chae and K. Yeom, “An Approach to Developing Domain Requirements as a Core Asset Based on Commonality and Variability Analysis in a Product Line,” IEEE Transactions on Software Engineering, Vol. 31, No. 7, 2005, pp. 551-569.
[12]	E. de Almeida, J. Mascena, A. Cavalcanti, A. Alvaro, V. Garcia, S. de Lemos Meira and D. Lucrédio, “The Domain Analysis Concept Revisited: A Practical Approach,” Proceedings of International Conference on Steel Rolling’06, Turin, 2006, pp. 43-57.
[13]	I. John and D. Muthig, “Tailoring Use Cases for Product Line Modeling,” Proceedings of Requirements Engineer-ing for Product Lines’02, Essen, 2002, pp. 26-32.
[14]	Z. Zhang, “Model Component Reuse-Conceptual Foundations and Application in the Metamodel-based Systems Analysis and Design Environment,” Ph.D. dissertation, Jyvaskyla Studies in Computing 39, University of Jyvaskyla, 2004.
[15]	A. G. Kleppe, J. B. Warmer and W. Bast, “MDA Explained: The Model Driven Architecture: Practice and Promise,” Addison Wesley, Longman Publishing Co., Inc., Boston, 2003.
[16]	S. Sendall and W. Kozaczynski, “Model Transformation: The Heart and Soul of Model-Driven Software Development,” IEEE Software, Vol. 20, No. 5, 2003, pp. 42-45.
[17]	A. Cockburn, “Basic use case template,” 2010. http://alistair.cockburn.us/Basic+use+case+template.
[18]	A. Kalnins and J. B. E. Celms, “Model Transformation Language MOLA,” Proceedings Working Conference on Model Driven Architecture: Foundations and Applica- tions (MDAFA’04), Link?ping, 2004, pp. 62-76.
[19]	I. Jacobson, “Object-Oriented Software Engineering: A Use Case Driven Approach,” Addison Wesley, Wokingham, England, 1992.
[20]	Object Management Group, “Unified Modeling Language (UML), version 2.2,” 2010. http://www.omg.org/technology/documents/formal/uml.htm.
[21]	A. Cockburn, “Writing Effective Use Cases,” Addison Wesley, Boston, 2001.
[22]	H. Gomaa, “Object Oriented Analysis and Modeling for Families of Systems with UML,” Proceedings of Inter- national Conference on Steel Rolling’00, Vienna, 2000, pp. 89-99.
[23]	A. Braganca and R. J. Machado, “Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines,” Proceedings of Southern Pover- ty Law Center’07, Kyoto, 2007, pp. 3-12.
[24]	B. Wang, W. Zhang, H. Zhao, Z. Jin and H. Mei, “A Use Case Based Approach to Feature Models’ Construction,” Proceedings RE’09, Atlanta, Georgia, 2009, pp. 121-130.