What
is to be done?
Identify a number of features that need to be implemented for this
iteration. You will have to talk to your customer to know exactly what
they want. I.e. you will have to conduct a planning meeting with your
customer. Usually you will not be able to deliver everything the customer
wants in one iteration. So you will have to prioritize the features. Make
sure you write unit tests for the features you decide to implement.
You will be evaluated based on the deliverables below, the quality of the
system produced, and your adherence to the practices described in class.
(a) You should have a working system that the customer as well as the
instructor and the TAs can run without complications. You will be asked to
show your code and the tests you wrote for the implemented features. You
will present the system to your customer on-demand.
(b) Your report should include a domain model of the system showing the
main entities and their relationships, a high-level technology diagram
showing the different components and layers of the architecture, and a
sequence diagram representing one story of your choice.
(c) Submit an updated version of the identified stories/items and their
new priorities. Highlight stories/items that were implemented, and
stories/items that are yet to be implemented (take pictures of your story
board).
(d) Write one report for the whole team explaining the results of this
iteration. The report should also include the individual efforts of each
member. For example, John implemented stories A and B, wrote the tests for
stories A, B, C and D, wrote section 3.1 in the report and reviewed
sections 1 and 2.
(e)As usual, the report should be targeted to your customer and should
have already been "signed off" by the customer (your TA) in the form of an
attached critique of the report.
(f) Each member in the team should submit a peer-evaluation
report.
Last updated
2012-01-09 12:02 |
|