Primary Actor : Web User
(Primary actor : User who will be using the system primarily)
Secondary Actor : None
(Secondary actor: User who will be using the system rarely)
Starting Point : Music categories are displayed
(Starting point for this use case)
Ending Point : Music Albums based on the selected categories and general search condition are displayed.
(Ending point for this use case).
Measurable Result: Required albums are displayed
Flow of Events: This use case is started when user visits the online music store. The user will be selecting the categories from the drop down list box and enters the general search criteria like “ Artist Name” “ Album Format” “ Etc. etc.”
Based on the entered criteria all the suitable albums will be displayed.
Alternate flow of events: If no matches are found for the selected category and the general search criteria then helpful hints will be displayed.
Primary Actor : Web User
(Primary actor : User who will be using the system primarily)
Secondary Actor : None
(Secondary actor: User who will be using the system rarely)
Starting Point : The web user should login with a valid userid and password or else he is given the option of creating a useraccount.
Ending Point : Selected music albums are purchased.
Measurable Result: Selected albums are purchased.
Flow of Events: The user is asked to login using valid useraccount or else he is given an option of creating a new account.
The user can select the required albums and add to cart and is given the option to review his selected albums.
User is asked to enter the payment information and the shipping information.
Alternate flow of events: If the albums are out of stock the required message will be displayed. If the payment method operation fails the required message will be displayed.
Primary Actor : Web User
(Primary actor : User who will be using the system primarily)
Secondary Actor : None
(Secondary actor: User who will be using the system rarely)
Starting Point : User will be prompted for userid and password of his choice.
Ending Point : The user account will be accepted as a valid user or rejected if it already exists in the system.
Measurable Result: Valid userid is created or rejected.
Flow of Events: This use case is started when users are prompted for valid useraccount .
User will enter user id and password and a check is made to see whether the userid is unique if not he will be prompted to enter another userid.
Alternate flow of events: Necessary hints are displayed.
Outstanding Issues: UserId must be minimun 6 characters and password must be 10 characters.