Changes between Version 2 and Version 3 of ERModel

Timestamp:

07/18/26 14:39:33 (8 days ago)

Author:

236024

Comment:

--

ERModel

@@ -2 +2 @@
 == Diagram ==
 
-[[Image(ERModel_v08.png)]]
+[[Image(wiki:ERModel:ERModel_v08.png, width=100%)]]
 == Data requirements ==
 
@@ -344 +344 @@
 ||v07||Changed names to attributes and relationships so that all relationships are named and no attributes or relationships share the same name.||
 ||v08||Changed the weak entity keys of !EventSessions, !EventEditions and !ActivitySessions to account for edge cases where two sessions or editions could otherwise have the same identifying values and need location/title/start time to distinguish them.||
+
+\\
+
+= Entity-Relationship Model AI Usage =
+
+AI was used during the Entity-Relationship model phase only to review and improve my own initial model. The first versions of the model were created by me, and the AI was used afterwards to inspect the model, compare it with the project requirements, suggest possible improvements, explain unclear modeling choices, and help write the model documentation.
+
+My conversations with AI models, just like now, are usually for challenging my own way of thinking about the project and debating possible inconsistencies thoroughly.
+
+The final modeling decisions were made by me. Some AI suggestions were accepted, such as improving relationship names, clarifying weak entity keys, documenting data requirements, and checking consistency between the ER diagram and the written description. Other suggestions were rejected or adjusted when they did not match the intended scope of the project, for example adding unnecessary application review data, modeling event attendance, or expanding company management. 
+
+The changes made based on useful AI suggestions are documented in the model history above. The full AI usage documentation is shown below.
+
+== Name of AI service/solution that was used ==
+
+OpenAI Codex / ChatGPT
+
+'''URL:'''
+https://chatgpt.com/
+
+'''Type of service/subscription:'''
+AI conversational and coding assistant, accessed through an OpenAI Plus subscription account.
+
+== Final result ==
+
+'''Diagram:'''
+
+[[Image(wiki:ERModel:ERModel_v08.png)]]
+
+'''Model description:'''
+
+The final result is ERModel_v08, an Entity-Relationship model for BEST Skopje Hub. The model represents students, members, membership stages, organizational functions, activity sessions, event editions, event sessions, applications, companies, attendance, absence announcements, volunteering, mentorship, and event/company cooperation.
+
+AI was not used to generate the final model from scratch. It was used to review my own model, suggest alternatives, explain unclear relationship/cardinality choices, and help improve the written data requirements. The final model decisions were selected and adjusted by me according to the actual scope of the BEST Skopje Hub project.
+
+== Entire AI usage log ==
+
+The following is a line-by-line log of the relevant interactions with the AI during the ER modeling phase.
+
+'''Prompt 1:'''
+Are you able to read the latest version ER model in this folder?
+
+'''AI response 1:'''
+The AI inspected the project folder, identified the latest ER model file at the time, and confirmed that it could read the TerraER XML structure. It listed the main entities and relationships found in the model.
+
+'''Prompt 2:'''
+Can you tell me if the ER model fulfills my requirements and if not, what is missing, and what is redundant?
+
+'''AI response 2:'''
+The AI compared the ER model with the BEST Skopje Hub requirements and the attached project description. It identified which concepts were already represented and suggested possible missing or redundant concepts, including attendance, applications, core team functions, member stages, event editions, and company cooperation.
+
+'''Prompt 3:'''
+I responded to the AI suggestions and explained which features were intentionally out of scope, such as attendance for events, application review data, and detailed company management.
+
+'''AI response 3:'''
+The AI revised its assessment based on my clarifications. It agreed that several earlier suggestions were unnecessary for this project and narrowed the advice to the parts that mattered for the ER model.
+
+'''Prompt 4:'''
+How could event/session eligibility be modeled in the ER Model?
+
+'''AI response 4:'''
+The AI explained that eligibility could be modeled either as an attribute, as a relationship to !MembershipStages, or through a separate audience group entity, but also explained that this could remain business logic if it was not configurable data.
+
+'''Prompt 5:'''
+I'm confused about the relationship between !FullMembers and !OrganizationalFunctions. Should it be N:M or 1:N or N:1?
+
+'''AI response 5:'''
+The AI explained that the relationship should be N:M because one full member can hold multiple organizational functions over time, and one organizational function can be held by different full members in different mandates.
+
+'''Prompt 6:'''
+Should valid_from and valid_to dates be added? I thought mandate implies that.
+
+'''AI response 6:'''
+The AI explained that mandate can be enough for the project if it represents the time period of holding a function. It suggested that valid_from and valid_to would only be necessary for more precise temporal tracking, which I decided not to include.
+
+'''Prompt 7:'''
+All relationships should be named and duplicate attribute/relationship names need to be fixed.
+
+'''AI response 7:'''
+The AI first suggested broad renaming, then corrected the suggestion after I clarified that only duplicate names needed to be changed. It helped identify duplicate names and suggested clearer names for relationships and attributes.
+
+'''Prompt 8:'''
+I wanted better names than "has" for identifying relationships such as !ActivitySessions and !ActivityTypes.
+
+'''AI response 8:'''
+The AI suggested names such as instance_of, edition_of, part_of, session_inst_of, and available_for, which helped improve the readability of the ER model.
+
+'''Prompt 9:'''
+I asked the AI to help organize the data requirements for ERModel_v07 based on my existing ER model.
+
+'''AI response 9:'''
+The AI extracted the entities, relationships, attributes, and keys from my existing model and suggested a draft structure for the data requirements. I reviewed, corrected, and adapted the explanations, candidate keys, and logical attribute types before including them in the final documentation.
+
+'''Prompt 10:'''
+Write the data requirements in TracWiki notation.
+
+'''AI response 10:'''
+The AI converted the data requirements into TracWiki-style headings and bullet lists.
+
+'''Prompt 11:'''
+I asked about the key of !EventSessions, especially because !EventSessions is weakly identified by both !EventEditions and !EventSessionTypes.
+
+'''AI response 11:'''
+The AI corrected its earlier interpretation and explained that the full key of !EventSessions should include the !EventEditions key, the !EventSessionTypes key, and the partial key of !EventSessions.
+
+'''Prompt 12:'''
+Check ERModel_v08 and the newest data requirements.
+
+'''AI response 12:'''
+The AI compared the actual ERModel_v08 file with the written data requirements and found several small mismatches, such as stale key wording and naming inconsistencies. These were corrected in the documentation.
+
+'''Prompt 13:'''
+I repeatedly asked the AI to check the model and text again.
+
+'''AI response 13:'''
+The AI rechecked the model and text multiple times, verifying that all entities, relationships, attributes, weak keys, relationship names, and data requirement descriptions matched. It found and helped fix small text issues.
+
+'''Prompt 14:'''
+I asked why names such as !EventEditions were being rendered as links in TracWiki.
+
+'''AI response 14:'''
+The AI explained that TracWiki automatically links CamelCase words and that adding an exclamation mark before such words prevents automatic linking.
+
+'''Prompt 15:'''
+I asked the AI to rewrite the text with exclamation marks before CamelCase entity names.
+
+'''AI response 15:'''
+The AI generated a TracWiki-safe version of the text where CamelCase model names were escaped with !, preventing unwanted wiki links.