Administration
From TaskDepender
(→Classes and structures) |
(→Introduction) |
||
| Line 5: | Line 5: | ||
The Administration is an API to the database that in one direction shields the GUI from handling the database transactions and in the other direction shields the Administration from being dependent on the implementation of the GUI. | The Administration is an API to the database that in one direction shields the GUI from handling the database transactions and in the other direction shields the Administration from being dependent on the implementation of the GUI. | ||
| − | First of all, the Administration must maintain some information that is relevant to | + | == Design == |
| + | |||
| + | First of all, the Administration must maintain some information that is relevant to a GUI. This is: | ||
* The selected tasks | * The selected tasks | ||
* The selected deliverables | * The selected deliverables | ||
| Line 18: | Line 20: | ||
The Administration numbers the actions and the GUI can undo that action. Internally in the Administration the complete administration is filled again when the database has rolled back the action. | The Administration numbers the actions and the GUI can undo that action. Internally in the Administration the complete administration is filled again when the database has rolled back the action. | ||
| + | |||
| + | The Administration can return lists of Tasks and lists of Deliverables. | ||
== Classes and structures == | == Classes and structures == | ||
[[Administration classes and structures]] | [[Administration classes and structures]] | ||
