Requirements evolution drives software evolution

8Citations
Citations of this article
43Readers
Mendeley users who have this article in their library.
Get full text

Abstract

Changes to software should be made with reference to the requirements of that software, as these requirements provide the reasons for a change. Requirements serve to tie the implementation world of the developers to the problem world of the stakeholders. Most empirical studies of requirements have shown that misunderstood and changing requirements cause the majority of failures and costs in software. However, research in software evolution has typically focused on how to evolve software and not why. In our view, evolving software is about solving requirements problems, that is, finding new implementations which will satisfy the requirements while respecting domain assumptions. We argue that by describing this relationship, an implementation choice that best meets stakeholder needs can be made. We describe a tool that models requirements problems. This tool can find incremental solutions to evolving requirements problems quickly. © 2011 ACM.

Cite

CITATION STYLE

APA

Ernst, N. A., Borgida, A., & Mylopoulos, J. (2011). Requirements evolution drives software evolution. In IWPSE-EVOL’11 - Proceedings of the 12th International Workshop on Principles on Software Evolution (pp. 16–20). https://doi.org/10.1145/2024445.2024450

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free