Hey I bought this book by Craig Larman. He has devoted around 2 chapters on use cases. I was wondering if any of you really feel or have experienced that you write better programs on using UML. I guess I'll be spending all my time in UML modelling rather than actual coding Thanks in advance. Chris
I'm actually using UML in my daily work and find it extremely useful (I'm doing both design and coding). The most important aspect of UML (IMHO) is that it's a kind of lingua franca for sw designers and developers. It greatly supports effective communication among project group members and helps minimize notation-related misunderstundings. I also find UML pretty comprehensive yet simple enoung to be quickly mastered. However, UML is just a notation. Simply visualizing your designs in UML won't make you / your colleagues write better code. That's what I think, anyway. Greg
UML is going to become industry standard in coming years. So it is better to learn it write now. By using UML , you become independent of the progamming language. Everyone all around world will talk one language that is UML. The platform will be common. This will be tremendous boon. It will be great help to Project Managers , Project Leaders & Programmers as the projects can be discussed effectively using UML diagrams , without communication gaps. Suppose you have mastered UML & you want to explain JAVA API 's to anyone, you can explain with greatest ease by using class diagrams. I think some way or other way s/w companies are using UML. I agree with Grzegorz Klebus saying " Simply visualizing your designs in UML won't make you / your colleagues write better code". But , there are tools like TogetherJ which generates Java code as you go on generating the model with UML. more such tools may come in future.
Shailesh, I agree that generating code from a UML tool might potentially be pretty useful. Class diagrams, after all, are pretty easily mapped to modern OO languages. I'm much less confident about the reverse-engineering from code to UML (with present tools). The problem is I personally had not-so-good experiences with one of major modelling tools. The round-trip engineering capability was far too imperfect to be useful. Regards, Greg
hi, Grzegorz Klebus and shailesh sonavadekar belief in UML is undersandable and I agree with them.However to generate a complete code automatically every time by using these diagrams I doubt. Also current IDE 's , for java which are based on Rapid Application devlopment (RAD) which hide the intricasies such as Corba linking , cannot be replaced by the IDE's which generate code by using OOAD techniques. There will always be a gap between coding and UML diagrams and they may not be completely linked.This is my feeling. pl. suggest. Prabodh
[This message has been edited by Prabodh Navare (edited November 26, 2000).]
Well, there's Rational Rose and Advanced Software's GDPro. Or you can check out UC Irvine's Argo/UML. I guess it depends on the price range you are looking at. John [This message has been edited by John Wetherbie (edited January 10, 2001).]
The only reason for time is so that everything doesn't happen all at once.
- Buckaroo Banzai
I have enjoyed using togetherJ. I agree that UML won't replace coding any time soon. But to just be able to create a bunch of classes and method stubs really quickly, it's hard to beat it. And it's nice to have it set up a diagram for an existing package. It can help you see relationships between classes, and realize where you might need to be refactoring. This can be great when you're trying to get back into a project, and have kind of forgotten how you set it up.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>"Those who cast the votes decide nothing. Those who count the<BR>votes decide<BR>everything." <BR> -Joseph Stalin<HR></BLOCKQUOTE>