Scenario 2 - bounswe/bounswe2024group12 GitHub Wiki

Persona

Name: James Hamlin

James Hamlin

Age: 31

Occupation: A game critic who has played many video games and wants to make his own game in the future.

Background and Story: James is a 31 year old man. He graduated from university with a Bachelor's Degree in Business Administration and after working as a white-collar for a few years, he decided to follow his dream of making video games. In order to produce his own games, he first decided to do research and analysis about games. While examining video games, he followed his entrepreneurial instincts and became a content producer about video games on different platforms such as YouTube, Twitch, Reddit and Twitter. His contents gained success and he is now a game-critic followed by many people for his contents related to video games. He still wants to produce his own games in the future but for now, he is analyzing as many video games as he can. Apart from the mentioned platforms, he also uses a website to publish quick reviews after playing games. He also has a large number of followers on this platform and almost once a week he writes a review on this website about the game he played recently.

Goals

  • James wants to enter the website to make a review about a newly released game.

  • He wants to create a list of the games he has published reviews for so that his followers can access all his reviews in one place.

Pre-conditions

  • He already has an account and has been using the website for a long time. After some point, he started using the site mainly to make reviews.

Scenario

  1. James enters the website and clicks the login button to enter his profile. He enters his email and password.

  2. After confirmation he is directed to the main page. He directly clicks to search button and types the name of the game he recently played.

  3. The game page appears on his screen with the name, descriptions, different informations and a photo of the game. He quickly looks for the stats of the game (overalll rating etc.) before making a review. Then he clicks the review button to make his review about the game.

  4. The site asks for a rating and a review (optional). He rates the game and writes a review about the game.

  5. Then he decides to make a list that collects all of his reviews in a single place and clicks on new list button. He adds games that he reviewed to his list and makes the list public for all users because he wants his followers to make use of his reviews.

  6. After achieving his goals of making a review and creating a new list, he logs out and leaves the site.

Acceptance Criteria

  • 1.1.1.2. Guests shall be able to log in to the application by providing their email and password.

  • 1.2.2.2 System shall provide lexical search for games and property values (genre, director, developer, etc.) available in Wikidata API.

  • 1.1.2.1.3. Users shall be able to navigate to the games page.

  • 1.2.4.1. System shall retrieve game logo from IGDB API.

  • 1.2.4.2. System shall retrieve game name, (if exists) one or two alternative names and a short description from Wikidata API.

  • 1.2.4.3. System shall retrieve longer description, (if available) in-game photos and videos from IGDB API.

  • 1.2.4.4. System shall calculate the overall rating of the game and display.

  • 1.1.3.2.7. Logged in users shall be able to review a game.

  • 1.1.3.3.2. Logged in users shall be able to create custom lists.

  • 1.1.3.2.5. Logged in users shall be able to add a game to one of their custom lists.

  • 1.1.3.3.1. Logged in users shall be able to change a list that they have created from public to private or vice versa.

  • 1.1.2.4.2. Users shall be able to view registered users’ stats which includes the number of games they own, played, currently playing, reviews, and lists.

  • 1.1.1.3. Logged in users shall be able to log out from the application.

Mockups

Login

  • Related scenario items: 1.

Main Page

  • Related scenario items: 2.

Page of a Game

  • Related scenario items: 3.

Reviews Section

  • Related scenario items: 3, 4, 5.