Develop an Access database based on a company or organization of your choice

Develop an Access database based on a company or organization of your choice.  Minimum requirements are listed in this document.

Project Milestones/Deliverables – Due dates are listed on the syllabus.

1. User’s Manual Database Description

• Begin the Final Project User’s Manual using the template provided on Blackboard. Write a short description of your database application and what it will do.

2. User’s Manual Entity Relationship Diagram (ERD)/Relationships report

• Create the tables and relationships in MS Access. The tables must possess the properties of entity integrity and the relationships must be defined with referential integrity enforced.
• All database objects should use naming conventions, tbl, qry, frm, rpt, etc

3. First Draft Database and User’s Manual:

• A database with the following
  • tables: at least 3 tables defined and possess the properties of entity integrity, and relationships defined with referential integrity enforced
  • queries: at least 1
  • forms: at least 1
  • reports: at least 1
  • Note: All database objects should use naming conventions, tbl, qry, frm, rpt, etc.
• Updated User’s Manual with the following:
  • A statement about each table that specifically describes why each individual table possesses the properties of entity

Example:

• In STUDENT, STU_NUM is the primary key, has no null values and all entries are unique. STUDENT possesses the properties of entity integrity.

• A statement about each relationship that specifically describes why the relationship exhibits referential

Example:

• ENROLL is an example of a table that exhibits referential integrity because all STU_NUM entries refer to an existing STU_NUM in STUDENT.

4. Second Draft Database and User’s Manual:

• A database with the following
  • tables: at least 3 tables defined and possess the properties of entity integrity, and relationships defined with referential integrity enforced
  • queries: at least 2
  • forms: at least 2
  • reports: at least 2
  • Note: All database objects should use naming conventions, tbl, qry, frm, rpt, etc.
• Updated User’s Manual

5. Peer testing including a completed user’s manual

Minimum Requirements:

• Proper design with tables that possess the properties of entity integrity, and relationships defined with referential integrity enforced
• Database objects named using naming conventions (tbl, qry, frm, rpt, mcr, bas)
• 3 tables
• 1 query with criteria using a comparison operator (Tutorial 3)
• 1 query using aggregate functions (Tutorial 3)
• 1 query using calculated fields (Tutorial 3)
• 1 advanced query (Tutorial 5)
• 1 action query (Tutorial 9)
• 1 multi-table select query (Tutorial 3)
• 1 parameter query that prompts for criteria, using wildcards so that you can leave the prompt blank and all records will display, (Tutorial 5)
• 1 SQL query that list all the fields of a table
• 1 SQL query that list only some the fields of a table, order by one of the fields
• 1 SQL query that list all the fields of a table using criteria
• 1 form for each table (Tutorial 4)
• 1 form with subform – (Tutorial 4)
• 1 form containing a combo box to find records (Tutorial 6, page 338)
• 1 form that lists all the database queries in a list box Tutorial 10, page 572)
• 1 report that contains data from more than one table and uses conditional formatting (Tutorial 7)
• 1 groups and totals report – The Groups and Totals report should group on a field and then do a calculation for each group. (Tutorial 7, page 315)
• 1 Navigation Form with tabs for Queries, Forms and Reports
  • Note: Only Forms and Reports can be added to a Navigation Form.  To add tables and/or queries to a Navigation form list tables and queries in a list box on a form and then add that form to the Navigation form. (Tutorial 10, page 572)
• Consistent design throughout all menus, forms and reports
• 1 User’s Manual, using the template provided, including the following:
  • All 5 items from the database specifications document:
    • A short description of your database application and what it will do
    • Business Rules
    • ERD/Relationships Report
    • A statement about each table that specifically describes why it possesses the properties of entity integrity.
    • Example: In STUDENT, STU_NUM is the primary key, has no null values and all entries are unique. STUDENT possesses the properties of entity integrity.
    • A statement about each relationship that specifically describes why it exhibits referential
    • Example: ENROLL is a table that exhibits referential integrity because all STU_NUM entries refer to an existing STU_NUM in STUDENT.
  • A table listing the requirements, the names of the objects that satisfy each requirement