SWEN-610

Class Schedule - SPRING 2026 TUES and THUR

Write ALL CODE in a feature/development branch. NOT your main branch.
On the due date (usually Tuesday), make a PULL REQUEST from your development branch INTO your main branch.
Your team mate will review the code in your pull request within 24 hours (typically by the end of Wednesday). Follow our expectations and code review guidelines when you prefrom your review.
Make changes to your code based on the feedback, then complete the pull request by merging it into your main branch.
TAG the final (merged) version of your code as a release. Final/ tagged version due 48 hours after Lab day (usually Thursday) by end of day.

- Session
- Date
- Topics
- Assignments
- Due
- 6
- 2/15
- - Complete Sprint 1
  - Rest 2
    - Chat
    - Rideshare
- Rest 1 due Tuesday this week
- 7
- 2/22
- - Sprint 2 plan - team
  - Client 0
    - Nightclub
    - Nutrikit
- Sprint 1 due Tuesday this week
- 8
- 3/1
- - Web Frontends 2 - css boogaloo
  - Javascript
- - Design Documentation - team
  - Client 1
    - Nightclub
    - Nutrikit
- Client 0 due Tuesday this week
- Break
- 3/8
- NO CLASS between 3/8 and 3/14
- None
- Rest 2 due Tuesday this week
- 9
- 3/15
- ReactJS
- - Client 2
    - Nightclub
    - Nutrikit
- Client 1 due Tuesday this week
- 10
- 3/22
- - Bootstrap
  - Fetch
- - Sprint 2 due
  - Sprint 3 plan - team
  - Client 3
    - Nightclub
    - Nutrikit
- Client 2, Sprint 2 due Tuesday this week
- 11
- 3/29
- - Software Metrics and Measurement
  - Defensive Coding
- Client 4
  - Nightclub
  - Nutrikit
- Client 3 due this week
- 12
- 4/5
- - Software Architecture and Patterns
  - the end is near
- None
- Client 4 due this week