The presentation mechanism itself usually has no knowledge of how these content elements relate to each other. This can be quite tedious if two formats are required since each must be maintained independently even though the underlying content is the same. This permits, where it makes sense, the same content to be presented in different interfaces, i.e., linearly, hierarchically, relationally, etc. HyperText environments have been demonstrated by peer-reviewed research to be detrimental to student learning in a variety of situations. Software is designed to take advantage of the computer's ability to truly serve as a non-linear instructional platform as opposed to simply being an information distribution platform.
Faculty are responsible only for maintaining content.
Skill sets associated with the software aspects of the project, i.e., development, deployment, maintenance, instructional design, and graphic arts do not become additional burdens the faculty must bear. The group will work with faculty to develop new ways for the software to present material. These new interactions can then be made available to all faculty who are using the software. For example, it is a future goal to build adaptive testing into this software and this feature would be available as an addition even to projects already deployed. The presentation consists of two parts, available in a variety of resolutions to meet your bandwidth capabilities.