Integrating collaborative requirements negotiation and prioritization processes: a match made in heaven

Kukreja, Nupul; Boehm, Barry

doi:10.1145/2486046.2486071

Cited by 11 publications

(8 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Table 1). Furthermore, as the WinWin methodology is the methodology most commonly used for electronic requirements negotiations [15], we include decision support within the WinWin methodology [6,33]. Moreover, we compare IntelliReq [31], which provides dedicated group decision support in requirements negotiations.…”

Section: Methodsmentioning

confidence: 99%

See 1 more Smart Citation

Designing Dynamic Decision Support for Electronic Requirements Negotiations

Lenz

2020

Dynamic Decision Support for Electronic Requirements Negotiations

View full text Add to dashboard Cite

Decision support in software development is particularly important for requirements negotiations to help assessing requirements and their different implementation alternatives. Changes related to requirements are likely, which impede decision making. To keep an overview of the assessment of requirements and to keep this assessment up-to-date throughout a software development project, flexible decision support processes are needed. In this paper, we design interactive dynamic decision support, which can handle changes related to requirements dynamically. The designed support component is compared to two state-of-the-art approaches for decision support in requirements negotiations.

show abstract

Section: Methodsmentioning

confidence: 99%

“…In the following, we will analyse in a scenario-based [17,32] comparison as to whether DynaDeS meets its design goals for requirements negotiations. DynaDeS will be compared with decision support based on the WinWin methodology [33] and IntelliReq [31].…”

Section: Scenario-based Comparison Of Dynamic Decision Support For Rementioning

confidence: 99%

Designing Dynamic Decision Support for Electronic Requirements Negotiations

Lenz

2020

Dynamic Decision Support for Electronic Requirements Negotiations

View full text Add to dashboard Cite

show abstract

“…Nupul Kukreja et al [17], in this have proposed a prioritization methodology to prioritize requirements of system and software. This methodology is a two-step approach and is based on decision theoretic model using a prioritization algorithm called TOPSIS viz.…”

Section: Literature Reviewmentioning

confidence: 99%

The Impact of Analytical Assessment of Requirements Prioritization Models: An Empirical Study

Asghar¹,

Bhatti²,

Tabassum³

et al. 2017

ijacsa

View full text Add to dashboard Cite

Abstract-Requirements prioritization is one of the important parts of managing requirements in software development process which plays its role in the success or failure of a software product. A software product can go wrong or fail if right requirements are not prioritized at right time. Thus, there is a need of a vast or complete requirements prioritization technique or model that spans all the factors that must be considered while prioritizing requirements whether it's for a traditional software development or agile software development. There are several requirements prioritization methodologies that aid in decision making and in prioritizing requirements but importantly many lacks to account the important factors that have significant influence in prioritizing requirements. A requirement prioritization methodology that takes account of important factors such as time and human behavioral factors that has an influence in prioritizing requirements is required. This new model/ technique expected to overcome the lack that is in existing prioritization techniques because of not considering time gap factor and human behavioral factor. Extensive study on literature of agile methodology, requirements elicitation and prioritization has been done to find out factors that influence the decision making process of requirement prioritization. It is found that as agile methodologies such as XP, SCRUM deliver products in increments, there is a time gap between each increment of approximate 4 weeks or more, this time lapse could cause human behavioral to change either because of market demand or any other personal reason and, thus, influences the prioritization decision. These factors could be termed as time factor and human behavioral factors. Thus, a requirement prioritization technique or model is needed that takes account of all such factors while prioritizing requirements whether it's for a traditional software development or agile software development.

show abstract

“…The author has also set the directions for future work which is to build a heuristic to bound the number of stakeholders to be preferred for assessment process. Naila Sharif et al [16], devised a new requirements prioritization technique called FuzzyHCV which is a hybrid of two domains (SE and Computational Intelligence). It is a fusion of two methodologies which are Hierarchical Cumulative Voting (HCV) and Fuzzy Expert System.…”

Section: B Requirements Prioritization Techniquesmentioning

confidence: 99%

Role of Requirements Elicitation & Prioritization to Optimize Quality in Scrum Agile Development

Asghar¹,

Bhatti²,

Tabassum³

et al. 2016

ijacsa

View full text Add to dashboard Cite

Abstract-One of most common aspect with traditional software development is managing requirements. As requirements emerge throughout the software development process and thus are needed to be addressed through proper communication and integration between stakeholders, developers and documentation. Agile methodology is an innovative and iterative process that supports changing requirements and helps in addressing changes throughout the development process.Requirements are elicited at the beginning of every software development process and project (product) and latter are prioritized according to their importance to the market and to the product itself. One of the most important and influencing steps while making a software product is requirements prioritization. Prioritizing requirements helps the software team to understand the existence and importance of a particular requirement, its importance of use and its urgency to time to market. There are many requirements prioritization techniques with their relative strength and weaknesses. Otherwise many of them fail to take account all the factors that must be considered while prioritizing requirements such as cost, value, risk, time to market, number of requirements and effect of non-functional requirements on functional requirements.There are several requirements prioritization methodologies that aid in decision making but importantly many lacks to account the important factors that have significant influence in prioritizing requirements. A requirement prioritization methodology based on several factors such as time to market, cost, risk etc has been proposed. The proposed model is expected to overcome this lack. In sprints, requirements will be prioritized both on the basis of influencing factors such as cost, value, risk, time to market etc. and through the effect of non-functional requirements over functional requirements. This will improve the overall quality of software product when it is included in the development process of scrum. Requirements will not only be prioritized based on sprints, human decision but by critically analyzing the factors (sub characteristics) that can cause the product to success/ fail repeatedly thus ensuring the consistency in right requirements and hence the right prioritized requirements will be selected for a particular sprint at a time.

show abstract

Integrating collaborative requirements negotiation and prioritization processes: a match made in heaven

Cited by 11 publications

References 8 publications

Designing Dynamic Decision Support for Electronic Requirements Negotiations

Designing Dynamic Decision Support for Electronic Requirements Negotiations

The Impact of Analytical Assessment of Requirements Prioritization Models: An Empirical Study

Role of Requirements Elicitation & Prioritization to Optimize Quality in Scrum Agile Development

Contact Info

Product

Resources

About