Designing a data model promoting data redundancy and normalization provides a design that requires minimal modification o handle. (Tipper 2011) For your organization I propose the following normalization steps using the table information provided to achieve normalized data table structures. represent the data in tabular format with no cells having a null value and no repeating groups. The primary keys haven't yet been identified. Figure 1 Figure 2 2. For defining the primary keys I split the Customers table into two tables Customer and Tour respectively.
But I already had a Tour table at this time containing Tour cost information. Because of this I renamed this Tour table intonating cost information to Tourist and named the other table containing the Turtledoves, Numberless and Solely attributes to Tour as shown in After the primary keys were defined e
...ach attribute for each table was then dependent on the primary key for that table respectively. For the Customer and Employee tables in Figure 3 single attribute primary keys were used to uniquely identify each customer and employee.
The composite primary key Customer, Employed, Tournament, Outrage, Treason for the Tour table allows this table to almost act like an invoice for each tour sale. My tables were in INFO and because I had no partial dependencies my tables were now in INFO Proposed Naming Convention and Entity Attributes The table names "Employee", "Customer", "Tour", and "Tourist" accurately define the data represented within each table. To better associate the data in the Tour with its operational purpose I will rename to Turnover.
For this organization Vive gone back and renamed several entities to better associate the entity to the
table it belongs to. For example the Firestone attribute in the table was renamed to Manifested to associate this first name attribute with the Firestone and not Customer First Name which was changed as well. See the captures below for entity and attribute names and their data types. Figure 6 Naming Convention for Employee and Customer Naming Convention for Tourist and Turnover Table Proposed Entity-Relationship Model Figure 8 Many Customers complete one invoice (Turnover) at the sale of a tour.
- Research Methods essays
- Experiment essays
- Hypothesis essays
- Observation essays
- Qualitative Research essays
- Theory essays
- Explorer essays
- Data Management essays
- Enterprise Resource Planning essays
- Data Modeling essays
- Data Warehouse essays
- Operator essays
- Relation essays
- Sql essays
- Agriculture essays
- Albert einstein essays
- Animals essays
- Archaeology essays
- Bear essays
- Biology essays
- Birds essays
- Butterfly essays
- Cat essays
- Charles Darwin essays
- Chemistry essays
- Dinosaur essays
- Discovery essays
- Dolphin essays
- Elephant essays
- Eli Whitney essays
- Environmental Science essays
- Evolution essays
- Fish essays
- Genetics essays
- Horse essays
- Human Evolution essays
- Isaac Newton essays
- Journal essays
- Linguistics essays
- Lion essays
- Logic essays
- Mars essays
- Methodology essays
- Mineralogy essays
- Monkey essays
- Moon essays
- Mythology essays
- Noam Chomsky essays
- Physics essays
- Plate Tectonics essays
