Learn More
  • Eric, Siu-Kwong Yu, C Copyright, Eric Siu-Kwong, Yu, Hector Levesque +16 others
  • 1995
Existing models for describing a process (such as a business process or a software development process) tend to focus on the \what" or the \how" of the process. For example, a health insurance claim process would typically be described in terms of a number of steps for assessing and approving a claim. In trying to improve o r redesign a process, however,(More)
The paper proposes a comprehensive framework for representing and using nonfunctional requirements during the development process. The framework consists of five basic components which provide for the representation of nonfunctional requirements in terms of interrelated goals. Such goals can be refined through refinement methods and can be evaluated in(More)
Quality characteristics are vital for the success of software systems. To remedy the problems inherent in ad hoc development, a framework has been developed to deal with non-functional requirements (quality requirements or NFRs). Taking the premise that the quality of a product depends on the quality of the process that leads from high-level NFRs to the(More)
Non-Functional requirements (or quality requirements, NFRs) such as confidentiality, performance and timeli-ness 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(More)
Non-functional requirements (or Quality Requirements, NFRs) such as conndentiality, 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 \NFR-Framework" which treats NFRs as goals to be achieved during development.(More)