This site is from a past semester! The current version will be here when the new semester starts.

Week 4 [Fri, Jan 29th] - Summary

We strongly recommend you to have a team project meeting before the tutorial. Do the following during the meeting:

  • Finish the tP tasks allocated for the week. For example, if you don't have a preliminary project idea by this week's tutorial (as per the tP schedule), the tutor will not be able to give feedback on it.
    • Note that the timeliness of tP tasks (i.e., the deadline is the midnight before the tutorial) is graded under the project management component of the tP.
    • Keep notes of the meeting, and update project documents -- the tutor will ask for those during the tutorial.
  • Help each other finish iP tasks. Tasks allocated to this week are especially troublesome and some peer help can be very useful.
  • Dealing with technical problems:

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

  • [W4.10] Automating the Build Process

Full ToC

Admin:

  1. Accept GitHub invitation from the module organization counted for participation
  2. Submit post-lecture quiz counted for participation

iP:

  1. Review some peer PRs counted for participation
  2. Learn from others (optional)
  3. Add Increments as branches: A-Gradle, 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, problem addressed) before the tutorial