search

ridhimainukurti / p1-Valid

CSA Course Guide
1 stars 0 forks source link

Ridhima's and Rini's FRQ Grading #42

Open ridhimainukurti opened 2 years ago

ridhimainukurti commented 2 years ago

RIDHIMA's GRADING

Feature Evaluation Score Grader
Each individual has GitHub Page, Wiki, or deployed Web Page that Highlights talking points and learnings from each FRQ Rini
Each Individual has their own set of FRQs running under one page or menu (ie Deployed Java/Spring or Replit) plus a 1 minute video Rini
Each Individual has GitHub of source for every FRQ that is integrated with Deployed Java/Spring or Replit Rini
At least 2 FRQs with input and output + FRQ's Guidelines Rini

Comparison of 3 FRQS:

Unit 2: My crossover partner has the code hardcoded with print statements however I had written the code in such a way that it was flexible enough and could ask for user input making it more flexible to the user.

Unit 6: My crossover partner had set a predefined list of words ending in ing while I let the user input words ending in ing. An improvement for me would be to specify the list or predefine it since it would make my code run easier

Unit 9: My crossover partner had really done a really good job of incorporating the main method within the FRQ file so that when you call it within the main.java file all you would need to do is call the FRQ9 file in order for it to run. An improvement for next time would be the implement this strategy so that in my main.java it wouldn't be cluttered with all the code and gives it more of a smooth run in repl as well

My Reflection: One of my strengths that I realized was that I had made the code soft coded where I asked for the user input a lot in my frqs making it more flexible to the user when they ran my FRQS. However one thing I noticed was that my partner had written the code in such a format that it would run smoothly especially with adding the main method within each frq and just calling it within the main.java made her main.java run easier. Also I saw my partner's guide on how to run her frqs and there were pictures and tangible that made it extremely easy for the user to know how to operate her code. I thought this was a good idea and decided on implementing this.

rkwreck commented 2 years ago

  1. (+) Learnings from each FRQ, good job on including tangibles for each FRQ. ✅

  2. (-) All of your FRQs run with working menu ✅ Directions are unclear sometimes, like with FRQ 3 when it prompts the user for "Enter a string for option2", what does option 2 mean? (-0.15) ❌ You have inputs on most FRQS, exceeding requirement. However, after running FRQ 4, the menu runs into an error and exits itself (-0.15) ✅

  3. (+) Github source is present for each FRQ w/ READMe ✅

Good job on organized ticket, easy for grader to follow, and including images on your wiki pages

Overall Score: 9.7/10