Crow's Foot Notation for Organic Pasture Clinic Database Design

Verified

Added on  2025/04/28

|5
|645
|284
AI Summary
Past papers and solved assignments for students. This report details the database design for Organic Pasture Clinic using Crow's Foot notation.
Document Page
Contents
Assumptions....................................................................................................................................2
Crow’s Foot Notation......................................................................................................................3
References........................................................................................................................................4
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Assumptions
There are few assumptions that have been made while creating this crow’s foot notation and
these all assumptions are important and discussed thoroughly in this report. As the scenario is of
the clinic that provides the skin treatments and provides a rejuvenating experience to the
customer there is a need to create different entities and attributes in order to explain the
dependencies and a proper structure of the clinic. So there is a total of seven entities that are
present in the cross foot notations which are named as:
Records
Appointment
Treatment
Bookings
Client
Payment
Therapist
All these entities are dependent and connected with the relationships like one-to-many
relationship and one-to-one relationship. The entity Record has a one-to-one relationship with
the entity appointment and this entity has R_id as primary key in order to uniquely identify the
records of the clients (Shin, et al., (2017)). The entity Appointment is interconnected with table
booking as one-to-many relationship and the attribute book_id is the foreign key constraint in
this table which is taking reference from table booking. For every client, there is a different
treatment which is identified by a code which is why the T_code attribute is the primary key in
table Treatment.
Moreover, the table Treatment and Appointment were dependent on each other with the many-
to-many relationship so to shun it this different entity named as Booking, is created and this
entity is individually connected with table Treatment and table Appointment with a one-to-many
relationship. For unique identification of the bookings, book_id is the primary key here. In table
client, the detail of the clients are stored like name, age, gender, etc that are mentioned as
attributes of this table and a client_id is created for every client. The payment table is to keep the
record of the payments of the treatments that were taken by the clients in which pay_id is the
primary key for every payment a client does. And the last is therapist table for every therapist
there is an id that is given and different attributes that will help the client to understand which
therapist the client need to visit (Wang, et al.,(2017)).
Document Page
Crow’s Foot Notation
Figure 1: Crow's Foot Notation
The overall report concludes a Crow's foot notation in order to provide a general view of the
scenario given which is based on a clinic named as Organic Pasture Clinic (OPC) which helps
customers to take different treatments with their highly skilled workers and professionals
(García, et al.,(2016)). So the given scenario finally created by using the draw.io and after going
through the brief of the assessment and the understanding which the scenario provide there
should be seven different entities that are created with their different attributes and among two
entities there is some sort of relationship is also there that is making these entities dependent on
Document Page
each other. The relationships are explained by the arrows as well as in the form of 1:1 and 1: M
form stated in the above diagram. Different constraints of the primary key and foreign keys are
also added in order to make it appropriate.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
References
Shin, K., Hwang, C., & Jung, H. (2017). NoSQL database design using UML conceptual data
model based on Peter Chen’s framework. International Journal of Applied Engineering
Research, 12(5), 632-636.
Wang, X., Peng, Y., Lu, L., Lu, Z., Bagheri, M., & Summers, R. M. (2017). Chestx-ray8:
Hospital-scale chest x-ray database and benchmarks on weakly-supervised classification and
localization of common thorax diseases. In Proceedings of the IEEE conference on computer
vision and pattern recognition(pp. 2097-2106).
García, M. M., Denno, B. D., Miller, D. R., Miller, G. L., Ben-Dov, Y., & Hardy, N. B. (2016).
ScaleNet: a literature-based model of scale insect biology and systematics. Database: the
journal of biological databases and curation, 2016.
chevron_up_icon
1 out of 5
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]