1/17
Mr. Harris @Trinity
Requirements
As a __, I want __ so that __.
The use of requirements are to express a user’s needs in their own words, while also getting them to express the purpose of their needs so the developers can understand that while making their website.
On a basic level, each requirement is essentially a feature.
Minimum Viable Product (MVP)
The smallest set of features necessary to have a website that meets all your requirements and you can do a demo with… so you can get feedback from users!
OAuth - What did you learn?
I learned several things regarding OAuth, considering I knew nothing about it before I started researching. First, for the basics, I learned how to make a button and customizing it using HTML. I learned how to create a client ID from Google Cloud console and connect it to my development server. I learned how to set up id_token as a variable (for each person), run it through a verification system that returned False when the domain isn’t from trinityschoolnyc.org. Notably, I learned that you could use domain = payload.get(“hd”) to get the domain of the user… hence, how I could check the domain in my test code.
OAuth - How is it relevant to your project?
Given the sensitivity of the information (faces and names of students at Trinity), it’s necessary for the website to have a sign-in system so only people with the @trinityschoolnyc.org domain in their email can access it! Thus, this feature is a security concern eternally relevant to everything Sticker Tag.
Figma
Flow charts
Lo-Fi vs Hi-Fi Prototypes
Plan-based vs agile development
Agile Methods
Kanban vs Scrum
Git
With Git, you can track your version history and go back to a previous version if your code suddenly stops working. You can also create branches when working with other people so as to not interfere with their code!
Stage files
Commit
Push
Create branch
Switch to branch
Merge
Resolving merge conflicts