Milestone 1 Report

CMPE 352 Milestone Report 1 (Group 5)

Contributors

• Ali Başaran
• Alperen Bırçak
• Arda Kabadayı
• Bilal Atım
• Can Uzduran
• Çisel Zümbül
• Deniz Ünal
• Ege Ekşi
• Halis Bal
• Harun Sami Çelik
• Mehmet Said Yolcu
• Zeynep Baydemir

Table Of Contents

• Table Of Contents
  • 1. Executive Summary
    • 1.1 Introduction
  • 2. List and Status of Deliverables
  • 3. Evaluation of Deliverables
  • 4. Evaluation of Tools and Processes
  • 5. Table of Work Done by Each Team Member
  • 6. Deliverables

1. Executive Summary

1.1 Introduction/Project Description

Our project is a multi-faceted social media platform geared towards the main players of the gaming industry, those being developers, gamers and event organizers. The projects main goal is to become a social media for video game enthusiasts to use for interacting with the community and discovering further communities they'd be interested in. Our secondary goal is to differantiate ourselves from existing social media that fills these niches, such as Reddit, by having unique core functionalities. The main functionalities users will interact with are the "Games", "Groups" and "Events" functionalities.

The main functionality concerning games and their communities is the "Games" page. This page will have an individual, unique page for every game by only giving the permission to create a game page to admins and verified developers. Initially, the database of games can be created by scraping various online game stores. The main games page will give the user ability to search, sort and filter games in order to find the main hub of a community. Each game page will host a review page to give an honest first impression to the users. The reviews functionality is especially important to ensure the game pages are community driven, and don't turn into a marketing tool. Indvidual pages will also have a forum that will act as the main interaction point for the players of those games.

The group functionality is going to be used to host any community that is related to gaming, but is not defined only by the a game. This can range from a group of friends that regularly play with eachother, to a community of users that favor a specific playstyle. To cover this range, they are two types of groups that are differantiated by their membership policy. A public group accepts anyone who wishes to join the community, while a private group accepts users by and appliation process. By having this distinction, we hope to cater to a diverse selection of users.

The forum functionality of the project is a multi purpose component that handles all the inter-community communication in the project. The usage of the forum structure was chosen because it is the main structure used in our main inspirations for the social aspects of the project, and works for both large and small communities. A forum will exist for each game, but also each group so that the project will be able to host small and medium sized communities.

The events functionality is an another core functionality of our project. The events page will be used to advertise various events, by professional event organizers or other community members. Those events range from large gaming conventions to online machinima performances. Gamers can filter those events to their interests and find opportunities to socialise with other gamers, participate in fun events or find new interests.

There will be a lot of other functionalities to make the users experience more streamlined and interactive. The platform will allow users to have a profile page to customize their online apperance. Users will be able to follow forums to have a central feed to consume content. More proffesional members of the community will be able to promote events, games and forum posts, which will act as a revenue generator.

In summary, we hope to create a central hub for the masive hobby that is video gaming. We tailored our core functionalities in a way that will result in a community driven social media that will also cater to proffesional users, so that the user does not feel alienated. We also think we achieved to differantiate ourselves from other social media so gamers will have a reason to choose us over competitors.

1.2 Project Status

Our software engineering team consists of 12 members. Our primary objective this semester has been to equally distribute the work among the team members and improve the project with contributions from each of us. In order to that, at first we all discussed about tasks and try to reach a common decision. Afterwards we divided each task into sub-tasks and tried to give responsibility to every member of team. Some tasks were challenging, so that they were assigned more than one person.

Initially, we agreed on a communication plan and weekly meeting time. We though that it will be beneficial to do our meetings face to face. Hence we hold our regular meetings on every Thursday in B5. Also, for the online communication we are using Whatsapp and Discord.

Then, everyone in the group created their own personal page and made a research about a repository. After that, we created our homepage and sidebar where all the links and information about the project can be found.

After these stuffs, we determined the core features of our project and the determined the functional and non-functional requirements according to our studies. We did research on how the requirements are created and observed the functionalities of websites that is similar to our project idea.

To help the customer comprehend our project and demonstrate how it would seem in various situations, we have prepared mockups. After that, we developed user scenarios based our mockup designs. To show which components our application consists of and how our application will work, we first have designed Use Case and Class Diagrams based on our requirements. Then to validate those diagrams we designed Sequence Diagrams.

1.3 Future Plans

We have worked on design issues until now. From now on, we will focus more on issues related to implementation. We are going to discuss about the tools and frameworks, which might be useful for us for the next semester. We will decide language preferences for the project and make some research about the project features. For example, we want to add a feature that enables users to signing up to our application with using their Steam accounts. For this feature we will make some research about the feasibility of it and read the Steam Web Api documentation. Also we will learn how to use Figma because it will help us to concretize the designs in our minds.

2. List and Status of Deliverables

Deliverable Name	Delivery Status	Due Date	Delivery Date
Up to Date Project Repository	Delivered	10/04/2023, Monday	10/04/2023, Monday
Requirements	Delivered	10/04/2023, Monday	23/03/2023, Thursday
Mockups and Scenarios	Delivered	10/04/2023, Monday	10/04/2023, Monday
Use Case, Class and Sequence Diagrams	Delivered	10/04/2023, Monday	10/04/2023, Monday
Project Plan & RAM	Delivered	10/04/2023, Monday	10/04/2023, Monday
Communication Plan	Delivered	10/04/2023, Monday	06/03/2023, Monday
Milestone Report	Delivered	10/04/2023, Monday	10/04/2023, Monday

3. Evaluation of Deliverables

4. Evaluation of Tools and Processes

5. Table of Work Done by Each Team Member

6. Deliverables