Abstract

This paper proposes a systematic treatment of NFRs in descriptions of patterns and when applying patterns during design. The approach organizes, analyzes and refines non-functional requirements, and provides guidance and reasoning support when applying patterns during the design of a software system. Three design patterns taken from the literature are used to illustrate this approach. 1. Introduction Requirements Engineering is now widely recognized as a crucial part of software engineering, and has established itself as a distinct research area. Equally important is how requirements drive the rest of software development. In particular, during the design phase, much of the quality aspects of a system are determined. Systems qualities are often expressed as non-functional requirements, also called quality attributes e.g. [1,2]. These are requirements such as reliability, usability, maintainability, cost, development time, and are crucial for system success

Citations