Suggestion for user manual
"Ernesto Revilla" <[email protected]> Tue, 24 Feb 2004 15:21:37 +0100
| Newsgroups | gmane.comp.python.modeling |
|---|---|
| Message-ID | <000d01c3fae1$85e949f0$0100a8c0@servidor> |
Dear Sébastien, (I think, in the last message I didn't put correctly the accent.) In section 2.3.4: Relationship In deleteRule: The entity in your example is not 'Author' but 'Writer'. On the other hand, the relationships are called there: * author and * books not: toAuthor and toBooks. Perhaps, there could be a clarification of the UML notation, so that the behaviour of modeling would be a bit clearer for persons without knowledge of UML. I attach it here for your consideration. Best regards, Erny Dear Sébastien, (I think, in the last message I didn't put correctly the accent.) In section 2.3.4: Relationship In deleteRule: The entity in your example is not 'Author' but 'Writer'. On the other hand, the relationships are called there: * author and * books not: toAuthor and toBooks. Perhaps, there could be a clarification of the UML notation, so that the behaviour of modeling would be a bit clearer for persons without knowledge of UML. I attach it here for your consideration. Best regards, Erny
relations.txt
(text/plain, 1 KB)
A entity's relation to another entity is always sketched on the opposite side, i.e.:
card2 card1
A<--y-------------x-->B
delRule2 delRule1
means:
card1
A----------x-->B (x describes, how A is related to B)
delRule1
and
card2
A<--y----------B (y describes, how B is related to A)
delRule2
if card1 is:
0,1: one instance of A may be related to one o no instance of B. (same as 'optional')
0,*: one instance of A may be related to any number of instances of B.
1,*: one instance of A has to be related to at least one instance of B.
1: one instance of A must be related to one instance of B. (same as 'required')
0,4: one instance of A may be related to none or at maximum 4 instances of B
The same with card2.
If delRule1 is:
* cascade: all Bs will be deleted if the corresponding A is deleted
* deny: deletion of A will be denied if at least one corresponding instance of B exist.
* nullify: if A is deleted, the corresponding attribute of B (pointing to A) will be cleared.
The same with delRule2.