MN405 Business Rules of Database

The organisers of the GreenID2018 international multi-conference need to keep track of a large collection of workshops associated with the event. Initial requirements analysis brings out the following User view requirements / business rules about what needs to be recorded. Assume that you are given a task to model the database by using these business rules.

Complete the information-level design of the database that satisfies the following constraints and user view requirements. In order to complete this information-level design you are required to answer questions 1(a) to 1(f). 

User view 1 requirement  / business rule

• There are several participants, each of which may sign up to one or more workshops. 

      User view 2 requirement  / business rule

• Each workshop has a name, ID and an identified organizer .
• Some workshops happen on a particular date and some workshops last more than one day. You may need separate entity to store days. 

User view 3 requirement  / business rule

• For each participant, it is important to record their name, email address, state (VIC, QLD,..) and the workshops which they wish to attend.
• Every participant must register for at least one workshop. 

User view 4 requirement / business rule

• There are a number of meeting rooms at the conference venue, each of a fixed capacity. Meetings rooms are identified by a floor and room number.
• Every workshop needs an allocated meeting room; where a workshop lasts for two days, it will use the same room on both days 

Questions:

1. Analyse the all user requirements given above, identify and list all entities described in each user requirement.                                                                                                                                            (5 Marks)


Add attributes to these entities and represent these entities (or Tables) and attributes as a collection of Tables and attributes/ database schema. You are required to arrange them as given in the example below. (5 Marks)

Note: Select suitable primary key for each table and underline it.

Eg.        Participant (Participant_ID, P_name, email, W_name.) 

1. Outline all business rules that describe relationships between entities. (5 Marks)

Note: You can make assumptions to create certain relationships, if it is not specifically mentioned in the given business rules.

Eg.          Every workshop needs an allocated meeting room 

1. Determine the functional dependences.                                                                                       (5 Marks)

Eg.  Participant_ID  à name, address,   

1. Then normalise these tables. Make the normalization to 3NF. State for every step in the normalization, which functional dependency causes it.

 (5 Marks)

1. Represent the structure of your database visually by using the entity-relationship (E-R) diagram. If you make any assumptions about data that doesn’t show from the problem, they must be described.

Note: You are required to use Visio or any other software tool to create the ER diagram.

(15 Marks)

2. Build this model using MS Access by creating these tables and Relationships. Populate these tables with appropriate data, at least 3 records in each table.

(10 Marks)

3. Write SQL queries for the following questions and execute them on the database you created in Question 4.

 Include screen shots of the outputs and all SQL statements you used to answer following questions this model using MS Access by creating these tables and Relationships.   Populate these tables with appropriate data, at least 3 records in each table.

1. List details of all workshops.

 (3 Marks)

1. The management is interested in knowing names and email addresses of participants outside of Victoria who have already registered for the workshops.

 (3 Marks)

1. Explain how to formulate a query to print details of workshop name, room number, floor number and room capacity

Hint : You need to  join tables using a suitable query. (4 Marks)

Answer:

1 A) Database Entities

1. TabParticipant: It is enclosing the participant’s information.

2. TabWorkshop: It is enclosing the workshop’s information.

3. TabOrganizer: It is enclosing the organizer’s information.

4. TabWorkshopParticipant: It is enclosing the workshop and participant’s information.

5. TabMeetingRoom: It is enclosing the meeting room’s information.

6. TabScheduleWorkshop: It is enclosing the workshop schedule’s information.

7. TabWorkshopRoom: It is enclosing the workshop and room’s information.
8. 1 B) Tables and Attributes

TabParticipant (FParticipantID, FParticipantName, FAddress, FState, FEmail, FPhone)

TabOrganizer (FOrganizerD, FOrganizerName, FAddress, FState, FEmail, FPhone)

TabWorkshop (FWorkshopID, FWorkshopName, FOrganizerID)

TabWorkshopParticipant (FParticipantID, FWorkshopID)

TabScheduleWorkshop (FWorkshopID, FStartDate, FEndDate, FDays)

TabMeetingRoom (FMeetingRoomID, FFloorNumber, FConferenceVenue, FCapacity)

TabWorkshopRoom (FWorkshopID, FRoomNumber, FStartDate, FEndDate)

1 C) Business Rules

• A participate may involved in any number of workshops.
• One workshop will be in the same room from starting to end.
• 1 D) Functional Dependency
• FParticipantID à FParticipantName, FAddress, FState, FEmail, FPhone
• FOrganizerD à FOrganizerName, FAddress, FState, FEmail, FPhone
• FWorkshopID à FWorkshopName, FOrganizerID, FStartDate, FEndDate, FDays, FRoomNumber
• FMeetingRoomID à FFloorNumber, FConferenceVenue, FCapacity

1 E) Normalized Tables

1 NF Tables

TabParticipant (FParticipantID, FParticipantName, FAddress, FState, FEmail, FPhone)

TabOrganizer (FOrganizerD, FOrganizerName, FAddress, FState, FEmail, FPhone)

TabWorkshop (FWorkshopID, FWorkshopName, FOrganizerID)

TabWorkshopParticipant (FParticipantID, FWorkshopID)

TabScheduleWorkshop (FWorkshopID, FStartDate, FEndDate, FDays)

TabMeetingRoom (FMeetingRoomID, FFloorNumber, FConferenceVenue, FCapacity)

TabWorkshopRoom (FWorkshopID, FRoomNumber, FStartDate, FEndDate)

2 NF Tables

TabParticipant (FParticipantID, FParticipantName, FAddress, FState, FEmail, FPhone)

TabOrganizer (FOrganizerD, FOrganizerName, FAddress, FState, FEmail, FPhone)

TabWorkshop (FWorkshopID, FWorkshopName, FOrganizerID, FStartDate, FEndDate, FDays, FRoomNumber)

TabWorkshopParticipant (FParticipantID, FWorkshopID)

TabMeetingRoom (FMeetingRoomID, FFloorNumber, FConferenceVenue, FCapacity)

3 NF Tables TabParticipant (FParticipantID, FParticipantName, FAddress, FState, FEmail, FPhone)

TabOrganizer (FOrganizerD, FOrganizerName, FAddress, FState, FEmail, FPhone) 

TabWorkshop (FWorkshopID, FWorkshopName, FOrganizerID, FStartDate, FEndDate, FDays, FRoomNumber)

TabWorkshopParticipant (FParticipantID, FWorkshopID)

TabMeetingRoom (FMeetingRoomID, FFloorNumber, FConferenceVenue, FCapacity)

1 F) ER Diagram

References

[1] W3schools.in, “Database Normalization,” n.d.

[2] Freetutes.com, “ Types of attributes,” n.d.