An evaluation of the utility of web development methods

Abstract

Although many web development methods exist, they are rarely used by practitioners. The work reported here, seeks to explain why this might be so, and suggests that, for many, the perceived benefits may be outweighed by the difficulty or effort required to learn the method. In attempting to gauge the utility of methods the authors undertook a 2-year study of 23 small web development projects, attempting to use a range of published (academic) methods. Of the 23 projects we found only one case where the developer continued to use an academic web development method throughout the lifecycle. The ability to understand a method and/or its techniques was repeatedly cited as the reason for its abandonment. Our findings also indicate a number of key areas, relating to terminology, completeness, and guidance, where existing methods may be failing their intended users. In attempting to further our understanding of web development methods we completed a comprehensive survey of web development methods; covering 52 web development methods, encompassing a range of different research communities, and drawing upon 63 different sources. Our findings here shed some light upon the confusion of methods for the would-be user. In summary, the findings are that, although there is much of value in a variety of methods, method choice is somewhat bewildering for the newcomer to the field, and many methods are incomplete in some dimension. By providing this work we hope to go some way towards supporting the software engineering community, in both academia and industry, in their understanding of the quality issues that exist with the take up and use of web development methods.

A requirements framework for novice web developers

“…As previously reported, web development methods are difficult to use for novice developers [4] however, a number of the students identified with two elements of WSDM [23] that the students believed could be used to good effect in any method. The framework is shown at Figure1.…”

“…We have previously divided these differences into three areas [4]: the user domain, the developer and development team domain and finally, the environment. The user domain is of particular interest to the requirements engineer because the web at the interface is of primary importance to the user and is an area where there are a number of differences.…”

Fagan Inspection: A Defects Finding Mechanism in Software Requirements Specification (SRS) Document

“…He and his team conducted a case study. They concluded that the introduction and need of Fagan inspection technique have a lot of importance as well as benefits [7]. After that a researcher Ferreira focused that software inspection finds and removes only those defects that are close to the injection point.…”