The practical guide to structured systems design: 2nd edition
The practical guide to structured systems design: 2nd edition
The Integrated Dictionary/Directory System
ACM Computing Surveys (CSUR)
Software Maintenance: The Problems and Its Solutions
Software Maintenance: The Problems and Its Solutions
Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design
Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design
Flowchart techniques for structured programming
ACM SIGPLAN Notices
Structured software maintenance
AFIPS '83 Proceedings of the May 16-19, 1983, national computer conference
Hi-index | 0.00 |
Documenting application systems has long been considered a necessary evil. Necessary because documentation provides a map to present systems, serves as a maintenance aid, and is required by the auditors; evil because it is an activity generally dreaded by those who develop the systems. Since normal behavior regarding unpleasant chores is avoidance, application systems documentation is sometimes absent and often incomplete. Documenting may be unpopular for a number of reasons, including psychological ones. One very obvious problem is that, except for a few automated tools at the program level, documentation is a manual process used in an automated environment. Automating the process is a way to reduce the laboriousness of the task. This paper is a case study of how one data processing organization applied student labor and a relational database management system in a prototype to automate much of their applications systems documentation function. The capabilities, fringe benefits, and future enhancements of the tool are discussed.