Assigment #9: Progress report + Requirements Document (showing current statuses of milestones)

Individually, let me know how much time you spent thus far on the project and what you worked on. This includes meetings with your project partners inside and outside of class, and any activity in support of the project, including research and documentation.

As a group, hand in a report that discusses:

• progress, issues/risks, outcomes (testing and documentation as per the done criteria (below), including rationales for design decisions, at least one of which was informed by experimentation or by scholarly research).
  • Done criteria: Each sprint ends with a potentially shippable product.
    • Testing level:
      • What were the tests and their outcomes?
      • Which features were formally tested (e.g. unit testing) ?
    • Documentation level:
      • design documentation (e.g. ER / UML diagrams; include discussion of issues, and evaluation of alternative solutions, i.e. rationale for your design decisions; at least one significant decision is informed by experimentation or by scholarly research. )
      • code documentation (e.g. javadoc, preconditions and postconditions...)
      • user documentation/manual (what does the user need to know to use your system, step-by-step, with screen shots to help illustrate)
    • Quality attributes = non-functional requirements, including readability (e.g. descriptive identifiers), ease of maintenance (e.g. abstract data types, method decomposition, separation of model and view), and any others that are applicable.
  • Requirements document, with statuses of milestones updated.