Description

The project was to create a data dictionary that can track a portion of the conference registration process. It was creating to track all aspects of interactions at the conference to show how much money was collect at each conference. The process to making this mock database was first to write out all the aspects that we need like the conference itself, the vendors, the session, and attendee’s information. In each section I just basically just wrote down all the things that I need in order to make this database affective. Starting with the conference itself, I realized that each conference will need their own identification so I created a conf_id attribute just so each conference can have something unique about them. Making the conf_id the primary key because it each is uniqueness. Then I go into the location that the conference is being held at. In the description each conference needs a vendor that can use for the conference. At the conference the vendor pays for a vendor table at the conference, so I made sure the ven_table_cost was included at the conference do to having a table at the conference. Also included was the conference date, time and each conference have a different seating capacity, so I made a conf_seating to clarify. The conference would not be a conference if they were not people to listen to it. I created an attendance table that included all the information so we can keep track of who is attending the conferences. To make sure each attendee has its own unique identification I created a “att_id” and made that the primary key. Next I created the vendor table which is where the conference will be held at. In that I included the cost of the vendor, and the status of the vendor just so the conference can know how the process is going. I also made the conference_rental_id the primary key because each conference is going to have their own rental identification just so it will not be confusing. For the conference cost table, I included the conference ID to specify each conference will have their own cost and vendor cost amount. Making all the cost be able to be more than billion dollars just in case. In the last table I choose to do a session table for the speakers at the conference. I made a sess_Id because we can have many different speakers at one event and their Id number would show the uniqueness of the ID number. The way I constructed this data dictionary is to basically think about what all I needed in order for the conference to be affective and also have all the key elements that were needed in the project.