Changes between Version 6 and Version 7 of ConceptualModel

Timestamp:

05/05/26 03:02:54 (11 hours ago)

Author:

181201

Comment:

--

ConceptualModel

@@ -2 +2 @@
 
 == Diagram
+[[Image(ERModel_v01.jpg)]]
 
 == Entities
@@ -133 +134 @@
 
 * {{{address}}} - Text (Required, location of the service).
+
+---- 
+
+{{{Review}}}
+
+The feedback that the {{{PetOwner}}} leaves for the {{{PetSitter}}} after a completed {{{Booking}}}. This is mandatory to maintain trust and establish quality on the platform. 
+
+'''Candidate keys:'''
+* {{{review_id}}} - '''Primary key'''; Unique surrogate key.
+
+'''Attributes:'''
+
+* {{{review_id}}} - Numeric (Required, Unique, Auto-generated integer).
+
+* {{{rating}}} - Numeric (Required, Integer from 1 to 5).
+
+* {{{comment}}} - Text (Optional).
+
+----
+
+{{{Service}}}
+
+Defines the type of care offered for the {{{Pet}}}, for example walking, overnight stay or short visit. If needed new services can be added without changing the database schema.
+
+'''Candidate keys:'''
+* {{{service_id}}} - '''Primary key'''; Unique surrogate key.
+
+'''Attributes:'''
+
+* {{{service_id}}} - Numeric (Required, Unique, Auto-generated integer).
+
+* {{{type}}} - Text (Required).
+
+* {{{description}}} - Text (Optional).
+
+
+----
+
+{{{Payment}}}
+
+Defines the financial transaction related to a {{{Booking}}}.
+
+'''Candidate keys:'''
+* {{{payment_id}}} - '''Primary key'''; Unique surrogate key.
+
+'''Attributes:'''
+
+* {{{payment_id}}} - Numeric (Required, Unique, Auto-generated integer).
+
+* {{{amount}}} - Numeric (Required, positive integer > 0).
+
+* {{{payment_type}}} - Text (Required, for example Cash or Card).
+
+== Relations
+
+{{{manage - Admin to User}}}
+* M:N relation
+* an {{{Admin}}} can manage multiple users, and a {{{User}}} can be managed by multiple admins.
+
+----
+
+{{{leaves - PetOwner to Review}}}
+* 1:N relation 
+* one {{{PetOwner}}} can leave many reviews to sitters, but each {{{Review}}} has one unique owner.
+
+----
+
+{{{receives - Review to PetSitter}}}
+* 1:N relation
+* one {{{PetSitter}}} can receive many reviews from clients, but each {{{Review}}} is meant for one unique {{{PetSitter}}}.
+
+
+----
+
+{{{is_a - Pet to PetType}}}
+* M:1 relation
+* many Pets can have one {{{PetType}}} (for example Cat), but each {{{Pet}}} has exactly one type.
+
+----
+
+{{{is_for - Pet to Booking}}}
+* N:N relation
+* a {{{Booking}}} can have two pets from the same owner, while a {{{Pet}}} can be part of many bookings during its life.
+
+----
+
+{{{books - PetOwner to Booking}}}
+* 1:N relation
+* a {{{PetOwner}}} can schedule many bookings, but each {{{Booking}}} is created by and owned by one unique {{{PetOwner}}}.
+
+----
+
+{{{is_booked - Booking to PetSitter}}}
+* 1:N relation
+* a {{{PetSitter}}} can be booked for many bookings, but each {{{Booking}}} is assigned to only one {{{PetSitter}}} at a time.
+
+----
+
+{{{provides - PetSitter to Service}}}
+* M:N relation
+* a {{{PetSitter}}} can provide multiple services (Walking, Overnight stay) and a {{{Service}}} (Walking) can be provided by many different sitters.
+
+----
+
+{{{requires - Booking to Service}}}
+* M:N relation
+* a {{{Booking}}} can require multiple services (Walking, Overnight stay) and a specific {{{Service}}} type can be requested in many different bookings.
+
+----
+
+{{{charged - Booking to Payment}}}
+* 1:1 relation
+* each {{{Booking}}} has exactly one {{{Payment}}} record, and each {{{Payment}}} record is associated with exactly one {{{Booking}}}