From: utzoo!decvax!watmath!jcwinterton Newsgroups: net.misc Title: System Documentation for the Maintenance Programmer Article-I.D.: watmath.2630 Posted: Tue Jun 15 03:58:46 1982 Received: Wed Jun 16 03:51:27 1982 WRT Burt Patkau's article, I will try and make a check list: 1. A log binder containing the system rationale and all the amendments. 2. ALL the listings currently active. 3. A reasonable source maintenance package containing protection for the "production" version so that it cannot be inadvertently destroyed. 4. A reasonable text manipulation system, hopefully on-line. 5. Reasonable turn around on compilations. 6. The files containing the standard system checkout data. 7. Documenation describing items 2 and 6 in detail, with amplifying flow-charts and/or layouts. (oops s/Documenation/Documentation/). 8. A boss who will be firm and understanding when the maintainer wants to "rewrite the whole mess", "quit this stupid job", "give up on this bug", "recode this program", etc. John Winterton