Using non-functional requirements to systematically support change

Non-Functional requirements (or quality requirements, NFRs) such as confidentiality, performance and timeliness are often crucial to a software system. Our NFRFramework treats NFRs as goals to be achieved during the process of system development. Throughout the process, goals are decomposed, design tradeoffs are analysed, design decisions are rationalised, and goal achievement is evaluated. This paper shows how an historical record of the treatment of NFRs during the development process can also serve to systematically support evolution of the software system. We treat changes in terms of (i) adding or modifying NFRs, or changing their importance, and (ii) changes in design decisions or design rationale. This incremental approach is illustrated by a study of changes in banking policies at Barclays Bank.

• Type: Conference
• Year: 1995
• Where: RE
• Authors: Lawrence Chung, Brian A. Nixon, Eric S. K. Yu
• Keywords: Design Decisions, Nfrframework Treats Nfrs, RE 1995, Software Engineering, Software System