While this section brings up some valid points, most of the technologies discussed are out of date. Many do not exist while others have been replaced by more modern alternatives. Since this writing is 11 years old, it is to be expected that the technologies discussed are no longer relevant.
Even though some of the specifics discussed in this section are no longer relevant, there are some underlying principles that have not changes. A designer should always check the logistics of using web as a medium for instruction. Is internet available to the students? Will chosen file formats be supported with available browsers and technologies? Be sure to note any special software or hardware requirements. Also consider the limitations of certain computer languages and plan for your needs.
The “Course Delivery Tools” section seems to be talking about Learning Management Systems (LMS). Oncourse is a good example of an LMS. While Boling and Frick point out that commercial systems my be expensive, there are now open source solutions as well. MOODLE is a very popular open source (free) LMS solution for those on a tight budget.
Chapter 5 goes on to explain that once the web prototype is created, the same type of testing used on the paper prototype should be completed.
Chapter 6 covers bug testing. One last, but important test that should be conducted prior to the official release. The final instruction should be tested on various browsers and screen/platform resolutions.
Anything the designers think their users might use to access their course should be considered in testing. Sometimes suggestions are issued to the learners as to what browser, platform or device will work best with the particular course, but compatibility should be as accommodating as possible.
Since this writing is out of date, it brings up a very good, yet unintentional point for my own instruction. If I deploy this as a usable course, I will need to keep up with changes in the portfolio sites I talk about, and update the instruction periodically to make sure the information stays relevant. In addition any links used need to be tested from time to time. Some times it is useful to have a reporting system or at the very least an email link for students to report undetected dead links. Anytime technology is the subject, the shelf life is greatly shortened and must be properly maintained.
No comments:
Post a Comment