696ddb8a01
git-svn-id: file:///Users/arjan/backup/gaphor/gaphor/trunk@2779 a8418922-720d-0410-834f-a69b97ada669
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
UML datamodel
|
|
=============
|
|
|
|
For it's data storage, Gaphor uses the UML metamodel specs as guidelines.
|
|
Actually, the datamodel is generated for a model file.
|
|
|
|
The model is build using smart properties (descriptors). Those descriptors fire
|
|
events when they're changed. This allows the rest of the application (visuals,
|
|
undo system) to update their state accordingly. The events are send using Zope
|
|
(3)'s signalling mechanism, called Handlers.
|
|
|
|
|
|
Model details
|
|
-------------
|
|
|
|
Pay attention to the following changes/additions with respect to the official
|
|
model:
|
|
|
|
Additions to the model have been put in the package AuxilaryConstructs.Presentations and .Stereotypes.
|
|
|
|
A Diagram element is added in order to model the diagrams.
|
|
|
|
A special construct has been put into place in order to apply stereotypes to
|
|
model elements. The current specs (2.2) are not clear on that subject.
|
|
We follow teh same direction as MonoUML (URL!)
|
|
|
|
|
|
TODO:
|
|
ValueSpecification is generated as if it were a normal attribute.
|
|
As a result, it's subclasses (Expression, OpaqueExpression, InstanceValue,
|
|
LiteralSpecification and its Literal* subclasses) are not available.
|
|
|
|
The Slot.value reference is singular.
|