Skip to content
This repository has been archived by the owner on Mar 7, 2018. It is now read-only.

Latest commit

 

History

History
157 lines (107 loc) · 5.34 KB

Use cases.md

File metadata and controls

157 lines (107 loc) · 5.34 KB

Use Cases

b. Use case model

UC1

Use case name: Create New Account.

Participating actors: HN User - System.

Flow of events.

  1. User selects Login in the menu.
  2. The system presents a form for creating a new account.
  3. The user completes the form by filling in username and password. The user then submits the form.

Pre-conditions: The user is not already logged into an account.

Post-conditions:

  • A: The system responds by going back to the previous page the user was on. A link with the user name and number of karma points shows up in the menu. Links with the title welcome and threads also shows up in the menu.
  • B: User is prompted that the user name has been taken.
  • C: Invalid username or password
UC2

Use case name: Login.

Participating actors: HN User -> System.

Flow of events:

  1. User selects Login
  2. The system presents a form for login.
  3. The user completes the form by filling in username and password. The user then submits the form.

Precondition: The user has an account, and is not already logged in to an account.

Exit condition:

  • A: The system responds by going back to the previous page the user was on. New links are added to the menu, links for an introduction to HN, threads and edit profile information.
  • B: User is prompted that the user name or password was incorrect.
UC3

Use case name: Update User Information.

Participating actors: HN User -> System.

Flow of events:

  1. Users select the link to user information.
  2. The system responds by presenting a form to the HN User, with the editable fields for the accounts information. and noneditable information about the HN User.
  3. The HN User make changes and submits the form.

Pre-conditions: The users are logged in.

Post-conditions:

  • A: The system responds by presenting the form with the updated information.
  • B: The system present to the user that something went wrong.
UC4

Use case name: Submit a thread.

Participating actors: HN User -> System.

Flow of events:

  1. The user selects the link to submit in the main menu.
  2. The system responds with a submit form.
  3. The user fills in the form giving a Title and URL linking to the news article. Leave URL blank to submit a question for discussion. If there is no URL, the text (if any) will appear at the top of the thread. Titles beginning with "Show HN" will appear under show.

Pre-condition: The users are logged in.

Post-condition:

  • A: The system responds with a thread successfully submitted message
  • B: The system present to the user that something went wrong.
UC5

Use cast name: Comment on a thread.

Participating actors: HN User -> System.

Flow of events:

  1. The user selects to comment on a specific a thread in the display of stories.
  2. The system responds with a form and details about the thread, and previous comments. The thread information is made up by the title, the number of points, creator of the thread, days since threaded, number of comments. The comments are presented with the username of comment submitter, days since threaded, the comments and a link to reply.
  3. The user fills in the comment in the form and submits it.

Pre-condition: The users are logged in.

Post-condition:

  • A: The system responds with showing the page of the comments.
  • B: The system present to the user that something went wrong.
UC6

Use case name: Create Thread.

Participating actors: Simulator Program -> System.

Flow of events:

  1. The user submits a post to the system API. The post consists of a Title, Text or URL.

Pre-condition: none

Post-condition:

  • A: The system API responds with a successful response and details about the created post.
  • B: The system API responds with error and details about the error.
  • C: The system API responds with status: System is unreachable, most likely offline.
UC7

Use case name: Comment on a thread.

Participating actors: Simulator Program -> System.

Flow of events:

  1. The user submits a post to the system API. The post consists of a Title, Text or URL.

Pre-condition: none

Post-condition:

  • A: The system API responds with a successful response and details about the created post.
  • B: The system API responds with error and details about the error.
  • C: The system API responds with status: System is unreachable, most likely offline.
UC8

Use case name: Query system status.

Participating actors: Simulator Program -> System.

Flow of events:

  1. The user requests the systems API for the current status.

Precondition: None

Post-condition:

  • A: The system API responds with status: system is operational
  • B: The system API responds with status: System is upgrading
  • C: The system API responds with status: System is unreachable, most likely offline.
UC9

Use case name: Query system latest.

Participating actors: Simulator Program -> System.

Flow of events:

  1. The user requests the systems API for the latest ingested thread or comment.

Pre-condition: None

Post-condition:

  • A: The system API responds with a thread or comment
  • B: The system API responds with status: System is upgrading
  • C: The system API responds with status: System is unreachable, most likely offline.