The customer met with management and decided that they would like the system to have the
functionality for the following use case. The customer further decided that they want the project
delivered on the same date as stated in the project plan but is willing to accept the additional
cost.
Use Case ID: DAV002 - Register New Member
Use Case Level: High.
Scenario:
Actor: Actor: DavMovie User.
Pre-conditions:
1) User has internet access and knows the URL of The DavMovie System. User Types
2) URL and sees the login screen on the browser.
Description:
1) The user initiates an action by clicking New Member Button .
2) The system shall display a New Member Information Form including personal
information and billing information.
3) The user shall fill out the form and click submit button.
4) The system shall validate the data including valid credit card numbers.
5) The system shall display the DavMovie Main page if validation is successful.
6) The system shall re-display the New Member Form with error message if there were
errors during validation.
Post-conditions:
1) DavMovie main page is displayed and user can start browsing.
Alternative Courses of Action:
1) Can login if new member form was already filled out.
Extensions:
1) None
Exceptions:
1) Connection is lost during login proccess.
2) DavMovie is down or under construction.
Concurrent Uses: None
Related Use Cases:
1) Search Movies.
2) Add Movie.
3) Delete Movie.
4) Add Admin.
5) Edit Admin.
------------------------------------------------------------------------------------------------------------
Decision Support:
Frequency: Visisting memebers fill the new member form 1 time during the entire
membership. Initially anticipate 100 new users per day.
Criticality: Medium: Visisting users need to complete the new member form and the
system shall validate it before they can start using the system. This is no so
critical since these are not members of the system yet.
Risk: Medium: System is implemented using standard web technology.
Constraints:
Usability: Any user that has access to the internet and has an e-mail address should
be able to understand the login screen since is very similar to e-mail server login
screen. User with expirince with graphical interfaces and know the basic function
of a button and edit box should find the screen intuitive.
Performance: User should see a response after 10 seconds on a worst case scenario.
Reliability: System should be able to handle login request in presence of congestion
and paket lost conditions.
------------------------------------------------------------------------------------------------------------
Modification History
Owner: David Peraza – Team 3
Initiation date: 01/27/04
Date last modified: 01/31/04