Wednesday, October 9, 2013

Use Case Narrative for Evernote


 Identification summary
Title: Create Notes
Summary: This use case describes the steps on how to create a new note.
Actors:
1.     User – Creates a new note
Creation Date: October 10, 2013                   Date of UpdateOctober 10, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.

Main Success Scenario:
1.     User creates a new note through his/her device.
2.     User enters a title for the note.
3.     User enters the note description.
4.     User saves the created note.
5.     Use case ends successfully.

Alternative Sequences:
3a. User attaches files to the note.
1.     User clicks the “add file” icon.
2.     User browses the selected file.
3.     User clicks the “attach” button to upload the selected file.

Error Sequences:
E2. User doesn’t have any title for the new note.
1. System prompts the user to input a title for the note.

Identification summary
Title: Delete Notes
Summary: This use case describes the steps on how to delete a note.
Actors:
1.     User – Deletes a note
Creation Date: October 10, 2013                   Date of UpdateOctober 10, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.

Main Success Scenario:
1.     User searches for a note through his/her device.
2.     User selects the searched note.
3.     User clicks the “delete” icon to delete the note.
4.     User clicks the “Confirm Delete” to fully delete a note.
5.     Use case ends successfully.

Alternative Sequences:
3a. User clicks “Cancel” to abort the delete process.
1.     User clicks the “Cancel” icon.

Error Sequences:
E2. User doesn’t have any note to delete.
1.     System prompts the user that there was no note deleted.



Identification summary
Title: Edit Notes
Summary: This use case describes the steps on how to edit a note.
Actors:
1.     User – Edits an existing note
Creation Date: October 10, 2013                   Date of UpdateOctober 10, 2013
Versionv1.0                                          Person in ChargePolicarpio, David Benjamin

Flow of Events

Preconditions:
1.     The user is already a verified member of the System.
2.     The user has already logged in to his/her account.
3.   The user has already created a note

Main Success Scenario:
1.     User searches for an existing note through his/her device.
2.     User selects a note that will be edited.
3.     User clicks the “Edit” icon.
4.     User makes changes within the note.
5.   User clicks the “Save” button to finalize the edited note.
6.     Use case ends successfully.




No comments:

Post a Comment