
Quality requirements, i.e. those requirements that pertain to a system's quality attributes, are traditionally regarded to be useful only when they are represented quantitatively so that they can be measured. This article presents a value-oriented approach to specifying quality requirements that deviates from the classic approach. This approach uses a broad range of potential representations that are selected on the basis of risk assessment. Requirements engineers select a quality requirement representation such that they get an optimal balance between mitigating the risk of developing a system that doesn't satisfy the stakeholders' desires and needs on the one hand and the cost of specifying the requirement in the selected representation on the other hand. This issue is part of a special issue on quality requirements.
1712 Software, 10009 Department of Informatics, 000 Computer science, knowledge & systems, 000 Computer science, knowledge & systems
1712 Software, 10009 Department of Informatics, 000 Computer science, knowledge & systems, 000 Computer science, knowledge & systems
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 35 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Top 10% | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Top 10% |
