[back]  [next] Session 5: Conceptualizing the Scope and Content

D.3. Translating the Script for Programming

To translate a written script to a form that's useful to a programmer, many tools can be used. Essentially, the job is to chunk a script into Web pages and create files for the text, pop-ups, PDF files, media, pictures, graphics and outside links.

A "translation" or communication tool or tools must provide the programmer with a description of what the viewer is to see on each page, options for actions the viewer may take, what happens as a result of any action taken. The translation tool must also convey how the files relate to one another to make this happen.

Translation tools can be relatively simple (like the planning tool Jonathan used for our scripts) or very complex, such as those used for actions with multiple and branching results, such as decision trees, algorithms or programs using applications of artificial intelligence. The complex translation tools often take the form of "Step. Action Results" charts, which detail possible learner actions and results of those actions at any given step in the instruction.

 

The NECTAS Experience continued ...

Since Jonathan acted as production manager for our workshop, we gave him our scripts for each session as we completed them. He "chunked the pages" and created and organized all the files to give to Robert, our programmer. He also provided a planning tool, showing file relationships. There can be 75 files for any of our sessions!

Behind the Scenes Icon You may want to look over the first three pages of the eight page planning tool for Session 4.

 

Group We learned that providing a Web map and the script for each session made the translation easier for Robert. In addition, for early sessions it was helpful for all of us (Nancy, Joicey and Martha as instructional designers, Jonathan as production manager, and Robert as programmer) to meet and go over the session. This meeting is called a "transfer meeting."

[Session Home] [back]   [next]