Supporting roadmapping of quality requirements
Regnell, Björn LU
; Berntsson Svensson, Richard
LU
and Olsson, T
(2008)
In IEEE Software
25(2).
p.42-47
- Abstract
- Would slightly better performance be significantly more valuable from a market perspective? Would significantly better performance be just slightly more expensive to implement? When dealing with performance, usability, reliability, and so on, you often end up in difficult trade-off analysis. You must take into account aspects such as release targets, end-user experience, and business opportunities. At the same time, you must consider what is feasible with the evolving system architecture and the available development resources.Quality requirements are of major importance in the development of systems for software-intensive products. To be successful, a company must find the right balance among competing quality attributes. How should you... (More)
- Would slightly better performance be significantly more valuable from a market perspective? Would significantly better performance be just slightly more expensive to implement? When dealing with performance, usability, reliability, and so on, you often end up in difficult trade-off analysis. You must take into account aspects such as release targets, end-user experience, and business opportunities. At the same time, you must consider what is feasible with the evolving system architecture and the available development resources.Quality requirements are of major importance in the development of systems for software-intensive products. To be successful, a company must find the right balance among competing quality attributes. How should you balance, for example, investments for improved usability of a mobile phone's phone book and better mobile positioning? In the context of quality requirements, decision making typically combines market considerations and design issues in activities such as roadmapping, release planning, and platform scoping. Models that address requirements prioritization in a market-driven context often emphasize functional aspects. (For a comparison of other relevant techniques with Quper, see the sidebar.) Quper provides concepts for reasoning about quality in relation to cost and value and can be used in combination with existing prioritization approaches (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/1193792
- author
- Regnell, Björn
LU
; Berntsson Svensson, Richard
LU
and Olsson, T
- organization
- publishing date
- 2008
- type
- Contribution to journal
- publication status
- published
- subject
- keywords
- requirements engineering, quality requirements, performance requirements, cost-benefit analysis, nonfunctional requirements, roadmapping, trade-off analysis
- in
- IEEE Software
- volume
- 25
- issue
- 2
- pages
- 42 - 47
- publisher
- IEEE - Institute of Electrical and Electronics Engineers Inc.
- external identifiers
-
- wos:000253376100018
- scopus:40949150319
- ISSN
- 0740-7459
- DOI
- 10.1109/MS.2008.48
- language
- English
- LU publication?
- yes
- id
- ab35dfb9-b240-4dbe-9447-0719a8bfee50 (old id 1193792)
- date added to LUP
- 2016-04-01 12:57:50
- date last changed
- 2022-02-26 18:33:19
@article{ab35dfb9-b240-4dbe-9447-0719a8bfee50,
abstract = {{Would slightly better performance be significantly more valuable from a market perspective? Would significantly better performance be just slightly more expensive to implement? When dealing with performance, usability, reliability, and so on, you often end up in difficult trade-off analysis. You must take into account aspects such as release targets, end-user experience, and business opportunities. At the same time, you must consider what is feasible with the evolving system architecture and the available development resources.Quality requirements are of major importance in the development of systems for software-intensive products. To be successful, a company must find the right balance among competing quality attributes. How should you balance, for example, investments for improved usability of a mobile phone's phone book and better mobile positioning? In the context of quality requirements, decision making typically combines market considerations and design issues in activities such as roadmapping, release planning, and platform scoping. Models that address requirements prioritization in a market-driven context often emphasize functional aspects. (For a comparison of other relevant techniques with Quper, see the sidebar.) Quper provides concepts for reasoning about quality in relation to cost and value and can be used in combination with existing prioritization approaches}},
author = {{Regnell, Björn and Berntsson Svensson, Richard and Olsson, T}},
issn = {{0740-7459}},
keywords = {{requirements engineering; quality requirements; performance requirements; cost-benefit analysis; nonfunctional requirements; roadmapping; trade-off analysis}},
language = {{eng}},
number = {{2}},
pages = {{42--47}},
publisher = {{IEEE - Institute of Electrical and Electronics Engineers Inc.}},
series = {{IEEE Software}},
title = {{Supporting roadmapping of quality requirements}},
url = {{http://dx.doi.org/10.1109/MS.2008.48}},
doi = {{10.1109/MS.2008.48}},
volume = {{25}},
year = {{2008}},
}