Draft
Understanding a program flow from pure source code and in particular the relationships of the individual classes can be very complex. Therefore we use package and class diagrams to provide a graphical overview.
The packages result from the Model-View-Controller (MVC) concept used by us, but also from the division into a library which performs all integration calculations and into the actual program which aproximates the integrals with this library.
The library uses two packages:
- Function
- integration The names are very clear here. The first name range stands for all possible functions and the second for all possible integration procedures.
The GUI uses three packages:
- Model
- view
- controller The classic MVC concept is used here. See bibliography for more information.
In our project we use two abstract data types. Both occur in the library. On the one hand we have the class Function, which provides an interface for all evaluable functions. On the other hand, we have the Integration class, which provides an interface for all integration methods.
Since the class diagrams are very large, they were divided into several parts. The UML diagrams describe the large core, small boundary functions were not more precisely.
