Journals

Weekly meeting time: Friday 12:30-1:00pm

5/5/24 – Final Hand In

  • Recorded final presentation
  • Uploaded final architecture diagram
  • Updated website with design document info
  • Updated website with final presentation links

4/23/24 – Class 15

  • Made final end-of-semester to-do list
  • Planned dates for any meetings to finish up things
  • Discussed anything left to finish and divided up work

4/16/24 – Class 14

  • Database connection error fixed
  • Main application set up and running
  • Discussed closing up the semester and what is left to do with the project
  • Went over current bugs that still need to be fixed

4/11/24 – Class 13

  • Worked on fixing the Django project structure and removing deprecated features
  • Briefly spoke with the client to plan for the rest of the semester
  • Also went over team roles and goals for the rest of the semester

4/4/24 – Class 12

  • Troubleshooting for running the application (getting UI files corrected, fixing old Python, Django conversion issues)
  • Finished planning tech talk
  • Discussed plans for the documentation plan and client hand-off plan

3/19/24 – Class 11

  • Starting planning tech talk, agreed on preferred date
  • Talked about plans for APPLES assignment
  • Discussed best way to proceed with current state of code/application

3/7/24 – Tech Talk/Database Restoration Meeting

  • Brainstormed and talked about tech talk ideas
  • Restored the database from backup file, ran sample query on SSMS
  • Installed dependencies/tools to run/work on code
  • Looked at early problems in the existing code, started thinking about how to fix

3/5/24 – Class 10

  • Discussed changes to architecture diagram
  • Went over restoring the database (how to do so)

2/29/24 – Class 9

  • Discussed ethics assignment, divided work to complete
  • Planned testing database backup
  • Went over goals for the next 2 weeks

2/25/24 – Weekend Team Meeting

  • Organized and practiced project presentation
  • Discussed system architecture and created architecture diagram
  • Planned running the code and beginning work on requirements

2/15/24 – Meeting with UNC School of Dentistry IT

  • Discuss the situation/issues with the Dentistry School’s database
  • Troubleshoot database access problems, let IT know what exactly needs to be done with it
  • Work out obtaining access to the Sterilization database so that code can be run
  • Discussed platform selection post meeting.

2/9/24 – Coach meeting 2

  • Check In on week 1 meeting goals
  • Updated Sam on communications with System Admin and that we have access to the repository
  • Reviewed deliverables for next ~2 weeks including platform selection and architecture diagram 

2/8/24 – Class 8

  • Sorted requirements into functional/non functional, definite, perhaps, and improbable
  • Received contact info for Dental School systems admin to gain access to data base
  • User stories live on website for D1 Deliverables.

2/6/24 – Class 7(No Class Held)

2/2/24 – First meeting with Sam

  • Familiarized with course calendar and resource locations
  • discussed project timeline
  • reviewed website and initial project requirements

1/30/24 – Class 6

  • delegated journal entry, project concept, and user stories responsibilities
  • reviewed timeline for February

1/29/24 – First Client Meeting

  • Met client and scheduled bi-weekly follow-ups
  • Discussed requirements and desires for project
  • received initial code repository from previous contributors

1/25/24 – No Class Held

1/23/24 – Class 4

  • Received project assignment
  • Updated website description, tabs, and meeting times
  • Reached out to schedule client meeting
  • Scheduled coaches meeting

1/18/24 – Class 3

  • Decide on project preferences
  • Fill out website info
  • Email preferences and website link

1/16/24 – Class 2

  • Share technical interests and strengths 
  • Decide on best times for weekly coach meetings
  • Begin to create website using UNC WordPress