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- Homework Assignment - Final Project Part Two: Production This is part two of your "final" assignment. Be sure to give it the attention that a regular "end of semester" final project warrants. In the previous part, you played the role of an Instructional Designer and created a 4-step training process for some aspect of some software. Now, the Great Student Randomalizer will randomly redistribute the instruction design documents amongst the class. The second half of your assignment will likely find you playing two roles. Role 1: Take the document that is assigned to you and create the software simulation that is described. Use Flash if possible as that allows us the easiest way to view the final product. If Flash is out of your range, then Powerpoint or some other package will suffice. The key, however, is that you simulate the original package as closely as possible within the confines of your development package. Hopefully, your instructional designer has provided you with the desired graphics, sounds, and so forth. Regardless, you are taking on all the development roles we discussed earlier, so you are (for the most part) your own graphics, audio, QA, and programming team. Create the training, and "deploy" it in such a manner that we can view it in class. Role 2: You are still the instructional designer and SME for your original document. If the person doing your programming is unclear on a step or process...or has some other difficulty with your design...he or she will need to be able to contact you for clarification. If you've picked some really odd software that is not readily available, you may have to provide the screenshots that your programmer requires.
Think and work smart! Yes, this is your big project and it's terribly important. But do remember: When you're in programmer mode, try to avoid being a burden on your instructional designer! Your designer is also a programmer for someone else, and she needs her time to write her program. Solve what problems you can on your own and really only contact your designer if you just don't have a clue. When you're in SME / ID mode, remember that your programmer may not have all the skills you'd like to have for your project. You might really, really want the thing done in Flash, but your programmer may not have or know how to use Flash. Be prepared to settle for a Powerpoint version of your training package. I will take the wierd dual-job issue into consideration with evaluating your work. But remember the goal of the whole process is to create a "workable" "simulation" of the original package. If the original button has a roll-over image, I'd like to see a roll-over image. If the button "pushes in" when clicked, I'd like to see that as well. (I won't scream and yell if I don't see 'em, but it's a bonus if you make it work.) Remember that drawing and entering text in fields is difficult to check for correctness. Program around it if you can. A standard way is to say, "In this screen, you enter the client's name which is Susan Smith. Click the Next button and we'll do it for you." Then..when they click Next, you move to the next screen that shows the field with the text in it. Then carry on with your simulation. Do the same for drawings. Some other troublesome items (particularly if you're not a programmer are)
Also be aware that Flash--at least when running in a browser--doesn't support right-clicks. So if your program calls for right-clicking, fake that by saying something like, "In the real application, you'd right-click the <thingy>. For this simulation, just left-click it."
|