iP:
tP:
This activity is worth 2x2=4
participation points.
The allocation will be sent via email, by Monday 2359.
Download the latest JAR file of the first iP by following the link provided.
FAQ: What if the student has not uploaded a JAR file, or the JAR file doesn't work at all?
A: When you submit the evaluation (step 8 below), there will be a way to indicate that the JAR was not available, or any other serious issues you faced.
Locate the User Guide of the app by following the link provided.
Open the Canvas survey (the one named iP Peer Evaluation 1
) that you will be using to submit your evaluation and take note of the things you need to evaluate.
Run the jar file in the following manner:
java -version
command to confirm you are using Java 11.java -jar {file_name}
command (rather than double-clicking) in the same terminal.Do a light testing of the app (not more than 10 minutes) to ensure the claimed features actually exist.
Do a quick examination of the code (~ 5 minutes) by following the provided link.
Submit your evaluation using the survey.
Repeat the above steps for the 2nd iP allocated to you (use the survey iP Peer Evaluation 2
).
If both iPs crash or fail severely in a similar fashion, the problem may be on your side. Please contact the teaching team to ask how to proceed.
Take note of the effort required for a typical iP: After seeing two more iPs, you should now be in a better position to estimate how much you need to do for the tP (reason: the expected workload for the tP is that each team member puts in about one typical iP worth of effort).
Lookout for these mistakes which were the most common in previous runs of the course:
You may code from any of the below to be used in your tP, provided you give credit to the source (and do not claim such code as yours).
Start implementing v1.0, by adding code in small steps, while working in parallel, aiming to produce a VERY simple working version after one week, and a bit more functional version at the end of iteration (i.e., after two weeks).
See the panel below for our recommendations on the project workflow.
We recommend that each person adds some JUnit tests to test their tP code.
Some examples from AddressBook-Level2:
seedu.addressbook.common.Utils.java
seedu.addressbook.common.UtilsTest.java
seedu.addressbook.parser.Parser.java
seedu.addressbook.parser.ParserTest.java
parse_emptyInput_returnsIncorrect()
. Cross-check the coding standard to confirm if this naming convention is allowed.seedu.addressbook.data.AddressBook.java
seedu.addressbook.data.AddressBookTest.java