Documenting-in-the-large vs. Documenting-in-the-small (1993)
Cached
Download Links
- [ftp.rigi.csc.uvic.ca]
- [ftp.rigi.csc.uvic.ca]
- [rigi.cs.uvic.ca]
- DBLP
Other Repositories/Bibliography
| Venue: | Proceedings of CASCON'93 |
| Citations: | 6 - 0 self |
BibTeX
@INPROCEEDINGS{Tilley93documenting-in-the-largevs.,
author = {Scott R. Tilley},
title = {Documenting-in-the-large vs. Documenting-in-the-small},
booktitle = {Proceedings of CASCON'93},
year = {1993},
pages = {1083--1090}
}
OpenURL
Abstract
There is a significant difference between documenting large programs and documenting small ones. By large programs we mean on the order of 1,000,000 lines, usually written by many different people over a long period of time. Most software documentation may be termed documenting-in-the-small, since it typically describes the program at the algorithm and data structure level. To understand large legacy systems, one needs documenting-in-the-large: documentation describing the high-level structural aspects of the software system's architecture from multiple perspectives. This paper outlines an approach to supporting software evolution through documenting-in-the-large. The approach is based on a flexible reverse engineering process which uses virtual subsystem stratifications to represent multiple abstract views of a software system. Keywords: documenting-in-the-large, reverse engineering, software evolution y This work was supported in part by the British Columbia Advanced Systems Inst...







