A Framework for Integrating Non-Functional Requirements into Conceptual Models

Abstract

The development of complex information systems calls for conceptual models that describe aspects beyond entities and activities. In particular, recent research has pointed out that conceptual models need to model goals, in order to capture the intentions which underlie complex situations within an organisational context. This paper focuses on one class of goals, namely nonfunctional requirements (NFR), which need to be captured and analysed from the very early phases of the software development process. The paper presents a framework for integrating NFRs into the ER and OO models. This framework has been validated by two case studies, one of which is very large. The results of the case studies suggest that goal modelling during early phases can lead to a more productive and complete modelling activity.

Dimensions of Business Processes Quality (QoBP)

“…The essential characteristic of a quality requirement is that it can be achieved in different degrees. These quality requirements do not directly relate to functionality in the process, but to conditions and constraints that should prevail [21]. While there has been some work on isolated aspects of quality, there is currently no quality model for business processes available.…”

Cost-Informed Operational Process Support

“…Researchers have explored how these requirements can be elicited from users and how to incorporate NFRs in conceptual models [2,5,11,13]. However, the cost perspective has a very close and direct link with BPM/WfM, much more so than most other NFRs.…”

Non-Functional Requirements Elicitation and Incorporation into Class Diagrams

“…However, non-functional requirements (NFRs) have an important effect on system quality and development costs. The well-known case of the London Ambulance System (LAS) is a good example [1]. The LAS was deactivated, because of several problems related to non-functional requirements.…”

“…However, it does not mean that software engineers cannot consider information about non-functional requirements [1]. Moreover, NFRs are always linked to functional requirements (FRs).…”