The Community for Technology Leaders
Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95) (1995)
York, England
Mar. 27, 1995 to Mar. 29, 1995
ISBN: 0-8186-7017-7
pp: 132
L. Chung , Comput. Sci. Program, Texas Univ., Dallas, TX, USA
B.A. Nixon , Comput. Sci. Program, Texas Univ., Dallas, TX, USA
E. Yu , Comput. Sci. Program, Texas Univ., Dallas, TX, USA
ABSTRACT
Non-functional requirements (or quality requirements, NFRs) such as confidentiality, performance and timeliness are often crucial to a software system. Our NFR-framework 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 a 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.
INDEX TERMS
Barclays Bank; banking; systems analysis; software engineering; software quality; management of change; formal specification; nonfunctional requirements; systematic change support; quality requirement; confidentiality; performance; timeliness; software system; system development; design tradeoffs; goal decomposition; design decisions; goal achievement; historical record; development process; evolution; banking policies; Barclays Bank
CITATION

E. Yu, B. Nixon and L. Chung, "Using non-functional requirements to systematically support change," Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)(RE), York, England, 1995, pp. 132.
doi:10.1109/ISRE.1995.512554
93 ms
(Ver 3.3 (11022016))