Open Access
Information and Software Technology
Philip Achimugu,Ali Selamat +1 more
Reads0
Chats0
TLDR
This study identifies and analyzes existing prioritization techniques in the context of the formulated research questions and identifies primary studies that relate requirements prioritization classified under journal articles, conference papers, workshops, symposiums, book chapters and IEEE bulletins.Abstract:
Context: During requirements engineering, prioritization is performed to grade or rank requirements in their order of importance and subsequent implementation releases. It is a major step taken in making crucial decisions so as to increase the economic value of a system. Objective: The purpose of this study is to identify and analyze existing prioritization techniques in the context of the formulated research questions. Method: Search terms with relevant keywords were used to identify primary studies that relate requirements prioritization classified under journal articles, conference papers, workshops, symposiums, book chapters and IEEE bulletins. Results: 73 Primary studies were selected from the search processes. Out of these studies; 13 were journal articles, 35 were conference papers and 8 were workshop papers. Furthermore, contributions from symposiums as well as IEEE bulletins were 2 each while the total number of book chapters amountedread more
Citations
More filters
Journal ArticleDOI
Software fault prediction metrics
TL;DR: Object-oriented and process metrics have been reported to be more successful in finding faults compared to traditional size and complexity metrics and seem to be better at predicting post-release faults than any static code metrics.
Journal ArticleDOI
Systematic literature review of machine learning based software development effort estimation models
TL;DR: A systematic literature review of empirical studies on ML model published in the last two decades finds that eight types of ML techniques have been employed in SDEE models, and overall speaking, the estimation accuracy of these ML models is close to the acceptable level and is better than that of non-ML models.
Journal ArticleDOI
Transfer learning for cross-company software defect prediction
TL;DR: This paper considers the cross-company defect prediction scenario where source and target data are drawn from different companies, and proposes a novel algorithm called Transfer Naive Bayes (TNB), which is more accurate in terms of AUC, within less runtime than the state of the art methods.
Journal ArticleDOI
Software development in startup companies: A systematic mapping study
Nicolo Paternoster,Carmine Giardino,Michael Unterkalmsteiner,Tony Gorschek,Pekka Abrahamsson +4 more
TL;DR: The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Journal ArticleDOI
A systematic literature review of software requirements prioritization research
TL;DR: It was generally discovered that, existing prioritization techniques suffer from a number of limitations which includes: lack of scalability, methods of dealing with rank updates during requirements evolution, coordination among stakeholders and requirements dependency issues.
References
More filters
Book ChapterDOI
The Analytic Hierarchy Process
Thomas L. Saaty,Kevin P. Kearns +1 more
TL;DR: Analytic Hierarchy Process (AHP) as mentioned in this paper is a systematic procedure for representing the elements of any problem hierarchically, which organizes the basic rationality by breaking down a problem into its smaller constituent parts and then guides decision makers through a series of pairwise comparison judgments to express the relative strength or intensity of impact of the elements in the hierarchy.
Book
Requirements Engineering: A Good Practice Guide
Ian Sommerville,Pete Sawyer +1 more
TL;DR: This book presents a set of guidelines which reflect the best practice in requirements engineering, and explains in an easy-to-understand way how you can improve your requirements engineering processes.
Journal ArticleDOI
A cost-value approach for prioritizing requirements
Joachim Karlsson,Kevin Ryan +1 more
TL;DR: A cost-value approach for prioritizing requirements is developed and applied to two commercial projects, finding it helps project managers select a subset of the customers' requirements and still produce a system that meets their needs.
Book
Managing software requirements: a unified approach
Dean Leffingwell,Don Widrig +1 more
TL;DR: Managing Software requirements describes six vital Team Skills for managing requirements throughout the lifecycle of a project and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders.
Journal ArticleDOI
An evaluation of methods for prioritizing software requirements
TL;DR: An evaluation of six different methods for prioritizing software requirements for a telephony system found the analytic hierarchy process to be the most promising method, although it may be problematic to scale-up.