Iteration 2 of your project will last for two weeks. Your deliverable is due at 11:55 PM on Friday, April 16th.
Overview
Over the next two weeks, your team will execute iteration 2 as described in the iteration plan that you submitted for Project 3. This means that you will assign tasks to team members and attempt to complete those user stories that were assigned to this iteration. Keep track of your daily progress using the Burn Down chart technique covered in the textbook. If you encounter tasks and/or user stories that were not in the original plan, be sure to add them and reshuffle your iteration plan accordingly. In this iteration, we are stressing the recently covered topics of testing and property satisfaction in FSP.
Deliverable
You should submit a PDF document as your deliverable with the following sections.
- Overview. Describe what your team did in this iteration, what problems you encountered and how you addressed them. In particular, describe what you did to start testing your code. Provide examples of the types of tests you are writing: e.g. unit tests, integration tests, system tests. Also describe what you've done to make it easy to run your tests as you work on your software prototype.
- Progress Report: List the tasks/user stories that your team completed and include a burn-down chart showing your team's progress over the course of the two week iteration.
- Diagrams: Provide any diagrams that you think best convey the progress of the system for this iteration. For instance, you might use a UML diagram to present the current state of the classes and relationships in the code completed during this iteration. Or you might show an architecture diagram (boxes and arrows) that presents the overall state of the system, what components have been completed, what will be worked on next, etc.
- Updated FSP (optional): If you have previously created an FSP diagram modeling the concurrency in your system, update your FSP model to include safety and liveness properties. Provide a paragraph or two that describe your new properties and what they mean. If you made any changes to the structure of your FSP specification as a result of your continued work on your software prototype, be sure to describe those changes.
- New Iteration Plan: Describe any new stories and/or tasks that were added to your iteration plan as a result of the work in this iteration. Recalculate your velocity using the formula in Chapter 10 of the Head First Software Development textbook and then include a new iteration plan that covers iteration 2 and iteration 3. Be sure to discuss the implications of this new plan: are you still on track with respect to the goals of the original iteration plan or did you have to re-scope the project based on the results of iteration 2?
Please submit your updated document via e-mail as a PDF document to Prof. Anderson by 11:55 PM on Friday, April 16th.
CAETE
All deadlines for CAETE students are one week behind those listed above.
Questions?
Contact Professor Anderson if you have any questions or concerns about this assignment.