Home Project Team Journal Deliverables Client Overview

Meeting Schedules

Client

Mentor

Team

Journals

Birdy Meeting 11/16:

Next steps

Final Presentation

Mentor Meeting 11/11:

Birdy Meeting 11/11:

Birdy Meeting 11/9

Recap:

Assignment:

Actions items:

Client Meeting 11/6:

Feedback on new design

Additional features/updates

Mentor Meeting 11/4:

Feedback on test coverage:

Feedback on demo:

Others: -Talk to Professor Hurlbert about transition and passing this project on

Birdy Meeting 11/2:

Recap

Action items

Client Meeting 10/30:

These are ordered in priority that Hurlbert prefers

Main Priority

Nice To Haves

Mentor Meeting 10/28:

Updates on Tech Talk

Testing

Feedback on demo

Client Meeting 10/23:

Weekly Feedback

Plan for Tech Talk

Mentor Meeting 10/21:

Demo Feedback

Future Plans

Birdy Meeting 10/19:

Updates

Action Items

Client Meeting 10/16:

Walking Skeleton Feedback

Mentor Meeting 10/14:

General Updates

Feedback on walking skeleton

Birdy Meeting 10/12:

Recap

Action items

Client Meeting 10/9:

Feedback on walking skeleton

Backend questions

Mentor Meeting 10/7:

Upcoming Presentation

Walking skeleton

Actions items

Client Meeting 10/2:

Feedback on walking skeleton

Updates on integration + backend

Mentor Meeting 10/1:

Feedback on walking skeleton

Feedback on architecture design/algorithm

Action items

-Fixing the format of our architecture design

Caronlina Cloud App Meeting 9/29

Overall Picture: Kubernetes and Docker images

How the platform works is that it adds our code on top of an image (e.g. openshift/node.js image) and uses docker to build a new “golden image”. This is what will be used to deploy. For the most part, deployments are stateless. If we redeploy, changes on the running pod will be gone. However, we can get persistent storage by setting up application with a storage volume.

Other Important Points

Birdy Meeting 9/28:

Architecture diagram + system

Walking Skeleton

Client Meeting 9/25:

About Database

Next steps

Mentor Meeting 9/25:

Recap of Meeting with Professor Hurlbert

APPLES Reflection

Architecture Diagram

Action items

Birdy Meeting 9/21:

Recap

Plans for Wednesday

Future plans

Client Meeting 9/18:

Giving Professor Hurlbert Updates

Design feedback

Next steps

Mentor Meeting (9/16):

Design

Future notes

Birdy Weekly Meeting 9/14:

Recap

Action items

Client Meeting 9/11:

User stories:

Design:

Questions:

Mentor Meeting (9/10):

Talked about meeting with Professor Hurlbert:

Went over the user stories:

Design:

Architecture:

Weekly Group Meeting (9/7):

User Stories:

Design:

*Backend:

Client Meeting (9/4)

Professor Hurlbert’s feedback on the design:

Mentor Meeting 9/2:

Jacob going over the website:

User stories:

Git collaboration:

Communication notes:

8/31/20 Weekly Group Meeting

Decisions:

Recaps + Plans:

Actions items:

Client Meeting (8/28)

Professor Hurlbert is envisioning 3 types of users:

End notes:

8/28/20 Weekly Group Meeting

Went through Git Collaboration:

Went through Code Style:

Next steps:

Action items:

Mentor Meeting (8/26)

Recap the meeting with Professor Hurlbert:

Should we learn R?:

Record of truth: should it be on the Excel spreadsheet or the website?:

The benefits of doing the design with InVision:

Data visualization:

Prototype: web and mobile:

Saving the different iterations of the architecture diagrams:

Communication management:

Git collaboration meeting:

Talk to Professor Hurlbert on the user stories:

Introduction Meeting w/ Professor Hurlbert (8/25)

Professor Hurlbert showed us the flat excel data + went over the column descriptions:

Questions on the requirement:

Why should the project be hosted on Carolina Cloud Apps?:

Why mySQL?:

Cron job: Do we need database versions?:

Slides 3-6 on the PowerPoint:

Action items:

Recap:

Agenda:

Action items:

Team roles:

Team rules:

Coding style:

Git collaboration: