You have been asked to creating a fun quiz game on the history of computing. The quiz is to have at least 3 questions, of your choice, about the history of computers or computer programming.

Each question is to be presented, one at a time, to the user. After a question is presented and the user enters their response, the program tells them immediately if they got the answer correct or incorrect, with a statement about the correct answer if their answer was wrong.

Once the user has answered all three questions, the program presents them with a statement that includes their numerical score (e.g. 2 out of 3), and an encouraging message depending on how well they did, according to the chart below.

 

12 N Paragraph 1 2 Styles 3 W 4 5 Perfect! 2 Great! 1 Good! 0 Try again! Your submissions to this project will be in four parts, following the programming design cycle: Proj 1.1 - Understand the Problem [due Monday] Demonstrate your understanding of the problem by describing how your program will solve the program criteria. Include what questions you plan to ask, what type of input you expect the user to enter, the prompts you will use to encourage the user to enter valid data, the output that will be printed to the screen, and a description of the overall flow of the program. Include a flow chart with all prompts and outputs as part of your submission. (minimum 300 words) Proj 1.2 - Plan the Logic [due Wednesday] Write the pseudocode that implements the program described in your submission for Proj 1.1- Understand the Problem. Be sure to include comments, variable declarations, descriptive variable names, proper indenting and white space. If you find that your program can be improved with a modification to your original description, include a paragraph to document the changes made. Proj 1.3 - Write the Code [due Friday] Translate your pseudocode from Proj 1.2 - Plan the Logic into Python code. Upload the .py file. Proj 1.4 - Test the program [due Sunday] Describe how you tested your program from Proj 1.3 - Write the Code. Include the test data you used. State any limitations to your program: for example, document any types of user input that will "break" the program currently. Reflect on any debugging or maintenance you would wish to do if you were to put this program into production. (minimum 300 words)