Changes between Version 3 and Version 4 of Prototype


Ignore:
Timestamp:
02/08/26 14:05:36 (2 weeks ago)
Author:
216009
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Prototype

    v3 v4  
    1111
    1212- [https://develop.finki.ukim.mk/projects/Scholaris/wiki/BuildInstructions Build Instructions]
     13
     14
     15= Use-Case Model AI Usage
     16
     17 **Name of AI service/solution that was used**: DeepSeek Chat
     18
     19 **URL**: https://www.deepseek.com/
     20
     21 **Chat Logs**: https://chat.deepseek.com/a/chat/s/ac3c3d6f-d413-4616-a432-5bfa965991ed
     22
     23 **Type of service/subscription:** Free online AI assistant (chat-based)
     24
     25== Final result
     26AI was used only as a support tool during Phase P4 to identify SQL/database errors
     27and to correct enum values and query mismatches between the Java prototype and PostgreSQL schema.
     28
     29All implemented use-cases, Java source code, and final SQL scripts were written and integrated manually.
     30
     31== Diagram
     32N/A (AI was not used to generate diagrams)
     33
     34== Results in details / description
     35During prototype development, AI assistance was used in the following situations:
     36
     37- Debugging PostgreSQL errors such as:
     38  * relation "university" does not exist
     39  * invalid input value for enum enrollment_status
     40
     41- Clarifying correct enum values:
     42  ENROLLED, PASSED, FAILED, DROPPED
     43
     44- Fixing SQL statements used in JDBC prototype methods such as:
     45  * INSERT INTO Student_Subject (...)
     46  * UPDATE Student_Subject SET Final_Grade ...
     47
     48- Verifying correct SELECT queries for:
     49  * viewing student grades
     50  * listing enrolled students per professor
     51
     52The AI did not generate the full prototype code, but was used for troubleshooting and validation.
     53
     54== Entire AI usage log ==
     55
     56=== Interaction 1 ===
     57Prompt:
     58"sto e greskata? imam tabela University ama INSERT dava relation does not exist"
     59
     60Response:
     61Explained PostgreSQL schema/search_path and case-sensitivity issues.
     62
     63=== Interaction 2 ===
     64Prompt:
     65"ERROR: invalid input value for enum enrollment_status: COMPLETED"
     66
     67Response:
     68Confirmed that COMPLETED is not part of the defined enum and suggested using PASSED/FAILED.
     69
     70=== Interaction 3 ===
     71Prompt:
     72"SELECT query for students enrolled in professor subjects"
     73
     74Response:
     75Suggested using DISTINCT to avoid duplicates.
     76
     77=== Interaction 4 ===
     78Prompt:
     79"UPDATE Student_Subject set grade and status"
     80
     81Response:
     82Provided corrected UPDATE using CASE for PASSED/FAILED status.