Hostname: page-component-7c8c6479df-5xszh Total loading time: 0 Render date: 2024-03-19T09:51:02.126Z Has data issue: false hasContentIssue false

User Stories Method and Assistive Technology Product Development: A New Approach to Requirements Elicitation

Published online by Cambridge University Press:  26 July 2019

Abstract

Core share and HTML view are not available for this content. However, as you have access to this content, a full PDF is available via the ‘Save PDF’ action button.

Requirements elicitation for assistive technology (AT) product development must be collaborative and systemic. This process must ensure that the needs of all different users are identified. For this, UCD methods introduce different tools that seek user involvement and their needs identification. One method commonly used in software development is User Stories. The aim of this paper is to analyse the use of User Stories for requirements elicitation in an AT product development project. This method was applied with three types of users: patients, companions and occupational therapists. For the involvement of these users, the method was customized and two main adaptations were adopted: the stories were written by the development team and all user needs were identified through observations of interactions between patients and prototype. As a result, the development team was able to identify numerous product requirements to be used in later development phases. These requirements were generated by the user needs identified with User Stories. Thus, the method with necessary adaptations, was efficient for requirements elicitation in the AT product development process.

Type
Article
Creative Commons
Creative Common License - CCCreative Common License - BYCreative Common License - NCCreative Common License - ND
This is an Open Access article, distributed under the terms of the Creative Commons Attribution-NonCommercial-NoDerivatives licence (http://creativecommons.org/licenses/by-nc-nd/4.0/), which permits non-commercial re-use, distribution, and reproduction in any medium, provided the original work is unaltered and is properly cited. The written permission of Cambridge University Press must be obtained for commercial re-use or in order to create a derivative work.
Copyright
© The Author(s) 2019

References

ABNT NBR IEC 60601-1-6 (2011), Equipamento eletromédico Parte 1-6: Requisitos gerais para segurança básica e desempenho essencial Norma colateral: Usabilidade.Google Scholar
Abras, C., Krichmar, D.M. and Preece, J. (2004), “User-Centered Design”, Encyclopedia of Human-Computer Interaction.Google Scholar
Alexander, I.A.N. and Maiden, N. (2004), Scenarios, stories, use cases, John Wiley &Sons Ltd, England.Google Scholar
Bertholdo, A.P.O., Da Silva, T.S., De O. Melo, C. Kon, F. and Silveira, M.S. (2014), “Agile usability patterns for UCD early stages”, In: Marcus, A. (Ed.), Design, User Experience, and Usability. Proceeding. Crete, Springer, Greece, pp. 3344. http://doi.org/10.1007/978-3-319-07668-3_4Google Scholar
Brasil, S.N., de P. dos D. da P. com D. (2009), Tecnologia Assistiva, CORDE, Comitê de. Brasília.Google Scholar
Campese, C., Scatolin, J.L., Esposto, R.F.S. and Costa, J.M.H.d. (2015), “Estudo dos métodos de UCD”, 10° Congresso Brasileiro de Gestão da Inovação e Desenvolvimentos de Produtos, Itajubá - MG, pp. 112.Google Scholar
Campese, C., Silva, T.N.R.d., Silva, L.L.G.d., Figueiredo, J.P. and Menegon, N.L. (2016), “Assistive technology and passengers with special assistance needs in air transport: contributions to cabin design”, Production, Vol. 26 No. 2, pp. 303312.Google Scholar
Chung, L., Nixon, B.A., Yu, E. and Mylopoulos, J. (2000), Non-functional requirements in software engineering. 1st editio, Springer Science+Business Media, New York. http://doi.org/10.1007/978-1-4615-5269-7Google Scholar
Cohn, M. (2004), User Stories Applied: For Agile Software Development, Addison Wesley.Google Scholar
Das, S.K. and Almonor, J.B. (2000), “A concurrent engineering approach for the development of medical devices”, International Journal of Computer Integrated Manufacturing, Vol. 13 No. 2, pp. 139147. https://doi.org/10.1080/095119200129984Google Scholar
Gardan, J. (2017), “‘Definition of users’ requirements in the customized product design through a user-centered translation method’”, International Journal on Interactive Design and Manufacturing. Springer Paris, Vol. 11 No. 4, pp. 813821. http://doi.org/10.1007/s12008-015-0275-2Google Scholar
IEEE (1990), IEEE Standard Glossary of Software Engineering Terminology, p. 94.Google Scholar
Leffingwell, B.D. and Behrens, P. (2010), By Dean Leffingwell with Pete Behrens, pp. 116.Google Scholar
Martin, J.L., et al. (2010), Design for patient safety. User testing in the development of medical devices, National Patient Satefy Agency, London, p. 68.Google Scholar
Martin, J., Murphy, E.A., Crowe, J.A. and Norris, B. (2006), “Capturing User Requirements in Medical Device Development: The Role of Ergonomics”, Pshysiological Measurement, Vol. 27 No. 8, pp. R49R62.Google Scholar
Oglio, P.D. (2006), Uma Ferramenta para Gerenciamento de Requisitos em Projetos Baseados em Extreme Programming, Universidade do Vale do Rio Dos Sinos.Google Scholar
Paula Filho, W. de P. (2000), “Engenharia de Software: fundamentos, métodos e padrões”, Manual do Engenheiro de Software, p. 260.Google Scholar
Pressman, R.S. (2010), Software Engineering. A practitioneŕs approach. 7th edn, McGraw-Hill, New York.Google Scholar
Rozenfeld, H., Forcellini, F.A., Amaral, D.C., Toledo, J.C.d., Silva, S.L.d., Alliprandini, D.H. and Scalice, R.K. (2006), Gestão de Desenvolvimento de Produtos Uma referência para a melhoria do Processo, 1a Edição, Saraiva.Google Scholar
Shah, S.G.S., Robinson, I. and AlShawi, S. (2009), “Developing medical device technologies from users’ perspectives: A theoretical framework for involving users in the development process”, International Journal of Technology Assessment in Health Care, Vol. 25 No. 4, pp. 514521.Google Scholar
Schiro, J., Pelayo, S., Weinhold, T., Del Zotto, M. and Marcilly, R. (2017), “Usability Validation of Medical Devices: Issues in Identifying Potential Use Errors”, Building Capacity for Health Informatics in the Future, pp. 298302. https://doi.org/10.3233/978-1-61499-742-9-298Google Scholar
Sharma, S. and Pandey, S.K. (2014), “Requirements Elicitation: Issues and Challenges”, International Conference on Computing for Sustainable Global Development (INDIACom), pp. 151155.Google Scholar
Sommerville, I. (2011), Engenharia de Software, 9.ed, Pearson Prentice Hall, São Paulo.Google Scholar
Tran, T. and Sherif, J.S. (1995), “Quality Function Deployment (QFD): An Effective Technique For Requirements Acquisition and Reuse”, Conference Software Engineering Standards Symposium.Google Scholar
Ulrich, K.T. and Eppinger, S.D. (2012), Product Design and Development. Fifth Edit, McGraw-Hill Irwin, New York.Google Scholar
Vredenburg, K., Mao, J.-Y., Smith, P.W. and Carey, T. (2002), “A Survey of User-Centered Design Practice”, Design Methods, Vol. 4 No. 1, pp. 471478.Google Scholar
Yin, R.K. (2011), Qualitative Research from Start to Finish, The Guilford Press, New York.Google Scholar
Zowghi, D. and Coulin, C. (2005), “Requirements Elicitation: A Survey of Techniques, Approaches, and Tools”, in Engineering and Managing Software Requirements, pp. 1946.Google Scholar