Presentation is loading. Please wait.

Presentation is loading. Please wait.

Background The Game Architecture Lessons Learned Q & A Web-Services Game Architecture PRESENTED BY Robby Robson, Eduworks Corporation Based on Science.

Similar presentations


Presentation on theme: "Background The Game Architecture Lessons Learned Q & A Web-Services Game Architecture PRESENTED BY Robby Robson, Eduworks Corporation Based on Science."— Presentation transcript:

1 Background The Game Architecture Lessons Learned Q & A Web-Services Game Architecture PRESENTED BY Robby Robson, Eduworks Corporation Based on Science Built by Engineers Perfected by Designers Powered by Eduworks DRAFT VERSION – TO BE UPDATED

2 Motivation 5.5% of school-aged children in the U.S. received special education for a learning disability Working memory functions play a key role in student's ability to learn. Working memory refers to the ability to store and manipulate information for brief periods of time. Correlation between working memory measures and achievement have been found to range between.55 and.95. Program designed to enhance working memory capacity and executive skills in 7 to 9 year old children 3/30/2012Web-Services Game Architecture2 *NIH Project 1R43HD A2 Memory and Executive Skills in Youth with Learning Disorders* Informally called “Learning Disabilities Cognition” or “LDCog”

3 Background Developed under direction of the Oregon Center for Applied Science (www.orcasinc.com)www.orcasinc.com ORCAS Team: – Dr. Catrin Rode (Principal Investigator) – Kevin Prier (Project Manager) Eduworks Team: – Andy Purviance (Creative / Game Design) – Aaron Veden (Software Engineer) 3/30/2012Web-Services Game Architecture3

4 Process 1.Cognitive Design – Memory exercise interspersed with problems – Game dynamics to improve engagement 2.Creative Design – PowerPoint Prototypes – Agile Development 3.Technical Design – HTML5 (used Adobe Edge) – Private Cloud / Web Service Architecture 4.Experimental Design – Testing in schools 3/30/2012Web-Services Game Architecture4 RAPID APPLICATION DESIGN: 6 weeks of cognitive and creative design 6 weeks of development (elapsed)

5 3/30/2012Web-Services Game Architecture5 The Game

6 3/30/2012Web-Services Game Architecture6 Several times Then 1.Remember a number (fast) 2.Do a math problem 3.Repeat steps 1 & 2 4.Remember all the numbers you have seen, in order

7 Remember! 3/30/2012Web-Services Game Architecture7

8 3/30/2012Web-Services Game Architecture8

9 How much? $.90 $.85 3/30/2012Web-Services Game Architecture9

10 Remember! 3/30/2012Web-Services Game Architecture10

11 3/30/2012Web-Services Game Architecture11

12 Fill in the blank! /30/2012Web-Services Game Architecture12

13 Remember! 3/30/2012Web-Services Game Architecture13

14 3/30/2012Web-Services Game Architecture14

15 What’s the number? /30/2012Web-Services Game Architecture15

16 Remember the order? /30/2012Web-Services Game Architecture16

17 Game Video 3/30/2012Web-Services Game Architecture17

18 Game Architecture Developed in HTML5 using Adobe Edge Game dynamics implemented using JavaScript Hosted in private cloud Desktop client used Web services to get and report data 3/30/2012Web-Services Game Architecture18 Web Server (HTML5) Web Server (HTML5) Computer in School Data Collection Service Live Monitoring of data User Mgmt Service

19 Cloud Architecture 3/30/2012Web-Services Game Architecture19 ORCAS Web Server VM - Web pages and services Router - passes web requests to the cloud gateway VM. Gateway VM - proxy requests to other VMs. Single web entry point. DB server VM - houses data. Not available to outside access. Physical machines running cloud End user accessing service through web browser

20 Architectural Advantages: 1.Maintenance:Can make updates more easily Aided by rapid web service development framework 2.Separation:Can reuse services separately 3.Security:Can protect identity more easily 4.Elasticity:Can scale up and down quickly 3/30/2012Web-Services Game Architecture20

21 Using the Cloud for Learning: The Grand Vision 3/30/2012Web-Services Game Architecture21 “Bob” is the user * Data and content are stored in the cloud Bob use services that live in the cloud. Bob’s services access other cloud services Some may know about Alice and Charlie Some know about Bob *He may be your uncle, too.

22 HTML5 Experience Chosen for cross-platform capabilities Used Adobe Edge – Good for designers (WYSIWYG) – Good for engineers (usable code / hooks for custom code) Used Flash to export multiple variations on graphics Challenges – Playing audio – Synching audio to on-screen events – Slow connection to one school (downloading background graphics) 3/30/2012Web-Services Game Architecture22 tags do not work well for kids (replaced by buttons)

23 Research Results 3/30/2012Web-Services Game Architecture23

24 Conclusions What worked well – Web service architecture – Rapid application development – Made good use of the tools we knew – CSS3 (all animations are in CSS3) – Live debugging in schools Challenges – Multimedia in HTML5 still evolving – Live debugging in schools 3/30/2012Web-Services Game Architecture24

25 Questions and Answers? Thank you! Based on Science Built by Engineers Perfected by Designers Powered by Eduworks 3/30/2012Web-Services Game Architecture25


Download ppt "Background The Game Architecture Lessons Learned Q & A Web-Services Game Architecture PRESENTED BY Robby Robson, Eduworks Corporation Based on Science."

Similar presentations


Ads by Google