next up previous contents
Next: 3. Source Code Organization Up: Toolkit for Conceptual Modeling Previous: 1. Introduction

2. System Architecture

In this chapter a high level overview of the TCM software system is presented. In figure 2.1 TCM is logically decomposed into a number of subsystems. Each subsystem is then worked out further as an UML static structure diagram (SSD) in subsequent figures. All classes in these SSDs also exist in the source code, but not every source code class is mentioned in these SSDs. The classes that are not mentioned are either implementation classes (data structures, user interface widgets etc.) or they are specializations of the classes that are mentioned for specific editors. The same applies to the relationships between the classes. Note also that we do not show the attributes and operations of the classes because that would clutter up the diagrams too much. But a complete and accurate overview of all classes of the source code and their attributes, operations and specialization relationships has been generated automatically and is described in chapter 5.

This system architecture is rather conceptual, it does not say exactly how the source code is organized physically. In chapter 3 the physical source code structure is presented.


  
Figure 2.1: Subsystems.
\includegraphics[angle=90,height=6in]{p/FSubsystems.eps}


  
Figure 2.2: Editor subject areas.
\includegraphics[angle=90,height=7.5in]{p/FEditorsSA.eps}


  
Figure 2.3: Shapes and Graph subject areas.
\includegraphics[angle=90,height=7.5in]{p/FShapeSA.eps}


  
Figure 2.4: Table subject area.
\includegraphics[angle=90,width=\textwidth]{p/FTableSA.eps}


  
Figure 2.5: Viewer subject area.
\includegraphics[angle=90,height=7.5in]{p/FViewerSA.eps}


  
Figure 2.6: Printer subject area.
\includegraphics[angle=90,height=4in]{p/FPrinterSA.eps}


  
Figure 2.7: Window subject area.
\includegraphics[angle=90,height=7.5in]{p/FWindowSA.eps}


next up previous contents
Next: 3. Source Code Organization Up: Toolkit for Conceptual Modeling Previous: 1. Introduction
Henk van de Zandschulp
2003-01-07