Logged out
Access All our Essays in an Instant
Swap your work for FREE access, or pay £4.99 for instant access
Design of the Data Model
Member rating: No Rating | Words: | Submitted: Wed Jan 04 2006
Page Preview
On the left is an image preview of every page of this document, and below are the first 150 words with formatting removed:
Design of the Data Model This is an ER diagram before any normalisation processes has been carried out. Above is a display of four of the entities of the AZ Cut n Stylez organisation, these are Appointment, Schedule, Client, and Provider. Below in the tables is shown some of the properties/attributes of the entities. Schedule Appointment Client Provider Date Client ID Provider ID Time Surname Surname Client ID First Name First Name Title Title DOB DOB Address 1 Address 1 Address 2 Address 2 Home Tel: Home Tel: Mobile: Mobile: Key Field: A specific field to identify the entity as a whole. e.g. Provider ID in the Provider entity. Non Atomic Data: Data that has not been broken up into its smallest possible parts to create new fields. This type of data is not specific and can lead to confusion. This makes searching for queries inside the data base that mach harder to achieve. E.g. when the field is labelled "Name" when it can be broken down into "title", "Surname" and "First name". And if possible middle name. Repetition...
Get instant access
- Instant, unlimited access to our documents in full
- Swap your work for free access, or pay £4.99
- To see the full version of this document and 149,430 others
