Use Cases

Summary

Use Case Diagram

http://i.hizliresim.com/V0VAmP.png

Use Cases

Use Case 1: Registration
Actors: Unregistered user
Description: An unregistered user creates an account and becomes a registered user through this process.
Triggers: The unregistered user clicks the "Sign Up" button to navigate to the sign up screen.
Pre-conditions: 1. User has succesfully loaded the registration page. 2. User has an e-mail address/social media account.
Normal flow of events: 1. The registration page is displayed to the user which contains a form in which the user can fill the necessary information for account creation. 2. User fills in the registration form entering at least the following information: First name, last name, an email address, a username and a password. 3. The unregistered user accepts Concertify's terms&privacy policy. 3. User receives an email from the system that has a link through which he/she can activate his/her account. 4. User activates his/her account through the provided link.
Extensions: 1. User enters some invalid information such as an incorrectly formatted email address or invalid password in which case he/she is prompted with an error message indicating the erroneous information field. The valid information is kept and refilled when the registration page is reloaded. 2. The unregistered user selects signing up with his/her social media account in which case he/she is redirected to the related confirmation page of the associated application.
Post-conditions: 1. A new record is created in the user database which contains the information provided by the user. 2. User is now registered and is able to login using the information he/she provided during registration.

Use Case 2: Logging into the system
Actors: Registered user
Description: A user with an account is able to login to the system through this process.
Triggers: A non-logged in user navigates to the login page.
Pre-conditions: 1. User has an existing valid account. 2. The user account is not suspended or deleted.
Normal flow of events: 1. User is presented with a login form through which he can login to the system using his/her email or username and password. 2. User fills in the form with his/her credentials. 3. User submits the form and logs into the sytem succesfully.
Extensions: 1. The information user has entered is invalid in which case he/she is prompted with an error message indicating that the login attemp was unsuccesful. 2. User has tried to log into an account unsuccesfully for five consecutive times in which case an email confirmation will be required for this account even if the correct credentials are provided at a later time. 3.User can also choose to log in with social media accounts.
Post-conditions: 1. User is logged into the system and is able to use the facilities provided to registered users.

Use Case 3: Searching for concerts and users
Actors: Registered user, Unregistered user
Description: A user is able to search for existing concert pages by specifying their artists, locations, dates, tags or creators. A user is also able to search for registered users by specifying their usernames.
Triggers: A user make a search query through quick search bar or the advanced search form.
Pre-conditions: 1. None
Normal flow of events: 1. User enters the keywords he/she would like to search for into the search bar. 2. The system finds the concerts that match these keywords and produces a search result accordingly. 3. User is presented with the search results and may go to a resulting concert page or user profile by clicking the related entry or may make a new search query if he/she is not satisfied with the results.
Extensions: 1. There may be no concerts or users that match the given keywords in which case the user is prompted with an advanced search form and asked to refine his/her search parameters in order to get better results. 2. The search query is found to include malicious content in which case the search request is rejected.
Post-conditions: 1. User is shown the results of the search query he/she has made. 2. Search statistics of the website is updated.

Use Case 4: Creating a concert page
Actors: Registered user
Description: A user is able create a new concert page by providing certain information about it such as; artist, location and date.
Triggers: A user clicks the "Create a New Concert Page" button.
Pre-conditions: 1. The user is properly logged in.
Normal flow of events: 1. User navigates to the concert creation page. 2. User fills in the following necessary information about the concert: artist, location and date. 3. User fills additional information about the concert if he/she desires. 4. User adds semantic tags to be associated with the concert page. 5. User completes the concert creating procedure and a new concert page is created.
Extensions: 1. After the user completes page creation, existing concerts are compared to the new concert and if a similar concert already exists (same date, artist and location), the user is asked to verify that this is not the concert he/she is trying to create a page for.
Post-conditions: 1. The concert page database is updated and the new concert page is now available for recommendation and search facilities. 2. Concert page history of the user is updated.

Use Case 5: View a concert page
Actors: Registered user, Unregistered user
Description: A user is able to view an existing concert page.
Triggers: A user navigates to a concert page.
Pre-conditions: 1. A concert page for the related concert exists.
Normal flow of events: 1. User navigates to a page for a concert he/she is interested in by some means available through the user interface e.g. from the home page, through the search facility or through another user's profile. 2. User is displayed the existing content for the related concert including the comments made by other users. 3. In this page, if the user is a registered user, he/she is presented with the options to propose an edit for a certain information, add a comment, mark as "will attend" or rate the concert.
Extensions: 1. None
Post-conditions: 1. User is shown the content for the concert he/she is interested in. 2. User is presented the option to mark the concert as "will attend".

Use Case 6: Add comment to a concert page
Actors: Registered users
Description: A user is able to add comments to an existing concert page through this process.
Triggers: A user submits a new comment through the comment section in a concert page.
Pre-conditions: 1. User is properly logged into the system.
Normal flow of events: 1. User enters into a concert page. 2. User enters the comment he/she desires into the comment box and sends the comment. 3. The comment section of the related concert is updated and the new comment is displayed.
Extensions: 1. The comment entered by the user is too long (longer than 5 lines) in which case the first 5 lines of the comment is displayed with an option to show the rest of the comment.
Post-conditions: 1. Comment section of the related concert is updated. 2. Comment count of the related concert is updated. 3. Comment history of the user is updated.

Use Case 7: View another user's profile page
Actors: Registered user, Unregistered user
Description: A user is able to view another user's profile page.
Triggers: A user navigates to another user's profile page.
Pre-conditions: 1. Such a "user profile page" for what the user has been looking for exists.
Normal flow of events: 1. User navigates to another user's profile page which can be linked from different pages such as the home page or from the results of a search or through a concert page etc. 2. The basic profile info of the user is displayed such as Profile Picture, Name, Location, Age, Gender, Musical Interest(these fields can be decided not to be shown in privacy setting by the user). In addition the user can see the other user's past concerts, upcoming concerts and the people that he/she follows. 3. There is also a "Follow" button that is showed only to the registered users.
Extensions: 1. None
Post-conditions: 1. User is shown the information about the other user that he/she is interested in. 2. Only the Registered user is presented the option to "follow" the other user that he/she is looking at.

Use Case 8: Editing user's profile
Actors: Registered user
Description: A user is able to edit his/her profile.
Triggers: A user navigates to his profile and clicks edit.
Pre-conditions: 1. The user account is not suspended or deleted.
Normal flow of events: 1. User navigates to own profile page which can be linked from the top menu or from other pages like a concert. 2. The basic profile info of the user is displayed such as Profile Picture, Name, Location, Age, Gender, Musical Interest(these fields can be decided not to be shown in privacy setting by the user). There is also an edit button. 3. User can edit or hide fields from other users.
Extensions: 1. Privacy settings
Post-conditions: 1. User is shown the information about the other user that he/she is interested in. 2. Registered user is only allowed to edit his/her own profile.