Elicitation and Modeling Non-Functional Requirements – A POS Case Study

Abstract

Proper management of requirements is crucial to successful development\nsoftware within limited time and cost. Nonfunctional requirements (NFR) are one\nof the key criteria to derive a comparison among various software systems. In\nmost of software development NFR have be specified as an additional requirement\nof software. NFRs such as performance, reliability, maintainability, security,\naccuracy etc. have to be considered at the early stage of software development\nas functional requirement (FR). However, identifying NFR is not an easy task.\nAlthough there are well developed techniques for eliciting functional\nrequirement, there is a lack of elicitation mechanism for NFR and there is no\nproper consensus regarding NFR elicitation techniques. Eliciting NFRs are\nconsidered to be one of the challenging jobs in requirement analysis. This\npaper proposes a UML use case based questionary approach to identifying and\nclassifying NFR of a system. The proposed approach is illustrated by using a\nPoint of Sale (POS) case study\n