CIS 4109 - Deliverables

Design Document

The Design Document should describe most of the details of the project from a developer's standpoint. This includes descriptions of any databases or forms used at a field level. It also includes descriptions of any objects, web pages, or scripts at the object or procedure level. Here are some details of what should be in this document.

The document should define the database structure used. It should list the records and describe the fields (including key fields). If possible, the type and size of each field should also be described. You may have to normalize the existing database before defining this new database structure. I suggest having a paragraph describing each record and then a simple table or printout showing each field's name, description, type and size.

The software specification must also define each input screen. The entire graphical interface does not have to be described, but you may describe it if you wish. You must describe what forms will be used to input, edit, and delete records. For example, how will you change the address for a customer/client? Will you bring up a generic form displaying/editing a single record and use the scroll bar to locate the correct record? Will you ask the user to enter the exact customer ID and then bring that record up in the edit form? Will you have the user enter part of the customer's last name, bring up a list of matching records, then have the user choose the record to edit which will then be brought up in the edit form?

Each report must also be defined. You should define what fields will be on the report and how the basic layout will appear. If the report is to mimic an existing report, a copy of the existing report would be helpful. Also describe how each report will be printed and what records will appear on the report.