Iteration 1

Make an appointment with your Client at which time you will demonstrate--with the jar whose modification date is no later than the due date-- that your system has the functionality that had been agreed upon between you and your client. This should occur as soon as possible after the due date.

Deliverable

Mail your TA/client a jar file, named <teamname>.jar. It should include the following directories and files (the names do not have to match exactly):

Directories

  • documents (3 points) -  has an index.html file that contains [links to] the following:
    • Vision statement - Is it clearly written? Is the extant work researched?
    • Project development principles - Is English crisp? Are principles traceable to practices?
    • Project development practices - Is English crisp? Are practices traceable to principles?
    • Javadoc - all public classes and public methods within those classes should have Javadoc. -  Complete? Useful?
    • Readme - complete, detailed instructions on how to: - Do instructions work as stated?
      • build your system
      • run your system.
    • Postmortem - Does it provide answers?
      • What went right?
      • What went wrong?
      • Specify any changes to your principles and practices for the next iteration.
    • Peer reviews - each team member reviews every other team member - Do they exist?
      • 1 - Unsatisfactory; 2 Developing; 3 Satisfactory; 4 - Exemplary
      1. Researched and gathered information
      2. Fulfilled team role's duties as assigned
      3. Shared the work equally
      4. Listened to other teammates' points of view
      5. Other (specify)
  • library -  has executables, typically jar files, that are not written by your team, but are needed to run your project.
  • scripts (1 point) - has the shell scripts needed to build and run your system. - Do they work?
  • source (3 points) -  your top-level package structure must be teamname.projectname. - Well designed? Compatible with Practices (e.g., coding conventions)?
  • [test] -  optionally include your unit test source files. Each test class is in the same package as the class it tests. You also may include these files in the source directory.
  • [testlibrary] - optionally has executables, typically jar files, that are not written by your team, but are needed to test your project.

Overall

  • Requirements (5 points) Does the system function as previously agreed?
  • Substance (3 points) How substantial is the system?