Mind-mapping: An effective technique to facilitate requirements engineering in agile software development

Mahmud, Imran; Veneziano, Vito

doi:10.1109/iccitechn.2011.6164775

Cited by 36 publications

(21 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Moreover, according to Derrick et al [153], the user story in groups generates more complete requirements. Another advantage is that one user can be verified and expanded by another user since the knowledge of one user helps to activate the knowledge of another group member, evaluate another's information, and ask for clarification. Finally, the mind mapping was considered effective by Mahmud and Veneziano [144] when they evaluated the effectiveness of this technique in SCRUM and concluded that mind maps are effective in increasing the quality of product backlogs.…”

Section: Resultsmentioning

confidence: 99%

“…it is the only technique that the analyst knows, it is the analyst's preferred technique for all situations, the analyst is following some explicit methodology, and that methodology prescribes a particular technique at the current time). However, according to the authors in [60,144,[154][155][156][157][158][159][160][161][162][163] the aspects that the analyst must take into account for measuring the effectiveness of an elicitation technique are: software context, quality of the obtained requirements, amount of information elicited, indicator of user satisfaction, the number of defects in requirements, number of correct requirements, level of requirements completeness, level of requirements accuracy, the requirements volatility grade, and the level of agreement among stakeholders. Therefore, with the aim of answering this question, we first evaluated these aspects by analysing the empirical evaluation of the studies identified.…”

Section: Rq2-mature Techniques That Improve the Elicitation Effectivementioning

confidence: 99%

See 1 more Smart Citation

Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques

2018

View full text Add to dashboard Cite

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.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Rq2-mature Techniques That Improve the Elicitation Effectivementioning

confidence: 99%

Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques

2018

View full text Add to dashboard Cite

show abstract

“…This session lasted for 3 hours and was led by the team lead (NB). The session involved brainstorming with the objective of forming a shared understanding of the major facets that will be included in the app content to meet the needs of end users [ 33 , 34 ]. Experts were provided with the results of the review of mobile phone cessation apps by Abroms and colleagues [ 15 ], the findings from the assessment of the most popular and frequently downloaded cessation apps, and the summarized results of the focus groups with young adult smokers from phase I before engaging in the mind mapping exercise.…”

Section: Methodsmentioning

confidence: 99%

Crush the Crave: Development and Formative Evaluation of a Smartphone App for Smoking Cessation

Baskerville¹,

Struik²,

Dash³

2018

JMIR Mhealth Uhealth

View full text Add to dashboard Cite

BackgroundEmerging evidence supports the use of smartphone apps for smoking cessation, especially in young adults given their high smoking rates and high smartphone ownership rates. Although evaluative evidence is encouraging for supporting smoking cessation, there remains a paucity of research describing the design and development processes of mobile health (mHealth) interventions.ObjectiveThe aim of this paper was to describe the process of developing Crush the Crave (CTC), an evidence-informed app to support smoking cessation in young adults, and the results of a formative evaluation of app usage behavior, as part of a broader program of research that seeks to establish the effectiveness of the CTC app.MethodsThe Spiral Technology Action Research (STAR) 5-cycle model (listen, plan, do, act, and study) was employed to guide the development, implementation, and dissemination of CTC. The approach to development and formative evaluation included focus groups with young adult smokers (n=78) across 2 phases, analysis of the content of existing apps, 2 sessions with content experts, and Google Analytics to assess user behavior during a 12-month pilot.ResultsLISTEN—focus groups revealed young adult smoker preferences of (1) positive reinforcement, (2) personalization, (3) social support, (4) quit support, (5) tracking the behavior, and (6) tracking quit benefits. PLAN—informed by evidence for smoking cessation, young adult preferences and an assessment of popular cessation apps, content experts produced a mind map and a storyboard describing app content and structure. DO—focus groups with young adult smokers provided feedback on the first version of the app with opinions on content and suggestions for improvement such as providing alerts and distractions from craving. ACT—refinements were made, and app content was organized using the 4 key design components informed by principles of persuasive technology for behavior change: credibility, task support, dialogue support, and social support. CTC was launched in April 2013 and piloted from the period July 2013 to June 2014 where 1987 Android users had 18,567 sessions, resulting in 59,384 page views and 89.58% (1780/1987) of users returning within the same day to use CTC. STUDY—a pragmatic randomized controlled trial of CTC was launched in August 2014 to demonstrate that including mHealth technology as a population-based intervention can help young adult smokers to quit. The results of this phase will be presented in a subsequent publication.ConclusionsCTC is one of the first smoking cessation apps designed to meet the needs of young adult smokers. The development was informed by the inclusion of young adults in the design and the systematic application of multiple stakeholder input, scientific evidence, and theory. The STAR model approach was followed from the beginning of intervention development, which should facilitate optimization of mHealth interventions in the future.Trial RegistrationClinicalTrials.gov NCT01983150; http://clinicaltrials.gov/ct2/show/NCT01983150 (Ar...

show abstract

“…In their work, the focus is on engineering a dedicated method for requirements elicitation, which we don't aim for. Also mind maps have been used for requirement elicitation, e.g., [24], [25], [26], [27], [28]. However, our approach is not based on mind maps (but on feature models), we only use a user interface that is very similar to the ones used for mind maps.…”

Section: Discussionmentioning

confidence: 98%

A feature modeling approach for domain-specific requirement elicitation

Troyer

Janssens

2014

2014 IEEE 4th International Workshop on Requirements Patterns (RePa)

View full text Add to dashboard Cite

In this paper, we presented an approach for domain-specific requirement elicitation. Building domain-specific software requires the expertise of people with very different background and with different levels of experience in software development. This complicates the process of requirement elicitation. The purpose of the approach is twofold. On the one hand, we want to unlock available information on requirement elicitation for particular domains. On the other hand, we want to provide a mechanism for guiding the stakeholders (noncomputing as well as computing people) through the requirement elicitation process in these domains. The approach is based on Feature Modeling, a variability modeling technique used in Software Product Lines. Furthermore, a tablet app has been developed to support the approach. We demonstrate the approach for two different domains, the domain of serious games for children and the domain of e-shop web applications. A first evaluation of the approach and the tool has been done by means of two explorative case studies and resulted in positive feedbacks.

show abstract

Mind-mapping: An effective technique to facilitate requirements engineering in agile software development

Cited by 36 publications

References 7 publications

Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques

Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques

Crush the Crave: Development and Formative Evaluation of a Smartphone App for Smoking Cessation

A feature modeling approach for domain-specific requirement elicitation

Contact Info

Product

Resources

About