Critical view

Graphics

Peer review

Computer Science Department

University at Albany

Software Review

A professional's tools are both the source of admiration (for what they can do) and frustration (for what they cannot do). Write a 5-7 page critique of a software package, program or system that you use or have somehow become familiar with.

For example, you can choose to write about an application, a utility like a Linux distribution, a data base package, operating system software like Vista or Mac OS, "proprietary" software you use at work, whatever. However, you cannot select a word processor, a web browser, or an instant messenger (I'll explain why in class).

Among other things, your critique should address:

• What is interesting about it? Why?

• What features / materials are available there?

• How can they be used by you or by others?

• How well are things organized? How could their interface, organization or overall use be improved?

• If applicable (depending on the software you review), describe how it could be used in college or in education generally.

Do not report simply on what's available feature by feature (if software) or page by page (if a web site). Instead draw attention to strengths and weaknesses (and what is missing). Speculate as you go too. How does this product fit in with the topics that matter to you (like DRM, say). Give details and examples. Do not assume your reader is familiar with your topic. Remember, you are not sitting at a terminal and guiding us through a demo; you are talking about the overall experience and social utility of the software. In other words, have fun with your subject.

You are expected to take a "critical" view, identifying program strengths and weaknesses.

In addressing the latter, you should propose improvements that can be made to enhance the software. You may have to restrain your enthusiasm or your criticism. For example, a game is not successful because it's "way cool." Similarly, Vista is not awful because it does not fulfill Microsoft's hype. See what I mean?

Here are a couple of warnings from semesters past. Software is inherently "under construction" from preleases to multiple generations of releases. Yet, do products become more stable when they mature? If packaged software is developed and marketed to make us more productive, why do we use so few of the features that are typically bundled in a package?

You should also look at this software the way an anthropologist would look at an artifact of another civilization. Does the software say anything notable about the society that uses it? Does the software have any obvious social purpose? If this were the only software you looked at, what conclusions would you draw about computing?

Remember, you must include one or more graphics in the graded papers. This can be an illustration copied from another source (a screen shot, for example, a logo, chart, whatever). It can also be an original illustration that you designed to fit the context.

Submit one copy on the due date noted in the class schedule. This will be exchanged with a classmate who will review and edit it. The peer reviewed copy will be returned to you the next class for final revision. Two copies of the final draft (along with the peer reviewed draft) are then given to me. One will be graded and returned to you; one will be retained for class files.

Top of Page

Last updated: 1/14/10