1 |
------------------------------------------------------------------------------- |
2 |
Rules about UML models: |
3 |
------------------------------------------------------------------------------- |
4 |
|
5 |
|
6 |
------------------------------------------------------------------------------- |
7 |
- Naming rules : |
8 |
---------------- |
9 |
Following rules are mandatory for all 'name' attributes of UML elements : |
10 |
|
11 |
A name attribute must : |
12 |
- only contain letter and digit characters |
13 |
=> all other characters are forbidden : punctuation symbols ... |
14 |
|
15 |
- respect case (case sensitive) |
16 |
- not exceeds 30 characters |
17 |
------------------------------------------------------------------------------- |
18 |
|
19 |
|
20 |
- concrete classes are final, i.e. do not have sub-classes. |
21 |
Alternatively, only abstract classes can have sub-classes. |
22 |
Motivation: ... |
23 |
--- |
24 |
|
25 |
|
26 |
- If no cardinality is defined on an attribute it is assumed to be "1" |
27 |
Motivation: ... |
28 |
---- |
29 |
|
30 |
|
31 |
|
32 |
- If no cardinality is defined on a collection it is assumed to be "*" |
33 |
Motivation: ... |
34 |
---- |
35 |
|
36 |
- If no cardinality is defined on a reference it is assumed to be "1" |
37 |
Motivation: ... |
38 |
---- |
39 |
|
40 |
|
41 |
|
42 |
- other constraints may be introduced on attributes: |
43 |
- maxLength on string types. |
44 |
|
45 |
- @@TODO we need to decide where we put the documentation of references and collections. |
46 |
It may be best to do so on the property corresponding to the navigable association end representing these two concepts |
47 |
in our profile @@ |