The specification is in the following website:

http://inst.eecs.berkeley.edu/~cs61b/fa16/materials/proj/proj3/index.html

Please only modify the places with "//FIXME".

Please don't modify the methods that already exist and finished.

Be sure to write UnitTest in the UnitTest file and write some own tests for the program (that is part of the grade).

You need to import the library before you start. It's the lib folder in the attached file called "cs61b-software".

For this final project,

You will be writing a library package to provide facilities for manipulating graphs, plus two clients that use the package. The package must be general: no specifics of either client may find their way into the code for the graph package. We will check that by running our own clients against your package. That is, in contrast to past projects where we didn't care how you arranged the internals of your program as long as it functioned according to the specification, in this case, part of the project code-the API for the graph package-will be set in stone.

Task -

Get or update the skeleton in the usual way (after committing all current work)

git fetch shared

git merge shared/proj3 -m "Start project 3"

Be sure to include tests of your program (that is part of the grade). The make file we provide has a convenient target for running such tests. Our skeleton directory contains a couple of trivial tests, but these do not constitute an adequate set of tests! Make up your tests ahead of time and update your make file to run them.

We will expect your finished programs to be workmanlike, and of course, will enforce the mechanical style standards. Make sure all methods are adequately commented-meaning that after reading the name, parameters, and comment on a method, you don't need to look at the code to figure out what a call will do. Don't leave debugging print statements lying around. In fact, don't use them; learn to use the debugger (either gjdb or that of IntelliJ or your favorite Java-system vendor).

The nature of the graph package is such that you'll probably want to do extensive JUnit testing on it. Always feel free to add private setup procedures for testing purposes only that set up conditions (such as graphs) that are used by several different tests.

Our testing of your projects (but not our grading!) will be automated. The testing program will be finicky, so be sure that

make check

runs your tests.