Week 11 PBL Final

[kylem314]

Crossover Scores

Kyle: 9.5/10 Yajat: 9.5/10 Charlie: Rohan:

[kylem314]

Team PBL Final

Jekyll site: Running here

Runtime feature video: Video

[kylem314]

Individual PBL Final - Kyle Myint

Feature: College slideshow Commits: All by me and JS algorithm specifically Wiki ideas/planning: Wiki (Under Slideshow for Colleges Final code in project: Here Video displaying functionality/code: Video

[1855387]

Eric Wang Crossover Evaluation of Charlie Total Score: 9.8/10

Individual 4.9/5 MVC Feature: 1/1 point. Calendar is complete, easily accessible on the website, and works well in the project. Individual Commits: 1/1 point. Commits are clear. Wiki: 0.9/1 point. The calendar is very well done and aesthetic but it is mentioned in the wiki that a feature for notifications and reminders that is not implemented. However, because the calendar is so good only 0.1 is taken off because that feature could have been very impressive. Final Program Code: 1/1 point. Code is fully working. 1 minute video: 1/1 the pair video with Rohan summarizes work quite nicely.

Team 4.9/5 GitHub Pages .5 / .5 - PBL theme had a consistent theme and color throughout and is very aesthetically pleasing. .5 / .5 - Sassy / Bootstrap illustration in GitHub pages - Database - CRUD operations in the Database with the college list for adding/deleting colleges Deployed Project 24/7 - Entire project works at intellijs.cf Async Operation (ie JavaScript fetch) described in GitHub pages Runtime Features shown in 1 minute video - 1 minute video summarizes content quite well, highlights features decently but probably more emphasis on best features would be better. Scrum Board - Scrum board shown in video and looks organized. MVC Package - a code overview showing a complete MVC package with spotify and database. However, the video should have highlighted the MVC package more clearly as it is arguably the most important aspect of the project. Taking off 0.1 point for hti sreason. Search on project database tables, easy to identify from UI Google Search or Google translate clearly implemented in the navabar.

---

Pair PBL Final - Charlie Zhu and Rohan

Feature: Deployment and Google Search (Rohan) and Javascript Calendar (Charlie) Commits (Charlie): All by Charlie and JS algorithms used within the calendar Commits(Rohan): All by Rohan and JS for search

Deployment (Rohan):

Wiki ideas/planning for Calendar (Charlie): Wiki(Under Slideshow for Colleges) Wiki ideas/planning for Google Search (Rohan): Wiki Final code for Calendar (Charlie): Here Final code for Google Search (Rohan): Nav Bar Deployment Highlights (Rohan): steps

Video displaying functionality/code of both features: Video

[yajatyadav]

Crossover Grading Score: 9.5/10, Comments by Devam

Individual PBL Final - Yajat Yadav Video displaying functionality/code

Feature: College Database, Spotify API for Calming Music Commits: All by me Wiki ideas/planning: Wiki page on Database+Calming Music Final code in project:

• Music, View
• Database, View

[devamshri]

Crossover for Yajat Yadav.

Overall score: 9.5/10

Crossover grading for Devam:

Points Checklist:

Individual-

• [x] PBL MVC feature (1/1): Database and Spotify API. In the video, he shows how his college admission date deadlines so people could remember. He also added a Spotify API to help calm the nerves of super stressed-out students.
• [x] commit shows algorithm in Java (0.9/1): He does a good job depicting some of the Java code he has written for the database and the Spotify API.
• [x] Wiki contains design ideas and usage (1/1): The wiki is very well detailed and has a bunch of information on the code for what was the backbone of the
• [x] Final program code (1/1): Running and deployed
• [x] 1 minute video showing runtime (1/1): Very well depicted video for his own features which include a college admission date deadline database and a music Spotify API.

Overall score for Individual: 4.9/5. Yajat has everything required for the project. It could have been a little easier if he gave me specific commits to look at rather than the whole thing, but I think he did a good job completing the harder tasks, which include the database and the Spotify API. I really think that he put a lot of time and effort into AP CSA this trimester.

Team Score: 4.6/5

• [x] 0.5/0.5 PBL theme is described in Github Pages (college application service with some miscellaneous stuff for calming the stress of 12th graders)
• [x] 0.5/0.5 Very clear Sassy / Bootstrap illustration in GitHub pages with images from their css file.
• [x] 0.5/0.5 Database - Github Pages includes thorough explanation of CRUD operations and POJO for database
• [x] 0.4/0.5 Deployed Project 24/7 - Project was not deployed at the time of grading, but is usually deployed.
• [x] 0.4/0.5 Async Operation is described in GitHub pages, but image is broken so explanation is confusing.
• [x] 0.5/0.5 Runtime Features are included in an (actually) 1 minute video
• [x] 0.5/0.5 Scrum Board : Overviewed how their scrum board was being used throughout the trimester, which really showed how organized the team was throughout the trimester.
• [x] 0.5/0.5 MVC Package : They did have a database that fit with the main theme of their project where they could add colleges and demonstrates the main MVC functionality of their website.
• [x] 0.3/0.5 Search on project database tables: not highlighted in video and not very easy to find on the runtime, but I figured it out and it has good functionality.
• [x] 0.5/0.5 Google Search: implemented and overviewed in video. In the navbar of the project.

[wrachel]

Grading for Kyle:

Graded by: Rachel

Individual Score: 4.9/5 Reasoning:

• 0.9/1 - One PBL MVC feature - He has one feature he worked heavily on and fully understands (as demonstrated in his 1 minute video), and he is able to describe the JS algorithm he developed. The only thing I would take off for is that there could be more user interaction in the feature that he developed (-0.2).
• 1/1 - Everything is very organized and easy to find. He has all his commits linked, and the commits that deal with the JS algorithm.
• 1/1 - Wiki with design ideas and usage - He has also linked his wiki which is very thorough.
• 1/1 - Final program code - links his program code and the files that contain the code that he wrote.
• 1/1 - A 1 minute video -His one minute video is actually one minute (which is very nice!), and also very thorough, as he highlights the feature that he developed really well.

Team Score: 4.6/5

• 0.5/0.5 PBL theme is described in Github Pages (college application service)
• 0.5/0.5 Very clear Sassy / Bootstrap illustration in GitHub pages with images from their css file.
• 0.5/0.5 Database - Github Pages includes thorough explanation of CRUD operations and POJO for database
• 0.4/0.5 Deployed Project 24/7 - Project was not deployed at the time of grading, but is usually deployed.
• 0.4/0.5 Async Operation is described in GitHub pages, but image is broken so explanation is confusing.
• 0.5/0.5 Runtime Features are included in an (actually) 1 minute video
• 0.5/0.5 Scrum Board : in video they overviewed how their scrum board was being used throughout the trimester which was a big plus.
• 0.5/0.5 MVC Package : They did have a database that fit with the main theme of their project where they could add colleges and demonstrates the main MVC functionality of their website.
• 0.3/0.5 Search on project database tables: not highlighted in video and not very easy to find.
• 0.5/0.5 Google Search: implemented and overviewed in video.

Total Score: 9.5/10