D5.1-Appendix E - Other Use Cases

From EChase
Jump to: navigation, search

Back to D5.1 System Specification

Content User searches for a content[edit]

Use Case Name: Content User searches for a content
Description: Content User wants to retrieve a specific content using the eChase search and retrieval engine. Such contents may be searched via eChase metadata repository and downloaded from Content Provider web sites.
Actors:
  1. Content User— An existing Content User
  2. Content Provider – One or more existing Content Providers
Preconditions: none
Triggers: The Content User uses the eChase search and retrieval engine for identifying specific content owned by Content Providers
Basic Course of Events:
  1. The Content User authenticates himself.
  2. The Content User accesses the eChase Search and Retrieval Tool.
  3. The Content User finds some specific content in a list.
  4. The Content User chooses one or more items from the list.
  5. The Content Users is redirected to the eChase Content Provider item page and the Content Download Use Case is invoked.
Exceptions: None
Postconditions: None
Open points: What if there is no content provider website to download from?

Content Aggregator creates a content product[edit]

Use Case Name: Content Aggregator creates content into the eChase system.
Description: Content Aggregator creates content into the eChase system using the appropriate tools. Content, searched and retrieved through eChase platform being re-arranged, commented out and represented to users in a new look
Actors:
  1. Content Aggregator— An existing Content aggregator
Preconditions:
  1. The eChase System has some contents available for aggregation.
Triggers: The Content Aggregator uses the eChase Content Aggregator set of tools for aggregation of basic contents
Basic Course of Events:
  1. The Content Aggregator authenticates himself.
  2. The Content Aggregator accesses the eChase appropriate tool.
  3. The Content Aggregator selects some specific content using eChase search engine and download the content in the eChase repository
  4. The Content Aggregator manipulates the basic content adding/modifying and creating a new "Product"
  5. According to the workflow the product is passed (changing state) to the next level of appointment/approval
  6. The Content Aggregator publishes the new product into the eChase product display
Exceptions: none
Postconditions: none

Content Provider uploads content to eChase[edit]

Use Case Name: Content Provider uploads content to eChase
Description: A Content Provider uploads content into eChase repository. The content could be: metadata, pictures, data, text, multimedia files etc.
Actors:
  1. Content Provider— An existing Content owner or provider
Preconditions:
  1. The Content Provider has a valid eChase account.
Triggers: The Content Provider wants to update eChase repository with his own data.
Basic Course of Events:
  1. The Content Provider authenticates himself.
  2. The Content Provider selects the type of data he wants to insert/update from the relative interface mask.
  3. The Content Provider performs an HTTP Upload of the selected data.
  4. The eChase system receives and stores/updates the data.
  5. The Content Provider being informed about the transaction status.
Exceptions: none
Postconditions: none

A new Content User creates an eChase account[edit]

Use Case Name: A new Content User creates an eChase account
Description: A web user wants to register to the eChase System. He accesses the eChase web site and he clicks on the "New User" button link. He fills the registration form supplying the required information and clicks the "ok" button
Actors:
  • Web Users
  • User Management Subsystem

Triggers:

A web user accesses to the eChase System.
Preconditions: none
Basic Course of Events:
  1. The user clicks on the "New User" button link of the eChase Web Site
  2. The system displays the "New User Form" to the user.
  3. The user fills in all the required fields of the form
  4. The user confirms the data he inserted by clicking the "ok" button
  5. The system notifies the user that data was received, the membership application will be processed and a password for accessing the system will be shortly sent to the user via eMail.
Exceptions: The user entered a non valid or non existent eMail address
Post conditions:
  • A new user account is created into the eChase System (Users repository Subsystem)
  • An eMail message is sent to the new user with a temporary password for accessing the system.
Business Rules: none
Technical Requirements: none

Back to D5.1 System Specification

Retrieved from "http://echase.ecs.soton.ac.uk/index.php?title=D5.1-Appendix_E_-_Other_Use_Cases&oldid=1550"