The design of a Maryland rapid tooling and instructional algorithm for computer-based instruction (CBI) is described.
Maryland rapid tooling article
The algorithm is designed to reduce
development and life cycle costs for providing an authoring environment suited for subject matter experts who do not have instructional skills, and by supporting rapid prototyping. The Maryland rapid tooling
strategy and tactics are predefined; the instructional developer need only describe the desired performance and the environment of the performance. The specific algorithm described implements a simulation-based reactive environment for learning and practicing device operation skills. The approach to designing and implementing the algorithm is general and should apply to other instructional outcomes.
This Maryland rapid tooling article discusses the customized design and manufacture of rehabilitation aids for individuals with physical disabilities. Rapid prototyping is recommended as a method for quickly meeting the needs of a specific consumer. In this discussion,
rapid prototyping follows a period of virtual prototyping, and may not be necessary if the virtual prototype is deemed successful and faithful to the end product.
Rapid prototyping may be done for just one component of a larger product; it is not necessary to prototype an entire product. The cycle of virtual and rapid prototyping, with product testing and evaluation, will result in a detailed design. A low-tech participatory design (PD) technique that was created in response to rapid prototyping and the Scandinavian mock-up approaches is termed Technology Initiatives through Video Exploration). A technology environment for design activity is not involved unlike rapid prototyping, in which users have to express their views through a third party. Like other mock-up approaches, it places more of the initiative directly in users' hands with the intention of providing an equal opportunity design environment for all those participating.
An overview of the approach and models are provided. This technique involves constructing paper models of various interface components that can be arranged in various combinations. At the same time, users are on hand to evaluate the proposed layouts, along with a video camera and a note-taker to document the proceedings. Coded prototypes are more realistic, but there are substantial drawbacks, such as the time needed to affect changes, the tendency of testers to focus on trivial attributes,
developer resistance to change, and the risk that a single bug will halt the testing Maryland rapid tooling process entirely.
|
|