-
Notifications
You must be signed in to change notification settings - Fork 8
5.1 Use Case Scenarios
isik5 edited this page May 18, 2017
·
1 revision
Sign up
Use Case | Register |
Actors | User |
Description | User becomes a registered user |
Flow of events | 1. User enters Heritago login Web page URL to their browser’s address bar. User accesses login page, enters e-mail, password and username. Then clicks sign up. |
Login
Use Case | Login |
Actors | User |
Description | User logins to the system |
Flow of events | 1. User enters Heritago login Web page URL to their browser’s address bar. 2. User accesses login page, enters e-mail, password then clicks login. System redirects user to the home page. |
Update profile
Use Case | Update profile |
Actors | User |
Description | User updates profile |
Flow of events | 1. User clicks update profile button in the home page, updates account data and clicks save. |
View portfolio
Use Case | View portfolio page |
Actors | User |
Description | User views portfolio |
Flow of events | 1. User clicks portfolio in the home page, then views all the heritage items he/she created. 2. Also able to edit and delete the items in this page. |
Create heritage item
Use Case | Create heritage item |
Actors | User |
Description | User creates a cultural heritage item |
Flow of events | 1. User goes to the create new item page, enters title, description and origin info. 2. Then clicks multimedia section and add audio, video or image. |
Edit heritage item
Use Case | Edit/delete heritage item |
Actors | User |
Description | User edits heritage item |
Flow of events | 1. User goes to the portfolio. Selects any heritage item, then clicks edit. 2. Afterwards edits any info of the item. |
Delete heritage item
Use Case | Edit/delete heritage item |
Actors | User |
Description | User deletes heritage item |
Flow of events | 1. User goes to the portfolio. 2. Selects any heritage item, then clicks delete. |
Search heritage item by name
Use Case | Search heritage item |
Actors | User |
Description | User searches heritage item |
Flow of events | 1. User goes to the search page and enters a keyword. 2. Then sees the related items which contains the keyword in the title. |
Advanced Search
Use Case | Advanced search heritage item |
Actors | User |
Description | User searches heritage item in advanced search tab |
Flow of events | 1. User goes to the advanced search page and enters user, title, description, tag, origin or time interval and clicks search. 2. Then sees all related items. |
Display multimedia section of item
Use Case | Display item |
Actors | User |
Description | User displays an item |
Flow of events | 1. User searches and finds items in one of the search pages, or goes to portfolio page and find an items. 2. Then clicks one of the items and displays the item. After clicks multimedia section, and sees all multimedia annotations on the item. |
Create annotations in the description
Use Case | Create annotations on the item |
Actors | User |
Description | User creates an annotation |
Flow of events | 1. User clicks to an item, then selects a part of the description text. 2. After, he/she clicks annotate and adds text, or multimedia annotation. |
Create annotations in the multimedia section
Use Case | Create annotations on the item |
Actors | User |
Description | User creates an annotation |
Flow of events | 1. User clicks to an item, then clicks multimedia section. 2. If there is an image, clicks annotate button and selects a part of the image. 3. Then adds the annotation. |
Display annotations on the item
Use Case | Display annotations on the item |
Actors | User |
Description | User displays annotations on the item |
Flow of events | 1. User clicks to an item, then clicks "see all annotations". 2. Then sees all the annotations made for the item, including which users they are created by. |
Filter annotations by user name or date
Use Case | Filter annotations by user name |
Actors | User |
Description | User filters annotations by user name |
Flow of events | 1. User clicks to an item, then clicks "see all annotations". 2. Then clicks filter, and selects users or dates that are available for filtering. 3. System shows only these users or dates if user choose to filter. |
Flag abuses
Use Case | Flag abuses |
Actors | User |
Description | User flag abuses |
Flow of events | 1. User finds an item in the system and sees the annotations. 2. Then he/she finds an inappropriate annotation on the item. 3. Then clicks "Report Abuse" and reports the item. |
Edit abusive content
Use Case | Edit abusive content |
Actors | Moderator |
Description | Edit abusive content |
Flow of events | 1. Moderator of the system sees all the reported items in the admin panel. 2. Then clicks any item and edit its fields. |
Kick out user
Use Case | Kick out user |
Actors | Moderator |
Description | Kick out user |
Flow of events | 1. Moderator of the system sees all the reported items in the admin panel. 2. Then notices that some particular users are reported often. 3. Then goes to user panel and ban that user from the system. |