1 |
|
:Stamp: $Id$ |
2 |
|
:Last-Modified: $Date$ |
3 |
|
|
4 |
This page lists a lot of UML tools: |
sources for references |
5 |
http://plg.uwaterloo.ca/~migod/uml.html |
---------------------- |
6 |
|
|
7 |
Recommended sources for references: IEEE, ACM |
Recommended sources for references: IEEE, ACM |
8 |
|
|
9 |
- Labeled, typed links as cues when reading hypertext documents; http://search.epnet.com/direct.asp?an=9702214682&db=afh |
- This page lists a lot of UML tools; |
10 |
|
http://plg.uwaterloo.ca/~migod/uml.html |
11 |
|
|
12 |
- Mapping UML to JAVA; http://doi.acm.org/10.1145/353171.353184 |
- Other non-commercial documentation tools; |
13 |
generating Java code from UML |
http://www.stack.nl/~dimitri/doxygen/links.html |
14 |
|
|
15 |
|
- Labeled, typed links as cues when reading hypertext documents; |
16 |
|
http://search.epnet.com/direct.asp?an=9702214682&db=afh |
17 |
|
|
18 |
|
- Mapping UML to JAVA (generating Java code from UML); |
19 |
|
http://doi.acm.org/10.1145/353171.353184 |
20 |
|
|
21 |
|
why uml |
22 |
|
------- |
23 |
|
|
24 |
Some statements from the UML book (Booch, Jacobson, Rumbaugh, p.6) |
Some statements from the UML book (Booch, Jacobson, Rumbaugh, p.6):: |
|
"A model is a simplification of reality." |
|
|
"We build models so that we can better understand the system |
|
|
we are developing." |
|
25 |
|
|
26 |
|
"A model is a simplification of reality." |
27 |
|
|
28 |
|
"We build models so that we can better understand the system |
29 |
|
we are developing." |
30 |
|
|
31 |
|
a spiral model of software development |
32 |
|
-------------------------------------- |
33 |
|
|
34 |
|
Phases: |
35 |
|
|
36 |
|
* ... |
37 |
|
* determining objectives, alternatives, constraints |
38 |
|
* evaluatin alternatives, identifying and resolving risks |
39 |
|
* developing, verifying |
40 |
|
* planning next phase |
41 |
|
* ... |
42 |
|
|
43 |
|
:: |
44 |
|
|
45 |
|
"It fosters the development of spesifications that are not necessarily |
46 |
|
uniform, exhaustive, or formal, in that they defer detailed elaboration of |
47 |
|
low-risk software elements and avoid unnecessary breakage in their |
48 |
|
design until the high-risk elements of the design are stabilized." |
49 |
|
|
50 |
|
"Overall, risk-driven documents, particularly spesifications and plans, are |
51 |
|
importatn features of the spiral model. Grean amount of detail are not |
52 |
|
necessary unless the absence of such detail jeopardizes the project."[#]_ |
53 |
|
|
54 |
|
.. [#] Boehm, B. (1988). "A spiral model for software development and |
55 |
|
enhancement". IEEE Computer 21 (5), pp. 61-72. |
56 |
|
|
57 |
|
duplication of data issue |
58 |
|
------------------------- |
59 |
|
|
60 |
Is the duplication of data an issue here? Even when the idea is that the |
Is the duplication of data an issue here? Even when the idea is that the |
61 |
UMLs are hand crafted, and not generated from the code at all, it might be a |
UMLs are hand crafted, and not generated from the code at all, it might be a |
63 |
A solution might be to be able to refer from .uml to the objects somehow. |
A solution might be to be able to refer from .uml to the objects somehow. |
64 |
Obviously gzz connections would solve this and perhaps this is all clear to |
Obviously gzz connections would solve this and perhaps this is all clear to |
65 |
you, sorry to disturb if so, and clarifications are welcome. --antont |
you, sorry to disturb if so, and clarifications are welcome. --antont |
66 |
(updata: re-read the article and saw the "this is a temporary system" note |
|
67 |
|
(update: re-read the article and saw the "this is a temporary system" note |
68 |
which refers to this, I guess? we did also discuss this on irc ones so i |
which refers to this, I guess? we did also discuss this on irc ones so i |
69 |
guess the issue is clear -- no need to reply and this can be removed at will) |
guess the issue is clear -- no need to reply and this can be removed at will) |