Skip to content

CMPE 451 Milestone 1 Report

Jump to bottom
cisel-zumbul edited this page Nov 3, 2023 · 37 revisions

CMPE 451 Milestone 1 Report (Group 5)

Contributors

Table of contents

1. Executive Summary

1.1 Summary of the Project Status

Up to the first milestone, we successfully implemented some of the required features for our game review platform. This includes all authentication features, game listing, filtering, and searching on the games page, as well as the game description page (except reviews and forums). We were also able to deploy our applications. In this way, we were able to complete the demo without any mock data. Additionally, we made significant improvements to the backend, particularly in the area of continuous integration and continuous deployment (CI/CD), although it's not fully functional at the moment. So, in general, we have reached the intended stage of development.

1.2 Changes That are Planned for Moving Forward

For the future, we have identified two changes in our plan. Firstly, we noticed that there were discrepancies in the appearance of our platform on the two different platforms (mobile and frontend) due to limited collaboration between the mobile and frontend teams for design. To solve this problem, we plan to increase the frequency of meetings between these teams to guarantee a consistent user interface between both platforms.

Secondly, based on feedback received during the demo, we believe that it is necessary to re-evaluate the planned avatar feature. We will conduct further discussions with our customers to meet their expectations and needs.

1.3 A summary of the customer feedback and reflections

Initially, we had negative customer feedback on our requirements. We learned that there has been some miscommunication on the importance of “Domain Specific” features. The meaning of that term, and how it applies to our project has been hard to grasp, so we had a long discussion with the product owners. After that discussion, we decided to research and brainstorm some ideas for domain specific features. We came up with a handful of ideas for features and compiled them in a wiki page. Following the research, we did a meeting with stakeholders to discuss those ideas. The meeting went great, and we decided on focusing on these new features while leaving some less important ones behind. Another important source of feedback was our milestone presentation. During the presentation, some issues with our initial release were discussed. One feedback was the inconsistent style and colors between the web ui and the mobile app. Moving forward, we will have better communication between the front-end teams so that this issue can be resolved. Another discussion topic was the “Avatars” function. While not implemented yet, this functionality seems important to the stakeholders and we will need to have a discussion on it.

6. Requirements Addressed In This Milestone

In Milestone 1, we have made significant progress in addressing several key requirements, primarily focusing on the authentication aspect outlined under sub-section 1.1.1 of the project requirements.

With the latest version of our platform that we’ve presented in the demo:

  • Users are able to register to the platform providing a unique username, email and a valid password. (req. 1.1.1.1.1)
  • Users are able to login to the platform providing their username and password. (1.1.1.2.1)
  • Users are able to logout. (1.1.1.3.1)
  • Users are able to change their passwords. (1.1.1.4.1)
  • Users are able to use forgot password getting through a verification process via providing their emails. (1.1.1.5.1) Also we’ve focused on another fundamental requirements under the sub-section 1.1.8 of the project requirements which is game. After we’ve managed to complete main functionalities in game for registered users and the guest users,
  • Users are able to filter games by their tags (1.1.8.1)
  • Users are able to search games by their name (1.1.8.2)
  • Users are able to access game specific info about the game like player type, genre, minimum system requirements. (1.1.8.4)

In addition to these functional requirements, we have also addressed security-related non-functional requirements:

  • The platform generates a JWT token for every user, and each endpoint verifies the authorization header of incoming requests to ensure authentication of valid users' requests. (2.2.2.2 & 2.2.2.3)

7. Individual Contributions

🏠Home

📜 Conventions

💻 Meeting Notes

Cmpe 352
Cmpe 451

📝 Requirements

🪧 Diagrams

📬 Deliverables

Cmpe 352
Cmpe 451

🎇 General Contributions

Cmpe 352 Contributions

Milestone 1
Final Milestone

Cmpe 451 Contributions

Milestone 1
Milestone 2
Final Milestone

📕 Mock Up

🕵️ User Scenario

☎️ Communication Plan

📝 RAM

📚 Research

📑 Templates

📱 Practice App

API Documentation for Practice App
Clone this wiki locally