4/6/2024 0 Comments Database design tutorial pdfThis removes redundant information, ensuring you store each fact once. The appointment will now store only the clinic's name: Appointmentįinding dependencies like this and splitting the tables is a process called normalization. This stores the details of each clinic: Clinic To avoid this, create a new entity, clinic. But there's a different address for each! APPOINTMENT_DATETIME CLINIC_NAME CLINIC_ADDRESS Storing the address on each appointment duplicates these details, making data errors likely.Į.g., both the appointments below are for the PHYSIO clinic. Every appointment at a clinic will be at the same place. For example, the appointment stores the clinic details. You represent this in an Entity-Relationship Diagram (ERD).Īt this point, we've identified the following information to store: PatientĪt this point you may identify new entities. It documents which aspects of the entities the system will store. The logical model fleshes out the details in the conceptual model.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |