In this issue, Roger Pressman champions the use of engineering and project management processes to build and maintain web-based applications. Before you start building it, you'd better understand the problem from the user's point of view, design a workable solution, implement it in a solid way, and test it thoroughly. You should also use solid project management techniques, control changes as you work, and have some mechanism for ensuring the end result's quality. Of course, there is another view. I contend that software engineering principles always work.
History is on the side of a solid engineering approach.
It is populated by a set of framework activities that occur for all business-critical WebApp projects, regardless of the size or complexity. Planning - estimates overall project cost, evaluates risks, and defines a development schedule for the initial WebApp increment. Analysis - establishes requirements for the WebApp and identifies the content that will be incorporated. Content design involves the creation or acquisition of content for the WebApp. User interface design involves defining the architecture, navigation, and graphic design which establish the structure of the WebApp and the flow of the user's interaction with it.