CSCI 350 - Software Engineering

Spring 2013

For 3/8:

At this point, your team should have a well-defined code base. This code base should meet the following constraints:
- All source files should be in a well-organized package hierarchy within a Mercurial repository.
- A suite of jUnit tests should provide as high a level of code coverage as is feasible.
- There should be a running executable that represents the current state of the project.
- All of the code in the code base should be as clean as possible.
One representative from each team will deliver a presentation that includes the following.
- Achievements relative to each goal.
- Risks
  - To what degree have previously identified risks been ameliorated?
  - Have any new risks been discovered?
  - What are the two biggest remaining risks?
- Demonstration of the running executable. Demonstrations of auxiliary executables are also welcome.
- A description of testing compliance. This should include:
  - Percentage of code base covered by jUnit tests.
  - A rationale for every method (or class) that is not covered by jUnit tests, along with a description of how these lines of code are being human-tested.
- Goals for the coming week.
- Responsibilities of each team member for the coming week.
The contents of the above presentation should also be recorded in a written document, submitted via Moodle.
All code completed during the week should also be uploaded.
If the team has decided to alter the requirements document any further, that too should be submitted.