iP (Individual Project): OverviewiP: Week 3


iP: Week 2

  1. Learn about the project
  2. Set up prerequisites
  3. Set up the project in your computer
  4. Add Increment: Level-0

The iP (and the tP) undergoes changes after each semester. As such, teething issues are a possibility. If you encounter any problem while doing the iP/tP, please post in the forum so that we can take necessary actions.

We discourage you from doing project tasks allocated to future weeks, although it is fine to stay ahead of the schedule a bit (but no more than a week ahead).
Reasons: In order to help you gain (and also to better simulate real projects), we want the project work to be and span a longer period, rather than to be done as a short burst.

Reminder: As per iP grading criteria, some increments need to be done in each week. Clumping all the iP work into a short burst of work will not earn you full marks.

Please follow instructions carefully. Any deviations can cause our grading scripts to miss your work (and result in you not getting credit for the work).

Deadline:

Note the typical deadline weekly project tasks:

But as there are no tutorials this week, you have until the next lecture to finish this week's iP tasks.

1 Learn about the project

  • Read the following two sections, if you haven't done so already:

Admin iP - Overview

Admin iP - Grading

2 Set up prerequisites

  • Ensure you have followed the Preparation sections of the following course tools:

Admin Programming Language

3 Set up the project in your computer

Read through this week's topics before starting the project.
If you encounter technical problems while doing the iP, follow the guidelines given below:

Admin Appendix D: Getting Help

  1. Fork https://github.com/nus-cs2113-AY2425S1/ip, while noting the points below:
    Keep the fork name as ip or else our grading scripts will not be able to detect it. You can change the fork name to something else after the semester (and the grading) is over e.g., after receiving your grade for the course.
    Untick the [ ] Copy the master branch only option so that you get a copy of the full repo.
  2. Enable the issue tracker of your fork (Go to Settings of your fork, scroll to the Features section, and tick the Issues checkbox). Reason: at times we post feedback on your issue tracker.
    If the issue tracker is enabled, you should be able to visit the following URL https://github.com/{your_user_name}/ip/issues
    e.g., https://github.com/johnDoe/ip/issues
  3. Clone the fork onto your computer.
  4. Set up the project in your IDE as explained in the README file, if you plan to use an IDE for the project.

4 Add Increment: Level-0

  • From this point onward, commit code at important points. Minimally, commit after completing each increment.
    Remember not to commit .class files and any other file that should not be revision controlled.
Duke Level-0: Rename, Greet, Exit


iP (Individual Project): OverviewiP: Week 3