Design Thinking and Scrum in Software Requirements Elicitation: A Case Study

2019 ◽  
pp. 179-194
Author(s):  
Rafael dos Santos Braz ◽  
José Reinaldo Merlin ◽  
Daniela Freitas Guilhermino Trindade ◽  
Carlos Eduardo Ribeiro ◽  
Ederson Marcos Sgarbi ◽  
...  
Keyword(s):  
Design Thinking ◽  
Requirements Elicitation ◽  
Software Requirements

scholarly journals Design Thinking: Challenges for Software Requirements Elicitation

Information ◽  
2019 ◽  
Vol 10 (12) ◽  
pp. 371 ◽  
Author(s):  
Hugo Ferreira Martins ◽  
Antônio Carvalho de Oliveira Junior ◽  
Edna Dias Canedo ◽  
Ricardo Ajax Dias Kosloski ◽  
Roberto Ávila Paldês ◽  
...  
Keyword(s):  
Design Thinking ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Agile Methods ◽  
Software Project ◽  
Functional Requirements ◽  
Use Of Data ◽  
Development Teams ◽  
Software Development Teams ◽  
User Workshop

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.

Capturing Requirements from Expected Interactions Between Software and Its Interactive Environment: An Ontology Based Approach

2016 ◽  
Vol 26 (01) ◽  
pp. 15-39 ◽  
Author(s):  
Xiaohong Chen ◽  
Zhi Jin
Keyword(s):  
Requirements Engineering ◽  
Systematic Approach ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Software Environment ◽  
Interactive Environment

Requirements elicitation is one of the most important and challenging issues in requirements engineering. This paper proposes a systematic approach for capturing the software requirements from the expected interactions between the software-to-be and its interactive environment. Firstly, the software environment ontology and the interaction ontology are developed for serving as the meta-models for the descriptions of the interactive environment and the interactions. Then a process has been proposed for guiding the analysts to capture the software requirements step by step from descriptions of the interactive environment and the expected interactions. Finally, a case study has been presented for illustrating the usage of our approach.

scholarly journals Using Design Thinking Principles to Improve Outpatients’ Experiences in Hospital Pharmacies: A Case Study of Two Hospitals in Asir Region, Saudi Arabia

Healthcare ◽  
2021 ◽  
Vol 9 (7) ◽  
pp. 854
Author(s):  
Dalia Almaghaslah ◽  
Abdulrhman Alsayari ◽  
Saleh Ali Alyahya ◽  
Rana Alshehri ◽  
Khawlah Alqadi ◽  
...  
Keyword(s):  
Saudi Arabia ◽  
Problem Solving ◽  
Management System ◽  
Design Thinking ◽  
Queue Management ◽  
End User ◽  
Study Results ◽  
Hospital Pharmacies ◽  
Asir Region

Introduction: Design thinking, an innovative problem-solving approach, has gained wide popularity in healthcare disciplines. The aim of this work is to improve outpatients’ experiences in hospital pharmacies in two hospitals in Asir region, Saudi Arabia. Methods: The design thinking approach, adopted from Stanford University’s D-School, was used in this study. Results: Several problems were identified: lack of comfortable environment in the pharmacies’ waiting area, lack of a queue management system, and workflow inefficiencies related to ordering and supplies of medicines. A prototype was proposed to overcome these challenges. Discussion and Conclusion: The design thinking approach helped in identifying end-user (patients visiting outpatient pharmacies) values and desires and provided an understanding of their struggles. It also proposed tailored solutions that could improve patients’ experiences while using the services of the outpatient pharmacies.

scholarly journals THE CHALLENGING COMBINATION OF AGILITY AND CONVERGENCE IN HYBRID PRODUCT DEVELOPMENT PROCESSES: AN EMPIRICAL ANALYSIS OF STANFORD'S ME310 PROCESS MODEL

2021 ◽  
Vol 1 ◽  
pp. 2991-3000
Author(s):  
Frank Koppenhagen ◽  
Tim Blümel ◽  
Tobias Held ◽  
Christoph Wecht ◽  
Paul Davin Kollmer
Keyword(s):  
Empirical Analysis ◽  
Systems Engineering ◽  
Process Model ◽  
Design Thinking ◽  
Solution Space ◽  
Problem Formulation ◽  
Study Approach ◽  
Development Processes ◽  
Student Projects

AbstractCombining agility and convergence in the development of physical products is a major challenge. Rooted in a design thinking approach, Stanford's ME310 process model attempts to resolve the conflicting priorities of these two design principles. To investigate how successful Stanford's hybrid process model is in doing so, we have used a qualitative case study approach. Our paper begins by outlining this process model's fundamental principles in terms of engineering design methodology. Subsequently, we present the results of our empirical analysis, which tracks the coevolution of problem and solution space by meticulously examining all prototype paths in ten of Stanford's ME310 student projects. We have discovered that convergence during solution finding does not correspond to the process model's theoretical specifications. Even in the phase of the final prototype, both the technical concept and the underlying problem formulation changed frequently. Further research should focus on combining the prototype-based ME310 approach with methods from systems engineering which allow for a more comprehensive theoretical exploration of the solution space. This could lead to improved convergence during solution development.

Sign in / Sign up

Export Citation Format

Share Document