CSE 222 Lab #2


Objectives

The Problem

Your customer, Cy Burnett, heads a major publisher of textbooks who is migrating toward on-line access.  Cy wants a relatively easy-to-maintain glossary facility. (A glossary is a list of difficult or specialized words, or terms, with their definitions, that is usually near the end of a book.) His initial requirements are as follows: These are the stated requirements for your program. If you have questions of clarification or need additional details, Cy is willing to answer them if you ask your instructor to contact him.

Method

Here's what to do:

Your grade will depend not merely on whether the final program meets the customer's initial requirements, of course, but also on the general software quality factors we've been discussing for the past half-year: understandability, precision, appropriate use of existing software components, maintainability, adherence to coding standards, and so forth.

A sample input file is available at:

A sample of program output for a glossary done as a single HTML file is available at: A sample of program output for a glossary done as several HTML files is available at: You should not assume that your glossary must look like one of these, which are merely samples of what the output might be. The samples are just something your requirements analyst and the customer cobbled together by hand for a small glossary, to serve as possible prototypes for the final program output. You should feel free to improve on them.

Possible Maintenance Activities

Here are some questions about possible maintenance activities involving this program: Any extra work is strictly optional, for your own benefit, and will not directly affect your grade.