Hi Prof Pranavan, we can work on the existing codebase from SoC (if permitted) and make changes to course content here. This is the least costly, safest fallback option.
This course will be delivered in blended learning mode (i.e., a mix of online and F2F activities) this semester.

Week 4 [Mon, Feb 2nd] - Summary

[MUST-WATCH] Course Briefing Segment - tP (8 minutes)

This week, we cover one more course briefing segment, given below. As with other course briefing segments, it is compulsory to watch.

tP Briefing (Part 1 -- Getting Started)

Video Video will be released closer to week 3 ...

As usual, the weekly briefing will be hybrid mode.

We strongly recommend you to have a team project meeting before the tutorial. Keep notes of the meeting, and update project documents -- the tutor will ask for those during the tutorial.

Do the following during the meeting:

  • Finish the tP tasks allocated for the week.
  • Help each other finish iP tasks. Tasks allocated to this week are especially troublesome and some peer help can be very useful.

On a separate note, our guidelines on dealing with technical problems:

Admin Appendix D: Getting Help

Topics:

  • [W4.1] Design: Models

  • [W4.2] Class/Object Diagrams: Basics

  • [W4.3] Class Diagrams: Intermediate-Level

  • [W4.4] Java: JavaFX

  • [W4.5] Java: varargs

  • [W4.6] Code Quality: Naming

  • [W4.7] Static Analysis

  • [W4.8] Code reviews

  • [W4.9] RCS: Managing Pull Requests I

Full ToC

Admin:

  1. Accept GitHub invitation from the course organization
  2. Submit weekly quiz

iP:

  1. Use GFMD in the PR description
  2. Review some peer PRs Fri, Feb 6th 1600
  3. Learn from others (optional)
  4. Add Increments as branches: A-CheckStyle, Level-10, A-Varargs

tP:

  1. Start weekly project meetings
  2. Start a collaborative doc to take project notes before the tutorial
  3. Decide on an overall project direction (user profile, value proposition) decide by tutorial, submit by: Sat, Feb 7th 23:59