Papers/Others

aging symptoms to verify the aging of a system

tomato13 2009. 10. 4. 00:00

http://www-vs.informatik.uni-ulm.de/de/intra/bib/2007/ICSEA07/data/076%20A%20Reengineering%20Approach.pdf

 

G. Visaggio, “Ageing of a Data Intensive Legacy System: Symptoms and Remedies”, Journal of Software Maintenance and Evolution, vol. 13, no. 5, pp. 281-308, 2001

 

1. Pollution, i,e., the system includes many components not necessary to carry out the business functions

2. Embedded knowledge, i.e., the knowledge of the application domain and its evolution is spread over the programs and can no longer be derived from the documentation

3. Poor lexicon, i.e., the names of components have little lexical meaning or are in any case inconsistents they identify

4. Coupling, i.e., the programs and their components are linked by an extensive network or data or control flows

5. Layered architectures, i.e., the system's architecture consist of several different solutions that can  no longer be distinguished; even though the software started out with a high quality basic architecture, the superimposition of these other hacked solutions during maintenance has damaged its qualtiy