Semester Project: Part 2

Now that you have generated a feature list, a use case diagram, and a module breakdown of your semester project, it is time to start your first iteration. Each teammate should select a use case or feature (whatever makes sense for your particular project) and apply steps 4-7 of the OO A&D life cycle that we discussed on the fourth slide of lecture 14 and in detail throughout most of the OO A&D textbook.


Each teammate should be generating requirements, filing out use case details, creating class diagrams, writing code and test cases. In addition, each teammate will need to coordinate with the rest of the team to make sure that they are all working towards a common goal for the end of this first iteration.


By the end of the first iteration, your team should produce a document that includes the following sections:


Introduction: What goal did the team set for itself? Was it achieved? If not, how close did you come? How did you divide up the work among the teammates and did you take a use-case driven approach or a feature-driven approach to this iteration (or a combination of the two)?


Requirements: Combine all of the requirements generated by the team into a single coherent list with no duplicates.


Use Cases: List all of the use cases created during this iteration.


Class Diagram: As best as possible, combine the class diagrams generated by the various teammates into a single coherent diagram that shows what the team was trying to achieve in this iteration. Indicate in some fashion what classes were implemented and which one where only partially implemented.


Plans for Next Iteration: Describe how the team plans to proceed for the second iteration. What will you finish from the first iteration and what new functionality/use cases will you target for the next iteration. How do you plan to divide the work up?


Create a single archive that contains the document, plus the source code and test cases created by the team for the iteration, and upload it by 11:55 PM on November 21st. This assignment is worth 50 points.

Kenneth M. Anderson, 2008