@neilernst

Dealing with change: An approach using non-functional requirements

, , and . Requirements Engineering, 1 (4): 238--260 (December 1996)
DOI: 10.1007/BF01587102

Abstract

Non-functional requirements (or quality requirements, NFRs) such as confidentiality, performance and timeliness are often crucial to a software system. Concerns for such NFRs are often the impetus for change. To systematically support system evolution, this paper adapts the lsquoNFR Frameworkrsquo, which treats NFRs as goals to be achieved during development. Throughout the process, consideration of design alternatives, analysis of trade-offs and rationalisation of design decisions are all carried out in relation to the stated goals, and captured in historical records. We show how such historical records of treating NFRs as goals also system-atically support system evolution. This approach is illustrated by a study of changes in loan policies at Barclays Bank. The study considered changes in NFRs, and associated changes in priorities, workload and functionality. The study's historical records helped quickly determine the impact of changes. We also present guidelines for consistently managing historical records, and address tool support for the change process. This is an extended and revised edition of a paper 34 appearing in theProceedings of the Second International Symposium on Requirements Engineering. York, England, March 1995. A draft of that paper was prepared when all three authors were at the Department of Computer Science, University of Toronto.

Description

also see http://citeseer.ist.psu.edu/chung97dealing.html

Links and resources

Tags

community

  • @lei
  • @neilernst
  • @dblp
  • @mstrohm
@neilernst's tags highlighted