An examination of the effects of requirements changes on software maintenance releases
Journal of Software Maintenance: Research and Practice
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Introduction to Algorithms
Optimizing Value and Cost in Requirements Analysis
IEEE Software
Change Analysis: A Step towards Meeting the Challenge of Changing Requirements
ECBS '96 Proceedings of the IEEE Symposium and Workshop on Engineering of Computer Based Systems
Software Requirements
Continual Resource Estimation for Evolving Software
ICSM '03 Proceedings of the International Conference on Software Maintenance
Empirical Studies on Requirement Management Measures
Proceedings of the 26th International Conference on Software Engineering
The Art and Science of Software Release Planning
IEEE Software
Lightweight Replanning of Software Product Releases
IWSPM '06 Proceedings of the International Workshop on Software Product Management
Software product release planning through optimization and what-if analysis
Information and Software Technology
Supporting Roadmapping of Quality Requirements
IEEE Software
Optimized Resource Allocation for Software Release Planning
IEEE Transactions on Software Engineering
Application of re-estimation in re-planning of software product releases
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process
Hi-index | 0.00 |
Volatility of features and dynamic change in stakeholders' needs often requires re-planning of an existing release plan to accommodate changes. H2W is a re-planning method that answers the questions of how, when, and what to re-plan of an existing product release strategy. For HOW, a greedy heuristic based on prioritization of candidate features is applied. A value-based re-planning approach is proposed for the WHEN question. For WHAT, a trade-off analysis between the degree of change related to the originally announced release plan and the improvement achievable by replacing existing features with more attractive ones is suggested. At each of the re-planning iterations, H2W either provides a new improved plan or states that an improvement does not exist. As a proof-of-concept, a case study is conducted.