New Jersey Institute of Technology College of Computing Sciences CIS365: File Structures and Management Rich Egan
A Public Research University

Quick Links: [Materials] [WebCT access/info]

Semester Project - P6: System Design

Goal: To apply the concepts and skills we're learning in class to a larger case.

Due Date: See Syllabus

Note:

For now, all you need to do is the design of this information. You will do the programming as part of the final submission. Please submit just the design package described here on the due date.

What to Do:

Design a mini-information system for your semester project company. You can start entirely fresh if you want BUT hopefully you will be able to use what you have done so far. Your mini-information system can involve any aspect of the organization, and can be entirely different from any programs and reports you have developed so far. (Alternatively it can build upon what you have done as long as it adheres to the guidelines below.)

Your information system should have the following features:

Mandatory Features

• System Menu: The system should display a menu to the user. Each feature listed here should be called from the menu. If you wish, features can ask the user to input some information.
• User Friendly: Be sure to make your screens user friendly, so users know what is being displayed and what kind of information to input.
• Indexed Data Files: The system should have at least 2 separate indexed data files. At least one of these data files must be indexed with multiple keys.
• Feature - Reports: The system should produce at least 2 types of reports. Each report may be for any user or employee of your organization: for a customer, a manager, a vendor, etc. 
• At least one of these reports each must use data from at least 2 different data files.
• Feature - Search: The system must locate a particular record or set of records in one of the data files that match a user request. This means that the user will be requested to input some value(s) and the system checks the data records to find all the records that satisfy this user request.
• Feature - Listing of Each Data File: The system should print the contents of each data file in a nice format. (Each record may be displayed on a single line if it fits, or across multiple lines.) This printout is in addition to other reports listed above.

Optional Features (for Extra Credit)

• Optionally, the system should allow the user to add records to the input data files, one record at a time.
• Optionally, the system may enable the user to modify existing records.

Notes

• Each feature in the system should open and close all the files it uses.
• Be sure to check for any possible error conditions.
• You can create your data files outside the information system, or as part of the information system.
• Please check the course Web site for notes on creating indexed files.

What to Turn In: NOTHING - this is the Design Package that you need to follow for your final project

Check-Off Sheet for the Design Package (see P6-Checklist and include it with P7)

Menu

( ) Is each feature included in the menu?

( ) Is detailed information included in the Design Package for each feature in the menu?

Data Files

( ) Are there at least two indexed data files?

( ) Is there an 01 record layout for each data file in the list of data files?

( ) Is it clear what the main key field(s) will be in each data file?

( ) Are at least 4 sample records shown for each data file?

( ) Is a listing of all the records in each data file included in the menu?

Reports

( ) Is it clear which data file(s) are used to produce each report? Is the correct data being used from each file?

( ) Do any of the reports require user input? Is the requested input sensible?

( ) Does the report make sense?

( ) Looking at the output mockup, is each report displayed in a user-friendly way?

( ) Are there at least 2 reports?

( ) Does one report use data from at least two data files? Does it make sense to combine these particular data from these particular data files into a report?

( ) Is it clear what error conditions could arise for each report?

Search

( ) Is a search for records from at least one data file included?

( ) Is the search field a primary or secondary key field for that data file?

( ) Is it clear what error conditions could arise for the search?

( ) How will the records returned by the search be displayed to the user? Looking at the output mockup, is the display user friendly?

Other Features

( ) Is it clear which data file(s) are involved in each feature and how?

( ) Does the feature require user input? Is the requested input sensible?

( ) Does the feature make sense?

( ) Looking at the output mockup, is each feature's output displayed in a user-friendly way?

( ) Is it clear what error conditions could arise for each feature?

This page:p6.htm