Reflect the fact that mentees don't need an account

The prototype being shared is hosted through Balsamiq: https://balsamiq.cloud/sfw1uih/pro9tuh

Update meeting minutes for oct 12th (detailed notes/action items)

There are prototype action items. Did we take care of them?

An explanation of how you will test the developed features of your system (in accordance with the tech stack chosen) as well as the method you will adopt to ensure continuous integration. Don't just use a technical term to describe the method; write a few sentences to explain the tools and techniques that will be involved. Read up on regression testing, and develop a feasiable plan that ensures when new code is added to your project that your project didn't break anything that was working before.

We have 2 Google Docs where some of the project's requirements are listed. We need to make sure all of them are clearly put "on paper" in the requirements.md file in this repo.

conclude prototype and questions

created sign up page

A detailed list of non-functional requirements and environmental constraints for the overall project.

W5 Client minutes and Team minutes.
W6 team meeting agenda.

A high-level description (about one paragraph) of the software you are building and who the target user groups are. Separately, explain how each user group is expected to use the software differently. (Recall that in order for two users to be considered as being in two different user groups, they must use the system differently either via a functional or non-functional system requirement.)

Look over the notes on github

Create a prototype to present a visual representation of our understanding of the system requirements for the client.

Client-Meeting to client-meeting

An overview of your system architecture presented as a data flow diagram (DFD), at both levels 0 and level 1, along with accompanying descriptions for each diagram. You must be very specific in this DFD so to design it in a way that supports an incremental and iterative development process. You can read an intro on DFDs and adopt its notation. Remember that a process does something, so be sure to use a verb to label your processes. In describing your DFD, highlight clearly which components will be delivered for each of the following milestones: peer testing #1, peer testing #2, and the final product. You may additionally wish to include extra components and label them as bonus features that may be developed if time allows.

Katrina gathered notes and functional requirements from her multiple meetings with the client, and we need to make sure the prototype we make will respond to all those notes and requirements the client communicated with us.

Update meeting minutes

Create meeting minutes oct 12

created login page

Identify the tech stack you plan to use. If this is the tech stack required by your client, then state that in the document. If your client is flexible, you must indicate a clear rationale of the choice made. This means an extra page with a table of at least 3 options and document all pros and cons for each before letting your client make a choice.

A detailed list of functional requirements for each milestone. Be sure to separate out the functional requirements for each system component based on the target milestone.

Add prototype issues

Edit/Combine Video demo for client

Create Aleks' part of video demo

Create Trello board for client

Upload and get link to video demo

Share feedback from the meeting to modify the prototype

https://discordapp.com/channels/756399767457628171/758257821937827870/761651910859817011

Finish prototype for video demo