Grading
Team
| Crossover Score | Runtime | Plan | Github | Analytics | | — | — | — | — | — | | 0.87 | Runtime | Link to Plan | Github | Analytics
Individuals
| Name | Team+Indi+Teacher | Key Commits | Video | Analytics | Individual Ticket | | — | — | — | — | — | — | | Rachit | 0.87+0.9+0 = 1.77/1.8 | ALL KEY COMMITS ARE BELOW | video | link | ticket | | Tanisha | 0.87+0.88+0 = 1.75/1.8 | ALL KEY COMMITS ARE BELOW | video | link | ticket | | Luna | 0.87+0.85+0 = 1.72/1.8 | ALL KEY COMMITS ARE BELOW | video | link | ticket |
Individuals: Check out everyone’s commits for frontend and backend here: Frontend Backend
Key Commits:
Tanisha -
- Backend Endpoints/Database Creation - Card Generation - Card Api Controller - Main - CardJpaRepository Class
- Card Service Class - Data Population
- Test analysis frontend file - Main commit
Rachit -
- Deploy Backend (Rachit): Commit where everything was finally deployed (just changed the name here)
- Fibonacci (finished version, both Binet’s Formula and Matrix Exponentiation): Commit
- Basic Sorting (All 4 types–merge, insertion, selection, and bubble): Backend Commit
-
CORS Support serverwide: Commit 1 Commit 2 - more types of requests Commit 3 - Enable Local -
Frontend - Got requests to adhere with proper headers and JSON: Commit 1 (build off other commits) - Finish making and organizing sorts Commit 2 - Batch Analysis Commit 3 - Fibonacci Frontend Calls w/ Animation
Luna -
- animations for the sorts based on the backend fetch
- fixing box sizing due to more numbs
- buttons for the displaying the sorts
- fibonacci building canvas base
- configuring animating the shell to work
Project
Project description Link to Plan
Sorting - Algos, Inheritance, Abstraction
Implementation
Link to Frontend Link to Backend
Issues
Reflection
We realized that we had trouble carrying out our ideation to meet requirements of the project. Because of this our ideation was delayed and we had to make up for lost time.
Team Facetimes ! 🤩
Collaboration 💡
Retrospective 💡
This project was a wonderful journey through the different types of sorts and we got to learn a lot about the java process. We wanted to target a lot of things, but for the scope and requirements of our project, as well as the time it took us to ideate and plan out our project, we were not able to completely make a resemblance of our original game: War. However, we believe that we were able to match our requirements for what we wanted the game to have and the requirements that the project needed. Overall, I think we did a great job balancing everything out and trying to include everything that we possibly could. Although our game has slightly deviated from the original war game, and the fact that we were not able to completely finish some goals (ex. different card ranks) due to some crunches and the project requirements, as well as our ideation time, we feel like we have been able to show our knowledge about Java and sorting algorithms, as well as fibonacci, with a lot of growth and improvement. We learned many things along the way, and we cannot wait to learn more as we go on an adventure with the Zesty Rachits!