Extreme programming explained: embrace change
Extreme programming explained: embrace change
Software Requirements
Requirements Engineering: The Emerging Wisdom
IEEE Software
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
Value-based software engineering
ACM SIGSOFT Software Engineering Notes
Software Requirements Prioritizing
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
Conducting Realistic Experiments in Software Engineering
ISESE '02 Proceedings of the 2002 International Symposium on Empirical Software Engineering
Requirements Engineering and Agile Software Development
WETICE '03 Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods
Proceedings of the 26th International Conference on Software Engineering
Practicing What is Preached: 80-20 Rules for Strategic IV&V Assessment
EQUITY '07 Proceedings of the 2007 IEEE International Conference on Exploring Quantifiable IT Yields
Simulating evolution in model-based product line engineering
Information and Software Technology
SimSWE - a library of reusable components for software process simulation
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process
Towards a process for architectural modelling in agile software development
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
A simulation-based fuzzy multi-attribute decision making for prioritizing software requirements
Proceedings of the 1st Annual conference on Research in information technology
A systematic literature review of software requirements prioritization research
Information and Software Technology
| Hi-index | 0.00 |
Agile and traditional plan-based approaches to software system development both agree that prioritizing requirements is an essential activity. They differ in basic strategy - when to prioritize, to what degree, and how to guide implementation. As with many software engineering methods, verifying the benefit of following a particular approach is a challenge. Industry and student/classroom based experimental studies are generally impractical to use for large numbers of controlled experiments and benefits are difficult to measure directly. We use simulation to validate the fundamental, yet typically intangible benefits of requirements prioritization strategies. Our simulation is directly based on detailed empirical studies of agile and plan-based requirements management studies. Our simulation shows, as many have claimed, that an agile strategy excels when requirements are highly volatile, whereas a plan-based strategy excels when requirements are stable, and that there exist mixed strategies that are better than either for typical development efforts.