CS383 HW#6: Implementation

Group Sprint Due: Monday 4/11/16 10:00pm. In-class sprint report 2:30pm Monday 4/11.

  1. Translate your project's design (use cases, diagrams) into code.
  2. Add/refine design details as needed.
  3. Review all class diagrams, consider all aggregations to see if they should instead be a user-defined association. If they have an association name, get the diamond off them; it is either/or. Association names should not be whole sentences or long phrases; those go in the diagram dictionary.
  4. Add "diagram dictionary" below each class diagram if you do not have it already, defining the semantics of your classes and associations.
  5. Review and/or add reviewer information to sequence diagrams if it is not already present.
  6. Correct instructor feedback items.
  7. Prioritize backlog items to target code deliverables for the most central use cases. Try to deliver the first runnable prototype.
  8. In your sprint report, demo use cases that are done and non-usecase progress that has been made.
  9. Your group submission should be organized into three sections/chapters: requirements, design, and implementation. Regarding the implementation, the document should not include all source files, but rather, project organization (directories, summaries of files' contents) and JavaDoc or equivalent reference information.