Entity-Relationship Model AI Usage
Name of AI service/solution that was used
ChatGPT
URL:
Type of service/subscription:
ChatGPT Plus subscription
Final result
Diagram:
The final entity-relationship diagram was created and edited manually in TerraER. The final diagram files are attached on the ERModel page as ERModel_v03.xml and ERModel_v03.png.
Model description:
AI was used only as assistance for reviewing the model structure, checking whether the documentation follows the Phase P1 instructions, and improving the textual explanation of entities, relationships, cardinalities, participation constraints, design assumptions, and model history.
The final ER model contains the following entity sets:
- Buildings
- Rooms
- Equipment
- Users
- Reservations
- Approvals
The final ER model contains the following main relationships:
- has between Buildings and Rooms
- includes_room between Rooms and Reservations
- makes between Users and Reservations
- has_equipment between Rooms and Equipment, with relationship attribute quantity
- requests_equipment between Reservations and Equipment, with relationship attribute requested_quantity
- has_approval between Reservations and Approvals
- approves between Users and Approvals
The final model supports reservations that may include a room, requested equipment, or both. Equipment may be assigned to specific rooms through the relationship has_equipment, and equipment requested as part of a reservation is represented through the relationship requests_equipment.
The final design decisions, the TerraER diagram, the exported image, and the uploaded documentation were reviewed and finalized manually by the project author.
Entire AI usage log
- Prompt:
I am working on Phase P1 of a Databases course project called Room Reservation System. I need to check whether my ER model follows the official Phase P1 instructions.
Response summary:
The AI helped review whether the ER model contained appropriate entities, relationships, candidate keys, primary keys, attributes, cardinalities, and participation constraints.
- Prompt:
The professor suggested that the model should support equipment in rooms, equipment in general stock, and reservations for a room, equipment, or both. How should I update the model?
Response summary:
The AI suggested extending the model so that equipment can exist in general stock, equipment can be assigned to rooms, and reservations can request equipment as well as rooms.
- Prompt:
Check whether the updated TerraER model is conceptually correct before exporting it.
Response summary:
The AI helped check the updated model and suggested corrections related to optional participation, numeric quantity attributes, and relationship cardinalities.
- Prompt:
The professor said that the ER diagram should not contain foreign keys and should not contain weak or associative entities. How should I correct Phase P1 and Phase P2?
Response summary:
The AI explained that the conceptual ER model should not include RoomEquipment and ReservationEquipment as entity sets with foreign keys. It suggested replacing them with many-to-many relationships: has_equipment between Rooms and Equipment with relationship attribute quantity, and requests_equipment between Reservations and Equipment with relationship attribute requested_quantity. It also explained that the corresponding relational tables should still appear later in Phase P2 as a result of ER-to-relational transformation.
- Prompt:
Rewrite the ERModel wiki documentation according to the corrected v03 model.
Response summary:
The AI helped prepare revised textual documentation for the ERModel wiki page, including updated entity descriptions, relationship descriptions, design assumptions, and model history. The final text was reviewed and adapted by the project author before being published on the wiki.
