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

Week 4 [Fri, Feb 2nd] - 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:

Admin Appendix D: Getting Help

Topics:

  • [W4.1] OOP + Java: Inheritance

  • [W4.2] OOP + Java: Polymorphism

  • [W4.3] Java: Constants

  • [W4.4] OOP + Java: Enumerations

  • [W4.5] Automated Testing of Text UIs

  • [W4.6] Code Quality: Readability

  • [W4.7] Code Quality: Refactoring

  • [W4.8] RCS: Creating Pull Requests

Full ToC

Admin:

  1. Accept GitHub invitation from the course organization
  2. Submit coding exercises via Coursemology

iP:

  1. Create a PR to the upstream repo Mon, Feb 5th 2359
  2. Add Increments: Level-4, A-TextUiTesting, A-CodeQuality
  3. Get ready to review PRs before the tutorial
  4. Review some peer PRs during the tutorial

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