iP:
tP:
This activity is worth 2x2=4
participation points.
iP Peer Evaluation 1
) that you will be using to submit your evaluation and take note of the things you need to evaluate.java -version
command to confirm).java -jar {file_name}
command to open it.iP Peer Evaluation 2
).Reminder:
Milestone requirements are cumulative. The recommended progress for the mid-milestone is an implicit requirement for the actual milestone unless a milestone requirement overrides a mid-milestone requirement e.g., mid-milestone requires a document to be in a temp format while the actual milestone requires it to be in the proper format. Similarly, a requirement for milestone n
is also an implicit requirement for milestone n+1
unless n+1
overrides the n
requirement. This means if you miss some requirement at milestone n
, you should try to achieve it before milestone n+1
or else it could be noted again as a 'missed requirement' at milestone n+1
.
Try to achieve all milestone requirements, but do not fret if you miss a few. You will get full marks as long as you achieve about 60% of the milestone requirements on average. Yes, that's a pretty low bar, but we have set it low in order to reduce workload and stress. Ideally, you should achieve close to 80-90%.
Add functionality in small steps, aiming to deliver the first working version of your product by the mid-milestone (i.e., in one week), and v1.2 at the end of this iteration (i.e., in two weeks).
As mentioned in the last week, if you split the iteration into two smaller increments of one-week each (recommended), name the first one v1.2
and the second one v1.2b
.
From this point onwards each member is expected to contribute the amount of code does not matter; even small contributions are acceptablesome code to each v1.3, v1.4 milestone, preferably each week; only merged code is considered as contributions The ability to deliver code incrementally is an important learning outcome of this module because incremental delivery, among other things, improves the visibility of your work.(Reason).
If you plan to rename the code packages, you may want to do it around this time. Doing it later can be more difficult (e.g., it can cause more merge conflicts), and can cause problems in our code authorship tracking. Also note that renaming packages is optional.
Note: you are required to follow the forking workflow for at least for the first part of this iteration: