kgao144 / csci-4322---term-project

Final Project for Modern Software Development Spring 2023

CSCI-4322 Term-Project

Final Project for Modern Software Development Spring 2023

Team members:

Grady Cliche
Hayden Grubb
Patrick Vaughn
Kyle Hawthorne
Kevin Gao

Project Description:

The project of interest is an improvement upon an 'Eliza' program in the Python language. 
In this project our team has decided to work in an Kanban variation of AGILE methodology.

csci-4322---term-project's Issues

Submit Function Issue

• Once dialogue starts with Eliza, typing 'quit' and each time you submit the input makes Eliza repeat some phrases and input textbox doesn't get cleared.

• Can continue to input phrases into text field and the Submit button itself continues to send message through.

• created a clear input text field function
  

Notes : I think the program still works the same with the clear text field function, haven't used it yet on my branch.

Project Final Report Deliverables

Sprint 1 Meeting 2- Requirements & Discussion

Meeting minutes

- We discussed the overview of the project
- We discussed the languages, IDEs, and development methodologies that we are going to use
- We found raw python code for the Eliza program
- We discussed requirements of features to be added to project

- We decided the program should have an interface that resembles a chat log with ways to submit and insert phrases that the user wants responded to.
- We decided the program should have a starting interface to introduce the user to Eliza.
- We decided the program should have different themes to the window.
- We left additional features up to the remaining time available to develop the program.

What has been done/completed?

- Set up individual environments and Github repositories
- We have a python base to Eliza that runs through terminal in a rough manner

What has not been done/completed & why?

- The development of the front end, as we are just starting out we are hashing out the workloads of each person and the features that are required for that front end.

What we do next meeting?

- We continue the development of the features and discuss issues we encounter.

Context Checking Feature

Include possibility for context checking in this prototype.

Sprint 2 Meeting 2: Weekly Meeting

Meeting minutes

- We discussed our thoughts and path for our 'Eliza' project.
- We discussed requirements of techniques needed to be added to our dialogue management
- We elaborated on what our client (professor) wanted in terms of dialogue management 

What has been done/completed?

- Started editing Doctor.txt to incorporate some techniques and responses to cater towards suicidal tendencies

What has not been done/completed & why?

- The final documentation hasn't been completed as we are currently still working on finishing our database file.

What we do next meeting?

- We will finalize the program and prepare for our seminar.

Sprint 2 Meeting 1: Meeting with Client (Professor)

Meeting minutes

- We discussed our thoughts and path for our 'Eliza' project.
- We discussed requirements of features to be added to project
- We are to learn about dialogue management techniques that can apply to depression in students.

What has been done/completed?

- Set up individual environments and Github repositories
- We have a python base to Eliza that runs on a Tkinter window
- Began research on dialogue management

What has not been done/completed & why?

- We haven't implemented any techniques of cognitive behavioral therapy into dialogue management because we are still researching and trying to fully grasp the concept and ways to implement it into our program.

What we do next meeting?

- We will attempt to finish up research and implement a couple of methods and attempt to compare answers given by ChatGPT in order to evaluate efficacy of the implemented techniques.

Additional Keywords

The program will be able to respond to more keywords than it currently does. (doctor.txt)

Acceptance Criteria-

• The number of keywords that Eliza responds to should be increased
• Some responses should be added for the new keywords

Sprint Meeting - Templates

Meeting minutes

What has been done/completed?

What has not been done/completed & why?

What we do next meeting?

Hurt Statement

Write a hurt statement and send it to [email protected].

Hurt statement:
What are the limitations of your group towards the project, who is not contributing, what is preventing you from accomplishing your goal

Enter Button Functionality

Description: Include keyboard 'Enter' functionality to the text boxes

Team hurt Statement

Write what caused team to have issues while developing project

Story Template

Title:
Description:
Acceptance Criteria:

Eliza Chat Interface Draft

Description: The chat box interface where the user is able to interact with the Eliza bot using typed inputs and Eliza will in return give a response.
Components:

• Submit button
• Text box for user inputs
• Chat history/log
• Pressing enter in textbox will continue feature

Sprint Template

Sprint - Number
Sprint Description -

Sprint 1 Meeting 1 - Interim Report

Meeting minutes

- We discussed the overview of the project
- We discussed the languages, IDEs, and development methodologies that we are going to use
- We discussed requirements of features to be added to project
- We worked on our interim report.

- We planned the layout for our paper and split up sections for each member to work on.

What has been done/completed?

- We wrote the paper and finalized it for submission.

What has not been done/completed & why?

- We haven't begun research yet into Eliza as we are starting to focus on the paper and beginning the process of researching.

What we do next meeting?

- We will gather our research material and compare and discuss the necessities for our 'Eliza' program.

Dialogue Management Research

• We are to research cognitive behavioral therapy techniques to implement into dialogue management.
• Look up a couple of techniques to apply to 'Eliza'

Time Log

Description: Adding time log to the chat history for each respective message
Components:

• Time per message