Big Grading 12/11

[rachit-j]

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!

[AniCricKet]

Team Review "Aniket Chakradeo" grading "WW3 (rats)"

• [x] The team should have a Web Page(s) that teach/explain: Fibonacci, Algorithm, etc.
• [x] The team should have a Web Page(s) that teach/explain: Sorting, Timing, Compares Swaps, etc.

Team Review ticket containing key Team and individual contributions

• [x] Growth/Accomplishments in work is according to historical Team Plan, or they show revisions to plan according to work
• [x] Short falls/Improvement that could be made in Work or Team Plan, team highlights next steps or improvements that could be made
• [x] Showing key accomplishments according to requirement in Java Backend such as API, Abstract Class(es), Inheritance, Polymorphic behavior, Sorting Algorithms, etc. In Sorting, there should NOT be static classes or static methods.

• [x] Showing key user interaction and learning(s). For instance how you visualized Sorting Algorithm: Bubble, Insertion, Selection, Merge... how you captured Big O, analytical data, usage of Data Structures... And/or, how you provided response and Feedback to user on their success in learning or experiencing your interface.

  Per check.
  0.87

  Freeform comment:

  Tanisha demonstrated how she changed what was in her initial plan, and what improvements could be made. Her project met the requirements for sorting and fibonacci.

[AniCricKet]

Individual Review "Aniket Chakradeo" grading "Tanisha Patil"

• [x] Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

• [x] Video, includes Web demo of key contribution to project, 1 minute (0.87) - Video is good and speaks well about her code but slight micommunications with other teammates.
• [x] Issue(s) that show plans/progress to team objectives (0.87) - Has plans for projects well documented and progress of the progress
• [x] Highlights of key commit(s) in Issues, summarizes code contributions (0.88) - Has several key commits in both the frontend and the backend and describes what each one is doing in detail
• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks (0.88) - Was very consistent across the 3 week period, actively contributing to the team

Per check:

(0.87 + 0.87 + 0.88 + 0.88)/3.6 =0.97/1

Freeform comment:

Tanisha was a key contributor to her team, and had several key commits for the backend API. She had O(n) and incorporated sorting algorithms. She spoke about revisions she made based off inputs on their original plan, and also talked about reflections on how she can improve the project more in the future

[QDBordtoshred]

Individual Review "Quinn Bireley" grading "Luna"

• [x] Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

• [x] Video, includes Web demo of key contribution to project, 1 minute
• [x] Issue(s) that show plans/progress to team objectives
• [x] Highlights of key commit(s) in Issues, summarizes code contributions

• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

  Per check.
  0.85

Freeform comment.

The developer demonstrated a systematic and growth-oriented approach through well-documented key commits and a forward-looking plan for future changes. The addition of a video presentation showcased effective communication skills. Clear definition of the developer's role, thorough exploration of runtime considerations, and exemplary work and communication techniques highlighted technical proficiency and collaboration. In essence, the project reflects a positive trajectory marked by continuous improvement and a holistic understanding of both technical and communicative aspects.

She was well spoken and understood the material presented. Everything was explained in depth and overall it was an impressive project.