|The analysis of a potential Web application focuses on three important questions: (1) what information or content is to be presented or manipulated; (2) what functions are to be performed for the end-user, and (3) what behaviors will the WebApp exhibit as it presents content and performs functions? The answers to these questions are represented as part of an analysis model that encompasses a variety of UML representations.|
|The following topic categories are presented:
And why you should not believe them.
"This document describes a set of requirements for a standard reference architecture for Web Services developed by the Web Services Architecture Working Group."
20 links that discuss usability and related subjects.
This site contains many useful links that are relevant to WebApps and conventional software
A paper that describes "new conceptual tools for effectively supporting the activity of requirements analysis of web applications.
A paper that describes a prototyping like approach for requirements gathering.
The authors of thisa paper argue "that a shift of paradigm is needed in web engineering from task-oriented to goal-oriented approaches ..."
A paper by Michael Beiber.
A brief discussion of WebApp prototypes with useful links.
The paper "shows how the well-known entity-relationship (E-R) modeling technique can be exploited when creating the middle tier in a 3-tier web application."
"Both designers and developers need a framework that in all stages of the engineering process allows them to specify the relevant aspects of the application. This paper concentrates on Web applications that automatically generate hypermedia presentations for their output."
Many books dedicated to analysis modeling for conventional softwarewith particular emphasis on use-cases and UML notationcontain much useful information that can be readily adapted by Web engineers. Use-cases form the foundation of analysis modeling for WebApps. Books by Kulak and his colleagues (Use Cases: Requirements in Context, second edition, Addison-Wesley, 2004), Bittner and Spence (Use Case Modeling, Addison-Wesley, 2002), Cockburn ((Writing Effective Use Cases, Addison-Wesley, 2001)), Armour and Miller (Advanced Use-Case Modeling: Software Systems, Addison-Wesley, 2000), Rosenberg and Scott (Use Case Driven Object Modeling with UML: A Practical Approach, Addison-Wesley, 1999), and Schneider, Winters, and Jacobson (Applying Use Cases: A Practical Guide, Addison-Wesley, 1998) provide worthwhile guidance in the creation and use of this important requirements representation mechanism.