This site is not ready yet! The updated version will be available soon.
CS2103/T 2020 Jan-Apr
  • Full Timeline
  • Week 1 [Aug 12]
  • Week 2 [Aug 19]
  • Week 3 [Aug 26]
  • Week 4 [Sep 2]
  • Week 5 [Sep 9]
  • Week 6 [Sep 16]
  • Week 7 [Sep 30]
  • Week 8 [Oct 7]
  • Week 9 [Oct 14]
  • Week 10 [Oct 21]
  • Week 11 [Oct 28]
  • Week 12 [Nov 4]
  • Week 13 [Nov 11]
  • Textbook
  • Admin Info
  • Report Bugs
  • Forum
  • Instructors
  • Announcements
  • File Submissions
  • Tutorial Schedule
  • Java Coding Standard
  • Participation Marks List

  •  Individual Project (iP):
  • Individual Project Info
  • Duke Upstream Repo
  • iP Code Dashboard
  • iP Showcase

  •  Team Project (tP):
  • Team Project Info
  • Team IDs
  • Addressbook-level3
  • Addressbook-level 1,2,4
  • tP Code Dashboard
  • tP Showcase
  • Week 5 [Sep 9] - Tutorial

    1 Discuss iP progress

    Quickly update the tutor about your iP progress:

    • Has at least one team member managed to set up Travis?
    • Has everyone completed Level-10 (i.e., the GUI) and A-Gradle? Any GUIs that went beyond the JavaFx tutorial?
    • Anyone has iP increments overdue more than one week?

    2 Discuss the code quality of iP PRs

    This activity is to be done as a team. One team member needs to be connected to the TV.

    1. Find the team you are allocated to discuss (given below).

      Team Discuss PRs of
      CS2103T-W11-1 CS2103T-W13-1
      CS2103T-W11-2 CS2103T-W13-2
      CS2103T-W11-3 CS2103T-W13-3
      CS2103T-W11-4 CS2103T-W13-4
      CS2103T-W12-1 CS2103T-W11-1
      CS2103T-W12-2 CS2103T-W11-2
      CS2103T-W12-3 CS2103T-W11-3
      CS2103T-W12-4 CS2103T-W11-4
      CS2103T-W13-1 CS2103T-W12-1
      CS2103T-W13-2 CS2103T-W12-2
      CS2103T-W13-3 CS2103T-W12-3
      CS2103T-W13-4 CS2103T-W12-4
      CS2103T-T09-1 CS2103-T16-3
      CS2103T-T09-2 CS2103-T16-4
      CS2103T-T09-3 CS2103T-T17-1
      CS2103T-T09-4 CS2103T-T17-2
      CS2103T-T10-1 CS2103T-T09-1
      CS2103T-T10-2 CS2103T-T09-2
      CS2103T-T10-3 CS2103T-T09-3
      CS2103T-T10-4 CS2103T-T09-4
      CS2103T-T11-1 CS2103T-T10-1
      CS2103-T11-1 CS2103T-T10-2
      CS2103-T11-2 CS2103T-T10-3
      CS2103T-T11-2 CS2103T-T10-4
      CS2103T-T11-3 CS2103T-T11-1
      CS2103-T11-3 CS2103-T11-1
      CS2103T-T11-4 CS2103-T11-2
      CS2103T-T12-1 CS2103T-T11-2
      CS2103T-T12-2 CS2103T-T11-3
      CS2103T-T12-3 CS2103-T11-3
      CS2103T-T12-4 CS2103T-T11-4
      CS2103T-T13-1 CS2103T-T12-1
      CS2103T-T13-2 CS2103T-T12-2
      CS2103T-T13-3 CS2103T-T12-3
      CS2103T-T13-4 CS2103T-T12-4
      CS2103-T14-1 CS2103T-T13-1
      CS2103-T14-2 CS2103T-T13-2
      CS2103-T14-3 CS2103T-T13-3
      CS2103-T14-4 CS2103T-T13-4
      CS2103-T16-1 CS2103-T14-1
      CS2103-T16-2 CS2103-T14-2
      CS2103-T16-3 CS2103-T14-3
      CS2103-T16-4 CS2103-T14-4
      CS2103T-T17-1 CS2103-T16-1
      CS2103T-T17-2 CS2103-T16-2
      CS2103-F09-1 CS2103T-F14-1
      CS2103-F09-2 CS2103T-F14-2
      CS2103-F09-3 CS2103T-F14-3
      CS2103-F09-4 CS2103T-F14-4
      CS2103-F10-1 CS2103-F09-1
      CS2103-F10-2 CS2103-F09-2
      CS2103-F10-3 CS2103-F09-3
      CS2103T-F11-1 CS2103-F09-4
      CS2103T-F11-2 CS2103-F10-1
      CS2103T-F11-3 CS2103-F10-2
      CS2103T-F11-4 CS2103-F10-3
      CS2103T-F12-1 CS2103T-F11-1
      CS2103T-F12-2 CS2103T-F11-2
      CS2103T-F12-3 CS2103T-F11-3
      CS2103T-F12-4 CS2103T-F11-4
      CS2103T-F13-1 CS2103T-F12-1
      CS2103T-F13-2 CS2103T-F12-2
      CS2103T-F13-3 CS2103T-F12-3
      CS2103T-F13-4 CS2103T-F12-4
      CS2103T-F14-1 CS2103T-F13-1
      CS2103T-F14-2 CS2103T-F13-2
      CS2103T-F14-3 CS2103T-F13-3
      CS2103T-F14-4 CS2103T-F13-4

    2. Locate PRs from that team: Go to the list of Duke PRs. Locate the PRs (you can filter using tutorial.* and team.* labels).

    3. Pick a PR to review, giving priority to PRs with fewer comments.

    4. Discuss abstraction aspect of the code: Go through the code, and discuss the abstraction (SLAP, arrow-head style code, too-long methods, too-deep nesting) aspect of the PR
      To identify long methods or deep nesting, zoom out and scroll through the entire PR code to do a visual inspection (no need to read the code line-by-line). After visually locating a method that looks too long/deep, have a closer look to see it can be improved by using better abstraction.If you are unsure about a case, you can also rope the tutor in to the discussion.

    5. Add comments: If the team agrees that the abstraction aspect of specific piece of code should be improved some way, add a comment (team members can take turns on adding comments).
      e.g., This method looks rather long; perhaps it can be shortened using SLAP?

    6. Repeat for remaining PRs: Continue to review PRs until the 30 minutes mark.

    After the tutorial, you can apply the insights gained from this activity to improve the code quality of your own iP, if necessary.

    3 Prioritize tP user stories

    • Show your list of tP user stories to the tutor (for progress tracking).
    • If you haven't done so already, prioritize tP user stories as explained in the   Project .