Project Assignment Form and Grading

Final Project Overview (Database Management Systems)

Technical Report Format

  1. Executive Summary (5 points)
    1. Goals
    2. Problems (that you encountered during your study)
    3. Results
    4. Recommendations
  2. Introduction (5 points)
    1. Company background
    2. Problem (that made a new system necessary)
  1. Entity-Relationship Diagram (20 points)
  2. Normalized Relational Schema (15 points)
  3. Report/Screen Validation (5 points)
  4. Implementation
    1. Database Table Creation (10 points)
    2. Input Forms (3 points)
    3. Query Design (15  points)
    4. Advanced Forms (8 points)
    5. Reports (9 points)
  5. Summary (5 points)

The overall organization of the report as well as its content will influence the grading.  

The presentation should be "professional quality" because in a real setting the presentation will be the first description of your project that management encounters--the thing upon which they base their first impression. A slick presentation helps to "sell" a project. It's hard to overcome a bad first impression in your actual (in the real world) presentation.

Be sure to include each of the components listed on the project page. The presentation should be submitted in a binder or should be bound, and your old deliverables should be submitted separately in a packet.  Be sure that grading comments remain on old deliverables.


Deliverable I -- E-R Diagram

The E-R Diagram should be developed through a step-by-step process. The steps which will be followed are listed below:

Part A:

Part B:


Deliverable II -- relational model

The relational model should be developed through a step-by-step process. The steps which will be followed are listed below:


Deliverable III -- Validation

Provide a validation of the reports and/or screens in terms of the E-R diagram.  When performing the validation, select the primary entity from which the report is derived, and then show how the attributes, including those from other entities, are obtained through foreign keys, composite keys, etc.  The form and report validations should appear in the deliverable in the same order in which they appear in the case description. Validate the forms and reports below:

Explanation of Validation


Deliverable IV -- Table creation/data entry

Using the relational model developed in Deliverable II, create a database and the appropriate tables. Be sure to create tables representing both the entities and the composite entities.  Using the reports, displays, and figures in the problem description, enter some sample data for each table. Make certain that you enter data into the composite tables that provides the linkage between the two tables being bridged.  The steps which will be followed are listed below:


Deliverable V Data Entry Forms design

Using tables developed in Deliverable IV, design and create the data entry forms specified below.  The forms will be graded on appearance and content.  Use Access to create the forms.  Do not use Visual Basic.  The steps which will be followed are listed below:


Deliverable VI Query design  

Using the tables developed earlier, develop a set of queries as specified in the query list.  Any queries that make use of a Join operation should use the WHERE clause rather than the INNER JOIN.  Points will be deducted for queries that use the INNER JOIN.  Include data in your tables to test each query.  Be sure to save the queries and submit the database.   Provide printouts of both the SQL view and the query result.  Be sure that there is data in your tables so that I can duplicate your results!

Note:  Don't forget that if your query includes an attribute name that has a # sign, like Mechanic#, the attribute name has to be enclosed in square brackets.

Query List


Deliverable VII Advanced Forms

Create and submit the forms specified below, which use queries to generate details.  Use Access or VBA to create each form.  I will be unable to help you with VBA, so use it at your own risk.  Submit both a diskette and printed copy.

Purchase Entry Form

Create a form with subforms to replicate the purchase entry form.  It will differ slightly from the case description to make it easier.  It should display the various purchases, but is not intended for input.   Therefore, you should disable all of the fields (set the Enable property to No). Here is a sample form:

As discussed in class, select the "primary entity" (which is the one that has connections to most other participating entities) and base the main form on it.  In this case it should probably be Purchase Agreement.  Then embed subforms to supply data from the other participating entities.  The above example has two subforms, because a subform can actually be based on more than one table.  Be sure that the primarykey/foreign key linkage is present in the main form and each subform, even if the fields are hidden, because they are required to link the forms.

If you want to link a subform to a combo or list box on the main form, click this link.  Although the clues page is tailored for a previous semester, there are still some useful pointers.  You probably won't need the hint page if you follow directions and make sure that the primarykey/foreign key linkage is present in the main form and each subform

Note that in the samples you cannot distinguish the subform from the form.  The same should be true of your forms.  Several properties have to be set in order to accomplish this.  Experimentation will be necessary.  The forms will be graded on both appearance and functionality


Equipment ENTRY Form

Create an Equipment Entry Form so that it will permit data entry when new equipment is received.  This form should be done without using subforms.  The Data Entry property for the form MUST be set to Yes. Your new form should resemble the one below.  The Model is selected through a list box.  Note that the Sale Price, Date, Manufacturer, and Inventory Count are all disabled. 

 

Note that in the samples the controls blend in with the form.  Your forms should have this feature.  Various properties have to be set in order to accomplish this (You can select all data entry fields at once by holding down the Shift key and selecting each).  Experimentation will be necessary. 


Deliverable VIII Reports

Create and submit the report(s) specified below.  Use Access or VBA to create each report.  I will be unable to help you with VBA, so use it at your own risk.    Be sure to use the clues provided to assist you with the reports.

==============

Report 1: Inventory Report

List all items in inventory.  Your report format should resemble the report shown below as closely as possible.  Test your report with multiple items in stock for at least one model.


==============

Report 2: Purchase Agreement

Create a purchase agreement that lists all item charges, calculates a sum of those charges to get the subtotal, calculates a sales tax of 7.75% of the subtotal, and then adds the tax to the subtotal to get the total.  Be sure to include purchase agreement information, customer details, and details about each item purchased on this contract, as well as credit card number (partially blanked) and card type.  Your report format should resemble the report shown below as closely as possible.  You may generate a listing of all agreements, although you can easily modify the report so that it is based on a parameter query that requests an agreement number.  Test your report with multiple purchases on at least one purchase agreement.


 


Notes:

This should go without saying, but whenever turning in a deliverable or the final project be sure to clearly label EVERYTHING that is to be graded.  For example, label each query as Query01, Query02, etc.  When forms or reports are placed on a disk label each one clearly, so the grader and the professor know which one to grade.

========

When turning in your database for each deliverable, please compress the database and turn it in on a floppy disk rather than on a zip disk.  To compress a database you go to 

To compact the access database automatically upon close, go to

========

When writing your Executive Summary and Introduction, use poetic license.  In other words, make something up.  Be sure to include and clearly label all portions that are listed in the specification.  The problems portion of the executive summary should be problems that you encountered, but not stuff like "we had trouble figuring out forms because they suck."  You'll have to make up the company background based on the little bit that is included in the case description. 

The Summary section should leave the reader wanting to adopt your system.  Remember, this report is the equivalent of your sales pitch to management, and the summary should be the closer.