Class relationship

The following table describes the relationships between the major classes that constitute the debugger.
Implementation of these classes should ensure that all main features of the debugger can be supported in a fairly straightforward way.

This table does not define the following two important elements:

• methods of each class

• run-time relationship between the classes' instances

The basic design principle of the classes is that <class>Manager or <class>Pool implement most of the logic controlling a number of <class> instances.
For example, a StringPool class can implement the Find() method; a SymbolPool can implement a FindByName(), a FindByAddress(), a PreviousSymbol() and other similar methods.