Skip to content

Instantly share code, notes, and snippets.

@thuyanduong
Created December 13, 2022 20:14
Show Gist options
  • Save thuyanduong/98121064616e50dc928b7739e7cfd345 to your computer and use it in GitHub Desktop.
Save thuyanduong/98121064616e50dc928b7739e7cfd345 to your computer and use it in GitHub Desktop.
Solo Capstone Project Winter 2023

Solo Capstone Project

Welcome to the Project Build portion of Winter Capstone 2023! 🥳 🎊 🎉

Know that your Marcy Lab Family is proud of the work you've put into getting to this moment of the program, but above all else, you should be proud of yourself! This journey is not yet over, and in this last stretch, we want to do everything we can to support you and allow you to build one last portfolio project to show us, show yourself, and show the world that you are undeniably job-ready.

Expectations

In many ways, this Capstone project is going to feel like a scaled-down version of your Demo Day project. But in other ways, it's going to feel different because you're going to own this entire project yourself. These are the expectations we have for you over the next 8 weeks:

  1. You will complete two Code Challenges a day. One must be the same Code Challenge the class went over for the day. The other can be any LeetCode or Codewars challenge of your choice. You should save all your code so that an instructor can review it with you during check-ins.
  2. You will track the progress of your Capstone Project using Agile methodologies (Scrum Board) and update it daily.
  3. You will check-in with your Capstone Advisors (Itzel and Carmen) twice a week for 1-hour each time. You will use this time to share your completed Code Challenges, give project updates, and receive a live Code Review.
  4. You will be demoing your progress in front of your Capstone Advisors (Itzel and Carmen) and your Project Manager (Ann) once a week.

Project Requirements

You will be building a full-stack application with the following requirements:

  1. Your front-end must be a React project that uses Context API as the primary state manager.
  2. Your styling must come from a pre-built CSS library.
  3. Your back-end must be an Express API that is organized into routes, controllers, and models.
  4. Your database must have two entities (database tables), and they must have a one-to-many relationship between them.

Here are some examples ERDs for web applications with two entities with a one-to-many relationship:

You can have stretch features in mind. However, you must prioritize building out full-CRUD on both your database tables.

Schedule and Weekly Objectives

Week Focus Weekly Objectives
July 11th - July 15th Project Scoping and Proposal Submit a high-quality, detailed Project Proposal
July 18th - July 22nd Wireframing and ERD Domain Modeling Submit a collection of high-quality, detailed technical planning documents
July 25th - July 29th Project Build Week 1 Complete full-stack, full-CRUD features for one entity
August 1st - August 5th Project Build Week 2 Complete full-stack, full-CRUD features for your other entity
August 8th - August 12th Project Build Week 3 Integrate all full-stack features together
August 15th - August 19th Project Build Week 4 Polish your application and implement stretch features
August 22nd - August 26th Case Study Writing Document your technical journey in a Technical Case Study
August 29th - September 2nd Presentation Prep Prepare a presentation on your Capstone Project

Key Deliverables and Deadlines

Assignment / Deliverable Due Date
Project Proposal Fri, July 15th
Wireframes and ERDs Fri, July 22nd
Complete feature work for one entity Fri, July 29th
Complete feature work for all entities Fri, August 5th
Finish MVP Fri, August 12th
Polish and Deploy Application Fri, August 19th
Project Presentation Wed, August 31st
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment