CS383 HW#8: Metrics
Due: in-class May 4 for code/demo. 5pm May 13 for documentation.
Broad Goals
- Put together a runnable finished product
- Put together end-of-semester documentation
- Whatever backlog items your team deems essential for finished product
- Expand testing section to include elements of integration and/or system
testing
- Identify a modest list of easy-to-obtain metrics for your system.
Include at least: #directories, #files, #classes, #methods,
largest class/method, source lines
of code, static disk requirements for binary distribution, runtime
memory requirements.
- Means of Distribution: how can someone download and run your project?
If client/server, this is three different things: how to download and
run a client, how to download and run a server, and any configuration
or pairing actions needed to point the clients at the server.
- Usability: enough documents or in-game instructions so someone can
figure out how to run your project, including the mechanics of
various use cases.