Prototyping Use as a Software Requirements Elicitation Technique: A Case Study

  • Dante Carrizo
  • Iván Quintanilla
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 746)


Prototyping is an agile software development methodology. It has also been proposed as a technique to obtain the software requirements from the stakeholders. However, there are few publications proposing a prescriptive guide and show its use in practice. This article presents a report of a case in which the prototype technique was used to elicit requirements of a software system in the university academic context. For this, authors propose a procedure to apply and they carry out elicitation sessions with two stakeholders who have different familiarity with the domain. The results show that the technique is effective in achieving a high coverage of the requirements and that it seems to perform better with stakeholders who have more familiarity with the domain. Although the results do not have statistical power, the case yields trends that can help development teams adopt this technique to produce the requirements in certain cases.


Requirements engineering Prototyping technique Familiarity with the domain Requirements production Case study 



This work was funded by the Research fund of the University of Atacama, project DIUDA 22298.


  1. 1.
    Sommerville, I.: Ingeniería de Software. Naucalpan de Juarez, México. Pearson Education (2011)Google Scholar
  2. 2.
    Radatz, J., Geraci, A., Katki, F.: IEEE standard glossary of software engineering terminology. IEEE Std, 610121990(121990) (1990)Google Scholar
  3. 3.
    Pressman, R.S.: Software Engineering: A Practical Approach. McGraw-Hill, New York (1988)zbMATHGoogle Scholar
  4. 4.
    Kotonya, G., Sommerville, I.: Requirements Engineering: Processes and Techniques. Wiley, Chichester (2002)Google Scholar
  5. 5.
    Andriole, S.J.: Fast, cheap requirements prototype, or else! IEEE Softw. 11(2), 85–87 (1994)CrossRefGoogle Scholar
  6. 6.
    Carey, J.M.: Prototyping: alternative systems development methodology. Inf. Softw. Technol. 32(2), 119–126 (1990)CrossRefGoogle Scholar
  7. 7.
    Jones, T.S., Richey, R.C.: Rapid prototyping methodology in action: a developmental study. Educ. Technol. Res. Dev. 48(2), 63–80 (2000)CrossRefGoogle Scholar
  8. 8.
    Berzins, V.: Rapidly prototyping real-time systems. IEEE Softw. 5(5), 25–36 (1988)CrossRefGoogle Scholar
  9. 9.
    Ollila, E.M., Suomela, R., Holopainen, J.: Using prototypes in early pervasive game development. Comput. Entertainment (CIE) 6(2), 17 (2008)Google Scholar
  10. 10.
    Asur, S., Hufnagel, S.: Taxonomy of rapid-prototyping methods and tools. In: Proceedings of Fourth International Workshop on Rapid System Prototyping. Shortening the Path from Specification to Prototype, pp. 42–56. IEEE (1993)Google Scholar
  11. 11.
    Bahn, D.L., Naumann, J.D.: Evolution versus construction: distinguishing user review of software prototypes from conventional review of software specifications. In: Proceedings of the 1997 ACM SIGCPR Conference on Computer Personnel Research, pp. 240–245. ACM (1997)Google Scholar
  12. 12.
    Vijayan, J., Raju, G.: Requirements elicitation using paper prototype. In: Advances in Software Engineering, pp. 30–37 (2010)CrossRefGoogle Scholar
  13. 13.
    Cho, H., Kinny, D., Lin, D.: Parallel prototyping for multi-language service design: a case study on introducing a multilingual tool into a Japanese local restaurant. In: 2013 International Conference on Culture and Computing (Culture Computing), pp. 86–91. IEEE (2013)Google Scholar
  14. 14.
    Mannio, M., Nikula, U.: Requirements elicitation using a combination of prototypes and scenarios. In: WER, pp. 283–296, ISO 690 (2001)Google Scholar
  15. 15.
    Abran, A., Moore, J.W.: SWEBOK: Guide to the Software Engineering Body of Knowledge. IEEE Computer Society, California (2004). Ed. 2004Google Scholar
  16. 16.
    Berry, D.M.: The importance of ignorance in requirements engineering. J. Syst. Softw. 28(2), 179–184 (1995)CrossRefGoogle Scholar
  17. 17.
    Dieste, O., Juristo, N., Shull, F.: Understanding the customer: what do we know about requirements elicitation? IEEE Softw. 25(2), 11–13 (2008)CrossRefGoogle Scholar
  18. 18.
    Kenzi, K., Soffer, P., Hadar, I.: The role of domain knowledge in requirements elicitation: an exploratory study. In: Proceedings of the Fifth Mediterranean Conference on Information Systems (MCIS) (2010)Google Scholar
  19. 19.
    Van Schooenderwoert, N.: Embedded agile project by the numbers with newbies. In: Proceedings of the AGILE Conference (AGILE), pp. 351–366 (2006)Google Scholar
  20. 20.
    Kristensson, P., Gustafsson, A., Archer, T.: Harnessing the creative potential among users. J. Prod. Innov. Manag. 21(1), 4–14 (2004)CrossRefGoogle Scholar
  21. 21.
    Rocha, Á., Vasconcelos, J.B.: A framework to analyse the approach adopted in the information systems requirements engineering activity. In: Proceedings of the SERP04 - The 2004 International Conference on Software Engineering Research and Practice, Las Vegas, USA (2004)Google Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  1. 1.Computer Science DepartmentUniversity of AtacamaCopiapóChile

Personalised recommendations