Requirements evolution: From assumptions to reality

Raian Ali*, Fabiano Dalpiaz, Paolo Giorgini, Vítor E.Silva Souza

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

22 Citations (Scopus)

Abstract

Requirements evolution is a main driver for systems evolution. Traditionally, requirements evolution is associated to changes in the users' needs and environments. In this paper, we explore another cause for requirements evolution: assumptions. Requirements engineers often make assumptions stating, for example, that satisfying certain sub-requirements and/or correctly executing certain system functionalities would lead to reach a certain requirement. However, assumptions might be, or eventually become, invalid. We outline an approach to monitor, at runtime, the assumptions in a requirements model and to evolve the model to reflect the validity level of such assumptions. We introduce two types of requirements evolution: autonomic (which evolves the priorities of system alternatives based on their success/failure in meeting requirements) and designer-supported (which detects loci in the requirements model containing invalid assumptions and recommends designers to take evolutionary actions).

Original languageEnglish
Title of host publicationEnterprise, Business-Process and Information Systems Modeling - 12th International Conference, BPMDS 2011 and 16th International Conference, EMMSAD 2011 held at CAiSE 2011, Proceedings
PublisherSpringer Verlag
Pages372-382
Number of pages11
ISBN (Print)9783642217586
DOIs
Publication statusPublished - 2011
Externally publishedYes

Publication series

NameLecture Notes in Business Information Processing
Volume81 LNBIP
ISSN (Print)1865-1348

Keywords

  • Contextual Requirements
  • Requirements Engineering
  • Requirements Evolution
  • Requirements at Runtime

Fingerprint

Dive into the research topics of 'Requirements evolution: From assumptions to reality'. Together they form a unique fingerprint.

Cite this