RocReadaR : Use Cases - RocReadaR Portal

Log In
DescriptionUser logs in to portal
ActorsUser, RocReadaR Portal
Pre-ConditionsUser has an account
Post-ConditionsUser becomes authenticated with the application
Main Flow
  1. User enters account name
  2. User enters password
  3. User clicks “Log In” button
Alternate Flows
  1. User enters account name
  2. User enters password
  3. User clicks “Log In” button
  4. Account and password are rejected for being incorrect
  5. Repeat steps 1-3
 Exceptions 
Log Out
DescriptionUser logs out of portal
ActorsUser, RocReadaR Portal
Pre-Conditions

User has an account

User is logged in

Post-ConditionsUser becomes logged out of the system
Main Flow
  1. User clicks log out button
  2. User is notified he/she has been logged out
Alternate Flows

 

 Exceptions 
Create User
DescriptionUser creates an account for another user
ActorsUser, RocReadaR Portal
Pre-Conditions

User has an account

User is logged in

User has permissions to create another user

Post-ConditionsNew user becomes created
Main Flow
  1. User navigates to users management page
  2. User enters a user role, username, email and password
  3. If the entered role is a publisher, User selects a Publisher
  4. If the entered role is an advertiser, User selects an Advertiser
  5. User clicks create
Alternate Flows

 

 Exceptions 
Publisher Creates Publication
DescriptionPublisher creates a publication
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Post-ConditionsPublication is created for the publisher
Main Flow
  1. Publisher navigates to the publications page
  2. Publisher clicks “Add Publication” button
  3. Publisher enters Publication title
  4. Publisher is prompted for an image file
  5. Publisher supplies image file
  6. Publisher clicks upload
  7. Image is uploaded to server
  8. Publication is updated in web browser with image and title
Alternate Flows

 

 Exceptions 
Publisher Creates Publication Issue
DescriptionPublisher creates a publication issue, and adds details and page recognition images to that issue
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Post-ConditionsPublication Issue is created for the publisher
Main Flow
  1. Publisher navigates to the publication page for the issue that is being created
  2. Publisher clicks “Add Issue” button
  3. Publisher enters issue details (Name, Year, Month, Number, etc.)
  4. Publisher clicks "create" button
  5. Publisher is prompted to upload the image files for the issue
    1. by browsing and selecting local files
    2. or by dragging a folder into the visible area
  6. System performs the “add page to issue” use case on each valid file
    1. The system will provide a notification if any files are invalid
  7. The system will prompt the Publisher to ask if they wish to add any advertisers to this issue, which the Publisher may do at this point.
  8. The portal displays the "Edit Issue" page
  9. Publisher clicks the "Done" button
  10. Publisher is directed to the publication page
  11. Publication issue is listed on the publication page
Alternate Flows

 

 Exceptions 
Publisher Edits Publication Issue Details
DescriptionPublisher edits information about a publication issue
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Publication issue is already created

Post-ConditionsPublication Issue details are edited
Main Flow
  1. Publisher navigates to their publications
  2. Publisher chooses publication
  3. Publisher selects issue
  4. Publisher clicks “Edit” button on issue
  5. Publisher modifies information about issue
  6. Publisher clicks “Done” button
Alternate Flows

 

 Exceptions 
Publisher Deletes Publication Issue
DescriptionPublisher deletes an issue from a publication
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Publication issue is already created

Post-ConditionsPublication Issue is removed from the Publication
Main Flow
  1. Publisher navigates to their publications
  2. Publisher chooses publication
  3. Publisher selects issue
  4. Publisher clicks “Delete Issue” button on issue
  5. Publisher is prompted for confirmation of deletion
  6. Issue is deleted from server
  7. Publisher is redirected to list of issues
Alternate Flows

 

 Exceptions 
Publisher Uploads Recognition Image for Publication Page
DescriptionPublisher uploads a single image used for recognition for a page
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Publication issue is already created

Post-ConditionsRecognition image created for that page
Main Flow
  1. Publisher navigates to desired issue of publication
  2. Publisher clicks “Add Page” button
  3. Publisher enters page number
  4. Publisher is prompted for an image file
  5. Publisher supplies image file
  6. Publisher Clicks upload
  7. Image is uploaded to server
  8. Page is updated in web browser to show new image
Alternate Flows

 

 Exceptions 
Publisher Links Media to Page
DescriptionPublisher links media to an existing uploaded image of a page
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Publication issue is already created

Publication page recognition is already uploaded

Post-ConditionsMedia becomes linked with the page
Main Flow
  1. Publisher navigates to desired issue of publication
  2. Publisher clicks image for page
  3. Publisher clicks “Add Media” button
  4. Publisher chooses media type
    1. Webpage, video, or image
  5. System prompts for “From URL” and “Choose File”
  6. Publisher clicks “Choose file” button
  7. Publisher chooses media file
  8. Publisher clicks “Done” button
  9. File uploads to server
  10. Media Displays below the image of the page
Alternate Flows
  1. Publisher navigates to desired issue of publication
  2. Publisher clicks image for page
  3. Publisher clicks “Add Media” button
  4. Publisher chooses media type
    1. Webpage, video, or image
  5. System prompts for “From URL” and “Choose File”
  6. Publisher clicks “From URL”

  7. Publisher supplies URL for media location

  8. Publisher chooses media file
  9. Publisher clicks “Done” button
  10. File uploads to server
  11. Media Displays below the image of the page
 Exceptions An invalid URL provided will raise an error
Publisher Edits Media on Page
DescriptionPublisher edits media on an existing uploaded image of a page
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Publication issue is already created

Publication page recognition is already uploaded

Publication page media is already linked with page

Post-ConditionsNew media becomes linked with the page
Main Flow
  1. Publisher navigates to desired issue of publication
  2. Publisher clicks image for page
  3. Publisher selects linked media
  4. Publisher clicks edit button
  5. Publisher changes media
    1. Changes URL
    2. Uploads a different file
  6. Publisher clicks “Done” button
Alternate Flows

 

 Exceptions An invalid URL provided will raise an error
Publisher Deletes Media on Page
DescriptionPublisher edits media on an existing uploaded image of a page
ActorsPublisher, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Publication is already created

Publication issue is already created

Publication page recognition is already uploaded

Publication page media is already linked with page

Post-ConditionsMedia linked to a page is delete
Main Flow
  1. Publisher navigates to desired issue of publication
  2. Publisher clicks image for page
  3. Publisher selects media
  4. Publisher chooses “Delete” button
  5. Media is removed from page
Alternate Flows

 

 Exceptions 
Publisher Associates with Advertiser
DescriptionPublisher associates with an advertiser to allow the advertiser to add media to the publisher's publications
ActorsPublisher, Advertiser, RocReadaR Portal
Pre-Conditions

Publisher has an account

Publisher is logged in

Advertiser has an account

Post-ConditionsThe Advertiser appears as a valid associate of the publisher
Main Flow
  1. Publisher navigates to the “advertisers” page
  2. Publisher clicks the “add advertiser as associate” button
  3. System displays a list of advertiser accounts
    1. Advertisers that have already been added will be marked to indicate this and be unselectable
  4. Publisher selects an advertiser and confirms they would like to add them as an associate
Alternate Flows

 

 Exceptions 
Advertiser Edits Media on Issue

DescriptionAdvertiser uploads media associated with a page or pages of a publication issue
ActorsPublisher, Advertiser, RocReadaR Portal
Pre-Conditions

Publisher has an account

Advertiser has an account

Publisher is logged in

Post-Conditions 
Main Flow
  1. Publisher selects a publication issue
  2. Publisher selects "grant advertiser permission"
  3. The system prompts for "Entire Issue" or "Select Pages"
  4. Publisher selects "Entire Issue"
  5. The system presents the advertisers associated with the Publisher
    1. If there are no advertisers associated with the Publisher, a message is displayed stating that an advertiser must be added first. The Publisher is directed to the "Publisher Associates with Advertiser" use case
    2. If an advertiser has already been selected, the advertiser is indicated as such in the list and is not selectable
  6. Publisher selects an advertiser and confirms
  7. The system notifies the Advertiser
  8. The Advertiser logs in
  9. The Advertiser navigates to the publication and issue
  10. The Advertiser edits the linked media and confirms his/her changes
  11. The system notifies the Publisher that there is a media edited awaiting confirmation
  12. The Publisher navigates to the issue and selects "View Advertiser Changes"
  13. The system displays the changes made by the advertiser
  14. The Publisher confirms the changes
  15. The system saves the changes
Alternate Flows

 If the Publisher selects "Select Pages":

  1. The Publisher selects the pages for the advertiser to be able to edit
  2. Flow continues as normal, but only the selected pages are visible to the advertiser

If the Publisher rejects the changes (in step 14)

  1. The Publisher writes and submits a short message why he/she rejected the changes
  2. The Advertiser receives the message
  3. Flow continues at step 8
 Exceptions 

 

 

Version Date Comment
Current Version (v. 9) Mar 13, 2016 22:04 IAN SALITRYNSKI (RIT Student)
v. 8 Feb 21, 2016 17:31 IAN SALITRYNSKI (RIT Student)
v. 7 Feb 21, 2016 16:53 IAN SALITRYNSKI (RIT Student)
v. 6 Feb 21, 2016 16:32 IAN SALITRYNSKI (RIT Student)
v. 5 Feb 21, 2016 15:34 IAN SALITRYNSKI (RIT Student)
v. 4 Feb 21, 2016 15:17 IAN SALITRYNSKI (RIT Student)
v. 3 Feb 21, 2016 14:27 IAN SALITRYNSKI (RIT Student)
v. 2 Feb 21, 2016 14:15 IAN SALITRYNSKI (RIT Student)
v. 1 Feb 18, 2016 17:48 IAN SALITRYNSKI (RIT Student)


Publisher is directed to the publication pagePublication issue is listed on the publication page