Analysis Document

This section describes the team project's analysis document, which includes a:

Statement of objective
Domain analysis
Statement of requirements
Set of use cases

This section serves as an executive summary of the proposed application.

It should clearly and distinctly describe:

The purpose: what is the application trying to achieve?
If the application solves an existing problem, what exactly is that problem?
If the application fills a need, what exactly is that need?
If the application takes advantage of an opportunity, what exactly is that opportunity?
Anything else that helps to justify this project's undertaking

The domain is the general field of business or technology in which your clients will use your web application.

Domain analysis is the process by which your team learns about the domain to better understand (i) the problem you are solving, or (ii) the need you are filling, or (iii) the opportunity you are exploiting.

Proper domain analysis is required to insure:

Faster development
Higher quality system
Anticipation of extensions

General knowledge about the domain beyond the statement of objective.
Glossary of terms specific to the domain whose definition is required by non-experts to understand the domain
Characterization of the users and customers within the domain
Description of the domain's business, social, cultural, or technological environment in which it is placed, and which is necessary to understand the proposed application
Description of the tasks and procedures currently performed in this environment

A requirement is a relatively short and concise piece of information, expressed as a fact.
It should be stated in present tense and active voice. For example, a requirement for an e-commerce application could be:
The system will support payment using credit cards, debit cards, or Paypal.
It must be clear, consistent, and unambiguous. For example, an e-commerce requirement like
The system will display secure operation.
is too general and vague. What kind of operation is involved and what does "secure" mean? A better requirement would be
Transaction summaries will only show the last 4 digits of the user's credit card number.
Each requirement should be numbered and presented in a list so that it can be uniquely identified.

Develop a set of use cases for all of the important user interaction scenarios envisioned for your application.

Use the format described in CS 2511: Voice Mail System Use Cases

Each use case should be given a name, and use case inclusion relationships should be indicated where appropriate.

The analysis document will be graded based on:

Completeness
Clarity
English grammar and style

The document must be formatted using PDF and given the name: team-n-analysis.pdf
where n is your team number.

The document is due by 8:00 p.m. on the day indicated on the Term Schedule using Web Drop.