Commonwealth Computer Navigator's Certificate/Milestone 5

Target date: 15 March 2007

Tasks

 * achieve a shared understanding of the instructional design template
 * allocate roles and responsibilities for development

The instructional design template
The instructional design template is available for use now.

The list below describes the roles. Within your teams, you need to start thinking about who will fulfill which roles.

Roles and responsibilities for development
The following are 'roles', not people. It could be that one person in your organisation covers a number of these roles!


 * Instructional Design
 * Subject matter expert
 * Multimedia Designer/Development
 * Editing
 * Peer review
 * Project Quality Assurance
 * User testing
 * Sponsor sign off

How these roles fit into the development process

Descriptions of roles

 * Instructional Design
 * Identifies and scripts the learning activities. Determines structure, style and presentation of the content. Identifies which media may be required to support learning activities.


 * Subject matter expert
 * Experienced user of Open Office. Will support the instructional designer, for example, by identifying gaps in the content and suggesting credible scenarios and activities. Will 'sign off' the module for its accuracy.


 * Multimedia Design/Development
 * Develops media files (graphics, flash files etc.) to support the learning design. Uses eXe to develop courseware.


 * Editing
 * Reviews content/media for use of language, for example, style, tone, spelling, appropriate usage of words, grammar. Also checks for consistent use of formatting, for example, heading styles used. [Will use editing guidelines established for this project]


 * Peer review
 * Another Educator/trainer/teacher. This person will run through the module to provide additional perpectives on the pedagogy and provide feedback from a teaching and learning perspective. In particular this review will check that the module adheres to the ICDL curriculum for the purposes of accreditation.


 * Project Quality Assurance
 * An overarching review to ensure consistency across the modules. Aspects to take into account will be how the project meets agreed 'principles', such as modularity/re-usability etc.


 * Technical testing
 * The modules are tested on a range of platforms to ensure that there are no technical errors. The content 'distribution will also be tested, for example, to ensure that the 'packages' are downloadable and will install and run.


 * User testing
 * Learners are selected to run through the module. They are observed as well as providing feedback themselves. Observers provide a view of the 'usability' of the module.


 * Sponsor sign off
 * Given all the above reviews and feedback, the module 'owner' will ensure the module meets the required standards and communicate this to the project sponsor who will sign off the module.