This phase deals with the design of all the resources required by the learning activities of the stage both those in and out of SL. This phase will be repeated for each stage of the project and identify where it is building on work from the previous stage.
The purpose for this phase is to ensure that all resources needed to create the learning experience are identiifed, designed effectively and constructed. Based on the learning activity or activities identified in the Develop the Learning Narrative phase, and on the list of required resources derived from that, this phase is primarily concerned with the questions around ‘How will we fulfill these requirements?‘ and documents the final answers to those questions. It thus considers the design of all the resources that are required for the final construction both those that will be built in SL and those that won’t.
Phase Leader: Lead Developer
- Identify the list of all elements from the Learning Design document that will be constructed in SL
- Identify the components of those elements (initially at high level only)
- Identify where content is required from outside of the SL development team
- Identify elements that already exist and/or which need a) construction b) adaptation c) additions
- Identify technical aspects of the build that need to be investigated (e.g. the need for a server service to stream live video/audio, need for a host for reliable storage of video to display (YouTube or ?) etc..)
Although the responsiblity of the development team, the identification of the necessary resources will need on-going discussion with the Learning Designer and Lead Educator to determine the exact nature of the resources (e.g. which texture to use for external walls)
What else is needed?
The following list will be constructed as the technical design and build progresses.
- comprehensive list of all elements
- detail of interaction between human and constructed element
- detail of interaction between elements
- naming standard/convention used
- back up information (where, when and how to retrieve)
- comprehensive list of all ‘global’ atoms used (e.g. scripts to report on content of elements, textures used across elements and/or projects)
What else is needed?
The Technical Design Specification will begin as a working document that initially lists the high level components identified as required in the previous phase (e.g. birthing unit). Following any conversations to clarify what is needed, the construction work and the on-going documentation of the various elements, sub-elements and atoms begins and is recorded as the construction progresses.
The final version of the working document is the eventual Technical Design Specification document and should act as a comprehenisve record of everything that has been built in SL. The eventual number of atoms is likely to run into thousands (even without considering versions) each one needs to be identified and identifiable.
The External Resource Design Spec could work in a similar fashion perhaps? How will we do this? Who should be responsible for it?