scholarly journals Pay to play or requirements prioritization in collectives

2011 ◽  
Author(s):  
Michael Weiss
Keyword(s):  
Requirements Prioritization

Requirements Prioritization Techniques for Global Software Engineering

2017 ◽  
Vol 6 (1) ◽  
Author(s):  
Samina Saghir ◽  
Tasleem Mustafa
Keyword(s):  
Software Engineering ◽  
Requirements Engineering ◽  
Search Tree ◽  
Software Requirements ◽  
Binary Search Tree ◽  
Time Zone ◽  
Analytic Hierarchy ◽  
Requirements Prioritization ◽  
Global Software Engineering ◽  
Hierarchy Process

<p>Increase in globalization of the industry of software requires an exploration of requirements engineering (RE) in software development institutes at multiple locations. Requirements engineering task is very complicated when it is performed at single site, but it becomes too much complex when stakeholder groups define well-designed requirements under language, time zone and cultural limits. Requirements prioritization (RP) is considered as an imperative part of software requirements engineering in which requirements are ranked to develop best-quality software. In this research, a comparative study of the requirements prioritization techniques was done to overcome the challenges initiated by the corporal distribution of stakeholders within the organization at multiple locations. The objective of this study was to make a comparison between five techniques for prioritizing software requirements and to discuss the results for global software engineering. The selected techniques were Analytic Hierarchy Process (AHP), Cumulative Voting (CV), Value Oriented Prioritization (VOP), Binary Search Tree (BST), and Numerical Assignment Technique (NAT). At the end of the research a framework for Global Software Engineering (GSE) was proposed to prioritize the requirements for stakeholders at distributed locations.<strong></strong></p>

The Role of Nonmonotonic Representations in Requirements Engineering

1998 ◽  
Vol 08 (03) ◽  
pp. 385-399 ◽  
Author(s):  
Grigoris Antoniou
Keyword(s):  
Software Engineering ◽  
Knowledge Representation ◽  
Requirements Engineering ◽  
Nonmonotonic Reasoning ◽  
Default Reasoning ◽  
Requirements Prioritization ◽  
Evolving System ◽  
System Requirements

This paper discusses the significance of nonmonotonic reasoning, a method from the knowledge representation area, to mainstream software engineering. In particular, we discuss why the use of defaults in specifications is an adequate way of addressing some of the most important problems in requirements engineering, such as: The problem of identifying and dealing with inconsistencies; evolving system requirements; requirements prioritization; and the quality of specifications with respect to naturalness and compactness. We argue that these problems need to be addressed in a principled, formal way, and that default reasoning provides adequate mechanisms to deal with them.

scholarly journals A Supporting Tool for Requirements Prioritization Process in Agile Software Development

2020 ◽  
Vol 5 (1) ◽  
pp. 15-27
Author(s):  
Khaled AbdElazim Muhammad ◽  
◽  
Ramadan Moawad ◽  
Essam Elfakharany ◽  
◽  
...  
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Agile Software Development ◽  
Continuous Growth ◽  
Requirements Prioritization ◽  
Prioritization Process ◽  
Development Life Cycle ◽  
Supporting Tool ◽  
Growth Change ◽  
Agile Software

Requirements engineering is a crucial phase of software engineering, and requirements prioritization is an essential stage of requirements engineering particularly in agile software development. Requirements prioritization goals at eliciting which requirements of software need to be covered in a particular release. The key point is which requirement will be selected in the next iteration and which one will be delayed to other iterations for minimizing risk during development and meeting stakeholders’ needs. There are many existing techniques for requirement prioritization, but most of these techniques do not cover continuous growth, change of requirements, and requirements dependencies. The prioritization techniques need to be more continuous, scalable, implemented easily and integrated with software development life cycle. This paper introduces a supporting tool for a proposed framework to prioritize requirements in agile software development. This framework tries to find solutions for the challenges facing this prioritization process such as how to make this prioritization continuous and scalable and how to deal with rapidly requirement changes and its dependencies. The proposed framework is validated in a real case study using its supporting tool, and the results are promising

Sign in / Sign up

Export Citation Format

Share Document