Changes between Version 1 and Version 2 of UseCaseModelAIUsage
- Timestamp:
- 09/02/26 21:01:33 (4 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UseCaseModelAIUsage
v1 v2 13 13 '''Diagram:''' No separate graphical use-case diagram was generated. 14 14 15 '''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, and how to prepare the TracWiki pages for the use-case model.15 '''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. 16 16 17 17 == Entire AI Usage Log == … … 36 36 37 37 '''AI response 5:''' The AI generated the relevant TracWiki pages. 38 39 '''Prompt 6:''' 40 How to best showcase expected attendance in !UseCase0003? 41 42 '''AI response 6:''' 43 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.
