Understanding the Dynamics of Requirements Evolution: A Comparative Case Study of Groupware Implementation.

This paper presents a conceptual framework that seeks to explain the dynamics of requirements change and evolution. As an initial validation of the framework, it was used to analyze two contrasting cases of groupware implementation. The framework makes a distinction between, on the one hand, requirements as problem definition and as solution specification, and, on the other hand, business requirements and software requirements. This distinction yields four different requirement domains. Changes in requirements can be triggered by breakdowns in any of these domains or by technology-driven initiatives. Requirements evolution, then, is the resolution of these breakdowns and the enactment of initiatives. An increased understanding of the dynamics of requirements evolution can be beneficial for structuring and managing a groupware implementation project and, more importantly, software maintenance in the post-deployment phase of a system.