Background The Game Architecture Lessons Learned Q & A

25
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

description

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

Transcript of Background The Game Architecture Lessons Learned Q & A

Page 1: Background The Game Architecture Lessons Learned Q & A

• 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

Page 2: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 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/2012

*NIH Project 1R43HD062245-01A2

Memory and Executive Skills in Youth with Learning Disorders*

Informally called “Learning Disabilities Cognition” or “LDCog”

Page 3: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 3

Background• Developed under direction of the Oregon

Center for Applied Science (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/2012

Page 4: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 4

Process1. 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

Architecture4. Experimental Design

– Testing in schools

3/30/2012

RAPID APPLICATION DESIGN:• 6 weeks of cognitive and creative design• 6 weeks of development (elapsed)

Page 5: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 53/30/2012

The Game

Page 6: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 63/30/2012

Several timesThen

1. Remember a number (fast)2. Do a math problem3. Repeat steps 1 & 24. Remember all the numbers

you have seen, in order

Page 7: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 7

Remember!

43/30/2012

Page 8: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 83/30/2012

Page 9: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 9

How much?

$.90 $.853/30/2012

Page 10: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 10

Remember!

33/30/2012

Page 11: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 113/30/2012

Page 12: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 12

?

Fill in the blank!

600, , 1000, 1200

700 8003/30/2012

Page 13: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 13

Remember!

63/30/2012

Page 14: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 143/30/2012

Page 15: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 15

What’s the number?

40 30

701 ?

3/30/2012

Page 16: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 16

Remember the order?

1 2 34 5 67 8 94

36

3/30/2012

Page 17: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 17

Game Video

3/30/2012

Page 18: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 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/2012

Web Server(HTML5)

Computer in School

Data Collection

Service

Live Monitoring of

data

User Mgmt

Service

Page 19: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 19

Cloud Architecture

3/30/2012

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

Page 20: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 20

Architectural Advantages:

1. Maintenance: Can make updates more easilyAided by rapid web service

development framework

2. Separation: Can reuse services separately3. Security: Can protect identity more easily4. Elasticity: Can scale up and down quickly

3/30/2012

Page 21: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 21

Using the Cloud for Learning: The Grand Vision

3/30/2012

“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.

Page 22: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 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/2012

• <A> tags do not work well for kids (replaced by buttons)

Page 23: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 23

Research Results

3/30/2012

Page 24: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 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/2012

Page 25: Background The Game Architecture Lessons Learned Q & A

Web-Services Game Architecture 25

Questions and Answers?

Thank you!

Based on Science • Built by Engineers • Perfected by Designers • Powered by Eduworks3/30/2012