Your SlideShare is downloading. ×
0
Use Case Narratives
Use Case Narratives
Use Case Narratives
Use Case Narratives
Use Case Narratives
Use Case Narratives
Use Case Narratives
Use Case Narratives
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Use Case Narratives

284

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
284
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Use Case Narratives Kevin Christian Salazar
  • 2. Use Case Diagram
  • 3. Use Case Narratives: 1. Add Annotation 2. Edit Annotation 3. Delete Annotation
  • 4. Identification Summary TITLE: Add Annotation SUMMARY: This use case describes the steps associated with adding new annotations to existing songs ACTORS: 1. User - adds annotations to songs 2. RapGenius - checks the submitted annotations CREATION DATE: July 8, 2013 DATE OF UPDATE: July 8, 2013 VERSION: V1.0 PERSON IN CHARGE: Kevin Salazar Flow of Events PRECONDITIONS: 1. User has already undergone the Log In account use case MAIN SUCCESS SCENARIO: 1. User browses a song 2. User highlights a line from a song and clicks annotate 3. User types the annotation and clicks save, or presses shift and enter 4. RapGenius saves the annotation 5. Use case ends successfully
  • 5. ERROR SEQUENCE: E2. Line already have an annotation 1. RapGenius displays an error message instead of providing a blank textbox E4. RapGenius rejects the submitted annotation 1. RapGenius deletes the submitted annotation which ends the use-case POST CONDITIONS: 1. Annotations for the song are updated
  • 6. Identification Summary TITLE: Edit Annotation SUMMARY: This use case describes the steps associated with editing annotations of songs ACTORS: 1. User - edits annotations of songs 2. RapGenius - checks the submitted annotations CREATION DATE: July 8, 2013 DATE OF UPDATE: July 8, 2013 VERSION: V1.0 PERSON IN CHARGE: Kevin Salazar Flow of Events PRECONDITIONS: 1. User has already undergone the Log In account use case 2. User has already undergone the Add Annotation use case MAIN SUCCESS SCENARIO: 1. User browses a song 2. User clicks the line he added annotation to and clicks edit 3. User types the new annotation and clicks save or presses shift and enter 4. RapGenius deletes the old annotation and saves the new one 5. Use case ends successfully
  • 7. ERROR SEQUENCE: E4. RapGenius rejects the submitted annotation 1. RapGenius deletes the submitted annotation which ends the use-case POST CONDITIONS: 1. Annotations for the song are updated
  • 8. Identification Summary TITLE: Delete Annotation SUMMARY: This use case describes the steps associated with deleting annotations of songs ACTORS: 1. User - deletes annotations of songs CREATION DATE: July 8, 2013 DATE OF UPDATE: July 8, 2013 VERSION: V1.0 PERSON IN CHARGE: Kevin Salazar Flow of Events PRECONDITIONS: 1. User has already undergone the Log In account use case 2. User has already undergone the Add Annotation use case MAIN SUCCESS SCENARIO: 1. User browses a song 2. User clicks the line he added annotation to and clicks delete 3. RapGenius prompts the user if he wants to delete the selected annotation 4. RapGenius deletes theannotation 5. Use case ends successfully POST CONDITIONS: 1. Annotations for the song are updated

×