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 12 [Apr 6] - Project

    tP:

    1. Tweak the product as per peer-testing results
    2. Draft the PPP
    3. Prepare for the demo rehearsal
    4. Double-check RepoSense compatibility

    tP: mid-v1.4

    when setting the v1.4 deadline in GitHub milestones, remember that the v1.4 submission deadline is Week 13 Monday for everyone (does not vary by tutorial day). Set your own deadline accordingly, or else the bot will flag it as an 'unsuitable' deadline.

    Remind yourself of the project grading criteria:

    1 Tweak the product as per peer-testing results

    • Learn the procedure for dealing with PED bugs you received:

    • Freeze features around this time. Ensure the current product have all the features you intend to release at v1.4. Adding major changes after this point is risky. The remaining time is better spent fixing problems discovered late or on fine-tuning the product.
    • Update documentation to match the product.
    • Consider increasing test coverage by adding more tests if it is lower than the level you would like it to be. Take note of our expectation on test code (given in the panel below).

    • After you have sufficient code coverage, fix remaining code quality problems and bring up the quality to your target level.

    2 Draft the PPP

    • Create the first version of your Project Portfolio Page (PPP).
      Reason: Each member needs to create a PPP to describe your contribution to the project. Creating a PPP takes a significant effort; it is too risky to leave it to the last week of the project.

    3 Prepare for the demo rehearsal

    • You will do a product demo during the tutorial to serve as a rehearsal for the final project demo at v1.4
      • Follow final demo instructions (given in the panel below) as much as possible .
      • Cover all features, not just the ones added in the recent iteration.
      • Make it a 'well prepared' demo i.e., know in advance exactly what you'll do in the demo.

    4 Double-check RepoSense compatibility

    • Once again, double-check to ensure the code attributed to you by RepoSense is correct.