Database Storage Engine Project M3 Class diagram: Difference between revisions
From LimeSurvey Manual
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
*Identify the important classes and define the data-classes for the system | *Identify the important classes and define the data-classes for the system | ||
*Define the structure of the database designs | *Define the structure of the database designs | ||
= Diagrams= | |||
There are three big parts in the diagrams: the factory part, the controllers and the general classes. Packages used in the diagrams will not result in namespaces. | |||
== General classes== | |||
[[File:general.png]] | |||
== Controllers== | |||
[[File:controllers.png]] | |||
== Engine factory== | |||
The engine classes (like the one in the DBSESF package) are trivial classes (one for each type of table). | |||
[[File:eninefactory.png]] | |||
Revision as of 20:17, 2 July 2010
About the milestone
This milestone includes documenting the Database Storage Engine with a class diagram. This will make it easier for future developers to make changes to the database system. This milestone is closely linked to the API milestone since the controllers will have to implement this API.
Todo
- Identify the important classes and define the data-classes for the system
- Define the structure of the database designs
Diagrams
There are three big parts in the diagrams: the factory part, the controllers and the general classes. Packages used in the diagrams will not result in namespaces.
General classes
Controllers
Engine factory
The engine classes (like the one in the DBSESF package) are trivial classes (one for each type of table).
