1. multi Learn toby Escarez ethan Faust jacob Mrozek ji Mun chris Patterson anirudh Srinivas calder Thami

2. The Problem In 2008, the national average ratio of students to computers was about 3.8 Teachers have difficulty gauging student performance over time Parents would like to know how their kids are doing more regularly

3. Introducing multi Learn Educational game Originally developed for use in India – Allows 4 students to use a computer No way to view statistics…

5. How are you building on the results from Winter 2010? Teachers and administrators find online access to be most convenient Some teachers feel overwhelmed by the amount of information provided by current systems Current online feedback from games is not reliable Parents already have access to feedback online Students respond well to simple graphs such as progress over time

6. Implementation Plans What is your approach/architecture? – Web application – Uses PHP and MySQL What are the major components? – Script to import data from SQLite to MySQL – Scripts to generate web pages with relevant data – Scripts to generate graphs

7. Implementation Plans (Continued) Are there any important changes from what you originally planned? – Data conversion server side vs. client side

8. What have you accomplished so far? Which components/capabilities have you implemented? – Data conversion – Graphing – Teacher interface – Debugging client application Are all the major requirements taken care of? – No, automatic data upload is needed – Implement student/parent views

9. Interesting Details Conversion from SQLite to MySQL MultiLearn source code – Compiling on 32 vs. 64 bit systems – Windows XP vs. Vista vs. 7 – No Documentation –.NET Framework v4 (beta version) Created our own graphing framework

12. Prototype Demonstration

13. Evaluation Plan How will you know your solution is a good one? – In-class testing – Teacher feedback What criteria will you measure? – Usability – Suitability of displayed statistics

14. Target Users Who are your target users for 5-week build? – Teachers Who are your target users for the final build? – Parents, Students, and Teachers

15. What’s Left? What are the components/capabilities that are not yet implemented? – Automation of user data upload – Parent and Student access – Refining the interface – Additional graphs Do you foresee any major problems? – The game crashing

16. What’s Left? (Continued) What unknowns are left? – What kind of information is important to teachers – Compare data to state/national standards – Printing data – Current version of MultiLearn How will you address completing these missing elements and mitigating risk? – Feedback from teachers – Start with WA state learning targets – Obtain current code

17. Timeline for remainder of quarter In-classroom testing (Week 5) Bug-free prototype (Week 6) Integrate teacher feedback (Week 6- 7) Additional functionality (Week 8-9) – Parent/student login – Use of MultiSpell data – Printing Paper/poster (Week 10)