An IMLE is an interactive learning environment. To date the best examples have been authored with Director or Authorware and published on CD-ROM (authoring with Flash makes the web an alternative delivery method).
The diagram at the foot of this page and following text outline the typical development cycle of an IMLE.
Identify aims and objectives of prototype
For example:
For example:
Determine instructional goals
An IMLE will seek to provide an instructional environment in which the learner can acquire knowledge and skills:
Exactly what these will be will be determined by:
Determine end-user profile
We will need to identify the profile of our end user(s).
For example:
Detail resources
We will need to list all the resources required to build our prototype.
Authoritative knowledge resources
For example:
Hardware
For example:
Software
For example:
Determine cognitive model
To be discussed by participant educators.
Determine instructional strategies
For example:
Specify knowledge to be taught
To be determined by educators.
Research examples
Current IMLE's should be analysed for design and approach.
Determine functional requirements
Considerations include:
Frequency of use Style of presentation may be dictated by usage patterns. For example, a presentation intended to be viewed once may employ an intensity of communication, repetition, and contain insistent dramatic content elements, such as sound effects, that will become tiresome in a title intended for instructional and reference purposes.
Keeping attention
Customisation We need to consider the benefits of tailoring instructional content towards a user's needs based on information input by the user. Designing interactive dialogues will exploit the true interactive and constructionist potential of our prototype.
Recording usage A user or educator may benefit from a record of responses to instructional drill and assessment activities.
Design interface
To be determined under the guidance of Hannah Gal.
Considerations include:
Unity and coherence Navigational and stylistic patterns will be expected by a user who understands the context they are in ie turning the pages of an electronic book. The design of the interface must be informed by considerations of clarity. Each design and style component must have a clear role within the context. There must be consistency in the design of navigation and menu elements and in the layout of the screens, balance in the organisation of components within individual screens, and a clear pattern of flow between screens.
Interface metaphor Although coherence is a primary consideration it was also important to design a progressive looking interface that conveyed a sense of both authority and creativity. These factors inform the choice of type style, colour scheme and presentational approach.
Graphical metaphors It is common for multimedia designers to employ real-world metaphors in the form of icons.
Create the navigation map
To be determined by collaboration between interface designers/authors/educators.
Create storyboards
To be determined by collaboration between interface designers/authors/educators.
Write scripts
To be determined by educators.
Obtain AV media content
This will involve purchasing preexisting media relevant to your production such as ...
Create AV media content
Considerations include:
Author prototype
Considerations include:
Testing
Alpha testing
to be carried out constantly through the authoring process.
Beta testing involves potential real users to use the prototype on a variety of systems and then complete a questionnaire. The problems encountered and suggestions made will inform a further process of refinement.
Debugging
To be completed by interface designers.
Understanding the requirements of the end user involves identifying appropriate delivery systems.
For educational institutions, where software and system maintenance is available, our prototype may be sited on a powerful server by a trained technician. The performance of such a delivery system will impose restrictions on the design and construction processes when decisions concerning playback speed and factors such as sound and colour bit-depth must be made.
For single users a fully documented CD-ROM package including an installation guide and specifying minimum system requirements is required.
Determine delivery methodology
For example:
Fully documented CD-ROM containing application, A READ.ME guide to installation and late breaking news. System resources. Internet browser bookmarks providing links to related web sites.
Installation on a server
Additional resources could be available from an accompanying internet site which might contain user feedback facilities, relevant links, and perhaps an online version with reduced functionality and interactivity.
Define minimum system requirements
Create packaging
To be determined under the guidance of Hannah Gal.
Create installation documentation
To be determined by interface designers.
Create users guide
To be determined by educators and interface designers.