Sunday, February 27, 2011

Group Work: Use Cases

1)
Functional: Users log in, Users can view their details, Users can view their account balance, users can delete their account, users can send gift vouchers, users and visitors can browse the catalogue by genre - price or alphabetical, admin staff may log in to the administration area, admin staff may bpdate any catalogue information, users may apply for a refund.

Non-Functional: Attract new users, uses can view their purchase history, users can edit their details, users can purchase more credit, users and visitors can browse the entire catalogue, users may purchasr and download catalogue items, users and visitors may sign up for a weekly newsletter, admin staff may apply refunds to user accounts, the service should support PC and Mobile devices, the service should be online 24/7 and 365 days a year, the interface should contain groovy web 2.0 elements.

2)
Must Have: Users can login, users can view their details, Admin staff may log in to the admin area, admin staff may update any catalogue information, the service should be online 24/7 365 days a year.

Should Have: Attract new users, users can edit their details, usres and visitors can browse the entire catalogue, users and visitors can browse the catalogue by genre price or alphabetically, admin staff may apply refunds to user accounts, the service should support PC and Mobile devices, the interface should contain groovy web 2.0 elements.

Could Have: Users can view their purchase history, users can purchase more credit, users may purchase and dowload catalogue items, users and visitor may sign up for a weekly newsletter.

Want to Have: users can view their account balance, users can delete their account, users can send gift vouchers, Users may apply for a refund.

3)
Identify key concepts:
-Log in
-View Details
-Account balance
-purchase history
-edit details
-delete account
-purchase more credit
-gift vouchers
-browse catalogue
-browse genre, price or alphabetical
-purchase and dowload items
-weekly newsletter
-admin area
-update catalogue info
-apply refunds
-appling for refunds
- PC and mobile
-online 24/7 365 days
-web 2.0
Initial model:
4)
5)
Use case name: Buying an item online
Actors: Visitor
Start page: Home Page
Use case descritpion:
1. The actor clicks on browse catalogue
2. The actor browses by alphabetical
3. The actor chooses a product
4. The actor proceeds to purchase the item.
5. The site shows the result of his purchase.

No comments:

Post a Comment