iP plays mostly a formative role in this course, i.e., it aims to ensure everyone has achieved the basic competency level needed for the tP (it does not aim to rank you based on programming ability or differentiate strong programmers from the rest). Hence, it is graded somewhat like an S/U component and almost everyone is expected to receive full marks for the iP.
The iP is worth 20 marks.
- Meeting the bars specified below for each aspect will earn you full
20marks for iP. - Falling below the bars specified for any of the aspects below will limit your iP score to less than half the marks in that aspect.
That is, you either get full marks, or less than half the marks for each aspect.
Implementation [10 marks]
- More than 90% of all deliverables have been completed in the final version of the iP submitted.
Requirements marked as optional or if-applicable are not counted when calculating the percentage of deliverables.
When a requirement specifies aminimalversion, reaching that minimal version is enough for it to be counted for grading. However, we recommend you go beyond the minimal version; the farther you go, the more practice you will get. - No major bugs.
- Reasonable use of OOP, e.g., at least some use of inheritance, with code divided into classes in a sensible way (e.g.,
Ui,Storage,Parser,Todo,Deadline,Event, etc.). - At least half of the public methods/classes have Javadoc comments.
- Reasonable code quality:
- No blatant violations of the coding standard (both Java and Git conventions).
- The code is neat, e.g., no chunks of commented-out code.
- At least some errors are handled using exceptions.
Grading is mostly based on a manual check of your final submission. Automated checks done along the way mainly help you self-monitor your progress.
You can track your iP progress (as detected by our scripts) on the iP Progress Dashboard page.