tP: v1.5
What's happening this week:
v1.5
This iteration focuses on applying internal quality control before the product is exposed to outsiders. 'Outsiders' here refer to other teams that will be testing your product during the practical exam dry run (PE-D).
In 1, you will do an alpha testing of your own product, and record bugs, which can then be fixed during 2.
Keeping in mind that this is your last chance to do any feature enhancements (due to the feature freeze in iteration v1.6), in task 3 you will decide which final touches you would want to implement, and proceed to implement them.
At the same time, the UG and the DG needs to be updated, as given in task 4.
Things to note:
This iteration is normally done in one week, but is spread over two weeks due to clashes with holidays. So, do the amount of work you would normally do if this was only one week long (i.e., no need to do more work because there is an extra week for this iteration).
The tP progress dashboard will stay in Week 11 for an extra week (i.e., even when we are in Week 12), to reflect that you can use Week 12 to do Week 11 tP tasks i.e., pending Week 11 tasks will not turn red until end of week 12.
Remind yourself of the project grading criteria:
alpha-bug
in your issue tracker.v1.4
jar file is ready.alpha-bug
label to the bug report, as our grading scripts will look for it when assessing your contribution level for this task.alpha-bug
.If you want to smoke-test your JAR file on an OS not available within your team, you can post a request in the forum to see if anyone else in the class can help you smoke-test it on that OS.
The panel below contains guidelines your peers will use when determining bugs in the final product -- knowing them might be useful in preventing such bugs in your product in the first place. You may skip the 'General' section.
Ways to level up your tP game:
Coming soon
.Contacts-Pro-User-Guide.pdf
.docs/index.md
): Update to look like a real product (rather than a project for learning SE) if you haven't done so already. In particular, update the Ui.png
to match the current product ( tips).v1.5.1
.v1.5
is strongly discouraged because if you miss that deadline, your team will not be able to benefit from the PE-D at all. It is better to have an earlier release to fall back on in case that happens.v1.6
later should be the same as the features tested during PE-D, which is the rationale for the feature freeze anyway.