PROGRAMMING ASSIGNMENT #3

Date: May 30, 2023

TEAM 2 MEMBERS:
Brandon Hazelton, Jasper Dolar, Kevin Helm, YiOnni Redmon

TEAM MEMBER RESPONSIBILITIES:

All team members were equally responsible for managing group work and evenly contributed to the
success of group assignment 3.

TEAMWORK:
1. One team member will be team lead for the programming assignment.
Programming Assignment #3
Team Lead: Kevin Helm

2. Team lead coordinated between all team members in conducting team meetings 3 times before
the deadline of the programming assignment. Team lead took minutes of the meeting and
attendance during all meetings and shared with all team members.

3. Team members discussed the project on our group chat on Discord.

MEETING MINUTES

Team Meeting 1:

Date: May 22, 2023 / Time: 8:00 PM

Attendance: Brandon Hazelton, Jasper Dolar, Kevin Helm, YiOnni Redmon

AGENDA: Discussed how the team will evenly divide the team project. Team Lead Kevin
assigned our tasks. Brandon and Jasper were tasked to complete the server side of the
project and to put together the project write-up and Kevin and YiOnni would be
responsible for the other half of the project including testing and verifying. Team
members also agreed to check on each other’s work before the project is submitted to
make sure it meets requirements.

Meeting adjourned: 8:20 PM

 Team Meeting 2:

Date: May 27, 2023 / Time: 9:20 PM

Attendance: Brandon Hazelton, Jasper Dolar, Kevin Helm, YiOnni Redmon

AGENDA: We all checked each other on the progress of our assignment and agreed to
complete the project by 6 PM on May 30th.

Meeting adjourned: 9:40 PM

Team Meeting 3:

Date: May 30, 2023 / Time: 5:30 PM

Attendance: Brandon Hazelton, Jasper Dolar, Kevin Helm, YiOnni Redmon

AGENDA: The team worked together and agreed to the completeness of the group
project. Team leader submitted the completed work per instruction.

Meeting adjourned: 6:40 PM

4. What to hand in:

a. Client and server codes – submitted.
b. Minutes of the 3 meetings
c. PDF file with screenshots of server and client-side output as shown in the expected
output section.
- Screenshots showing each client making a connection with the server separately
(2 screenshots)
- Screenshots showing Client X and Client Y (as established by the server) sending
messages to the server separately in different order that is:
1. Client X sends a message to the server first then Client Y sends a
message to the server (2 screenshots)
2. Client Y sends a message to the server first then Client X sends a
message to the server (2 screenshots)

Individual Work:
Team members individually completed peer evaluation form on Canvas.
OUTPUT SCREENSHOTS:
Each client making a connection with the server separately:
Client X

Client Y

Screenshots showing Client X and Client Y (as established by the server) sending messages to the server separately in
different order that is:
Client X sends a message to the server first then Client Y sends a message to the server

Client Y sends a message to the server first then Client X sends a message to the server