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 7 [Sep 30] - Tutorial

    1 Exercise on Requirements: PR Tracker

    • Divide the team into sub-team A and sub-team B, 2-3 members each.
    • 7-8 minutes Write the answers to the following questions on the white-board.

    Question adapted from a past exam paper.

    Pull Request Tracker (PRT) is a desktop application meant to help CS2103 tutors deal with GitHub PRs more efficiently (compared to the GitHub Web interface). For example, it will help tutors find and review PRs from their mentees easily. It will help the managers of the module (e.g., professor, head TA) to easily keep track of how tutors are dealing with mentee PRs. PRT will communicate with GitHub using the GitHub API.

    Sub-team A:

    • Write 1 must-have and 1 nice-to-have user stories, covering user types tutor and manager.
    • Write at least 1 NFRs, related to performance/scalability and/or usability.
    • Give at least 1 terms worth recording in the glossary.

    Sub-team B:

    • Complete the following use case. Give at least one extension. Note that the tutor should give comments in the order of PR size (i.e., give comments to smaller PRs first). Assume the following use cases exists already: U1. Sort PRs by a criterion, U2. Add comments to a PR

    System: PRT
    Use Case: U3. Add comments to mentee PRs
    Actor: ...
    Precondition: ...

    ...

    • 7-8 minutes Discuss the answers with the whole team and the tutor

    2 Review Requirements of a Peer Team

    • Find the team you have been allocated to discuss in the panel below and click on the link to locate their team PR.
    Team Discuss PR of Backup team to discuss
    CS2103T-W11-1 CS2103T-W13-1 CS2103T-W12-1
    CS2103T-W11-2 CS2103T-W13-2 CS2103T-W12-2
    CS2103T-W11-3 CS2103T-W13-3 CS2103T-W12-3
    CS2103T-W11-4 CS2103T-W13-4 CS2103T-W12-4
    CS2103T-W12-1 CS2103T-W11-1 CS2103T-W13-1
    CS2103T-W12-2 CS2103T-W11-2 CS2103T-W13-2
    CS2103T-W12-3 CS2103T-W11-3 CS2103T-W13-3
    CS2103T-W12-4 CS2103T-W11-4 CS2103T-W13-4
    CS2103T-W13-1 CS2103T-W12-1 CS2103T-W11-1
    CS2103T-W13-2 CS2103T-W12-2 CS2103T-W11-2
    CS2103T-W13-3 CS2103T-W12-3 CS2103T-W11-3
    CS2103T-W13-4 CS2103T-W12-4 CS2103T-W11-4
    CS2103T-T09-1 CS2103-T16-3 CS2103-T14-3
    CS2103T-T09-2 CS2103-T16-4 CS2103-T14-4
    CS2103T-T09-3 CS2103T-T17-1 CS2103-T16-1
    CS2103T-T09-4 CS2103T-T17-2 CS2103-T16-2
    CS2103T-T10-1 CS2103T-T09-1 CS2103-T16-3
    CS2103T-T10-2 CS2103T-T09-2 CS2103-T16-4
    CS2103T-T10-3 CS2103T-T09-3 CS2103T-T17-1
    CS2103T-T10-4 CS2103T-T09-4 CS2103T-T17-2
    CS2103T-T11-1 CS2103T-T10-1 CS2103T-T09-1
    CS2103-T11-1 CS2103T-T10-2 CS2103T-T09-2
    CS2103-T11-2 CS2103T-T10-3 CS2103T-T09-3
    CS2103T-T11-2 CS2103T-T10-4 CS2103T-T09-4
    CS2103T-T11-3 CS2103T-T11-1 CS2103T-T10-1
    CS2103-T11-3 CS2103-T11-1 CS2103T-T10-2
    CS2103T-T11-4 CS2103-T11-2 CS2103T-T10-3
    CS2103T-T12-1 CS2103T-T11-2 CS2103T-T10-4
    CS2103T-T12-2 CS2103T-T11-3 CS2103T-T11-1
    CS2103T-T12-3 CS2103-T11-3 CS2103-T11-1
    CS2103T-T12-4 CS2103T-T11-4 CS2103-T11-2
    CS2103T-T13-1 CS2103T-T12-1 CS2103T-T11-2
    CS2103T-T13-2 CS2103T-T12-2 CS2103T-T11-3
    CS2103T-T13-3 CS2103T-T12-3 CS2103-T11-3
    CS2103T-T13-4 CS2103T-T12-4 CS2103T-T11-4
    CS2103-T14-1 CS2103T-T13-1 CS2103T-T12-1
    CS2103-T14-2 CS2103T-T13-2 CS2103T-T12-2
    CS2103-T14-3 CS2103T-T13-3 CS2103T-T12-3
    CS2103-T14-4 CS2103T-T13-4 CS2103T-T12-4
    CS2103-T16-1 CS2103-T14-1 CS2103T-T13-1
    CS2103-T16-2 CS2103-T14-2 CS2103T-T13-2
    CS2103-T16-3 CS2103-T14-3 CS2103T-T13-3
    CS2103-T16-4 CS2103-T14-4 CS2103T-T13-4
    CS2103T-T17-1 CS2103-T16-1 CS2103-T14-1
    CS2103T-T17-2 CS2103-T16-2 CS2103-T14-2
    CS2103-F09-1 CS2103T-F14-1 CS2103T-F13-1
    CS2103-F09-2 CS2103T-F14-2 CS2103T-F13-2
    CS2103-F09-3 CS2103T-F14-3 CS2103T-F13-3
    CS2103-F09-4 CS2103T-F14-4 CS2103T-F13-4
    CS2103-F10-1 CS2103-F09-1 CS2103T-F14-1
    CS2103-F10-2 CS2103-F09-2 CS2103T-F14-2
    CS2103-F10-3 CS2103-F09-3 CS2103T-F14-3
    CS2103T-F11-1 CS2103-F09-4 CS2103T-F14-4
    CS2103T-F11-2 CS2103-F10-1 CS2103-F09-1
    CS2103T-F11-3 CS2103-F10-2 CS2103-F09-2
    CS2103T-F11-4 CS2103-F10-3 CS2103-F09-3
    CS2103T-F12-1 CS2103T-F11-1 CS2103-F09-4
    CS2103T-F12-2 CS2103T-F11-2 CS2103-F10-1
    CS2103T-F12-3 CS2103T-F11-3 CS2103-F10-2
    CS2103T-F12-4 CS2103T-F11-4 CS2103-F10-3
    CS2103T-F13-1 CS2103T-F12-1 CS2103T-F11-1
    CS2103T-F13-2 CS2103T-F12-2 CS2103T-F11-2
    CS2103T-F13-3 CS2103T-F12-3 CS2103T-F11-3
    CS2103T-F13-4 CS2103T-F12-4 CS2103T-F11-4
    CS2103T-F14-1 CS2103T-F13-1 CS2103T-F12-1
    CS2103T-F14-2 CS2103T-F13-2 CS2103T-F12-2
    CS2103T-F14-3 CS2103T-F13-3 CS2103T-F12-3
    CS2103T-F14-4 CS2103T-F13-4 CS2103T-F12-4
    • Go to the PR.
    • Go the to the preview of the Developer Guide via the Netlify preview link.
    • 7-8 minutes Read the following sections and add review comments of areas to improve and doubts.
      If the DG does not have enough content for you to review, you can review the backup team (see the third column in the allocation panel). If even the backup team is not suitable, choose any random teams having tutorials in the same day and not in the same tutorial as you.
    • To be done collectively with sub-team members.

    • Add the review comment in the correct place of the code.

    • Choose the Start a review option rather than Add single comment.

    • Each person can do their own review, but coordinate with sub-team members to avoid duplicating the same point.

    • Phrase your comments as question/doubts (e.g., Is this format correct? Should it be ... instead?) rather than directives (e.g., Change this to ...).

    • Do not finalize the review at this stage. Just keep adding comments.

    • Sub-team A: use cases
      • Is the step numbering correct?
      • Are all possible extensions mentioned?
      • Are there any unnecessary UI details mentioned?
      • Any other formatting/notational errors?
    • Sub-team B:
      • User stories
        • Is the user story format correct?
        • All three parts present?
        • Does the benefit match the function?
        • Any important user stories missing?
      • NFRs
        • Are the NFRs are really Non-Functional?
        • Is each NFR well-defined (i.e., possible to decide when it has been met)?
        • Is each NFR reasonably achievable?
        • Are more relevant NFRs have been left out?
    • 7-8 minutes Discuss your comments/observations/doubts with the tutor and other team members to confirm the comments you entered are correct.
    • 5 minutes Update your review comments if necessary, based on the discussion you just had. After that, you can submit the review.
      After adding comments, you may want to unsubscribe from the PR to avoid getting GitHub alerts from that PR in the future.