DOCUMENTATION - CREATING PLANNING PRESENTATION

[keanacobarde]

User Story

I, as the instructor, want to see that my wayward student is planning a project thoroughly and thoughtfully. I want to see that they know exactly which audience they're catering too, what featues they're planning on implementing, and their process. I want to be able to understand their intention and their plan of execution in a succinct, timely, but still highly detailed manner.

Acceptance Criteria

AS LAID OUT BY THE FRONTEND CAPSTONE GUIDELINES - ALL OF THESE SHOULD BE INCLUDED WITHIN YOUR PRESENTATION

• [x] Your presentation should be created using a web presentation software (i.e. google slides, canva, prezi) so that you can share the links with the instructional team
• [x] Your proposal must clearly articulate the solution to the problem it is solving for your customers.
• [x] Your proposal must define a minimum of four user stories that describe the core functionality of your application. These stories should live in the project board of your repo. NOTE: Registration and login do not count since you are given the code for those. For help on authoring good user stories, please refer to the Write better user stories and bug tickets article.
• [x] Your proposal must include a hyperlink to your ERD and it must be accessible by the instructors as well as a picture of your ERD. If we cannot access your ERD, the proposal will automatically be rejected. To test your link, open an incognito window in chrome, paste the link. If you cannot access it or need to log in, the instructors will not be able to either.
• [x] Your proposal must include a hyperlink to your wireframes that comprehensively show the journey of a user through your application. You may use Figma, Google Jamboard, Google Slides, etc. If we cannot access your wireframes, the proposal will automatically be rejected.
• [x] Each view/page must be represented. Do not include login/register unless you need to customize those views for your user experience.
• [x] Buttons or links must be included with notes/arrows describing what happens when the customer clicks on it. To test your link, open an incognito window in chrome, paste the link. If you cannot access it or need to log in, the instructors will not be able to either.
• [x] Include 3 projects (artifacts) that show your growth over the time in the cohort and share your growth journey with us by screenshotting some code examples that also show your growth. (1-2 minutes)
• [x] Create a project board outlining your MVP and Stretch goals in tickets
• [x] If you are using an external API, gather all sample data and be prepared to demo your API during your presentation (via Postman AND with an HTTP request in code (i.e. fetch, axios, etc.) before committing to use the API.
• [x] You must have an ERD for your project
• [x] You must have a user-related data scheme. This means that different people can authenticate with your application, and the resources that are created must be assigned to individual users.
• [x] In addition to having user-related data, you need to have at least one more 1 -> many relationships defined in your ERD. Having a many -> many relationship is recommended, but not required for your client side project.

Dependencies

• PLANNING AND WIREFRAMING MUST BE COMPLETELY DONE.

  2 , #3

• Older projects. Try to finding older projects that showcase your skill at a certain point. What are some things you've improved on?

Dev Notes

• Make sure your Figma ducks are in a row. All the annotations that you need are there and everything is easily accessible.
• Make sure you know. your. shit. Think of edge cases. Think of the relationship each part of your data has with the other part. What happens when you delete an expense? What relationship is severed? What happens when you delete a category? What happens to the expenses associated with that category? What happens when you change the total amount of monthly income you're seeing? What if someone goes over the limit for what they can expend from a specific category. Think about this stuff!
• Time yourself and know what you're going to say. Like the instructions say. Don't just wing it. Be prepared for what they may or may not ask you about.
• Make it clear that you designed the wireframe with a certain UI library in mind, but if that doesn't work, it's going to take a similar structure regardless.

[keanacobarde]

PRESENTATION COMPLETED: APPROVAL RECEIVED FOR CODING https://docs.google.com/presentation/d/1AyDi_ZOX5Rd4IiM9J5cv9pd8nJ5PtfXhhdRS3L0EtaI/edit?usp=sharing