Next Article in Journal
Adopting Augmented Reality to Engage Higher Education Students in a Museum University Collection: the Experience at Roma Tre University
Previous Article in Journal
An Optimization Model for Demand-Responsive Feeder Transit Services Based on Ride-Sharing Car
Open AccessArticle

Design Thinking: Challenges for Software Requirements Elicitation

1
Department of Computer Science, University of Brasília (UnB), P.O. Box 4466, Brasília–DF, CEP 70910-900, Brazil
2
Faculty UnB Gama, University of Brasília (UnB), P.O. Box 4466, Brasília–DF, CEP 70910-900, Brazil
3
Department of Production Engineering, University of Brasília (UnB), P.O. Box 4466, Brasília–DF, CEP 70910-900, Brazil
*
Author to whom correspondence should be addressed.
Information 2019, 10(12), 371; https://doi.org/10.3390/info10120371
Received: 21 October 2019 / Revised: 25 October 2019 / Accepted: 30 October 2019 / Published: 28 November 2019
Agile methods fit well for software development teams in the requirements elicitation activities. It has brought challenges to organizations in adopting the existing traditional methods, as well as new ones. Design Thinking has been used as a requirements elicitation technique and immersion in the process areas, which brings the client closer to the software project team and enables the creation of better projects. With the use of data triangulation, this paper brings a literature review that collected the challenges in software requirements elicitation in agile methodologies and the use of Design Thinking. The result gave way to a case study in a Brazilian public organization project, via user workshop questionnaire with 20 items, applied during the study, in order to identify the practice of Design Thinking in this context. We propose here an overview of 13 studied challenges, from which eight presented strong evidence of contribution (stakeholders involvement, requirements definition and validation, schedule, planning, requirement details and prioritization, and interdependence), three presented partial evidence of contribution and two were not eligible for conclusions (non-functional requirements, use of artifacts, and change of requirements). The main output of this work is to present an analysis of the use of Design Thinking to see if it fits properly to be used as a means of solving the challenges of elicitation of software requirements when using agile methods. View Full-Text
Keywords: agile methodology; requirements elicitation; design thinking; software evaluation agile methodology; requirements elicitation; design thinking; software evaluation
Show Figures

Figure 1

MDPI and ACS Style

Ferreira Martins, H.; Carvalho de Oliveira Junior, A.; Dias Canedo, E.; Dias Kosloski, R.A.; Ávila Paldês, R.; Costa Oliveira, E. Design Thinking: Challenges for Software Requirements Elicitation. Information 2019, 10, 371.

Show more citation formats Show less citations formats
Note that from the first issue of 2016, MDPI journals use article numbers instead of page numbers. See further details here.

Article Access Map by Country/Region

1
Back to TopTop