= Prototype Implementation

**Implemented use-cases:
**

- [https://develop.finki.ukim.mk/projects/Scholaris/wiki/UseCase1001Implementation UseCase1001Implementation] – Add University

- [https://develop.finki.ukim.mk/projects/Scholaris/wiki/UseCase2001Implementation UseCase2001Implementation] – Assign Grade to Student

- [https://develop.finki.ukim.mk/projects/Scholaris/wiki/UseCase3001Implementation UseCase3001Implementation] – Enroll in Subject

- [https://develop.finki.ukim.mk/projects/Scholaris/wiki/BuildInstructions Build Instructions]


= Use-Case Model AI Usage 

 **Name of AI service/solution that was used**: DeepSeek Chat

 **URL**: https://www.deepseek.com/

 **Chat Logs**: https://chat.deepseek.com/a/chat/s/ac3c3d6f-d413-4616-a432-5bfa965991ed

 **Type of service/subscription:** Free online AI assistant (chat-based)

== Final result 
AI was used only as a support tool during Phase P4 to identify SQL/database errors
and to correct enum values and query mismatches between the Java prototype and PostgreSQL schema.

All implemented use-cases, Java source code, and final SQL scripts were written and integrated manually.

== Diagram 
N/A (AI was not used to generate diagrams)

== Results in details / description 
During prototype development, AI assistance was used in the following situations:

- Debugging PostgreSQL errors such as:
  * relation "university" does not exist
  * invalid input value for enum enrollment_status

- Clarifying correct enum values:
  ENROLLED, PASSED, FAILED, DROPPED

- Fixing SQL statements used in JDBC prototype methods such as:
  * INSERT INTO Student_Subject (...)
  * UPDATE Student_Subject SET Final_Grade ...

- Verifying correct SELECT queries for:
  * viewing student grades
  * listing enrolled students per professor

The AI did not generate the full prototype code, but was used for troubleshooting and validation.

== Entire AI usage log ==

=== Interaction 1 ===
Prompt:
"sto e greskata? imam tabela University ama INSERT dava relation does not exist"

Response:
Explained PostgreSQL schema/search_path and case-sensitivity issues.

=== Interaction 2 ===
Prompt:
"ERROR: invalid input value for enum enrollment_status: COMPLETED"

Response:
Confirmed that COMPLETED is not part of the defined enum and suggested using PASSED/FAILED.

=== Interaction 3 ===
Prompt:
"SELECT query for students enrolled in professor subjects"

Response:
Suggested using DISTINCT to avoid duplicates.

=== Interaction 4 ===
Prompt:
"UPDATE Student_Subject set grade and status"

Response:
Provided corrected UPDATE using CASE for PASSED/FAILED status.