Part 1: Begin With The Running Program From Your Phase 4

Part 1begin With The Running Program From Your Phase 4

Part 1begin With The Running Program From Your Phase 4

Begin with the running program from your Phase 4 Individual Project where the examination question class hierarchy was fully implemented in a menu-driven program. An exam class was developed to load the exam from a file and display each question to the screen.

Modify the program from part 1 to change the menu to the following: Load an exam, Take an exam, Show exam results, Quit.

Choice 1: No functionality change. Load the exam based upon the user's prompt for an exam file.

Choice 2: The program should display a single question at a time and prompt the user for an answer. Based upon the answer, it should track the score based upon a successful answer. Once a user answers the question, it should also display the correct answer with an appropriate message ("Good job" or "Better luck next time"). Upon completion of the exam, the program should return the user to the menu.

Choice 3: The program should display the total points available and the total points scored during that exam. A percentage score should also be displayed. (Optional: if you choose to track which problems were missed, you could display that information for the user.)

Choice 4: No change to this functionality from the Phase 4 IP. You should consider creating an additional class Student that will track student's score through methods such as addPointsPossible, addPointsScored, getPointsPossible, and getPointsScored. You should also enhance your Exam class to include methods getPointValue and getAnswer. You may also want to add a method to only display one question at a time, such as displayQuestion.

Paper For Above instruction

The project involves modifying an existing menu-driven examination program to enhance its functionality and incorporate object-oriented programming principles. In the initial phase, the program supported loading questions from a file and displaying them. The task now is to reconfigure the interface and add features that improve user interaction, scoring accuracy, and code extensibility.

The revised menu should center around four primary options: loading an exam, taking the exam one question at a time, displaying results, and quitting the program. The first choice requires no change—simply load the exam from a specified file. For this, the existing file handling and exam-loading mechanisms will suffice, but the program should prompt the user for the filename each time they opt to load an exam.

The second option involves presenting questions individually. To do this efficiently, the exam class should include a method such as displayQuestion that outputs a single question in a user-friendly format. When a question is presented, the user inputs their answer. The program then compares this answer with the correct response, which should be retrievable via an added getAnswer method in the exam class. Based on the correctness of the answer, the program updates the user's score and displays a message to reflect their performance, such as “Good job” for correct answers or “Better luck next time” for incorrect ones.

To manage scoring, it is advisable to introduce a Student class that tracks points earned and points possible throughout the exam lifecycle. This class would include methods like addPointsPossible, addPointsScored, getPointsPossible, and getPointsScored, providing encapsulation and better organization of score-related data. As questions are answered, these methods would be called to keep an accurate tally.

The third menu choice involves summarizing the exam results. The program should display total points possible, total points scored, and calculate the percentage score, possibly including a list of missed questions if that feature is implemented. This will likely utilize methods from the Student and Exam classes, such as getPointsPossible and getPointsScored.

The quit option returns control to the main menu, effectively ending the program session or prompting for further actions if necessary. Overall, these enhancements will make the program more interactive, informative, and modular, adhering to good object-oriented design practices.

References

  • Gaddis, T. (2018). Starting Out with Java: From Control Structures through Data Structures (6th ed.). Pearson.
  • Deitel, P. J., & Deitel, H. M. (2019). Java How to Program (11th ed.). Pearson.
  • Giordano, C., & Livshits, B. (2017). Object-Oriented Programming in Java. Wiley.
  • Horstmann, C. S. (2018). Core Java Volume I--Fundamentals (11th ed.). Pearson.
  • Ericson, C. (2018). Real-Time Collision Detection. CRC Press.
  • Object-Oriented Programming Concepts. (2020). IEEE Software, 37(2), 87–89.
  • Java Documentation. Oracle. https://docs.oracle.com/javase/8/docs/api/
  • Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley.
  • Martin, R. C. (2008). Clean Code: A Handbook of Agile Software Craftsmanship. Pearson.
  • Robert C. Martin. (2009). Agile Software Development, Principles, Patterns, and Practices. Prentice Hall.

Related Assignments