UML diagrams

raptors892004 · **Posted:** Tue Nov 07, 2006 11:36 am

Can someone recommend a tool which simplifies the making of UML diagrams.. I have the code done but have to make the UML diagrams now Confused

Thanks in advance

wtd · **Posted:** Tue Nov 07, 2006 11:44 am

Dia is a free diagramming tool.

http://www.gnome.org/projects/dia/

Yes, it is available for Windows.

I would like to note that if you're writing UML diagrams after the code, then they serve no purpose. Generally speaking, though, UML diagrams are less than worthless.

raptors892004 · **Posted:** Tue Nov 07, 2006 3:44 pm

I cant agree more but unfortunately I have to hand them in along with the school project. Thank you for the link Smile

r.3volved · **Posted:** Tue Nov 07, 2006 5:14 pm

Dia is a great program (and FREE!)

Otherwise, Visio and Rational Rose are the other two that I've used.
...Visio is great as it integrates with other Office products, but it is not free
...Rose is hideous and I don't like it at all

Dan · **Posted:** Tue Nov 07, 2006 5:35 pm

We use argouml for the software engering corses i am taking.

http://argouml.tigris.org/

it is free and made in java.

batman · **Posted:** Tue Nov 07, 2006 6:24 pm

Are the uml diagrams u are doing for java????????????//
Anyways if it is it is very very simple esspecially if ur done the code already. If u want i can explain to u how its done. Ive never heard of uml diagrams being used for Turing though.

Dan · **Posted:** Tue Nov 07, 2006 6:29 pm

The idea of UML digarms is noramly that you use them befor you write your code to plan it out. If you allready have your code made then it is rather odd that you whould be making a UML digram about it.

r.3volved · **Posted:** Tue Nov 07, 2006 8:13 pm

UML is used for all sorts of project management, not just software.
It isn't required for writing an application for yourself, however it is an extremely useful and necessary tool for developing projects for a client.

What kind of UML diagrams are you doing?
Use cases and scenerios?
...if you knew more about UML then you'd understand why it is recomended.

1of42 · **Posted:** Tue Nov 07, 2006 9:32 pm

Hacker Dan wrote:

The idea of UML digarms is noramly that you use them befor you write your code to plan it out. If you allready have your code made then it is rather odd that you whould be making a UML digram about it.

Sounds sort of like that's what he SHOULD have done according to his teacher, but since he didn't see the need for them (which I can't blame him for; often UML diagrams serve no really useful purpose, especially in trivial programs) he's now making them after the fact in order to meet his teacher's expectations.

Dan · **Posted:** Wed Nov 08, 2006 1:00 am

Any how geting back to UML software. Argouml has great options for doing every thing from class digragms to use cases to even distrubtion digrams. My point to batman was noramly you make a plan befor you do somthing not affter you do it. An intresting part of argouml is that it can aucatly generate some code for you (most likey not turing but java and a few others).

I know form personal exprice how frustinating it can be to be forced to me a desging for a program that you could make in a few mins with out thinking about it but i dougth there is much if any software in existcne that whould make UML digramas from code since it defeates the purposes.

Just out of cerusity what kind of corses is this for?

wtd · **Posted:** Wed Nov 08, 2006 1:24 am

Hacker Dan wrote:

noramly you make a plan befor you do somthing not affter you do it

It is idiocy to plan out a project on a large scale before writing any code.

The best laid plans...

Dan · **Posted:** Wed Nov 08, 2006 1:37 am

I am not saying you make the one plan and never change form it, you have to update and change your plan as you devlop the product. But coding befor any kind of plan at all? I could see that on small projects but for a big project you whont some kind of idea about whats going on befor diving in.

wtd · **Posted:** Wed Nov 08, 2006 1:41 am

That's why you don't do big projects.

Big projects are just collections of small projects. You take your project. You figure out what the smallest possible useful subset of it is. You implement that. You get it right, then move on.

That's a plan. UML is just lines and words on paper.

Dan · **Posted:** Wed Nov 08, 2006 1:43 am

Ah but as you just side, taking a big project and making it in to small ones is a plan Razz

. I was refuring to planing and desgin in general, some aspects of uml and software engering i whould have to say are a wast of time in most cases.

wtd · **Posted:** Wed Nov 08, 2006 1:45 am

Well, it's not so much a plan as a philosophy.

	Computer Science Canada Programming C, C++, Java, PHP, Ruby, Turing, VB Username: Password: Register
Wiki Blog Search Turing Chat Room Members