Cross references are features

When a software system is developed by a large team of programmers, and has matured’ for several years, changes to the code may introduce unexpected interactions between diverse parts of the system. This occurs because the system has become too large for one person to fully understand, and the original design documentation has become obsolete as the system has evolved. Symptoms of structural problems include too many unnecessary recompilations, unintended cyclic dependency chains, and some types of difficulties with understanding, modifying, and testing the system. Most structural problems cannot be solved by making a few “small” changes, and most require the programmer to understand the overall pattern of interactions in order to solve the problem.

[1]  Ellis S. Cohen,et al.  Constraint-Based Tiled Windows , 1986, IEEE Computer Graphics and Applications.

[2]  Victor R. Basili,et al.  Error localization during software maintenance: generating hierarchical system descriptions from the source code alone , 1988, Proceedings. Conference on Software Maintenance, 1988..

[3]  James A. Senn,et al.  System structure and software maintenance performance , 1989, Commun. ACM.

[4]  Ellen M. Vdorhees,et al.  The cluster hypothesis revisited , 1985, SIGIR '85.

[5]  Walter F. Tichy,et al.  Smart recompilation , 1986, TOPL.

[6]  Ellen M. Voorhees,et al.  The efficiency of inverted index and cluster searches , 1986, SIGIR '86.

[7]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.

[8]  Rolf Adams,et al.  Software Change Dynamics or Half of all Ada Compilations are Redundant , 1989, ESEC.

[9]  Gail E. Kaiser,et al.  Change management for very large software systems , 1988, Seventh Annual International Phoenix Conference on Computers an Communications. 1988 Conference Proceedings.

[10]  Ellen M. Vdorhees The cluster hypothesis revisited , 1985, SIGIR 1985.