Figure 1.2: The format of a typical reengineering pattern.
Figure 1.3: A map of reengineering pattern clusters.
Chapter 2: Setting Direction
Figure 2.1: Principles and guidelines to set and maintain direction in a reengineering project.
Chapter 3: First Contact
Figure 3.1: Assess the feasibility of the project during your "First Contact" with the system.
Figure 3.2: The architecture diagram as you inferred it from the discussion with the maintainer.
Chapter 4: Initial Understanding
Figure 4.1: Obtain an Initial Understanding of a software system and cast it into a higher-level representation.
Figure 4.2: Mapping a series of relational tables onto an inheritance hierarchy: (a) one to one; (b) rolled down;(c) rolled up.
Figure 4.3: Identify a qualified association via a key consisting of a foreign key (patient ID) and two extra columns (date, nr).
Figure 4.4: Refining the hypotheses concerning the Euro representation. (a) An initial hypothesis where the open questions are inserted as Notes (subclasses for the different currencies) and (b) a refined hypothesis after verification against the source code (flyweight approach); the modifications are shown as Notes.
Figure 4.5: White noise obtained by a bottom-up design extraction approach. The figure shows a fragment of an inheritance hierarchy augmented with all method invocations and attribute accesses for a medium-sized system. The visualization is performed by CodeCrawler [Deme99] [Lanz99].
Figure 4.6: Class size overview with node size showing the number of lines of code and gray value showing the number of...
Copyright Elsevier Science (USA) 2003 under license agreement with Books24x7