The truth and the lies about Uml?

[Marcello Dias]

How many of you Use UML?

Hi IŽm not a Java programmer(At least not yet).

I would like to know what do you think about Uml?

I see many people saying that some tools generate code from Uml Models,that the programmer have to write really few lines.

But are theyŽre fancy system or rudimentary classes that canŽt be comparted to ‘Human Touched Code’,
I f you were a beginner that would like to learn Java(most ot produce ERP) what technologies would you study first,What Java and UML Books Would You Read?


Marcello Dias

[Paul Nichols (TeamB)]

Post by Marcello Dias
How many of you Use UML?

I do... Using TogetherSoft or Argo UML, depending on the compay's
preference/budget.

The Enteprise versions of JBuilder have a UML tool. Very basic, but somewhat
functional. The Architect version include an integrated version of
TogetherSoft.

Post by Marcello Dias
I would like to know what do you think about Uml?

UML is great from going to concept, to design, to implementation. However, I
would not get bogged down into countless State or Activity Diagrams. They
are ok to use in complex models, but I rarely use Activity or State
Diagrams. Use Case, Packages, and Class Diagrams are our mostly used
diagrams. We do use Sequence diagrams at times as well.

Post by Marcello Dias
I see many people saying that some tools generate code from Uml

Models,that the programmer have to write really few lines.

Post by Marcello Dias
But are theyŽre fancy system or rudimentary classes that canŽt be

comparted to 'Human Touched Code',

Post by Marcello Dias
I f you were a beginner that would like to learn Java(most ot produce ERP)

what technologies would you study first,What Java and UML Books Would You
Read?

Post by Marcello Dias
Marcello Dias

[Marcello Dias]

"Paul Nichols \(TeamB\)" <***@computer-logic.net> wrote:

Hi,

Thank you that clarified a lot of things.

I think for me it would be interesting to have a huge llok in UML before learning Java.

Marcello

[e***@gmail.com]

Read a book on object oriented design like
Object-Oriented Analysis and Design with Applications (2nd Edition)
by Grady Booch

Starting with UML is like starting with a book to draw flow charts.
You should first understand object oriented design.

When you do get into UML, do not go overboard with the
code generation bit. With most tools all you get is a skeleton of
the code.

--
EventStudio 2.5 - http://www.EventHelix.com/EventStudio
Model in Plain Text; Generate Sequence Diagrams in PDF/Word

[Buch]

Post by Marcello Dias
I would like to know what do you think about Uml?

If you work alone, and will continue to do so, you don't need UML or
anything.
But, some people need to preserve knowledge, or distribute knowledge to
group, therefore UML is
evil, but necessary in this case.
Source code with UML diagrams looks more professional, and adds to price.

[Paul Nichols (TeamB)]

Post by Buch

Post by Marcello Dias
I would like to know what do you think about Uml?

If you work alone, and will continue to do so, you don't need UML or
anything.

Well I might beg to differ with you.. Best way to get a client to sign off
on requirements, is to have an easily readable form of documentation. UML,
especially Use Cases, followed by a Use Case Doc, is an excellent way to do
this.

Plus have you ever tried to pick up a middle size to large system you did
years ago and try to figure out why you did X?

I agree you can go overboard, but that is true about anything..

Post by Buch
But, some people need to preserve knowledge, or distribute knowledge to
group, therefore UML is
evil, but necessary in this case.

Why evil?
Necessary I agree with.

Post by Buch
Source code with UML diagrams looks more professional, and adds to price.

Well I do not want to dig through thousands to millions of line of code, to
know generally whats going on :)

[Buch]

Post by Paul Nichols (TeamB)
Well I might beg to differ with you.. Best way to get a client to sign off
on requirements, is to have an easily readable form of documentation. UML,

We had different markets on mind. I meant if you are alone, will be alone,
and are writing some software for
unknown user.
As for requirements, I agree partially. Yesterday I made software to do
something on large number of pdf's in database,
and it was not small utility, and I did not made any documentation. There
was no need to.

Post by Paul Nichols (TeamB)
Plus have you ever tried to pick up a middle size to large system you did
years ago and try to figure out why you did X?

I must admit that I can figure what I wanted almost instantly. If I feel
like something will be problem to
understand, I make comments in source, or in adjacent documentation.
As for the rest, I do common tasks mostly the same way for many years ...

Post by Paul Nichols (TeamB)
Why evil?

It consumes time, therefore money also.
In perfect world, you should have code automatically when you draw diagram,
or have diagram when you write code ...

[Paul Nichols (TeamB)]

Post by Buch

Post by Paul Nichols (TeamB)
Well I might beg to differ with you.. Best way to get a client to sign off
on requirements, is to have an easily readable form of documentation. UML,

It consumes time, therefore money also.
In perfect world, you should have code automatically when you draw diagram,
or have diagram when you write code ...

If you have ever used TogetherSoft or Rational Rose, that is precisely what
both environments will do.

[Alexey N. Solofnenko]

... and Together does it better than Rational Rose.

- Alexey.

Post by Paul Nichols (TeamB)
If you have ever used TogetherSoft or Rational Rose, that is precisely what
both environments will do.

[Paul Nichols (TeamB)]

Post by Alexey N. Solofnenko
... and Together does it better than Rational Rose.
- Alexey.

Agreed!!!