Predicting good requirements for in-house development projects
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Quantifying requirements volatility effects
Science of Computer Programming
The impact of requirements changes on specifications and state machines
Software—Practice & Experience
A holistic approach to managing software change impact
Journal of Systems and Software
Computers and Electronics in Agriculture
Public process management: a method for introducing standard business reporting
Proceedings of the 12th Annual International Digital Government Research Conference: Digital Government Innovation in Challenging Times
Controversy Corner: Improving test efficiency through system test prioritization
Journal of Systems and Software
Timeboxing: a process model for iterative software development
Journal of Systems and Software
V:ISSUE:LIZER: exploring requirements clarification in online communication over time
Proceedings of the 2013 International Conference on Software Engineering
Hi-index | 4.10 |
One of the most chronic problems in software development is the fact that application requirements are almost never stable and fixed. Frequent changes in requirements are not always caused by capricious clients (although sometimes they are). The root cause of requirements volatility is that many applications are attempting to automate domains that are only partly understood. As software design and development proceeds, the process of automation begins to expose these ill-defined situations. Therefore, although creeping requirements are troublesome, they are often a technical necessity. Several threads of research and some emerging technologies are aimed at either clarifying requirements earlier in development or minimizing the disruptive effect of changing requirements later