CS 5500 Assignment #7.
Assigned: Wednesday, 23 October 2013
Due: Wednesday, 6 November 2013

Working in an instructor-approved team of four students
(except for a few smaller teams approved by the instructor),
develop a rapid prototype of the greatly simplified version
of the semester project specified below.

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.  You should
not assume that permission will 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 rapid prototype
    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 prototype 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

Your prototype's build process must result in software that
can be invoked by cd'ing to the directory containing your
software's executable and executing a command of the following
form:

    ./arc5500 <pathspec> <pathspec>

where <pathspec> is a sequence of tokens generated by

    <pathspec>  ::=  -f <pathname>
                  |  --file <pathname>
                  |  -d <pathname>
                  |  --dir <pathname>

and <pathname> is a Linux path name for a file (in the -f and
--file cases) or directory (in the -d and --dir cases) that
already exists on the CCIS shared file system.

If the <pathspec> uses the -f or --file options and names a
file, that file should be in WAVE or MP3 format.  (You needn't
support the more obscure WAVE and MP3 formats, but you should
support the more popular WAVE and MP3 formats.)

If the <pathspec> uses the -d or --dir options and names a
directory, then every file within that directory should be in
WAVE or MP3 format, and that directory should not contain any
subdirectories.

Recognition of the WAVE and MP3 formats should not rely on file
name suffixes.

If the command line is correct and each <pathname> is correct,
then the arc5500 program should compare the recordings to see
whether either is likely to have been derived from the other.

If a match is found, then the arc5500 program should print
"MATCH: " to standard output, followed by the approximate
offset in seconds at which the match was found (as measured
from the beginning of the longer recording), followed by one
space, followed by the short name of the file containing the
longer of the two recordings, followed by one space, followed
by the short name of the file containing the shorter of the
two recordings, followed by a newline.

If no match is found, then the arc5500 program shouldn't print
anything.

If the command line is correct, and all input directories and
files are free of errors, then the arc5500 program should
terminate with an exit status of 0, regardless of whether any
matches were found.

If the command line is incorrect, or a <pathname> is incorrect,
then the arc5500 program should write one or more error messages
to standard error, each beginning with "ERROR" and terminating
with a newline.  After writing these error messages to standard
error, arc5500 should terminate with an exit status other than 0.

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