Week 5 iLab Database design using Visio (Part A and B both)




  1. A. Lab #: BSBA BIS245A-5A


  1. Lab 5A of 7: Database design using Visio, and based on data requirements and business rules focusing on normalizing data to third normal form.


  1. C. Lab Overview—Scenario/Summary:



  1. 2. Given a situation containing entities, business rules, and data requirements, create the conceptual model of the database using a database modeling tool.



You have been asked to create a database model using the MS Visio Database Model Diagram Template. The purpose of this iLab is to provide experience normalizing the database to third normal form based on limited instructions, data requirements, and associated business rules.


Upon completing this iLab, you will be able to

  1. 1. create a new Visio file for database design; and
  2. 2. using the data requirements and the business rules provided, develop a conceptual model (ERD), including attribute data types and required field length


  1. Deliverables



Section Deliverable Points
Step 1 YourName_Lab5A_ERMatrix.docx
Step 3 YourNameLab5A.vsdx (Visio Diagram)


  1. E. Lab Steps



  1. 1. Download the ER matrix starter file document from the Week 5 iLab page, and save the file to your local drive.
  2. 2. Using Citrix for MS Visio and/or MS Access
  3. If you are using the Citrix remote lab, follow the login instructions located in the iLab area in Course Home.
  4. 3. Start MS Visio
  5. open Microsoft Office, Visio application, or
  6. b. if you are using Citrix, click on Microsoft Office Applications folder to start Visio.




Step 1: Identify the entities and relationships.


  1. Over the past 4 weeks, you have created ERDs based on information provided. This week, you will complete the ERD being sure to normalize it to

3NF (third normal form). Normalization is the systematic application of rules designed to eliminate redundancy from the database. Data in previous weeks was, to some extent, normalized for you. This week, it is not. An abbreviated list of the data requirements follows.


College Scheduling Data Requirements


Student ID

Student First Name Student Last Name Course Code

Course Name

Course Description Course Credit Hours Course Time

Course Days Instructor ID Instructor First Name Instructor Last Name Room Number

Room Capacity




  1. b. Open the Word file in the Week 5 Lab Materials, Lab5A_ERMatrix.docx c. Save the Word file as YourName_Lab5A_ERMatri
  2. d. An ER Matrix helps define both the entities and the relationships between the entities. Using the partially completed ER Matrix below as a guide, complete

the matrix.


Hint: You should end up with four entities.


  1. List each entity both across and down.
  2. Determine whether a relationship exists between entities and define that relationship with a verb phrase. (NOTE: The entity with the greatest number of related entities is usually the center of the ER diagram.)
  3. Identify minimum (Optional or Mandatory) and maximum (only one, or one or more).




Student        Course






none             Enrolls in; Mandatory

One or


Is taken by:Â Â Â none

Optional One or more


  1. e. Save the completed matrix to submit as part of your iLa


Step 2: Create the initial ERD based on the matrix.


  1. Open a new blank Database Model Diagram in Visio. If you need assistance with this, refer to the Week 1 Lab Instructions. Be sure that all options are set consistent to those used in previous weeks so that you generate your model in Crow’s Foot notation.


  1. b. One of the issues in denormalized data is that it can result in many-to-many relationships that are not compatible with the relational database. Visio does not allow creation of a many-to-many relationship because of this incompatibilit Therefore, for any many-to-many relationships in your data, you will need to create two one-to-many relationships. See the example below.




  1. Based on the information from Step 1, create the initial ERD for the College Scheduling database including the many-to-many relationships. If you need assistance to create the entities, refer to iLabs from Weeks 1 and 2.


  1. d. Assign the primary keys and attributes from the data requirements to the proper entitie


  1. e. Save the file as YourName_Lab5vsdx.


Step 3: Normalize the ERD


  1. While the initial ERD is accurate, if you design a database without deviating from it, you will encounter problems. For example, a course is offered many times. If you use the course code, for example, BIS245, as the primary key,

you will only be able to list the course once. There are three possible solutions.

  1. 1. Assign another primary key, such as an auto-number field, so that the course can be listed multiple time However, this is not acceptable because it introduces redundancy rather than reducing it.
  2. 2. Use a composite primary key consisting of the Course Code and the

Section code. If you create a unique section code (EXAMPLE: YearTerm_Section or 2016SpringA_A), then you can list the course repeatedly. Again, this introduces redundancy, and is not an acceptable solution.

  1. 3. Split the table to create two table To stay consistent with DeVry terminology, create a second Section table. To ensure that a course is not entered twice, you might modify the Section code to include the course: BIS245_2016SpringA_A. By consistently using this format, you should not be able to duplicate the section, and can avoid a complicated composite key. However, as the Section table will serve as an associative entity, it is acceptable to borrow the primary keys of the parent tables.


  1. b. Open the Visio file from Step 2, and add a new page. Change the page tab to read Revised. Revise the initial ERD based on the following information.
  2. 1. A Course may exist without being offered. It exists in the catalog.

Courses are scheduled for a term and given a section. It is the schedule course (Section) that students enroll in, that are scheduled

in rooms and assigned instructors.

  1. 2. A Student can exist without being enrolled in a course.
  2. 3. An Instructor can exist without being assigned to teach a course.
  3. 4. A Room can exist without being scheduled for a course.
  4. Save the file with your revised ERD.


Lab 5A Final Deliverables

  1. YourName_Lab5A_ERMatrix.docx (Word Document) from Lab 5A, Step
  2. YourName_Lab5vsdx (Visio Diagram) from Lab 5A, Step 3.


Submit these files to the Week 5 iLab Dropbox.




  1. A. Lab #: BSBA BIS245A-5B


  1. Lab 5B of 7: Completing Forms


  1. C. Lab Overview—Scenario/Summary




  1. 5. Given a physical database containing tables and relationships, create forms which demonstrate effective user-interface design and allow for efficient entry and retrieval of dat




The iLab begins with creating a form in Access using the Form Wizard. After the form is created, the user can use Themes to change the appearance of the form. The second part of the iLab uses Form Design to create a form. Finally, the form will be customized.


Upon completing this iLab, you should be able to


  • create a form using the Form Tool;
  • create a form using Form Design; and
  • create a form using the Form Wizard.


  1. Deliverables


Submit the MS Access Database file that contains the forms created in this iLab.



Step Deliverable Points
1 Form 1—Form Tool—step-by-step 5
2 Form 2—Form Design—step-by-step 5
3 Form 3—Form Wizard—Employee/Customers Multi-Table Form


4 Form 4—Suppliers and Products Multi-Table Form 10




  1. E. Lab Steps



  1. 1. Download the Access starter file from the Week 5 iLab page, and save the file to your local drive.
  2. 2. Using Citrix for MS Visio and/or MS Access
  3. If you are using the Citrix remote lab, follow the login instructions located in the iLab area in Course Home.
  4. b. You will have to upload the Lab5_Start.accdb file to your Citrix folder. Follow the instructions located on the iLab area in Course Home.
  5. 3. Start MS Access
  6. If you are using Citrix, click on Microsoft Office Applications folder.
  7. b. If you are using Visio on a local computer, select Microsoft Office from your Program Menu.




Step 1: Using the Form Tool
Select Employees table as in the following figure. You will see the Employees table highlighted.



Click the Create tab, and then click the Form tool.




After clicking the Form button, a new form is created by Access.




The appearance of the form can be easily modified using the Themes option on the Design ribbon. As you move your cursor over the various themes, the form will adjust to preview how the modified form would look. You may select any of them for your form.


Click the Save button to save the form. Name it Lab5_Form1, and then close the form.


Step 2: Using the Form Design
Click the Create tab, then, click on the Form Design. (Make sure that you do not have any of the tables selected in the Tables list on the left side of the screen.)




After clicking the Form Design, a new form will be shown as the following diagram shows.




Click the Add Existing Fields option, and then click Show All Tables to show all the tables in the database.




Drag and drop fields from the Customer Table to the form. You can also double click the fields that you want to add. Select at least eight fields from the Customers table. Adjust the location of the fields, then, click the Form option in the View list to see the form. The View button is highlighted at the right or right click the design window at the top and select Form View.



Use these tools to toggle back and forth between Form View and Design View. See below.




After viewing the form, click the View button again, and select Design View to get back to the form design. Save the form as Lab5_Form2.

Step 3: Creating Multi-Table Forms
You can incorporate data from several tables in a single form. In this step, you will create a form that displays data concerning one employee. The form will also display data concerning the many customers that your employees serve. This type of relationship between employees and customers is called one-to-many relationships (one employee serving many customers). In this relationship, the Employees table is the one table and the Customers table is the many table.


To create the multi-table form using the Form Wizard

·      click the Create tab, then sele4ct the Form Wizard; and

·      make sure that the Customers table is selected in the Table/Queries box.


·      Select CustomerID, CompanyName, ContactName, ContactTitle, Address, City, Region, PostalCode, Country, and Phone Fields from Customers table.

·      Back in the tables/Queries, click on the down arrow and select Employees table. See the illustration below.



·      You also have the option to select Form with subform(s) or Linked forms. Select Form with subform(s), then click next.

·      In the next screen, you have the option of selecting the layout of your subform. Select Tabular, and then click next.



Assign a title to your form (Lab5_Form3) and subform (Lab5_Subform3), and click finish.



·      Click on View, and then view the form in Form View.



NOTE: You can drop down the Reports to field and see other options.

Before closing the form, go to Design View, and change the caption property for the form to Employees. Right click the Form title field and select Properties to see the Property sheet on the right. (See below.) Return to the Form View before saving your form.




In From View, your form should display nine records, showing employees and the customers that they serve. These records can be cycled through using the navigation options available (in Form View only) on the lower left of the application screen.


You will be prompted to save changes when closing the form. Say Yes to save changes at the prompt, and then close the form. (From3)


Step 4: Create a Multi-Table Form
Following instructions provided in Step 3, create a multi-table form, showing what products are supplied by which supplier. (Remember to consider the relationships and one-to-many above).


Requirements: There is ONE Supplier for MANY Products. You must display the following fields: SupplierID, CompanyName, ContactName, ContactTitle, Address, City, Region, PostalCode, Country, and Phone fields along with ProductID, ProductName, and CategoryID.


Your form should look like the following.



There should be 29 records in your suppliers, each providing numerous products.


Save your form as Lab5_form4 and the Subform as Lab5_Subform4.


Step 5: Submit Deliverables
Save your MS Access Lab5_Start.Accdb file as YourName_Lab5_Final.accdb


Submit the Access file created during this assignment to the Dropbox located on the Silver tab at the top of this page. (See the Syllabus section ”Due Dates for Assignments & Exams” for due date information.)




There are no reviews yet.

Be the first to review “Week 5 iLab Database design using Visio (Part A and B both)”

Your email address will not be published.