Present : Andy, Nathan, Dave, Phebe, Martin, Karen

1. Nathan reported that the classes RouteVertex and TerrainMap have been completed. It is also suggested to use broken terrain for testing.
2. Dave reported that the class TerrainGen was also completed. Nathan had find a bug, and it had also been fixed.
3. Martin reported that the package gui is underway. He will complete as much as he can for Thursday.
4. It is suggested that in class QuickButtons, the buttons JButton loadTerrain, genRoute are to be kept. For expRoute Export Route, it is better to have it split into saveRoute and printRoute.
5. The menu will contain the algorithm choice of Dijkstra, and can keep the last algorithm used for the next run unless this is altered (to show the capability of allowing further development).
6. Karen reported that she had produced 20 different terrain testing data for manual testing, ranging from 2 x 2, 3 x 3 to 1 x 5 grids. It is considered adequate for the purpose of manual testing. A 1 x 5 grid for the pathological case in which the canal passes under itself was also included. It is interesting to find out that it is cheaper to go down the cliff edge and tunnel underneath than to go down the less steep slope.
7. Phebe reported that the user manual is ongoing updated according to the available materials at hand. The major outstanding parts on Running Instructions and Examples are dependent on the release of GUI.

Coding

8. Nathan will start the class router.CanalRoute, and he estimated that the routing algorithm can be done by Monday 14 /2/2000.
9. Constructor (load a route from disk and create a new CanalRoute Object) of CanalRoute may be changed. Nathan will investigate and inform others about the decision made.
10. Sub-class Dijkstra (extendable to modifiedDijkstra) is to be included in CanalRoute.
11. Terrain implements the terrain as a 3-D array. TerrainMap’s constructor reads in a file from disk and create a TerrainMap object.
12. Martin will complete the code for the class CostInfo.
13. For class CostInfo : The currency will be Sterling £ and pence. The RouteVertex will use sub-grid of 50. The output is to return total cost.

Testing

14. The three classes next to be tested are :

CostInfo

TerrainMap

RouteVertex

15. The "test harnesses" will be placed under the testdata directory with 3 sub-directories of src, terrain, and test harnesses.
16. Martin requires some dummy TerrainMap data for the his preliminary testing of his code on TerainDisplay before it is released. Basically need to have data for getHeight(), getMaxHeight() and getMinHeight(). Dave will prepare the TerrainMap test data for Martin.
17. Karen will prepare the test harness for TerrainMap. Filenames to be provided as input, and displaying terrain as output. Some suggestions were to provide long and/or wide file data, strange characters etc. for testing.
18. Program Strategy

18.1 The program should not just break, always throw runtime exceptions and catch. User understandable error messages should also be provided.