Access Prototype

MGS 351�Introduction to Management Information Systems

Team Project Overview

• As a consulting group, build a database for a real-world company
• Using Microsoft Access 2019

​

• Database should help to solve or improve a situation at company
• Database should provide business value

​

• Must have first-hand experience with company
• One group member must have previously worked for the company

​

• Will be building prototype in Microsoft Access, and then building out the final project in Salesforce

​

Project Documents

• Project documents can be found on MGS 351 course website
• Project Overview
• Access Prototype Slides

​

​

Prototype Phases

1. Individual Brainstorming
2. Group Brainstorming
3. Project Proposal Draft (answering the 5 questions)
4. Project Proposal Presentation
5. ERD Rough Draft
6. Project Proposal & ERD
7. Project Proposal Re-grades (if necessary)
8. Prototype Database
9. Prototype Presentation & Deliverables
10. Peer Evaluations

​

Prototype Checklist

Begin Project Proposal:

• This will take place during recitation (Week 3)

​

• Brainstorm ideas for project based on your previous work experience

​

• Completed individually

​

Phase 1: Individual Brainstorming

​

• This will take place during recitation (Week 3)

​

• Share ideas as a group
• Pick a favorite idea and a back-up idea

​

• Submit “Who, Where, What” to UBLearns

​

• TA will review all group ideas during recitation

​

• Be prepared to discuss with the TA which idea the group will most likely choose

​

​

Phase 2: Group Brainstorming

• TA will meet with each group to discuss the final idea you will use for your final project

​

• As a GROUP, answer the 5 questions on the next slide

​

• Proposal draft should be in typed and in paragraph format

​

• Due in recitation at the start of class (Week 5)

​

Phase 3: Proposal Draft

At minimum, the 1 page narrative should be in paragraph form, single-spaced and include the following content:

1. Overview of company/organization/person you are building the information system for and a general description of the proposed system.
2. Identification of the business expert in your group and their current or past relationship with the organization you are building the system for.
3. Proof of how this information system will create business value for the organization. Sharing examples or stories of the current shortcomings is a great way to illustrate this. If no business value is derived from your proposed system, then you need to consider another idea for your project.
4. Description of any specific business problems you are trying to solve or opportunities you are trying to take advantage of.
5. Purpose of the system you selected, the functions this system will be expected to perform and the users of this system. In other words, why are you building this system, what is it specifically going to do, and who is going to use it?

​

​

Phase 3: Proposal Draft -

Questions to Answer

• Presentations should be about 3 minutes long

​

• Proposal presentations take place in recitation (Week 5)

​

• Business Casual Attire

​

• Everyone in the group must present EXCEPT the business expert

​

Phase 4: Proposal Presentation

Must cover 3 main points:

1. Background of the company

• What does the company do?
• What system does the company currently have implemented?

2. Problem

• Flaws in the company’s current system
• Why is the current system an issue for the company?

3. Solution

• How will your database solve the company’s issue/streamline the process for the company?
• How will your database create business value for the company?

Proposal Presentation

​

• All relationships should be 1:M

​

• Designate primary keys

​

• Foreign keys should be placed in correct entity

​

• Include appropriate attributes in each entity

​

• ERD must be computer generated using MS Word or another tool (hand drawn ERDs will not be accepted).

​

• Due in recitation (Week 6)

Phase 5: ERD Rough Draft

1. Initial Project Design Cover Page Report from the Team Information Database.

​

2. Members Report from the Team Information Database.

​

3. 1 page write-up describing the information system your group proposes to design and implement.

​

4. Entity Relationship Diagram of the proposed system.

​

Note: Due 24 hours prior to recitation (Week 7); The write-up must be typed and the ERD must be computer generated using MS Word or another tool (hand drawn ERDs will not be accepted).

​

Phase 6: Project Proposal & ERD

Write-up should include the following content:

• Overview of company/organization.
• General description of the proposed system.
• Identification of the business expert in your group and their relationship with the organization.
• Proof of how this information system will create business value for the organization.
• Description of any specific business problems you are trying to solve or opportunities you are trying to take advantage of.
• Why are you building this system, what is it specifically going to do, and who is going to use it?

Project Proposal & ERD

Entity-Relationship Diagram (ERD):

• All of the relationships on the diagram must be simplified to a 1:M
• Once the relationships are simplified, the ERD should have a minimum of 3 entities. This will result in a minimum of 3 tables in your final database system.
• Each entity must be labeled with a descriptive name. You should clearly list the attributes and the key attribute(s) of the entity.
• The primary key must be bolded or underlined and the foreign key attributes must be included with the proper entities.

​

​

​

Project Proposal & ERD

Proposal Grading Requirements

• The submission is complete with all of the deliverables

​

• The idea is based on a real company

​

• One of the students in the group is a business expert for that company

​

• The proposed project creates some real business value

​

• The relationships on their ERD are all 1:M and set correctly

​

Note: If any of those first five requirements aren’t met, the group will have to resubmit a new proposal and/or design.

​

Proposal Grading Requirements

• Once the previous criteria is met:

- How well does the ERD match to project description? 

​

• Primary keys have been set properly and foreign keys are in the related tables

• If you have received a grade:
• Approved, start working on project

​

• “Professor Murray needs clarification”:
• Go see Professor Murray

​

• No Grade/Professor Murray box not checked:
• Review proposal with TA
• Go see Professor Murray

​

Phase 7: Proposal Re-Grades

Stage 1: Entity Creation and Data Entry

• Tables, relationships, records

​

Stage 2: Forms/Subforms

​

Stage 3: Queries and Reports

​

Stage 4: Switchboard and Macros

​

Phase 8: Prototype Database

Stage 1: Entity Creation/Data:

• Minimum of three (3) tables

​

• Each table must include a minimum of 10 records

​

• Each table requires a primary key; foreign key

​

• Use of proper data type

​

• Use of input masks/validation rules/properties

​

​

Prototype Database

Stage 2: Forms/Subforms:

• Enough forms so the user can add/edit/delete data in all of the tables

​

• Required to include at least one subform/linked form

​

• Required to include the following command buttons on each form:
• Add, Delete, Find, Print, Close

​

• Must have user-friendly interface
• Properly labeled controls
• Aligned & formatted
• Correct tab order
• Color scheme

​

Prototype Database

Stage 3: Queries and Reports:

• Must have a least five (5) useful reports
• Must add business value to the company

​

• Two (2) reports must be grouped or summary reports

​

• One (1) report must be a parameter based report

​

• Proper formatting
• Use Relevant Titles/Control Names
• Titles should briefly describe what the report is displaying
• Proper alignment
• Color scheme

​

​

Prototype Database

Stage 4: Switchboard and Macros:

• Menu must auto-open when database is started

​

• Must have the following buttons:
• Help
• Exit
• All forms
• All reports

​

• Incorporate color scheme

​

​

​

Prototype Database

Final Prototype Deliverables

​

1. Database file

* Upload to Microsoft Access Prototype group submission box on UBLearns

* File Name: “Final Prototype Database”

​

​

2. Recorded Presentation

* Upload to Microsoft Access Prototype group submission box on UBLearns

* File Name: “Prototype Presentation”

​

3. Peer Evaluation submitted by each group member - this link will be emailed to you

​

​

​

​

• Will be recorded and submitted to UBLearns

​

• Presentations must be 6 – 8 minutes

​

• Everyone on the team must present

​

• Business Casual Attire

​

• Must present as persuasive sales pitch (i.e. consultants)

​

• Make sure to hide menus for submission/presentation
• File > Options > Current Database > Uncheck:
• Display Navigation Pane
• Allow Full Menus

​

Phase 9: Prototype Presentation

Prototype Presentation

1. Describe the current problem at the company

​

2. Describe your solution to this problem

• Explain elements of database that solve this problem
• Act as consultants; sales pitch to the company you are building the database for
• Assume classmates/audience are the board of the company you selected - pitch to them

​

3. Demonstration of database

• Show the most important/impressive parts of your database
• Do not show every single form/report in your database
• DO show subform, 2 grouped reports, report based on query
• Do NOT open tables, queries, or relationships

​

​

• Each member must complete a Peer Evaluation (link will be emailed to you)

​

• Due Week 11

​

​

Phase 10: Peer Evaluations

Prototype Grading Breakdown

Access Database (24 points total)

+

Prototype Presentation (6 points total)

​

TOTAL POINTS (Out of 30)

​