Journal of Meetings and Decisions

Client Meeting: April 22nd, 2020

Discussed final project presentations
- Include system diagram/architecture, what is the use of our product, demo, our opinion on the technologies we used (bad/good), mention limitations (such as cost), etc. in a PowerPoint.
- Prepare a demo: When demoing, show off what we are most impressed by.

Showed updated front end to match what our client wanted.
Talked about UI updates to make the webpage easier to comprehend as a user.
- Add proximity message.
- Add a "No Schools Nearby" message if there are no schools nearby.
Talked a bit more on UI updates (color schemes, etc.)

Discussing how we only have one week left for development and should focus on the finalization.
Checked-off what bugs we have fixed and which small ones still need to be fixed.
Next deliverables:
- Handoff plan due this weekend.
  - How we made the webpage (what technologies we used, AWS switchover, etc.)
- How to prepare for the final project.

Discussed the deliverables we met from the previous week.
Talked about ways to optimize our website so it loads quicker.
Told to focus more on developing a working mobile version of the webpage rather than focusing on optimization.
Demoed the website to ensure we don't have any major coding to do, mainly just working on webpage resizing issues and small bugs.
Talked about redesigning the home page to match exquisite UI design standards.
Spend the next couple of weeks making hand-off videos, docs, etc.

Discussed the front-end design with our client.
- Might have to change up the home page a bit to make it more full.
- Add in a statement explaining what skillED is.
Made a plan for each member so we can make progress on our project effectively.

Only three week-long sprints remain.
- Ambitious and reach goals will likely not be possible.
Demonstrated database schema, current state of front end.
Deliverables for next week:
- Implement functioning search.
- Implement some manner of comparison between schools and programs.
  - Likely in the form of filtering and sorting.
- Create tutorial for Firebase entry to make hand off easier.
- Look into AWS hosting.
- Connect Google Maps API.

Went over/checked off the previous week's deliverables.
Defined our deliverables for the next two weeks:
- Work on the search algorithm for our frontend.
- Work on refactoring the database.
- Figure out a way to make adding data into our database easy for someone else (maybe by video).

Discussed what we plan to have done by next week.
- Same points as coach meeting.
Decided pulling class times will likely be too difficult.
- Talked about Coursicle and how they pair with institutions to get class times.
- If this is something Rocky and Vitaly wanted to explore more, they could.
Clients expressed interest in us using ed.gov College Scorecard API.

For next week:
- Everyone will have gone through a Vue.js tutorial to acquaint themselves.
- Put scraped school data into Firestore database.
- Perhaps continue to work on the front-end side.
We will keep separate git branches at first to get used to Vue.
Discussed the need for some info in the database to move forward with search functionality.
Talked about our current wire-frame and what possible other pages or routes we'd like to consider.
- Compare page.

Set our technologies in stone: Python, Firebase, Vue, etc.
Looked over our Specifications.
- Need to go and add a few more bullet points about our features.
Will need an API to resolve ZIP codes to a location.
- This will go under our Tech Stack: (Google Maps API).
For the Tech Stack:
- Bullet point our APIs, technologies, libraries, etc.
For the Wireframe:
- Make some mock-ups of the frontend design (1 or 2 different pictures of our interfaces, one being the search aspect).
For the Database:
- Discuss the database schema/how the database will be organized.

Talked about how to localize our data by focusing on the greater-Raleigh area.
We can push off the idea of data automaton until we get a working product.
Adding a Control Management System (CMS) would be nice eventually for admin control.
We could potentially work with a user login system with Firebase.
Expectations for next week: Have the demo homepage and complete specifications.

How are we going to get our data?
- Programs being offered, cost, time, how far away the school is, etc.
What will the scaling of this project be?
- Local, state-wide, or country-wide. We decided local at first, then build on that.
A mobile version would be nice to have, but this can be handled by the Vue.js framework.
Developing a skills test to point towards certain majors would be nice to have too.
Adding a rating/review system.
- Endorsing various programs, etc.

Discussed who our client is and what our project is about.
Seems as if our content is public, and we will need to group the data in order to propose it to the client.
- Discussed how we will update this database?
- We will need to automate as much data as possible.
We need to figure out what data we want/need for the user audience.
Discussed database technologies such as Firebase, MongoDB, SQL, etc.
- How will we index our data with our queries?

Short introductions to one another.
Talking about the AGILE framework for making the project.
Discussed potential overriding of client decisions should the technology not be favorable to the team.

Page updated

Google Sites

Report abuse