| 5 | | This phase transforms the entity-relationship model from Phase P1 into a relational database schema implemented in PostgreSQL. The database objects are created in the official project schema named '''project'''. |
| 6 | | |
| 7 | | The relational model was created using partial transformation. Strong entity sets are transformed into separate relations, while many-to-many relationships and associative entity sets are transformed into separate relations with composite primary keys. Optional participation is represented using nullable foreign keys where appropriate. |
| | 5 | This phase transforms the corrected entity-relationship model from Phase P1 into a relational database schema implemented in PostgreSQL. The database objects are created in the official project schema named ''project''. |
| | 6 | |
| | 7 | The relational model was created using partial transformation. Strong entity sets are transformed into separate relations, one-to-many relationships are represented using foreign keys, and many-to-many relationships are transformed into separate relations with composite primary keys. Optional participation is represented using nullable foreign keys where appropriate. |
| | 8 | |
| | 9 | In the corrected ER model v.03, ''has_equipment'' is a many-to-many relationship between Rooms and Equipment with the relationship attribute ''quantity''. Therefore, it is transformed into the relation ''room_equipment''. Similarly, ''requests_equipment'' is a many-to-many relationship between Reservations and Equipment with the relationship attribute ''requested_quantity'', so it is transformed into the relation ''reservation_equipment''. |
