Is UML practical? [closed]

Answer 1

I think the UML is useful thought I think the 2.0 spec has made what was once a clear specification somewhat bloated and cumbersome. I do agree with the edition of timing diagrams etc since they filled a void...

Learning to use the UML effectively takes a bit of practice. The most important point is to communicate clearly, model when needed and model as a team. Whiteboards are the best tool that I've found. I have not seen any "digital whiteboard software" that has managed to capture the utility of an actual whiteboard.

That being said I do like the following UML tools:

1. Violet - If it were any more simple it would be a piece of paper

2. Altova UModel - Good tool for Java and C# Modeling

3. MagicDraw - My favorite commercial tool for Modeling

4. Poseidon - Decent tool with good bang for the buck

5. StarUML - Best open source modeling tool

Answer 2

UML is used as soon as you represent a class with its fields and methods though it's just a kind of UML diagram.

The problem with UML is that the founders book is too vague.

UML is just a language, it's not really a method.

As for me, I really find annoying the lack of UML schema for Opensource Projects. Take something like Wordpress, you just have a database schema, nothing else. You have to wander around the codex api to try to get the big picture.

Answer 3

In a sufficiently complex system there are some places where some UML is considered useful.

The useful diagrams for a system, vary by applicability.
But the most widely used ones are:

• Class Diagrams
• State Diagrams
• Activity Diagrams
• Sequence Diagrams

There are many enterprises who swear by them and many who outright reject them as an utter waste of time and effort.

It's best not to go overboard and think what's best for the project you are on and pick the stuff that is applicable and makes sense.

Answer 4

I am coming to this topic a little late and will just try an clarify a couple minor points. Asking if UML is useful as far too broad. Most people seemed to answer the question from the typical/popular UML as a drawing/communication tool perspective. Note: Martin Fowler and other UML book authors feel UML is best used for communication only. However, there are many other uses for UML. Above all, UML is a modeling language that has notation and diagrams mapped to the logical concepts. Here are some uses for UML:

• Communication
• Standardized Design/Solution documentation
• DSL (Domain Specific Language) Definition
• Model Definition (UML Profiles)
• Pattern/Asset Usage
• Code Generation
• Model to Model transformations

Given the uses list above the posting by Pascal is not sufficient as it only speaks to diagram creation. A project could benefit from UML if any of the above are critical success factors or are problem areas that need a standardized solution.

The discussion should expanded out from how UML can be over kill or applied to small projects to discuss when UML makes sense or will actually improve the product/solution as that is when UML should be used. There are situations where UML for one developer could sense as well, such as Pattern Application or Code Generation.

Answer 5

UML seems to good for large projects with large teams of people. However I've worked in small teams where communication is better.

Using UML-esque diagrams is good though, especially in the planning stage. I tend to think in code, so I find writing large specs hard. I prefer to write down the inputs' and outputs' and leave the developers to design the bit in the middle.

Answer 6

UML has its place. It becomes increasingly important as the size of the project grows. If you have a long running project, then it is best to document everything in UML.