Changes

==Prototype Notes==

==Prototype Notes==

A few things about my prototype. It's designed to get across the ideas of possible functionality, not actually be a fully working completely accurate prototype. I've hardcoded a lot of stuff which won't be in the actual program. Please evaluated it based on what it implies it would/could do, rather than what it actually does (example: numbers for percentage are wrong, but implies that they would be displayed and displayed correctly). Things to note about it are as follows: <br \>

A few things about my prototype. The final program will be in Python, the prototype is in flash because I know Actionscript and am able to quickly make a prototype with it. It's designed to get across the ideas of possible functionality, not actually be a fully working completely accurate prototype. I've hard coded a lot of stuff which won't be in the actual program. Please evaluated it based on what it implies it would/could do, rather than what it actually does (example: numbers for percentage are wrong, but implies that they would be displayed and displayed correctly). Things to note about it are as follows: <br \>

- The 1st screen is what the teacher would see, and have the opportunity to input a question, an answer, as well as the maximum time the students will have to answer. Then they would click send/submit and the students would recieve the question on their screens. <br \>

- The 1st screen is what the teacher would see, and have the opportunity to input a question, an answer, as well as the maximum time the students will have to answer. Then they would click send/submit and the students would receive the question on their screens. <br \>

- The 2nd screen is what the student would see after the teacher submits a question. The teachers question is displayed as well as a timer and a space for an answer. When the timer runs out, an answer is submitted regardless, otherwise the student can just input an answer and send/submit it. <br \>

- The 2nd screen is what the student would see after the teacher submits a question. The teachers question is displayed as well as a timer and a space for an answer. When the timer runs out, an answer is submitted regardless, otherwise the student can just input an answer and send/submit it. <br \>

- The 3rd and 4th screens are both for the teacher. The 3rd screen is the general statistics of the class: Percent that got it correct, the number of students that selected each answer, the average time it took them to answer. The 4th screen is a representation of the class room organized by the name of the XO per student. The teacher can hover over the XO symbol to see the XO's name immediately, and if they continue to hover over it (like in the XO user interface) more information about that particular XO will be displayed such as what answer was selected, and the exact time it took them to answer. <br \>

- The 3rd and 4th screens are both for the teacher. The 3rd screen is the general statistics of the class: Percent that got it correct, the number of students that selected each answer, the average time it took them to answer. The 4th screen is a representation of the class room organized by the name of the XO per student. The teacher can hover over the XO symbol to see the XO's name immediately, and if they continue to hover over it (like in the XO user interface) more information about that particular XO will be displayed such as what answer was selected, and the exact time it took them to answer. <br \>