Applied Simulation
Today is our last day so we'll wrap up the semester. I'll collect the Cell Phone papers, then I'll have just a few final words and take a few closing comments. Then you're done! Topics
Homework
Topics:
Homework:
Topics: Homework:
Yet another brief day as all we have to do is see Luke's presentation from last week. Topics:
Homework:
Today is a very brief day to let you start your Thanksgiving a bit early. Topics:
Homework:
Topics
Homework
I don't think it's possible for the day to get any simpler. Topics:
Scavenger Hunt:
Topics: Homework:
Topics:
Homework:
Topics:
Homework:
Topics:
Homework:
Today we tackle the issues surrounding the second half of your "final" project. ...among other things...
Homework
Topics:
Homework:
No Class in the classroom today. Please take this time to work on your Software Simulation Instructional Design packet. They're due next Thursday!
Topics:
Homework:
Topics:
Homework:
Topics:
Homework:
Three Real Life Sims: Bobby, Alex, & Brian Topics:
Homework:
Oct 2, 2007 No SL Presentations today. Topics:
Homework:
Sep 27, 2007 Two Real Life Sim presentations. Bobby & Jesse Topic: Homework:
We begin by checking out the "bling" and see what you've come up with. Then we'll have a Second Life Sim presentation by Brian. After that, we'll visit another couple of locations that I have found.
Scavenger Hunt : A pet of some sort. We'll meet at the Beach House and show them off.
Real Life Simulation Presentation by: Bobby Topics: Homework:
Second Life Sim: Mike Other places by Damian Homework
Real Life Sim: Jerilyn Topics:
Homework
Today we meet in Second Life at 11am.
Here are the topics we will be covering today:
Homework
Sep 4, 2007 Today we meet in Second Life at 11am.
Today we meet in the classroom lab.
Today we meet in Second Life. Homework:
|
APPLIED SIMULATION -Ventrilo Information- On the surface, software simulation sounds exactly like what it is: using one software package to simulate another software package. Usually this is done for training purposes. The easiest way I've found to explain it is to share the story of how I got involved in the process. Many years ago, the Canadian version of the DMV created a new software package that would track drivers' licenses, license plates, and insurance...among other related information. All the DMV agents had to use this new software, which meant they all had to be trained how to use the new software. So the Canadian DMV contacted the company that I worked for and hired us to create the training. They sent us copies of their software, helped us to install it and get it working on our system, and gave us dummy-data to work with. Our Instructional Design team then talked to the DMV to find out specifically what they wanted to train their learners. Then our ID team spent a great deal of time working with the software in order to themselves learn how the software worked and all the ins-and-outs of the involved processes. Then they created the training lesson plans. After the plans were firmed up, they were sent to the graphics department and the programming department where our training program was created. Essentially---remember, we're talking about software simulation--we created a fake version of the DMV software that looked exactly like the real version--and in many instances worked just like the real version. On top of this simulation, we put our training. Typically this was a box of text containing explanation and instructions. Frequently, the textbox would be accompanied by audio-voiceovers. The textbox explained the workings of various buttons, fields, and other on-screen elements, as well as explained the processes that the learner would be involved in when using the real program. In addition, the textbox frequently had a collection of buttons that would allow the learner to repeat an instruction, back up to a previous step, or get additional help. Typically, the simulation would be divided into a number of lessons. Each lesson dealt with a particular topic or process and would walk the learner through the process step-by-step. For instance, if we wanted to teach the learner how to create a record for a new driver, the textbox might say:
Depending on the instructional design, the textbox might include a graphic of the button. A giant red arrow might also appear on the screen pointing to the button. The user would then click on the button and our simulation would react exactly as the real program would; the screen might change, dialog boxes would appear and need to be filled in, and so forth. If the user clicked the wrong button, the training-half of the simulation would provide feedback and additional help, then again prompt the learner to perform the correct action. Once the learner had completed all the actions in a particular lesson, a review might be given. Almost always some sort of qualifying test would then be run--again through the simulation, but without the step-by-step assistance. The textbox for this might only say:
The learner would then have to work his/her way through the process--in the simulated environment--to pass the examination. Along the way, the CBT software may be recording data about the learner's movements, such as tracking how many tries he took before successfully completing "the next step" of the process. This data is then evaluated--either by the simulation engine or by a human who looks at the data--to determine if the learner has successfully learned the information and has qualified to move to the next lesson or to begin working with the actual software. Many times the CBT training is wrapped in some sort of encompassing theme to make the training process less dry. For instance, the DMV CBT I mentioned was wrapped inside a...racing board game. The learner had a token--a race car, no less--that he moved around the board. Each square on the board was a lesson simulation. The textbox and all the other CBT elements, therefore, had a similar racecar board-game feel. Checkered flags, red-and-green lights, and so forth were all designed around this "fun" theme. Such a complex learning environment, however, also required a small training session in how to use the training software! So the first part of the CBT was an explanation of how the CBT environment, how to use the mouse, and the functions of all the textbox buttons.
For Northrop Grumman, I created a simulation of their at-that-time new browser-based materials requisitioning system. Initially, this was done in Toolbook then converted to a web-delivery style so that the user could take the training from their own workstations on the company LAN. I have taken one lesson and re-created it in Flash to use as an example of the sort of thing we're dealing with. (The recreation isn't a perfect recreation. Time has not been on my side this semester.) |