-
Notifications
You must be signed in to change notification settings - Fork 1
Lab Report 9
In this lab, we created a draft scenario for final milestone and inspected the standard that we will implement in our app. Then, we opened the issues and planned the next week.
In-draft scenario: For mobile, a user logs in and searches the archive for one of Carlsen's games. They open a specific game from the Grand Slam Final tournament in the analysis board. After reviewing it, they browse other games from the same tournament. When they find an interesting game with a decisive result, they save it using either the like or bookmark feature.
That evening, they return to make a post about the saved game. They go to their profile, find the game in their bookmarks/likes, and open it in the analysis board. They copy a position from the game, go to the feed to make a new post, and tag it with "Tactics."
The frontend flow starts with someone seeing this post while browsing their feed. The "Tactics" tag catches their interest, so they click it to see related posts. The user selects one post they want to object to and can input their own suggested variation - either a single move or a sequence. They search for a specific game to ensure they remember the sequence correctly. The user can click through to see other games containing the same tactical pattern in a given position. After picking one of these games, they explore alternative moves. Then, the user wants to explore more games in that tournament and clicks on the name. They click on another game. Finally, they select a move and add their annotation to it.
This walkthrough covers the key features: analysis tools, content sharing, community interaction, and finding tactical patterns across different games.
- Backend: Create Edit-Delete endpoints for Posts
- Backend: Enhance List post items endpoint
- Backend: Create Follow/Unfollow User Endpoint
- Mobile: Remove Search Post by id from the Main Screen
- Mobile: Make Position Copyable on Game Analysis Screen
- Backend: Create Backend Structure for Annotations
- Frontend: Annotate Steps
- Frontend: Multistep comments
- Backend: Create User Page Endpoints
🏠 Home
- Communication Plan for CMPE451
- Responsibility Assignment Matrix(RAM) for CMPE451
- Requirements Document for CMPE451
- Project Plan for CMPE451
- Web Annotation Data Model (WADM) Documentation
CMPE352
- Domain Analysis - Video Games
- Wikidata Research
- Mobile Development Research
- Web Development Research
- Application Programming Interface (API) Research
- Repository Research
- Useful Resources
- Requirements
- Responsibility Assignment Matrix
- Project Plan
- Elicitation Questions
- Scenarios
- Mockups
- Milestone Report 1
- Use Case Diagram
- Class Diagram
- Sequence Diagrams
- Milestone Report 2
- Milestone Report 3
- Meeting #10 ‐ 15.05.2024
- Meeting #9 ‐ 08.05.2024
- Meeting #8 ‐ 17.04.2024
- Feedback Meeting - 17.04.2024
- Meeting #7 ‐ 27.03.2024
- Meeting #6 ‐ 22.03.2024
- Customer Meeting ‐ 17.03.2024
- Extra Meeting ‐ 15.03.2024
- Meeting #5 ‐ 13.03.2024
- Meeting #4 ‐ 06.03.2024
- Meeting #3 ‐ 28.02.2024
- Meeting #2 ‐ 21.02.2024
- Meeting #1 ‐ 16.02.2024