Week 1:
Compiling a list of ideas for the project

Week 2:
Project idea selected (SuS Tool) and Pre-Proposal created (due 1/19)

Week 3:
Design document created. Details all the aspects of the project (due 2/2)

Week 4:
With the design document turned in, coding begins. Initial goal is the basic
GUI for the program (just main window and placeholder controls)

Week 5:
Support classes created (Date, IPAddress, Location, etc..). Researching how to
connect the database with the program (will be an Access database).

Week 6:
Created the custom wan configuration form. Allows the user to specify locations
that reflect the logical layout of their wan.

Week 7:
Connected the database to the program. Retrieval and inserting of data working.
Reading in data and putting it in the database is slow...will ask Dr. Mock about
that during the meeting on 2/28.

Week 8:
Implemented the ability to save the custom wan. Previously, everything was hard-coded.
This took some work as I had to come up with a file format for the data. I opted for
a format that resembled a language. each branch is contained in a set of {} and the
ip ranged for each location is in parrens. The good part about this system is the fact
that you can have a location without an ip range. This allows for better customizing
in the configuration form.

Week 9:
The whole reason behind a custom wan is so that users can select a location and all the
ip's that belong to that location are loaded (as well as child nodes). This requires
a dynamic sql statement building routine. Currently, this is not implemented and the
only sorting it does is at a leaf node. Looking into different possibilities with the
sql generation.

Week 10:
Tried to implement a non-recursive sql generation routine for the sake of simplicity.
However, using a tree datastructure is just begging for recursive iterations so I am
redoing it with a recursive implementation. I was also using redundant code in multiple
areas of my code for connecting to the database. I've pulled those out and created a
universal method that does the same thing. This method will call the routine to build
the sql, connect the database, get the results, populate the grid, and close the 
connection. I haven't finished the sql generator though so it is hard to test it.

Week 11:
Added in registry settings to store the locations and paths of the different files
and folders needed by my program. On startup, it searches the registry for a defined
key. If it doesn't find the key, it creates it and prompts the user to enter the
needed information. If it does find it, it loads the information and continues with
the initial loading.

Week 12:
Finished the recursive implementation for the sql generation. Everything appears to
work.

Week 13:
Fixed a few bugs that were causing crashes (mainly, trying to modify files that were already open).

Week 14:
Went through and commented the code that wasn't already. Things are nearly complete

Week 15:
Updated my design document to show the changes that were made through the process. Everything
is done now and ready to be turned in.