| Version 5 (modified by olivier, 6 years ago) (diff) |
|---|
Global Software Architecture
The basic idea is to follow the ModelViewController, as in the initial design proposal below (Inkscape SVG source) :
However, we want to use the DjangoFramework?, in which the "Controller" is somewhat called "View", which is arguable but quite coherent : a View, in Django, determines what to render, not how to render it. This is a subtle difference. Anyway the most important point is to properly separate the data from the various rendering routines and modules.
So here is the UML class diagram, where you'll find views and the model, no controller (source edited with ArgoUML) :
Attachments (2)
- architecture.png (73.4 KB) - added by Olivier Guilyardi <olivier@…> 6 years ago.
-
class_diagram.png
(37.7 KB) -
added by olivier 6 years ago.
UML Class Diagram
Download all attachments as: .zip


