The How? When? and What? for the Process of Re-planning for Product Releases
ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
A systematic review on strategic release planning models
Information and Software Technology
The agile requirements refinery: Applying SCRUM principles to software product management
Information and Software Technology
Proceedings of the 11th International Conference on Product Focused Software
Software quality trade-offs: A systematic map
Information and Software Technology
Release planning with feature trees: industrial case
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
Improving software product management: a knowledge management approach
International Journal of Business Information Systems
Software quality across borders: Three case studies on company internal alignment
Information and Software Technology
| Hi-index | 0.00 |
When dealing with quality requirements, 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. Our experience from the mobile-phone domain shows that much can be gained if development team members share a common framework of quality indicators and have a simple, easy-to-use model for reasoning about quality targets. To support quality-requirements analysis, the Quper (quality performance) model combines cost and benefit views into a roadmap of each important quality indicator for the particular domain. The practical application of Quper involves six steps. This article is part of a special issue on quality requirements.