- Individual Task: Explore AB3 features Sat, Aug 29th 23:59
- Team Task: Set up a project meeting time Tue, Sep 1st
- Team Task: Check up on team's collective iP status Tue, Sep 1st
Intro to tP Week 3
This week, we kick off the tP with a few light individual and team tasks, described in the sections below.
indicates an individual task (i.e., each team member has to do the task, graded individually).
indicates a team task (i.e., some or all members may do the work, graded for the whole team).
/ indicates a one-person-per-team task (i.e., one member can do the task on behalf of the team, although other members are welcome to pitch in).
Stronger teams are welcome to stay one week ahead of the tP schedule. However, do not move ahead more than one week, as doing the tP in a short burst will interfere with some of its learning outcomes.
1 Individual Task: Explore AB3 features Sat, Aug 29th 23:59
Objectives: (1) To get each of you to think of ways to improve AB3; (2) To detect any compatibility issues between your local setup and the expected Java version.
Submission: via the Canvas survey named
tP: AB3 Initial Experienceby Sat, Aug 29th 23:59Steps:
- Download the latest released version (i.e., the jar file) of AB3 from its upstream repo.
- Get it running on your computer. Play around with it to familiarize yourself with its current features.
- Add yourself to the list of contacts in AB3 (using the
add ...command). - Take a screenshot of the AB3 window while it shows the contact info you added earlier. Save it as a
.pngfile. - Think about how the AB3 user experience can be improved, for example, by tweaking the command format, the GUI, or the features. Note down your ideas as a list of feature suggestions, in free text (i.e., no specific format).
Suggested: Try to come up with at least 5 ways to improve AB3, going beyond the simple/obvious ones (i.e., this is a chance to be insightful but also creative).
Also keep the following tP constraints/recommendations in mind when doing this, as improvements that are not aligned with tP constraints are unlikely to be useful later.
- Use the Canvas survey mentioned above to submit the screenshot and the feature suggestions.
Note: The feature suggestions you submit will be shared with your team members later so that your team can use them when designing the tP product.
2 Team Task: Set up a project meeting time Tue, Sep 1st
- After forming teams, set up a weekly project meeting time/venue (and communication channels) with your team members:
- Submission (one person per team): via Canvas. Submission will open Friday evening, after team forming is complete for all tutorials. We'll let you know when it is open.
Details to submit:Which day of the week, and at what time, will your team hold weekly team meetings?What is the mode (online or F2F)?If F2F, where will you be meeting? If online, which software will you be using for the meeting?Have all team members explicitly agreed to the above plan? If anyone has not agreed, state who and why (e.g., uncontactable).
3 Team Task: Check up on team's collective iP status Tue, Sep 1st
- Check with all team members if any of them need help with the iP, and try to provide as much help as you can from within the team, e.g., offer to sit with them while they do the iP so that you can try to help when needed.
- Submission (one person per team): via Canvas. Submission will open Friday evening, after team forming is complete for all tutorials. We'll let you know when it is open.
After completing this task (i.e., after asking all team members if they need help with the iP and coming up with a plan to help those who do), one member should submit a brief status summary.
e.g.,One member is slightly behind and one significantly behind. We plan to have a code-together session on Sunday so that we can help them if they encounter problems.