Module Development Process
Information on this page provides an overview for creating an effective Links module. (The module requirements page provides more details for current developers.) Components explain:
![]()
Interactive Learning
Project Links' primary mission is to link the concepts of higher math to applications in engineering and science. One component of this mission is the concept of Web-based Interactive Learning, allowing students to actively participate and learn in ways unavailable through traditional textbooks and lectures. The power of interactive learning relies on providing hands-on activities for students as they work through the modules--reinforcing concepts as students "learn by doing."
Project Links is not meant to serve as a web repository for textbooks or lecture notes: "on-line" is not synonomous with "interactive." Students want to do more than simply click for more information (remember, most high-school and college students have been using computers since kindergarten--what may be new technology to you is not new to them). The web's inherent properties of point-and-click navigation and non-linearity opens the door for you, as a module developer, to dynamically illustrate and teach concepts by engaging students with different media (video, applets that respond to user input, animation, sound, links to other resources, etc.). Effective Links modules, like Drag Forces and Vibrating Strings, take advantage of web-based education and not only engage students with interactivity, but truly link concepts of higher math to real-world applications.
![]()
Module Criteria
A completed module will include all of the following:
- Interactive web-based Lessons
- Instructor Support Materials
- Student Handouts
- Instructor's Manual
- Assessment of the Students
- Metadata
- Abstract
- Objectives
- Prerequisites
- Technical Requirements
- Other supporting details
- Documented Reviews
- Student Usability Testing
- Independent Content Review
- Pilot Testing in Classrooms
- User Interface and Educational Technology
- Other supporting details
![]()
Module Development Process
Complete the Module Design Questionnaire
The questionnaire is designed to help developers organize their ideas and content for a Project Links Module.
Create a storyboard for your Lesson
A storyboard is a plan that outlines the ideas and materials needed to build a Project Links Module (including both on-line and supporting materials). The questionnaire provides information and questions to help you build a storyboard for your module. Storyboarding organizes your content in the context of Links' design and navigation template. An outline, flowchart or text describing what should go on each page should suffice (and we do mean each page). Good storyboarding is paramount for building content into a web lesson--think of it as a blueprint for your module. Among other things, it answers these questions:
- What is the scope and subject of the module?
- How will it be divided into chunks of information?
- How do these chunks of information relate to other chunks which have already been built/used?
- What dynamic activities (applets) need to be built?
- What supporting (non-computer) materials need to be supplied with the module?
- How will the module take advantage of the media?
Lots of text is best left to paper rather than having it read on the screen. When designing a module, take advantage of the power of using Java applets for high levels of interactivity, using VRML for visualization and manipulation, and so on. Design activities that can't be accomplished by a lecturer or on a piece of paper. Keep in mind that the module is simply one set of materials to be used in the classroom: instructors can and should still use handouts, textbooks, and other materials.Here are some resources that may help you:
- Storyboard examples for the Drag Forces module.
- Applet Storyboards for the applets in the Vibrating Strings module.
- Project Links Developers pages to become more familiar with the formats, tools, assumptions of use, and so on.
- Look for re-usable pieces already developed for Project Links.
Check the list of modules that are being developed.- Yale's Web Style Guide provides lots of good guidelines for web design in general.
Review by the Technical Manager and authors.
Initial review to insure that the new module meets Project Links goals and assumptions, and content is presented according to authors' intended design. Modifications to module by technical management staff as necessary.The following steps might not be conducted in the
order listed, and many review steps must be repeated if needed.
Content Review
Formal content review by at least one expert in the content area. The evaluation instrument will be a checklist produced by the SUNYA Evaluation Consortium. Once the module has been developed to the satisfaction of the author and the technical manager, a qualified expert in the subject matter will be found, and provided with the checklist. If a small financial incentive is necessary in order to obtain a quality review, then this should be part of the author's funding request for the module. In general, content reviewers will be asked to work through the module, validating the module content and the accuracy of the materials presented. They will be asked to complete a short review of the module delineating content viability.
Edits as necessary based on Content Review.
Authors and the technical manager will make edits as necessary based on feedback from the content reviewer.
Educational Technology and User Interface Review by experts in the field of educational technology.
A standard review that looks at the module from a technological/instructional point of view and provides validation of the module's appropriate use of instructional/technological theory. A written review will be provided based on a checklist of suggested topics. Review will be provided by scheduling with the technical manager.
Edits as necessary based on Educational Technology and User Interface Review.
Authors and the technical manager will make edits as necessary based on feedback from the ed/tech review.
Student Usability Testing.
A standard review where a small number of students use the module and provide information pertaining to usability from a student's point of view. An observational checklist and interview protocol will be established (perhaps videotaping students). Review will be provided by scheduling with the technical manager.
Edits as necessary based on Usability Testing.
Authors and the technical manager will make edits as necessary based on feedback from usability testing.
Pilot Testing in classrooms (collecting evaluation data).
A review provided by our evaluation team from the SUNYA Evaluation Consortium. Includes observations and interviews with faculty and students. Similar to providing "internal validity" in research--in evaluation, it is proof of the module's "merit," that it does what it is supposed to do. Data in this step can be collected over a long time period if desired by including additional sites, new methods of implementation or new methods of cognitive assessment.
Edits as necessary based on Pilot Testing.
Authors and the technical manager will make edits as necessary based on feedback from pilot testing.
Utilization in multiple classrooms and at multiple sites.
A review provided by our evaluation team from the SUNYA Evaluation Consortium. Includes observation, interviews, focus groups and paper-pencil methods on instructors and students' perceptions and on cognitive outcomes. This will provide the "external validity" of the module, or in evaluation terms, information pertaining to its "worth."
Final edits as necessary.
![]()
home
Copyright © 1998 Rensselaer Polytechnic Institute. All Rights Reserved.
info@links.math.rpi.edu ... Last Updated: