The impacts of non-functional requirements in web system projects

Publication Type:
Journal Article
International Journal of Value Chain Management, 2008, 2 (1), pp. 18 - 32
Issue Date:
Full metadata record
Files in This Item:
Filename Description Size
Thumbnail2007002839.pdf206.81 kB
Adobe PDF
In web system development, the Non-Functional Requirements (NFRs) are typically considered only briefly during the requirements elicitation stage and not rigorously articulated by either web developers or the client. This paper reports on an investigation into this issue involving interviews with web developers who were engaged in commercial web development projects. The results from this qualitative research highlight that web developers commonly do not pay sufficient attention to NFRs. This arises due to uncertainty, lack of time, lack of knowledge in the importance of NFRs and partly because NFRs are not readily available and documented from previous similar projects. Web developers also do not elicit NFR at the same time and at the same level of details as Functional Requirements (FRs). This study highlights that exploring the domain at an early stage of development will help developers to better understand NFR. A lack of rigour in articulating NFRs may significantly impact on the development effectiveness and the quality of the resulting web system. An evaluation of NFRs may also lead to discovering new FRs. © Copyright 2008, Inderscience Publishers.
Please use this identifier to cite or link to this item: