| Version 2 (modified by , 4 days ago) ( diff ) |
|---|
Use-case Model AI Usage
Name of AI service/solution that was used
Name: OpenAI Codex / ChatGPT
Type of service/subscription: AI assistant available through the user's OpenAI account.
Final Result
Diagram: No separate graphical use-case diagram was generated.
Results in details / description: AI assistance was used to clarify how Board members should be represented as admin actors, how current users can be handled when the schema has no login table, how to use current time in SQL queries, how to document applications when real forms contain more fields than the ER model, how to showcase expected attendance and how to check the TracWiki pages against the current schema.
Entire AI Usage Log
Prompt 1: How should I treat Board positions if all Board members may have administrative access, but different Board members usually work in different areas?
AI response 1: The AI suggested using Board Member as the actor for administrative use cases and mentioning the concrete area of responsibility only when needed in the scenario.
Prompt 2: How should the application know which student or member is performing an action if the current schema has no login table?
AI response 2: The AI explained that login and permission checks can be handled by the future application, while the use-case SQL can use concrete sample values from the database.
Prompt 3: How can I list upcoming activity sessions using the current moment instead of a fixed test date?
AI response 3: The AI suggested using CURRENT_TIMESTAMP in the condition for future activity sessions.
Prompt 4: How should application submission be documented when real applications may have more fields than the current ER model?
AI response 4: The AI suggested using only the fields present in the current relational schema and documenting the scenario through the applications table.
Prompt 5: Generate the TracWiki pages with the context provided.
AI response 5: The AI generated the relevant TracWiki pages.
Prompt 6: How to best showcase expected attendance in !UseCase0003?
AI response 6:
The AI suggested showing expected attendance through required_attendance. The use case can list whether attendance is expected for the current member and only allow an absence announcement when a matching required_attendance row exists.
