Supporting roadmapping of quality requirements

Björn Regnell, Richard Berntsson Svensson, T Olsson

Research output: Contribution to journalArticlepeer-review

58 Citations (SciVal)


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
Original languageEnglish
Pages (from-to)42-47
JournalIEEE Software
Issue number2
Publication statusPublished - 2008

Subject classification (UKÄ)

  • Computer Science


  • requirements engineering
  • quality requirements
  • performance requirements
  • cost-benefit analysis
  • nonfunctional requirements
  • roadmapping
  • trade-off analysis


Dive into the research topics of 'Supporting roadmapping of quality requirements'. Together they form a unique fingerprint.

Cite this