This site is from a past semester! The current version will be here when the new semester starts.
CS2103/T 2020 Jan-Apr
Schedule
  • Full Timeline
  • Week 1 [Jan 13]
  • Week 2 [Jan 20]
  • Week 3 [Jan 27]
  • Week 4 [Feb 3]
  • Week 5 [Feb 10]
  • Week 6 [Feb 17]
  • Week 7 [Mar 2]
  • Week 8 [Mar 9]
  • Week 9 [Mar 16]
  • Week 10 [Mar 23]
  • Week 11 [Mar 30]
  • Week 12 [Apr 6]
  • Week 13 [Apr 13]
  • Textbook
  • Admin Info
    • Links
  • 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 4 [Feb 3] - 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.
    • If you can, do the post-lecture quiz together; while the deadline for the quiz is Thursday midnight, doing it before the tutorial will help you identify unclear areas, which you can then clarify during the tutorial.
    • Dealing with technical problems:

    • [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] RCS: Managing Pull Requests

    • [W4.7] Code reviews

    • [W4.8] Static Analysis

    • [W4.1] Design: Models

    • [W4.1a] Design → Modelling → Introduction → What

    • [W4.1b] Design → Modelling → Introduction → How

    • [W4.1c] Design → Modelling → Introduction → UML Models

    • [W4.2] Class/Object Diagrams: Basics

    • [W4.2a] Design → Modelling → Modelling Structure → OO Structures

    • [W4.2b] Design → Modelling → Modelling Structure → Class Diagrams (Basics)

    • [W4.2c] Design → Modelling → Modelling Structure → Object Diagrams

    • [W4.2d] Tools → UML → Object vs Class Diagrams

    • [W4.3] Class Diagrams: Intermediate-Level

    • [W4.3a] Tools → UML → Notes

    • [W4.3b] Tools → UML → Constraints : OPTIONAL

    • [W4.3c] Tools → UML → Class Diagrams → Associations as Attributes

    • [W4.3d] Design → Modelling → Modelling Structure → Class Diagrams - Intermediate

    • [W4.3e] Paradigms → OOP → Associations → Association Classes

    • [W4.4] Java: JavaFX
    • [W4.4a] C++ to Java → Miscellaneous Topics → JavaFX
    • [W4.5] Java: varargs
    • [W4.5a] C++ to Java → Miscellaneous Topics → Varargs :

    • [W4.6] RCS: Managing Pull Requests
    • [W4.6a] Tools → Git and GitHub → Manage PRs

    • [W4.7] Code reviews
    • [W4.7a] Quality Assurance → Quality Assurance → Code Reviews → What
    • [W4.8] Static Analysis
    • [W4.8a] Quality Assurance → Quality Assurance → Static Analysis → What

    Admin:

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

    iP:

    1. Review some peer PRs
    2. Add Increments as parallel branches: A-Gradle, A-CheckStyle, Level-10, A-Varargs

    tP:

    1. Start weekly project meetings
    2. Decide on an overall project direction (user profile, problem addressed)
    3. Start a collaborative doc to take project notes before the tutorial