RocReadaR : Use Cases - RocReadaR Mobile App

Created by IAN SALITRYNSKI (RIT Student), last modified on Feb 21, 2016
Launch Mobile Application
DescriptionLaunching the application on a mobile device should indicate progress to the user.
Actors User, Mobile Application
Pre-ConditionsMobile Application Not Launched 
Post-ConditionsMobile Application Launched 
Main Flow
  1. User taps on application icon on mobile device
  2. Application displays splash screen
  3. Application displays progress spinner or loading bar while loading additional components
  4. Application displays main screen 
Alternate Flows 
 Exceptions 
Application Recognizes Page
DescriptionThe application should recognize a page that has been uploaded to the server
Actors User, Mobile Application
Pre-ConditionsMobile Application Launched, Publication media and recognition images uploaded through RocReadaR Portal
Post-ConditionsMedia content icons appear on screen
Main Flow
  1. User points device's camera at printed page
  2. Mobile Application sends images to server
  3. Server recognizes image
  4. Server returns content to Mobile Application
  5. Mobile Application displays media content icons for relevant content found 
Alternate Flows
  1. User Points application at printed page
  2. Page is not oriented correctly, is obscured, or cannot otherwise be recognized
  3. Application overlays guidelines to instruct user on usage
  4. User follows guidelines
  5. Return to main flow
 Exceptions 
User Opens Video
DescriptionWhen user taps video icon, the video(s) should display
ActorsUser, Mobile Application
Pre-Conditions

Use Case "Application Recognizes Page" is completed

A video option is available for the recognized page

Post-ConditionsVideo is displayed
Main Flow
  1. User taps video icon
  2. Application switches from main view to a list showing the attached videos of the page
  3. User taps list element
  4. Video is displayed
Alternate Flows

 

 ExceptionsNo videos attached to current page
User Submits Comment
DescriptionUser adds a comment to an article
ActorsUser, Mobile Application
Pre-Conditions

Use Case "Application Recognizes Page" is completed

Post-ConditionsComment is Posted
Main Flow
  1. User taps comments icon
  2. User taps on text field
  3. User enters text
  4. User submits comment
  5. The mobile application sends the comment to the server
  6. The mobile application awaits a response from the server
  7. The server validates the comment against its automatic filter
  8. The server posts the comment
  9. The server notifies the mobile application
  10. The mobile application notifies the user
Alternate Flows
  1. Comment is rejected by automatic filter
  2. Server notifies mobile application
  3. Mobile application prompts user to edit comment
  4. User edits text
  5. Go to Main Flow step 4

 

  1. The server marks the comment to be reviewed
  2. The server notifies the mobile application
  3. Mobile application notifies user that comment will be reviewed before appearing
 Exceptions 
User Opens Photo
DescriptionUser opens a photo attached to an article
ActorsUser, Mobile Application
Pre-Conditions

Use Case "Application Recognizes Page" is completed

Post-Conditions

Photo is displayed

A picture option is available for the recognized page

Main Flow
  1. User taps photo icon
  2. Application switches from main view to a collection of photos attached to the article
  3. User taps on a photo
  4. Photo opens in fullscreen
Alternate Flows
  1. User can zoom in on photo using multitouch gestures
 Exceptions 
User Logs in to Publication
DescriptionUser verifies subscription to publication when attempting to view content
ActorsUser, Mobile Application
Pre-Conditions

User has a printed copy of a publication that requires a subscription

Post-Conditions

User becomes authenticated

Main Flow
  1. User hovers phone over publication
  2. Mobile Application recognizes page
  3. Mobile Application identifies that content needs a subscription
  4. Mobile Application prompts user for credentials for publication
  5. User inputs credentials for publication
  6. Server authenticates user
Alternate Flows

 

 ExceptionsInvalid Credentials may require the user to re-enter credentials

 

Version Date Comment
Current Version (v. 4) Feb 21, 2016 14:12 IAN SALITRYNSKI (RIT Student):
Added change history
v. 3 Feb 21, 2016 14:06 IAN SALITRYNSKI (RIT Student):
Added main uses cases
v. 2 Feb 18, 2016 19:49 IAN SALITRYNSKI (RIT Student)
v. 1 Feb 18, 2016 17:48 IAN SALITRYNSKI (RIT Student)