iP:
tP: v1.2
This activity is worth 2x2=4
participation points.
Wait for the email notifying you which iPs are allocated for you to evaluate. When the email is sent out, it will also be announced via course announcements.
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 in that email.
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 17.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 implementation effort for the tP is estimated with reference to the implementation effort required for a typical iP).
What's happening this week:
Having practiced the workflow in the previous iteration, this week's iteration v1.2 adds the first functional code changes.
v1.2
The breadth-first iterative approach requires each intermediate version to be a working version. However, to make things a bit easier for us (as we are only getting started with the project), we will not be releasing any new product version at the end of this iteration. This means you have the freedom to create PRs for small code changes, without the pressure to implement a feature end-to-end within one PR (or even within this iteration).
Things to note:
COMMON MISTAKE: Not following the required phrasing style for the first sentence of Java method header comments.
Each member is expected to in each .
Reason: As each iteration focuses on a different learning outcome, it is better for you to take part in each of them fully.
Prefer smaller PRs.
Reason: The ability to divide work into small yet meaningful PRs is another intended learning outcome.
Steps:
v1.3
, not by the current iteration v1.2
).v1.2
.v1.2
.Shocked by iP to tP transition? Around this time you will realize how the speed you can implement things in the tP is significantly slower compared to the iP. As discouraging as this might feel, there are several ways this can contribute towards the learning outcomes of this course, and it is not expected to affect your tP grade either.
Feel free to improve AB3 in any way you see fit. While not very 'buggy', AB3 is not 'perfect' either (it is not meant to be a 'model solution'). In particular, find and fix any bugs it has. If you are not sure if something is a bug or an intended behavior, you can post in the forum to check.
While we are on the topic, also note that the architecture of AB3 doesn't suit every kind of application either. As you gain more experience in other application domains, you will learn different types of architectures that you can add to the collection of different architectures that you can consider for future projects. The same goes for the tool chain and the tech stack of AB3. Therefore, do not try to apply AB3 as a template for every other project you encounter in the future.