CS 5500 Assignment #12.
Assigned: Tuesday, 26 November 2013
Due: Wednesday, 4 December 2013

Working in an instructor-approved team of four students
(except for a few smaller teams approved by the instructor),
complete the semester project as specified in assignment 7.

Your prototype's source code must be written entirely by
your team.  Your team may not use source code written by
other students, source code obtained from the World-Wide
Web or other sources, and it may not use software packages
that are not already installed on the CCIS Linux machines.

In exceptional circumstances, you may ask the instructor
for permission to use third party source code.  Unless that
permission has already been granted in connection with one
of your prototypes from a previous assignment, you should
assume permission will not be granted.

Your prototype must include a README file (which *must* be
in UTF-8 plain text, use a consistent end-of-line convention,
consist entirely of lines shorter than 80 characters, and
be named README) that

1.  lists all members of your team,
2.  gives the preferred email address(es) for contacting
    your team,
3.  tells the grader(s) how your team's software can be
    compiled and run on any CCIS Linux machine in the main
    lab,
4.  acknowledges any third party software used (by permission!)
    in your submitted software.

All of the files necessary to construct and to run your
prototype must be combined into a gzip'ed tar file whose
name ends in tar.gz.  Submit that gzip'ed tar file before
10pm on the date it is due using the submit script that's
described at the course assignments page:

    http://www.ccs.neu.edu/course/cs5500sp13/assignments.html

Your software will be graded on these criteria:

1.  the quality of the instructions and documentation
    in your README file,
2.  the ease of constructing and running your prototype
    on CCIS Linux machines,
3.  your prototype's correctness with respect to
        parsing correct command lines
        reporting errors for incorrect command lines
        recognizing and allowing the supported file formats
        reporting errors for unsupported file formats
        producing correct error messages
        not producing extraneous output
        not attempting to create files outside of /tmp
4.  your prototype's reliability with respect to
        matching identical audio recordings
        matching extracts of a recording against its original recording
        matching altered excerpts against their original recordings
5.  your prototype's efficiency
6.  and the readability of your source code, which includes
        comments
        proper indentation (don't use tab characters!)
        all lines less than 80 characters
        adherence to accepted conventions and coding practices

----------------------------------------------------------------