The impacts of non-functional requirements in web system projects

Yusop, N; Zowghi, D; Lowe, D

The impacts of non-functional requirements in web system projects

Yusop, N Zowghi, D

Lowe, D

Permalink

Publication Type:: Journal Article
Citation:: International Journal of Value Chain Management, 2008, 2 (1), pp. 18 - 32
Issue Date:: 2008-08-18

Open Access

Copyright Clearance Process

Recently Added
In Progress
Open Access

This item is open access.

Adobe PDF

Download full textAdobe PDF (206.81 kB)

View on publisher's site

View statistics

Full metadata record

Field	Value	Language
dc.contributor.author	Yusop, N	en_US
dc.contributor.author	Zowghi, D https://orcid.org/0000-0002-6051-0155	en_US
dc.contributor.author	Lowe, D	en_US
dc.date.issued	2008-08-18	en_US
dc.identifier.citation	International Journal of Value Chain Management, 2008, 2 (1), pp. 18 - 32	en_US
dc.identifier.issn	1741-5357	en_US
dc.identifier.uri	http://hdl.handle.net/10453/10267
dc.description.abstract	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.	en_US
dc.relation.ispartof	International Journal of Value Chain Management	en_US
dc.relation.isbasedon	10.1504/IJVCM.2008.016116	en_US
dc.subject.classification	Business & Management	en_US
dc.title	The impacts of non-functional requirements in web system projects	en_US
dc.type	Journal Article
utslib.citation.volume	1	en_US
utslib.citation.volume	2	en_US
utslib.for	1503 Business and Management	en_US
utslib.for	1402 Applied Economics	en_US
utslib.for	1505 Marketing	en_US
pubs.embargo.period	Not known	en_US
pubs.organisational-group	/University of Technology Sydney
pubs.organisational-group	/University of Technology Sydney/DVC (Research)
pubs.organisational-group	/University of Technology Sydney/DVC (Research)/Graduate Research School
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology/School of Electrical and Data Engineering
pubs.organisational-group	/University of Technology Sydney/Strength - HCTD - Human Centred Technology Design
pubs.organisational-group	/University of Technology Sydney/Strength - STEM Education Futures
utslib.copyright.status	open_access
pubs.issue	1	en_US
pubs.publication-status	Published	en_US
pubs.volume	2	en_US

Abstract:

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:

http://hdl.handle.net/10453/10267