Improving User Participation in Requirement Elicitation and Analysis by Applying Gamification Using Architect’s Use Case Diagram

Customer involvement and lack of expressive communication mechanism are the major problems in capturing Architecturally Significant Requirements (ASR) in requirement elicitation and analysis stage in the software development. In our earlier work we have introduced Architect Use Case Diagram (AUCD) an enhanced version of use case diagram, which is useful to specify functional and quality attribute requirements in one diagram. Gamification is an emerging technique used in the software industry to improve the user’s commitment, inspiration and performance. In this paper we proposed gamification using AUCD, a new methodology for requirement elicitation and analysis. The combination of gamification and AUCD motivates the users to participate in the requirement elicitation and analysis actively, which helps the analyst to capture more architecturally significant requirements. The proposed gamification using AUCD method is applied in different projects for validating the effectiveness. The research result shows that gaming using AUCD improves user participation in requirement elicitation.

[1]  Jan Wiesenberger,et al.  Visual Requirement Specification In End-User Participation , 2006, 2006 First International Workshop on Multimedia Requirements Engineering (MERE'06 - RE'06 Workshop).

[2]  Miguel Mira da Silva,et al.  Gamifying requirement elicitation: Practical implications and outcomes in improving stakeholders collaboration , 2014, Entertain. Comput..

[3]  Muneera Bano,et al.  A systematic review on the relationship between user involvement and system success , 2015, Inf. Softw. Technol..

[4]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[5]  Bashar Nuseibeh,et al.  Characterizing Architecturally Significant Requirements , 2013, IEEE Software.

[6]  Kurt Bittner,et al.  Use Case Modeling , 2002 .

[7]  Daniela E. Damian,et al.  StakeSource2.0: using social networks of stakeholders to identify and prioritise requirements , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[8]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[9]  Neil A. M. Maiden,et al.  End-user requirements blogging with iRequire , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[10]  Alistair Sutcliffe,et al.  Requirements elicitation: Towards the unknown unknowns , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).

[11]  Mario Piattini,et al.  Gamification in software engineering - A systematic mapping , 2015, Inf. Softw. Technol..

[12]  Michel R. V. Chaudron,et al.  In practice: UML software architecture and design description , 2006, IEEE Software.