Gear Gurus 2.0 CSA Mini Project Review Ticket

[hsinaDitaM]

Team

Crossover Score	Runtime	Initial Plan & Reflection	Repositories	Analytics
0.85	Link	Plan and Retrospective Review	Frontend & Backend	Frontend & Backend

Individual: Soham

Crossover Score	Video	Runtime	Key Commit(s)	Analytics
0.86	Link	Link	Sorting & Database & Frontend	Backend & Frontend

Individual: Mati

Crossover Score	Video	Runtime	Key Commit(s)	Analytics
0.845	Link	Link	Frontend & Backend	Frontend & Backend

Individual: Aniket

Crossover Score	Video	Runtime	Key Commit(s)	Analytics
0.84	Link	Link	Backend & Frontend	Frontend & Backend

[JasoXDDD]

Individual Review "Haoxuan" grading "Mati"

• [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.84, no talking)
• [x] Issue(s) that show plans/progress to team objectives (0.85)
• [x] Highlights of key commit(s) in Issues, summarizes code contributions (0.85)

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

  Per check.
  0.845 extra efforts

  Freeform comment.
  Made major contributions in both the Frontend and Backend, made the art that can showcase fibbonacci sequences, and showcased sorting in the main project.

[anawandh]

Individual Review Aditya Ajay Nawandhar grading Soham K

• [x] Soham showed that they were a key contributor to both repositories through his commits and working project. He also displayed knowledge when presenting his code and information. Their plans were present as well.

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

• [x] Video, includes Web demo of key contribution to project, 1 minute --> 0.79 (used captions)
• [x] Issue(s) that show plans/progress to team objectives --> Was present in the ticket (0.8)
• [x] Highlights of key commit(s) in Issues, summarizes code contributions --> Did all sorts and frontend w/ backend himself. 0.85

• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks --> ( See comments below) 0.85

  Per check.
  0.8 + 0.85+0.85 + 0.79 / 3.6 = 0.86/0.9

  Freeform comment.
  Many commits (highest) on both frontend and backend. A lot of greens and reds in the commits showing addition of work and less copy pasting. Completed 4 diffrent sorts along with inheritance in code, use of extends and also aspects of analysis using time objects. Could have made the child classes in diffrent files for easier readability.

The video was good but no audio. the video showed all work could have focused on main points. The demo of the application was great and showed testing using postman.

Writing code for all 4 sorts and also the frontend. Analytics were good as well. 0.86

[tanishapatil1234]

Team Review "Tanisha" grading "Gear Gurus "

• [x] The team should have a Web Page(s) that teach/explain: Fibonacci, Algorithm, etc. 0.85
  • Yes, the visual for fibannoci was a good visualization. Interesting art work.
• [x] The team should have a Web Page(s) that teach/explain: Sorting, Timing, Compares Swaps, etc. 0.9
  • Their table is very interesting. Displays sorts and other analysis.
• [x] Team Review ticket containing key Team and individual contributions 0.8
  • Yes, team review contains all individual contributions. However commits are a little sporadic.
• [x] Growth/Accomplishments in workis according to historical Team Plan, or they show revisions to plan according to work. 0.8
  • They were originally planning to incorporate visualizing the sorting (moving cars) but they changed their plan due to time restrictions
• [x] Short falls/Improvement that could be made in Work or Team Plan, team highlights next steps or improvements that could be made 0.83
  • Again they highlighted there improvements of adding animation to the cars sorting.
• [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. 0.9
  • Sorting algorithms displayed inheritance, no static classes

• [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... 0.8

  • I liked the interaction with the artwork, also I like the table

  Per check.
  .9+.8+.83+0.8+0.8+0.8 +0.9+0.85/7 = 0.84

  Freeform comment.
  Provide positivies and growth summary.
  Justify or comment on final score.

All criteria met, presentation was retrospective about adding animation in the future. The reason I gave above a 0.8 is because they included a table with analytics. This showed understanding of the sorting algorithm to a greater degree and was something not explicitly required.

[tanishapatil1234]

Individual Review "Tanisha" grading "Aniket"

• [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.8
  • Video is made, discusses contributions. However video has no audio only captions
• [x] Issue(s) that show plans/progress to team objectives. 0.8
  • Yes, had plans and objective outlined. Not linked in individual ticket but plans exist.
• [x] Highlights of key commit(s) in Issues, summarizes code contributions 0.9
  • Yes, highlights key commits which summarize code contributions.
• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks 0.9
  • Yes commits on both frontend on backend started off/ended of slow but throughout the three weeks were fairly consistent.

Per check.
(0.8 + 0.8 + 0.9 + 0.9)/4 = 0.85

Freeform comment : Aniket had a good amount of contributions to his team. He mostly worked on the Fibonacci visualization which was unique. He mentioned that he hopes to try more OOP methods in his Java instead of imperative. This shows growth and understanding of the requirements.

[AniCricKet]

Project Summary

Initial Plan

Our initial plan was to build a virtual car website focusing on electric cars from notable brands such as BMW, Chevrolet, Tesla, and Lucid. In terms of the backend, we deployed and rebuilt using Spring, incorporated an image database for car visuals, implemented car classes with inheritance, used a simple database to store car information, and integrated a sorting algorithm. On the frontend, we created an appealing display of cars with images and specifications, maximized layouts and includes for blogs and timeboxing, and built tables for each company. For integration, we developed API endpoints, established communication via AJAX or Fetch API for real-time updates, and implemented a random car generator.

Changes we made to the plan

Originally, we misinterpreted the requirements and thought of this project more as a passion project and that's why our idea was a car showroom. Then, to make our project meet the requirements for sorting algorithms, we sorted the cars by price and showed the comparisons of the different space and time complexities for 4 different sorting algorithms. And to incorporate fibonacci, we made a fibonacci art feature, which designs a unique art piece made out of circles, inspired by wheels, based on a fibonacci sequence.

Issues we ran into:

Fibonacci Problems:

1. Magic Numbers: There are several magic numbers in the code (e.g., 20 in recursiveDraw, 300 and 200 in recursiveArtWithBinet). These made part of the code difficult to understand and cause confusion.
2. Random Number Usage: The randomHSLColor method generates random HSL colors. Which sometimes isn't visually appealing
3. Code Redundancy: There is some redundancy in code, particularly in the initialization of the list of Supplier objects. Which made debugging difficult.
4. Error Handling: The code does not include error handling for potential issues, such as invalid input for the Fibo constructor or potential exceptions during matrix operations.

Sorting Problems:

1. Unable to call the car database from another backend file
2. Unable to sort pictures along with data
3. Statistics were not being counted properly so I had to do each sort on paper to make sure it was accurate.

Future improvements

Some things we were thinking of were having animations to help the user visualize how the sorting algorithms work, rather than just see the comparisons in time durations and swaps of each. It would show each card visually move across the screen into the correct position.