Introducing Non-functional Requirements in UML

Introducing Non-functional Requirements in UML

Guadalupe Salazar-Zarate (Technical University of Catalonia, Spain), Pere Botella (Technical University of Catalonia, Spain) and Ajantha Dahanayake (Delft University of Technology, The Netherlands)
Copyright: © 2003 |Pages: 13
DOI: 10.4018/978-1-93177-744-5.ch007
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

This chapter introduces an approach concerned with the non-functional features of software systems. The specific objectives of the research focus on the possibility of developing mechanisms to capture non-functional information in the development of software systems in a similar manner to its counterpart, the functional information. Particularly, the research described in this chapter focuses on the possible extension of the Unified Modeling Language (UML) (Booch et al., 1998). In order to get an initial specification of some non-functional requirements, the Software Quality Standard ISO/IEC 9126 (International Standard, 1991) is used. The language NoFun (Botella et al., 2001) is the basis used to achieve some organization about the non-functional concepts used in this approach.

Complete Chapter List

Search this Book:
Reset