The impacts of non-functional requirements in web system projects

Publication Type:
Conference Proceeding
Citation:
Proceedings of the European and Mediterranean Conference on Information Systems, EMCIS 2006, 2006
Issue Date:
2006-12-01
Full metadata record
Files in This Item:
Filename Description Size
Thumbnail2006004781.pdf1.2 MB
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 a lack of rigor in articulating NFRs may significantly impact on the development effectiveness and the quality of the resulting Web system.
Please use this identifier to cite or link to this item: