Approach to define a non-functional requirements elicitation guide using a customer language

3Citations
Citations of this article
24Readers
Mendeley users who have this article in their library.

Abstract

Non-functional requirements (NFR) have a crucial role in the software development process because they correspond to the characteristics and restrictions on which the software must running and represent factors that influence the time and cost of software development. Nevertheless, many organizations do not perform these requirements elicitation properly. This paper presents an approach to creating a NFR elicitation guide focused on customer language. To create the approach was performed a systematic review which identified and analyzed related works. Also a survey was conducted which helped to know the current situation of NFR elicitation in software development organizations and obtained suggestions for composition of the NFR elicitation guide. Finally, the results of applying the proposed approach presents evidence that the use of the process is feasible and produces better quality requirements.

Cite

CITATION STYLE

APA

Silva, A., Pinheiro, P., Albuquerque, A., & Barroso, J. (2016). Approach to define a non-functional requirements elicitation guide using a customer language. In Proceedings of the International Conference on Software Engineering and Knowledge Engineering, SEKE (Vol. 2016-January, pp. 575–578). Knowledge Systems Institute Graduate School. https://doi.org/10.18293/SEKE2016-195

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free