|
|
|
|
|
Ongoing Documentation This is another old and thorny data processing problem, which for a consultancy is exacerbated by the fact that our clients usually plan to do their own maintenance. IMPAC's completed documentation comprised 16,000 lines accompanied by 250 diagrams, divided into six volumes. Almost all of this was produced during the development, and was revised continually. The review process detailed earlier was a major factor contributing to the consistency and completeness of the final product. Another factor was the dividing up of the documentation so that each team member had sole responsibility for certain sections, and no one person carried the entire burden. Only two man weeks were required after the system was shipped to proof-read and correct the final version.
|
Teamwork As stated earlier, the most significant feature of the team was a full-time "user project manager". The size of the remainder of the team increased from two during the analysis phase, to four in the design phase, then five and then back to four. All analysis and high level design was done by people working in pairs. Design and coding of all complex programs also involved at least two and sometimes three people. This, coupled with the technical reviews in which all team members participated, produced a very high level of teamwork, and we feel the resultant synergy contributed to the quality of the product. The team habit is so strong that even though the other members are scattered across three new projects, this article has been passed on for review!
Click here if you would like to download a pdf version of this article.
|
|
|
|