My goal for this project is to create and distribute a prototype for a project idea that I have. I'm hoping to get feedback and functionality requests in regards to the prototype. In the end, I hope to create a final design document that will be able to be used along with my prototype to create a useful teacher tool that will assist teachers in understanding more about their students knowledge.
Eventually, this project is going to be a program for the teacher to use to test students on their knowledge of math. The results will then be displayed to the teacher. The results will include things like % of users that answered the question correctly. A graphical display of what all of the submitted answers were and how many of each student picked that answer. The average time of student answers. And finally, a graphical display of all the students in the activity that when hovering over any particular student, will show the individual statistics about the student. This will help the teacher learn quickly what the weak points of the class as a whole are, as well as each individual student. With this knowledge the teacher easily determine what topics require more time for the students to learn. Teachers will be able to run the activity and students will be able to join. Hopefully we'll figure a way to efficiently connect somewhere between 10-15 students to each teacher. Also, currently the project will call for the teacher to input the question, answer, and amount of time to be given to the students to answer. Ideally the schoolserver.rit.edu will be able to host 'packets' of pre-made questions that the teacher can download and use.
If you are a teacher and want to evaluate my project, please either click here or look just below to run the prototype. It will launch in the same window, so when you're done hit the back button to get back to this page. Please read the prototype notes as it explains what each screen is for. Once you're done running it, please go here to discuss it (or once again look below). The latest version is where you would add your input. If you need any help or would just prefer to individually contact me feel free to send me an email at firstname.lastname@example.org
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:
- The 1st screen is what the teacher would see, and have the opportunity to input a question, input up to 4 answers, as well as select the correct answer. They would then click on answer to send the question out to the students.
- 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 all of the possible answers submitted by the teacher. It currently only supports 4 but I'd like to allow the teacher to determine how many possible choices there are. When the timer runs out, an answer is submitted regardless, otherwise the student can just input an answer and send/submit it. Currently I have the problem of the correct answer still being selected, I cannot figure out how to fix it in flash right now, but that won't be the case in the final version of the activity.
- 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.
Please see the related pictured below as well
I lack some art skills (sorry)
^^This is a concept for the final screen in the prototype. It will have the XO names right below the symbol, and the symbols will be highlighted red or green based on whether or not they answered correctly. Hovering over the XOs for a little bit will then show additional information like the last screen in the prototype. There should be back buttons added to go back to the previous screen as well as a 'ask another question' button and a 'end questioning' button.
1) Design Doc(done)
Need - Design GUI interface and layout - Finalize remaining milestones Want - Learn Python(not done at all)
2) GUI Layout(done)
Need - Finalize GUI design and layout - Get screen shots of GUI design and layout onto the wiki(linking directly to the flash) Want - Learn more Python(not done at all) - Get GUI design and layout out to community and get feed back right away on it(soon to be done)
3) Create GUI
Need - Actually make GUI in python - Finalize ideas about the rest of prototype (how much I can do with remaining time) Want - I/O with user (just input text and using it)
4) Create the rest of the prototype
Need - Complete prototype
Need - Get it out to the community and get feedback Want - Find a developer or two interested in coding actual functionality
6) Finalize Design Doc
Need - Using information/feedback from community, create a final design document and get it out to the community Want - Find a developer or two interested in coding actual functionality
I'm doing the prototype in flash for ease of distribution and because I can get it out quicker. I'm literally a day or two away from being able to distribute it to the whole world and ask for feedback. Keep an eye on 'Project Files/Git' for a link to the flash application.
The end goal for this project currently (for me) is to end up with a final design document for a project that the community has deemed useful and necessary. If you're interested in helping me, or working on the actual implementation after the design doc has been created, let me know. If you have any questions or concerns or requests please please PLEASE let me know so I can address them as quickly as possible.
Alex Jones email: email@example.com
^^frequently on #sugar