Converging on the optimal attainment of requirements

Feather, Martin S.; Menzies, Tim

doi:10.1109/icre.2002.1048537

Cited by 56 publications

(59 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[24,38,48,50,57]). By computerizing the process of selecting nominated solutions, it is possible to focus the stakeholders' attention on a relatively small number of candidate solutions instead of wasting their time by discussing all possible alternatives [19]. In order to automate and to provide a small set of candidate solutions to choose from, it is necessary to put some constraints on the final product.…”

Section: Using the Results Of Requirements Prioritizationmentioning

confidence: 99%

Requirements Prioritization

Berander¹,

Andrews²

Engineering and Managing Software Requirements

185

124

View full text Add to dashboard Cite

Abstract:This chapter provides an overview of techniques for prioritization of requirements for software products. Prioritization is a crucial step towards making good decisions regarding product planning for single and multiple releases. Various aspects of functionality are considered, such as importance, risk, cost, etc. Prioritization decisions are made by stakeholders, including users, managers, developers, or their representatives. Methods are given how to combine individual prioritizations based on overall objectives and constraints. A range of different techniques and aspects are applied to an example to illustrate their use. Finally, limitations and shortcomings of current methods are pointed out, and open research questions in the area of requirements prioritization are discussed.

show abstract

Section: Using the Results Of Requirements Prioritizationmentioning

confidence: 99%

Requirements Prioritization

Berander¹,

Andrews²

Engineering and Managing Software Requirements

185

124

View full text Add to dashboard Cite

show abstract

“…The objective was to maximise the cumulative measure of the stake holder's importance to the company under resource constraints. Feather and Menzies [2] proposed a Defect Detection and Prevention (DDP) process based on a real-world instance: a NASA pilot study. It is an iterative model to seek the near-optimal attainment of requirements by applying simulated annealing.…”

Section: Related Workmentioning

confidence: 99%

“…There has been much recent work on search based optimisation for requirements engineering problems [1,2,3,4,5,6,7,8]. This work has traditionally considered objectives such as cost and value of requirements and sought to maximise the value of the requirements delivered, while minimising the cost [2,5,7].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Comparing the performance of metaheuristics for the analysis of multi-stakeholder tradeoffs in requirements optimisation

Zhang

Harman

Finkelstein

et al. 2011

Information and Software Technology

View full text Add to dashboard Cite

“…After initial screening, requirements have to be prioritized, interdependencies need to be defined, and cost estimations have to be established in order for the selection process to take place. Several methods for attaining requirement priority exist, including AHP [50], the 100-point method [51], triage [52,53], attainment [54], negotiation [55], and the planning-game [56]. Prioritization can be performed by customers and/or customer representatives, as well as by internal experts from marketing and product management.…”

Section: Related Researchmentioning

confidence: 99%

Requirements engineering: In search of the dependent variables

Gorschek

Davis

2008

Information and Software Technology

View full text Add to dashboard Cite

When software development teams modify their requirements engineering process as an independent variable, they often examine the implications of these process changes by assessing the quality of the products of the requirements engineering process, e.g., a software requirements specification (SRS). Using the quality of the SRS as the dependent variable is flawed. As an alternative, this paper presents a framework of dependent variables that serves as a full range for requirements engineering quality assessment. In this framework, the quality of the SRS itself is just the first level. Other higher, and more significant levels, include whether the project was successful and whether the resulting product was successful. And still higher levels include whether or not the company was successful and whether there was a positive or negative impact on society as a whole.

show abstract

Converging on the optimal attainment of requirements

Abstract: Abstract

Cited by 56 publications

References 13 publications

Requirements Prioritization

Requirements Prioritization

Comparing the performance of metaheuristics for the analysis of multi-stakeholder tradeoffs in requirements optimisation

Requirements engineering: In search of the dependent variables

Contact Info

Product

Resources

About