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.
KeywordsGamification Architect’s use case diagram (AUCD) Architecturally significant requirements (ASR)
This work was supported by the Golden infotech (goldeninfotech.com) software organization. The authors also would like to acknowledge to the Golden infotech for the support.
- 2.Chen, L., Babar, M.A., Nuseibeh, B.: Characterizing architecturally significant requirements. IEEE Software 30 (April 2013)Google Scholar
- 3.Suteliffe, A., Sayer, P.: Requiremnts Elicitation: Towards the Unknown Unknowns, Requirements Engineering Conference (RE), 2013 21st IEEE InternationalGoogle Scholar
- 5.Sathis Kumar, B., Krishnamuthi, I.: Capturing architecturally significant requirements using architect’s use case diagram. Int. J. Appl. Eng. Res. 10(6), 15141–15164 (2015)Google Scholar
- 6.Ribeiro, C., Farinha, C., Pereira, J., da Silva, M.M.: Gamifying requirement elicitation: practical implications and outcomes in improving stakeholders collaboration. Entertain. Comput. 5, 35–345 (2014)Google Scholar
- 8.Sathis Kumar, B., Krishnamuthi, I.: CloudASR an android application for capturing architecturally significant requirements visually in cloud computing applications using platform as service. Int. J. Appl. Eng. Res 10(5), 13505–13514 (2015)Google Scholar
- 9.Lange, C.F., Chaudron, M.R., Muskens, J.: In Practice: UML software architecture and design description. IEEE SOFTWARE 23, 40–46 (2006)Google Scholar
- 10.Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addition Wesely (2001)Google Scholar
- 11.Somerville, I.: Software Engineering. Pearson Education India (2011)Google Scholar
- 12.Bittner, K., Spence, I.: Use Case Modeling. Addison Wesley (2002)Google Scholar
- 13.Lim, L., Damian, D., Finkelstein, A.: Stakesource2.0: Using social networks of stakeholders to identify and prioritise requirements. In: 33rd International Conference on Software Engineering, pp. 1022–1024 (2011)Google Scholar
- 15.Seyff, N., Graf, F., Maiden, N.: End-User Requirements Blogging with iRequire, ICSE’10, ACM, 2–8 May 2010Google Scholar
- 16.Asarnusch, R., David, M., Jan, W., Astrid, B.: Visual requirement specification in end-user participation. In: Proceedings of the First International Workshop on Multimedia Requirements Engineering: IEEE Computer SocietyGoogle Scholar