CSC 309 Examples

CSC 309
Examples

This directory contains examples of CSC 309 project milestones, showing approximately what class deliverables should consist of. The examples show the evolution of the design, implementation, and testing of an electronic calendar tool. The project directory structure is that described in the standard operating procedures handout, volume 1.

The calendar tool is a software system comparable in size and style to the CSC 309 projects. Since class projects differ in scope and focus, the calendar tool examples do not show exactly what your deliverables must contain. The examples do provide helpful concrete information for the phases of the 309 projects.

Milestone 2 example -- high-level package design only; minimal class stubs to support javadoc generation

Milestone 3 example -- refinement of model/view design and implementation; testing with canned data and stubs

Milestones 4 and 5 example -- refinement of model/view design and implementation; functional testing using TestNG; end-user acceptance testing

For functional testing, see in particular:

the Schedule.java model class
and its companion ScheduleTest.java testing class.
the Makefile to compile an run the Schedule tests
the TestNG configuration file
the command-line execution script that runs the compiled tests

For acceptance testing see:

a sample acceptance testing directory structure
a concrete example of an acceptance test plan

Other examples of possible use in 309 projects:

RMI -- client/server example using Java RMI -- Remote Method Invocation

groupable_header -- some classes that implement column and sub-column table headings

misc-java -- miscellaneous Java examples, developed during office hour discussions

sample midterm -- explanation of the style and topics to be covered the midterm

junit 3 sample -- very simple file setup for running Junit Version 3 on csl machines; see in particular the XTestDriver.java file.

cobertura example, with junit , testng -- simple code file and test driver used to illustrate the code coverage output of the Cobertura tool, as discussed in lecture notes weeks 7.