hello,
i would like to introduce a discussion about uml in general
and its advantages/disadvantages, cause using uml seems to
be 'trendy' for some people today.
first of all, uml is a so called 'modeling language' that's where
the ML comes from. in this sense uml helps to visualize your project's
- processes (use cases, sequence diagrams),
- components (class diagrams, package diagrams)
- ...
its also a way to communicate with programers or even the end users.
on the other hand uml helps you analysing obvious weaknesses of your
project.
finally, i don't think that uml was ment to show the work you have
done (by importing all your classes into a case tool and generating
class diagrams).
frankly, i don't think that it's quite usefull to view a 200 KByte png image
of a class diagram in a framed window. maybe it could be usefull for
someone who is involved into the (jetspeed) project for some time,
cause he knows all the processes.
but someone who is pretty new to the project, needs more information
(documentation).
maybe some of you remember, that i whould like to initiate some kind of
a 'jetspeed/java apache documentation project'. a requirement was that
we switch from 'just implementing by coding' to
'modeling via uml and finally implementing by coding'.
in this case a CASE tool whould be a inteligent way of generation the code
infra structure
out of the uml diagrams you have created.
beside uml, documentation for the programers, the administrators
and the end user to completes your work.
last but not least, you should allways consider that now one really needs
nice pictures,
so using uml could be a complete waste of time if a project works without
it.
i hope some of you could get into this discussion ;-)
regards
daniel
--
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
