The other skills of the software architect
Proceedings of the first international workshop on Leadership and management in software architecture
A UML Profile for Modelling Measurable Requirements
ER '08 Proceedings of the ER 2008 Workshops (CMLSA, ECDM, FP-UML, M2AS, RIGiM, SeCoGIS, WISM) on Advances in Conceptual Modeling: Challenges and Opportunities
Spectrum Analysis for Quality Requirements by Using a Term-Characteristics Map
CAiSE '09 Proceedings of the 21st International Conference on Advanced Information Systems Engineering
1st international requirements engineering efficiency workshop: REEW 2011
ACM SIGSOFT Software Engineering Notes
On Context Modelling in Systems and Applications Development
Proceedings of the 2011 conference on Information Modelling and Knowledge Bases XXII
The brave new world of design requirements
Information Systems
Eliciting user requirements using Appreciative inquiry
Empirical Software Engineering
Managing implicit requirements using semantic case-based reasoning research preview
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
RCDA: Architecting as a risk- and cost management discipline
Journal of Systems and Software
Monitoring system-of-systems requirements in multi product lines
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
| Hi-index | 0.00 |
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.