“…A relevant aspect that is worth highlighting is that in 24 of the 109 studies (∼22%) more than one requirements elicitation technique was used [44–46, 48, 51, 52, 56, 59, 61, 69, 70, 77, 79, 87, 94, 99, 104–106, 112, 120, 132, 136, 153].…”
Requirements elicitation is a critical activity that forms part of the requirements engineering process because it has to discover what the software must do through a solid understanding of the wishes and needs of the various stakeholders and to transform them into software requirements. However, in spite of its relevance, there are only a few systematic literature reviews that provide scientific evidence about the effectiveness of the techniques used to elicit software requirements. This study presents a systematic review of relevant literature on requirements elicitation techniques, from 1993 to 2015, by addressing two research questions: Which mature techniques are currently used for eliciting software requirements? and Which mature techniques improve the elicitation effectiveness? Prior literature assumes that such 'maturity' leads to a better-quality understanding of stakeholders' desires and needs, and thus an increased likelihood that a resulting software will satisfy those requirements. This research paper found 140 studies to answer these questions. The findings describe which elicitation techniques are effective and in which situations they work best, taking into account the product which must be developed, the stakeholders' characteristics, the type of information obtained, among other factors.
“…A relevant aspect that is worth highlighting is that in 24 of the 109 studies (∼22%) more than one requirements elicitation technique was used [44–46, 48, 51, 52, 56, 59, 61, 69, 70, 77, 79, 87, 94, 99, 104–106, 112, 120, 132, 136, 153].…”
Requirements elicitation is a critical activity that forms part of the requirements engineering process because it has to discover what the software must do through a solid understanding of the wishes and needs of the various stakeholders and to transform them into software requirements. However, in spite of its relevance, there are only a few systematic literature reviews that provide scientific evidence about the effectiveness of the techniques used to elicit software requirements. This study presents a systematic review of relevant literature on requirements elicitation techniques, from 1993 to 2015, by addressing two research questions: Which mature techniques are currently used for eliciting software requirements? and Which mature techniques improve the elicitation effectiveness? Prior literature assumes that such 'maturity' leads to a better-quality understanding of stakeholders' desires and needs, and thus an increased likelihood that a resulting software will satisfy those requirements. This research paper found 140 studies to answer these questions. The findings describe which elicitation techniques are effective and in which situations they work best, taking into account the product which must be developed, the stakeholders' characteristics, the type of information obtained, among other factors.
“…The procedures and requirements have been described elsewhere. 8,9 The approach is summarised in Figure 1. The 'guideline' to be developed can be used to develop PACT scenarios (M1, Figure 1) from which domain requirements 17 of the intended teletreatment services can be elicited.…”
Section: Methodsmentioning
confidence: 99%
“…The use of scenarios can play an important role, because they can bridge the collaboration gaps. 8,9 A scenario is defined here as a concrete description of an activity that the users engage in when performing specific tasks. 10 In practice, is is difficult to address the appropriate content and themes when constructing a scenario.…”
Lack of user acceptance of telemedicine services is an important barrier to deployment and stresses the need for involving users, i.e. medical professionals. However, the involvement of users in the service development process of telemedicine services is difficult because of (a) the knowledge gap between the expertise of medical and technical experts; (b) the language gap, i.e. the use of different terminologies between the medical and the technical professions; and (c) the methodological gap in applying requirement methods to multidisciplinary scientific matters. We have developed a guideline in which the medical and technical domains meet. The guideline can be used to develop a scenario from which requirements can be elicited. In a retrospective analysis of a myofeedback-based teletreatment service, the technically-oriented People-Activities-Context-Technology (PACT) framework and medically-oriented principles of evidence-based medicine were incorporated into a guideline. The guideline was developed to construct the content of a scenario which describes the new teletreatment service. This allows the different stakeholders to come together and develop the service. Our approach provides an arena for different stakeholders to take part in the early stages of the design process. This should increase the chance of user acceptance and thus adoption of the service being developed.
“…Requirements Elicitation (RE) is the process by which the requirements are determined. Related work of RE in the domain of mobile app for health have been found in (Widya et al, 2009). Their work is framed in a UCD approach, in which highlight the need for UCD development and argue for an early user involvement (Samaras & Horst, 2005).…”
Full adoption of Information Technologies in the healthcare domain is a reality. New paradigms as mobile computing can support a big amount of healthcare needs. The aim of this research work is to present the application of good practices in the design of healthcare information technology following a methodological approach for apps in mobile environments involving fictitious users based on knowledge of real users in the app design. Real users' needs have been extracted from empirical researches, guidelines and standards, favoring an outstanding role to users. In order to illustrate the approach and provide a resource to designers, a case study showing how to obtain an accessible design is introduced. The mobile app considered supports a Personal Health Record and self testing for anticoagulated patients who are often elderly. The access characteristics of the elderly and their possible disabilities are essential aspects to keep in mind in the design of a mobile user interface. To address users' needs on the healthcare mobile applications it has been concluded that the requirement elicitation must take into account functional requirements concerning aspects that characterize a disease, and accessibility requirements related to special needs of patients suffering a disease.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.