search

keanacobarde / BEDuo

0 stars 0 forks source link

SETUP/PLANNING - DOCUMENTATION + PRESENTATION PITCH #3

Closed keanacobarde closed 5 months ago

keanacobarde commented 6 months ago

User Story

I, as the developer, must include the following items within a Google Slides presentation during my capstone planning presentation:

Acceptance Criteria

As stated within the Backend Capstone Planning Proposal: 

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
Your proposal must clearly articulate the problem it is solving for your customers.
Your proposal must clearly articulate the solution to the problem it is solving for your customers.
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](https://medium.com/@Carmichaelize/writing-better-user-stories-and-bug-tickets-3cb5165e7db). 
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.
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. 
Each view/page must be represented. Do not include login/register unless you need to customize those views for your user experience.
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.
Include 1 project (artifact) that shows your growth over the time in the backend cohort and share your growth journey with us by screenshotting some code examples that also show your growth. Be ready to explain the code samples.
Include 1 Data Flowchart. Pick a part of your application where you’re creating, deleting, or updating a resource. Create a flowchart that explains what needs to happen in the client and server side codebase for that action to be initiated and completed. (From user clicks a button, the user sees the updated information on the DOM).
Include 1 Stretch goal. Pick a backend stretch goal you may not get to or a property you wish you could add to your backend. Explain the steps you would have to take to incorporate this property into your application.
Create a project board outlining your MVP and Stretch goals in tickets
Clearly explain how your frontend will communicate with your backend and how we are able to do this with code. 
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.
You must have an ERD for your project
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.

Dependencies

Dev Notes

keanacobarde commented 6 months ago

https://classroom.google.com/c/NjQ5NzU0MDM2NDM3/a/NjQ5NzU0MDM2NTc4/details

keanacobarde commented 5 months ago

Created presentation got approved for planning.