Joseph E. Koob II

Currently there are a number of venues in which music educators have the opportunity to analyze and select software for their programs, including conferences (presentations, "technology rooms", exhibits), ordering examination copies from software companies, and workshops designed to introduce a variety of software programs to teachers. Unfortunately educators rarely have the time to examine in detail a wide selection of software so that they can make the best possible choices for their students and programs. A specific analysis of software using a planned evaluation form/procedure can greatly facilitate not only the educator’s initial reactions to a program, but also serve as a long-term memory tool as future programs are analyzed and compared.

While there are a great many acceptable written formats for analyzing software, there are generic elements that should probably be considered as part of any software evaluation process:

Title

Author

Publisher: with address and phone number if available

Format availability (Apple, Commodore, MAC, IBM compatible) and specific disk size available

System requirements [e.g. IBM, minimum 386 with 2 megs RAM, VGA color, mouse recommended; CD-ROM, supports 16-bit soundboards]

Educational level recommended (this may be listed in software brochure or on the program box/disk, however it should also be considered as an integral part of the evaluation. You may want to place this near the end of your evaluation form so that it is one of the last elements you consider.)

Introductory Information presented on the disk should be included where it is vital to remembering distinct aspects of the program valuable to the educator’s needs. This information is generally available on the diskette and sometimes in accompanying materials:

Introduction

Main Menu: list if important

Sub-Menu(s): list all divisions/sub-divisions if important

Program elements/sections should be listed or checked off:

Tutorial

Practice

Testing

Game

Overall presentation relevant to level/age of student using disk should be considered:

Color: important for younger students, but surprisingly adds interest and dynamics to any program level and age level

Type size and readability: especially consider age level

Graphics/animation: age level and interest grabbing, keep in mind what children/students are playing with today; technologically they are very sophisticated

Amount on Screen: Crammed screens are boring to youngsters and disconcerting to almost everyone; even graphics can be overdone!

Page up/page down: can be an important feature in certain programs

Timing: is the self-paced, adjustable, or set (slow, medium, fast)

Feedback: What kind of feedback does the student receive? How? When? (positive/negative; immediate/delayed; practice/quiz/test results) What format does the feedback take? (# right/wrong; percentage; etc.)

Fun: is the program entertaining? Students are used to fast-paced, interactive games with high-quality graphics and animation.

Sound: quality of sound effects and music; is the program MIDI based?

Comments: Always save room for additional remarks/notes that will remind you of the particular software environment you have reviewed.

Designing a form to meet your specific needs is a personal endeavor, however, a generic form design can give you some ideas for your own effort. The focus should always be on being comprehensive, while saving as much time as possible. With wordprocessors today you can get quite elaborate with fonts and graphics if you wish; here is a basic example:

A self designed evaluation form is an ideal way to approach software review. University faculty who teach workshops introducing software to teachers can have their students design their own personal review forms and keep notebooks of reviews as an element of their course work. Designing the form for individual preferences, as well as for speed and usability, can make the software review process a positive learning experience and a wonderful tool for a teacher’s developing use of technology in the classroom.

Title:_____________________________________________________

Author:_____________________________________________________

Publisher:_________________________________________________________________

(Name) (Address) (Telephone)

Size: ____ 3 ____5 1/4 ____ CD-ROM

System Requirements:_____________________________________________________

Introduction:______________________________________________________________

___________________________________________________________________________

____________________________________ ________________________________

____________________________________ ________________________________

____________________________________ ________________________________

____________________________________ ________________________________

____________________________________ ________________________________

____________________________________ ________________________________

____________________________________ ________________________________

Timing: _____________________ Music/Sound

Effects:____________________________________

Graphics/Animation_____________________ FUN?__________________________

Screen presentation:______________________________________________________________

Feedback:_________________________________________________________________

(Positive/Negative) (Immediate/Delayed) (Format of Results)

Educational Level__________________________________________________________