Project Description:
Oak Hill School District is exploring ways to use virtual environments for professional development and for training and evaluating performance of new teacher candidates by simulating a classroom with students (adults acting as students) in a classroom setting. Pre-service teacher candidates will participate in simulations of typical classroom behaviors, misbehaviors, and interactions and receive feedback and guidance from administrators, who will play the role of the students.

Project Contact:
Tracy Cole
Director of Technology & eLearning
Oak Hills Local School District
513.260.2899
cole_t@ohlsd.org

UCSIM Staff:
Project Manager: Chris Collins (OS: Fleep Tuque)
Lead Programmer: Matt NeCamp (OS: Matthaus Highwater)
Avatar Design: Ayan Daniels (OS: Ayan Deluxe)
Animation Design & 3D Modeling: Alex Davis (OS: Alex Davis)


Child Avatars

Requirements:
– A total of 6 avatars are needed, 3 male and 3 female
– Target age and appearance avatars should be in the late childhood/pre-teen stage of adolescence
– Avatars should range in skin tone, body type, and hair color
– Avatars should be modestly dressed

ohsd_avatars_grouped

Child avatars designed for Oak Hills School District classroom project.


Classroom Space

Requirements:
– Classroom should accommodate up to 20 avatars to simulate a full class of students
– Desks should be arranged in small group clusters
– Where possible, Oak Hills SD logos and color schemes should be used

ohsd_classroom_snapshots_001


Behaviors Control Panel (HUD)

Behaviors Control Panel

Initial design of the control panel version 1.0.1, fully expanded.

Requirements:
– The behavioral control panel that the administrators will use should have a low footprint on the screen to reduce visibility issues and should be clearly labeled and intuitive to use.

– The entire control panel should be minimizable by the user with a single click of the power button.

– The control panel will have four main menus representing different categories of behaviors/actions.  These menus can be opened or closed independently of the others.

– Each behavior button should trigger an animation/action, a text blurb in local chat about the action (“Fleep Tuque nods yes.”), and potentially a sound function.

– An “LED” indicator light should show which menus or actions are currently active/playing.

– An information screen should provide contact info and other details about the development of the control panel.

– A help screen should provide instructions for how to use the control panel.