This site is from a past semester! The current version will be here when the new semester starts.
CS2113/T 2020 Jan-Apr
**Schedule**
  • Full Timeline
  • Week 1 [from Mon Jan 13]
  • Week 2 [from Wed Jan 15 noon]
  • Week 3 [from Wed Jan 22 noon]
  • Week 4 [from Wed Jan 29 noon]
  • Week 5 [from Wed Feb 5 noon]
  • Week 6 [from Wed Feb 12 noon]
  • Week 7 [from Wed Feb 19 noon]
  • Week 8 [from Wed Mar 4 noon]
  • Week 9 [from Wed Mar 11 noon]
  • Week 10 [from Wed Mar 18 noon]
  • Week 11 [from Wed Mar 25 noon]
  • Week 12 [from Wed Apr 1 noon]
  • Week 13 [from Wed Apr 8 noon]
  • Textbook
  • Admin Info
    • **Links**
  • Report Bugs
  • Forum
  • Instructors
  • Announcements
  • File Submissions
  • Tutorial Schedule
  • repl.it link
  • Java Coding Standard
  • Forum Activities Dashboard
  • Participation Dashboard
    •  Individual Project (iP):
  • Individual Project Info
  • Duke Upstream Repo
  • iP Code Dashboard
  • iP Progress Dashboard
    •  Team Project (tP):
  • Team Project Info
  • Team List
  • tP Code Dashboard
  • tP Progress Dashboard
    •

    • Week 3 [from Wed Jan 22 noon] - Tutorial

    0 [CS2113 students only] Form teams

    • Form teams, under the guidance of the tutor. See the panel below for team forming constrains and other related info.


    [Picture: The team that was at the top of early Google]

    When to form teams

    • CS2113T: Your team will be formed by the CS2101 side.
    • CS2113: Your team will be formed at the start of the week 3 tutorial. Please try to arrive on time for that tutorial; if you are not there at the team forming time and others in the class are unaware which team you wanted to be in, we'll have to put you into a team randomly.

    Team size

    • The default team size is five.

    Team composition

    • We allow some freedom in choosing team members, subject to these constraints:
      • All team members should be in the same tutorial. Delay forming teams until your place in a tutorial is confirmed. We do not allow changing tutorials to team up with your preferred team mates.
      • Teams of single nationality are not allowed unless the only language common among all team members is English. e.g. an all-Singaporean team that include both Chinese and Malay students. Rationale: to train you to work in multicultural teams, to ensure that English is used for all project communication
      • No more than one exchange students per team Rationale: to increase interaction between exchange students and NUS students.
      • Same gender teams are discouraged but allowed. Rationale: to train you for mixed-gender work environments.
    • We may modify teams when circumstances call for it. There is no avenue for you to object. Staying with your preferred team is not guaranteed.

    1 Register the team before leaving the tutorial

    • Get your team ID from the tutor. Each student must submit your team ID via the LumiNUS Class Groups page -- for us to know which team you joined. Note the team ID follows a specific format.

    Team ID

    • To be given to you after forming teams.
    • Has the form TUTORIAL_ID-TEAM_NUMBER e.g, CS2113-W14-2 means you are in tutorial CS2113-W14 (i.e., in module CS2113, on Wednesday, at 1400-1500), team 2.

    Our tutorial IDs are different from LumiNUS. Format: CS2113T-W09 means a tutorial of CS2113T module, held on Wednesday at 0900, and so on.

    Module Venue Time Tutorial ID
    in LumiNUS
    (don't use this!)    		 Our Tutorial ID
    (use this!)    		 Tutors
    (contact details)
    CS2113T COM1-B103[1] Mon 16:00 LC03 CS2113T-M16 Damith
    CS2113T COM1-B103 Mon 17:00 LC04 CS2113T-M17 TBD
    CS2113T COM1-B103 Tue 12:00 LC01 CS2113T-T12 Ryan, Wei Xiang
    CS2113T COM1-B103 Tue 13:00 LC02 CS2113T-T13 Tejas, Wei Xiang
     CS2113  COM1-B103 Tue 14:00 T01 CS2113-T14 Glen, Rachel
     CS2113  COM1-B103 Tue 15:00 T02 CS2113-T15 Jerry, Manaswini

    2 Introduce yourselves

    • Introduce yourself to the tutor and the members of your team and the partner team (i.e., the other team under your tutor)

    3 Fix a weekly project meeting time

    • If you haven't done so already, set up a weekly project meeting time/venue (and communication channels) with your team members.

    Team Communications

    • Use English for all team communications, both spoken and written.
    • We recommend at least one 1-2 hour face-to-face project meeting per week, in addition to any online meetings. Reason: you need to know how to run both types of project meetings. The project meeting time can be used to discuss project related things, but also, can be used as a time for team members to work on the project tasks individually (having all members in the same place will facilitate easier collaboration and more peer-learning).
    • Fix a weekly 1-2 hour time slot and a venue for project meetings after the team has been finalized (latest by week 3 tutorial). All members are expected to attend weekly project meetings (not doing so could lower the peer evaluation ratings you receive, which in turn will be factored into your grade).
      The best time to have the weekly project meeting is, after the previous week's lecture but before the deadline for weekly tasks.

    4 Help team members troubleshoot iP problems

    • Do a quick demo of your iP to the tutor.
    • If anyone is facing problems in the iP, work together to solve them.

    5 Find coding standard violations extra

    • Do the following exercise, if you have time.

    Identify coding standard violations in the following code:

    1. COM1-B103 is also known as the Active Learning Lab

    COM1-B103 is also known as the Active Learning Lab