First page Back Continue Last page Graphics
Changes
Project procedures
Build script
Version control
Test harnesses
Notes:
I've already indicated that I documented the tools, packages and patches that needed to be installed to develop the system.
I persuaded the project manager that a consistent build process would be a good idea and one of the developers (Mark Goodwin) volunteered to create an "Ant" script to control it. (Mark also started maintaining documentation via a webserver on his workstation.)
I recommended changing version control system to CVS and using its branching capabilities to avoid the need for the manual "bookkeeping" of file version numbers. See:
http://www.octopull.co.uk/VCS/
Several other developers recommended CVS and it was adopted shortly after I left the project. (The specific change control procedures I recommend were not adopted initially – although they have since been adopted.)
For the work I did I wrote test harnesses for the server functionality that the client would be using – which meant that I wasn't trying to debug both business logic and presentation logic at the same time. But I was unable to pusuade anyone else on the project (especially the project manager) of the effectiveness of this approach until some months later.