1 |
:Stamp: $Id$ |
:Stamp: $Id$ |
2 |
|
|
3 |
|
|
4 |
|
- Perspectives to UML class diagrams, or classifiers in general: |
5 |
|
|
6 |
|
Cook and Daniels, Designing Object Systems: Object-Oriented |
7 |
|
Modeling with Syntropy. Prentice Hall, 1994. |
8 |
|
Referred in Fowler and Scott: UML distilled, |
9 |
|
2nd ed., Addison-Wesley. |
10 |
|
|
11 |
|
XXX Couldn't find this one yet. |
12 |
|
|
13 |
Issues |
Issues |
14 |
------ |
------ |
15 |
|
|
48 |
trashbin |
trashbin |
49 |
-------- |
-------- |
50 |
|
|
51 |
|
+ creating UML diagrams should be natural part our of design |
52 |
|
(pegboard) and documenting (architecture docs) processes |
53 |
|
|
54 |
|
- Include PEGs: possibly not-yet accepted or not-yet implemented proposals |
55 |
|
for architectural changes. |
56 |
|
|
57 |
|
|
58 |
- diagrams are from human to human |
- diagrams are from human to human |
59 |
|
|
60 |
+ we don't wan to generate diagrams from the code or generate |
+ we don't wan to generate diagrams from the code or generate |