Advertisement

User Requirements Elicitation

  • Steffi DaveyEmail author
  • Jonathan Saunders
Chapter
Part of the Security Informatics and Law Enforcement book series (SILE)

Abstract

This chapter identifies why the collection of end user requirements is such a defining and important stage of any serious game development project. It outlines requirements elicitation techniques and discusses their strengths, weaknesses and where they are useful. It will then discuss how to analyse the data that has been obtained. Finally, it will describe the processes and lessons learned along the various stages of end user requirements gathering using a concrete case example.

Keywords

Serious games User requirements Requirements elicitation Elicitation techniques AUGGMED 

References

  1. Abugabah, A. J., & Alfarraj, O. (2015). Issues to consider in designing health care information systems: A user-centred design approach. Journal of Health Informatics, 9(1).Google Scholar
  2. Ahmad, S. (2008). Negotiation in the requirements elicitation and analysis process. In: 19th Australian Conference on Software Engineering (pp. 683–689). IEEE: Los AlamitosGoogle Scholar
  3. Courage, C., & Baxter, K. (2005). Understanding your users: A practical guide to user requirements methods, tools, and techniques. Morgan Kaufmann, San Francisco.Google Scholar
  4. Davis, A. D. O., Hickey, A. J. N., & Moreno, A. M. (2006). Effectiveness of requirements elicitation techniques: Empirical results derived from a systematic review. In 14th IEEE International Requirements Engineering Conference (RE'06) (pp. 179-188). IEEE.Google Scholar
  5. Hauge, J. B., Duin, H., Oliveira, M., & Thoben, K. D. (2006). User requirements analysis for educational games in manufacturing. In 2006 IEEE International Technology Management Conference (ICE) (pp. 1-8). IEEE.Google Scholar
  6. Hickey, A. M., & Davis, A. M. (2003) Elicitation technique selection: how do experts do it? In Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. (pp. 169-178). IEEE.Google Scholar
  7. Kasurinen, J., Maglyas, A., & Smolander, K. (2014). Is requirements engineering useless in game development?. Requirements Engineering: Foundation for Software Quality.Google Scholar
  8. Kelly, D., de Boer, J., Uhlenbruck, P., & Webb, S. (2015) Requirements gathering and testing by game playing. In 2015 IEEE 28th Canadian Conference on Electrical and Computer Engineering (CCECE) (pp. 1556-1560). IEEE.Google Scholar
  9. Kumar, A., & Sharma, A. (2015). A SWOT analysis of requirements engineering for web application. Journal of Advances Research in Science and Engineering, 4, 34–43.Google Scholar
  10. Lane, S., O’Raghallaigh, P., & Sammon, D. (2016). Requirements gathering: The journey. Journal of Decision Systems, 25, 302–312.CrossRefGoogle Scholar
  11. Langdon, G. G. (1984). An introduction to arithmetic coding. IBM Journal of Research and Development, 28(2), 135–149.MathSciNetCrossRefGoogle Scholar
  12. Leffingwell, D. (1997). Calculating your return on investment from more effective requirements management. American Programmer, 10(4), 13–16.Google Scholar
  13. Nuseibeh, B., & Easterbrook, S. (2000). Requirements engineering: a roadmap. In Proceedings of the Conference on the Future of Software Engineering (pp. 35-46). ACM.Google Scholar

Copyright information

© Springer Nature Switzerland AG 2019

Authors and Affiliations

  1. 1.CENTRIC, Sheffield Hallam UniversitySheffieldUK

Personalised recommendations