FRQ review- Yajat and Harry

[wiz124]

FRQ crossover Analysis and FRQ

FRQ2

• Mine was implemented into PBL with user input while Yajat's was in Replit
• We both had inputs for all parts of the FRQ. One key difference was that my FRQ was more convenient to see the results of a user's input. Yajat's code required multiple runs in order to show all aspects of the FRQ.
• My FRQ however, requires input in all fields which could be annoying for a user who wants to see only one certain output. In this case, Yajat's FRQ would be more convenient.
• The code used to implement the FRQ was similar for both of us. We made use of constructors, substring function and Math.sqrt function as well.

FRQ3:

• My FRQ shows where to input and how many inputs are required. There is no menu to selecting a question number after selectin an FRQ unit in Yajat's FRQ.
• Mine showed my code used to code the FRQ and would be updated once the user inputs the required values. Yajats takes the user step by step through the process of answering the FRQ.
• Yajat's is missing question 1 part d which I have. In addition, his question 2 calculates the area of a square
• My question 2 is able to show a graphical representation of a user defined squared within the graphed region
• User interface is a lot cleaner in Yajat's FRQ. My question 2 and question 1 is bit of a mess visually. '
• A key difference is that I used a switch case statement while Yajat stuck with a if else statement when we answered question 1

FRQ4

• our question was same for the both of us. We had the use put in a string. Mine would take longer to produce results because it takes more clicks to use
• Our execution for question 1 was basically the same. We both used a for loop with two if statements. We would update the variable when a longer streak was found.
• For the coin game, our execution was also pretty much the same. We both used a while loop but I had more if statements to check for conditions. Yajat restructured his code to have a method that would check for certain conditions.
• Our implementation was a bit different. We had the same idea to have the user set the number of rounds but I gave the user the option to have players start with different amount of coins. I also had a visual representation of the final score. Yajat only had the user give same amount of coins to both players.

Summary: Overall, I think I did good in executing the FRQs and implementing them. I believe that my FRQs were convenient to access and easy to use. The inputs were all self explanatory and user friendly. In addition, I achieved transparency by have the code on the implementation to show the user how the result of the FRQ was achieved. One thing I could've done better is with the input design and error handling. Some of my FRQs can't handle certain inputs and require certain inputs to work like FRQ 8. Otherwise, it won't execute the FRQ algorithm correctly. Compared to Yajat's FRQs, my limited html knowledge caused me to have certain restrictions on user input for FRQs like FRQ 6 question 1. I wanted to have a user defined array but I didn't know how I would have dynamically changing input field. However, I was able to implement more FRQs than Yajat. Links FRQ links: https://taxevasion.pentahex.xyz/about/harry FRQ reflection: https://github.com/wrachel/TaxEvaders/wiki/Harry's-FRQ Crossover link:https://github.com/yajatyadav/intellijs/issues/29

[yajatyadav]

Overall score: 10/10, graded by Yajat Yadav

FRQs covered: 9/9

• All 9 of the FRQs are under management.
• There is a Wiki page that highlights key learnings, as well as challenges faced, for each FRQ. The key learnings are really in depth, but I would recommend adding code snippets of the FRQ next to the points you are talking about; for example, include the code showing recursion in your Unit 10 reflection.
• All FRQs are running on a deployed website. The website layout is user-friendly and makes it easy to navigate from one FRQ to another.
• There is a Github of source tracking the commits made to FRQs on the deployed webpage

FRQs with input/output: 9/9

• All parts of each FRQ have user input/output implemented on the website
• Based on the question, appropriate inputs (checkboxes, numbers, dropdowns, etc.) are used

Glows: You did a great job seamlessly integrating all of your FRQs onto your PBL. I also liked that you implemented input/output for all of your FRQs, and it worked correctly when I tried it with some values. Additionally, I liked how for the input, you used different tools, such as checkboxes and text boxes based on what the input type was (boolean, int, etc.). Finally, I liked how for each page, you included the code for the FRQ below the input/output section.

Grow: I would recommend changing your method of submitting inputs for the FRQ. For some of the questions, the user has to fill all the fields before being allowed to submit. This might not be helpful in some cases. For example, in Unit 2, the user might want to only change the light sequence and not have to reenter values for inserting a segment. Also, you might want to try handling some exception cases. For instance, when I try putting String values where an int should be, the code breaks, and instead you should handle such edge cases and display appropriate error messages.