Iteration 3
Overview¶
Update on Mar 23
Moving forward, each group is required to set up a project board in their group repository.
In this iteration you want to aim for (one or more) User Stories that satisfy all (or most) of the following qualities:
-
part of the core requirements (subset of "Must have")
-
distinguish your app from other similar apps out there
-
could be considered among the most challenging requirements to be implemented
-
what makes yours "more than" a simple CRUD app
These are the deadlines for this iteration.
| Day | Date | Time | |
|---|---|---|---|
| Update Requirement Specification Document | Mon | Mar 23 | 11:00 PM |
| Retrospective for iteration 2 | Mon | Mar 23 | 11:00 PM |
| Upload Design and Planning Document | Mon | Mar 23 | 11:00 PM |
| Revise Design and Planning Document | Thu | Mar 26 | 11:00 PM |
| Deliverable (source code of a working app) | Thu | Apr 02 | 11:00 AM |
In light of the recent events, the deadline for some of the tasks are pushed to Mon, Mar 23 but I strongly recommend that you attempt to complete these task as early as possible. In particular the "Retrospective" of last iteration and "Planning" for the next iteration.
It goes without saying that you must prioritize your health and safety which includes e.g. plans of departure (if you were going to leave campus, then do so as soon as you can and put all course related activities on hold).
Update Requirement Specification Document¶
You only need to update the Requirement Specification Document if you want to make any changes to the specification of your proposed software project. That is, you can leave it as is, if you are happy with it.
Retrospective for iteration 2¶
You must add a "Retrospective" section to the end of your "Design and Planning Document" for iteration 2. The retrospective is an opportunity for your team to inspect itself and create a plan for improvements to be enacted during the next iteration. Review what you had done in iteration 2; note things that you have and have not delivered, note the challenges you had, and reflect on how you shall proceed in the next iteration to do a better job.
The "Design and Planning" Document¶
Add it3_dap.md file to your repository. The file contains the same sections as in previous iterations, namely:
-
A UML class diagram reflecting the "model" for iteration 3.
-
A wireframe of your user interface (only what you will build in iteration 3)
-
Iteration Backlog (list the User Stories that you will implement in this iteration).
-
Tasks (a tentative list of the "to do" in order to successfully complete this iteration).
When you meet again with your group on Thur, Mar 26, you may want to update the "Design and Planning" document to reflect the changes you make.
The Project Meeting will most likely be done remotely (e.g. video chatting) with your advisor and/or instructor. We will post further instructions when we get closer to the next project meeting day.
Final Deliverable¶
At the end of iteration 3, you must deliver a software that does what you have listed in the iteration backlog.
You must always keep your group repository updated with the latest changes; we will consider your last commit by Thur, Apr 02, 11:00 AM as your submission.