Team Issue

[F1nnC]

Crossover Score	Runtime	Plan	Github	analytics
.83	Live	Plan	link	commits

name	crossover score	runtime	key commits	analytics
Finn Carpenter	0.85	Bars	Sorting Table, Fib Code Bars, Sorting Frontend	Profile, Frontend, Backend
Justin Nguyen	0.88	leaderboard	fixed sorting, built leaderboard, update leaderboard functionality, leaderboard issue	Profile, Frontend, Backend
Theo Huntalas	0.85	Sorting	Frontend - Linking to Backend, Backend - Inheritance and Sorting Handling	Profile, Frontend, Backend

name	video
Finn	Video
Justin	Video
Theo	Video

[aliyatang]

Individual Review "Aliya T" grading "Finn C"

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

  Freeform comment

• Worked on Fibonacci sequence (recursion, for, while loop)
• Good key commits showing contribution to backend and frontend connection
• Clear live explanation and video, presentation/demonstration, and explanation of code

• Good attempt and noted improvements for Fibonacci sequence animation. Had code but it didn't work.

  Per check.
  0.55 not attempted/no check 0.7 attempted, incomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.

Score: 0.85/0.9

[vivianknee]

Individual Review "Vivian Ni" grading "Theo Huntalas"

• [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
  • video has voiceover explaining code. Goes in depth on his part of the project
  • two videos. one on backend and one on frontend.
• [ ] Issue(s) that show plans/progress to team objectives
• [x] Highlights of key commit(s) in Issues, summarizes code contributions
  • explained what he did on frontend and backend. Created sorting API on the backend and did JS scripting on the frontend.
• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks
  • consistent commits and contributions on both backend and frontend

Per check. 0.55 not attempted/no check 0.7 attempted, incoomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.

Freeform comment.

• Made significant contributions to backend and frontend. Key developer for sorting API, including all 4 algorithms, setters, and getters. Designed fronted and coded javascript CRUD connections for backend

0.85/0.9

[vivianknee]

Team Review "AVK Team - Vivian" grading "JTF Team -Finn"

• [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.55 not attempted/no check 0.7 attempted, incoomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.

  Freeform comment.

  • visualization for fibonacci
  • lots of plans for improvement and ideas to advance the project
  • documentation for improvements throughout the 3 weeks

0.83/0.9

[DasMoge124]

Individual Review "Kevin: grading "Justin"

• [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
• Shows evidence of using 4 different kinds of sorting for specific numbers
• [x] Issue(s) that show plans/progress to team objectives
• Managed to document for improvements throughout the three weeks
• [x] Highlights of key commit(s) in Issues, summarizes code contributions
• Highlighted the key contribution of the leaderboard
• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

• Showed the key commits for the leaderboard.

  Per check.
  0.55 not attempted/no check 0.7 attempted, incoomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.

  Freeform comment.
  Provide positivies and growth summary.
  Justify or comment on final score.
  Be sure to provide extra details on anything below 0.7 average or above 0.8.

0.88 Successful integration in the backend and evidence of effort.

Improvements: Make the sorting results display Make the feature less simple and sorted by highest times. SASS, make the sass a lot simpler