UML case studies

[Abed Rabie]

Dear All,

Good luck for u all. I would like to ask about links and urls that contains case studies using UML for object oriented analysis and design.

Looking forward to hear from u soon.

Thanks and best regards

[Abed Rabie]

Dear All,

Is their anyone can help me finding some UML case studies or recommend to me a free book.

Thanks and best regards

[Stan James]

Here's an interesting blog on the different ways people use uml: http://martinfowler.com/bliki/UmlMode.html What are your goals with it?

For free resources, browse Scott Ambler's AgileModeling.com. His Diagrams of UML 2 is a good page to keep bookmarked.
[ April 12, 2005: Message edited by: Stan James ]

[Pj Murray]

Good luck finding the case studies. I've read a few good ones over the years but a lot of unbalanced sales-brochure like testimonials.

UML is an important specification and can be very useful when used to help with the design phase of projects.

What vendor case studies won't mention is:

UML requires a large amount of write-off in current training investment as programmers become application modelers.

UML/MDA requires new development routines and practices.

UML and MDA is often sold to management and imposed on Java developers, which is one of the reasons why MDA has met with strong resistance from Java developers.

UML/MDA tools vendors tend not to provide the source code and often demand expensive professional services fees to modify or customize the tools. This can result in expensive professional services for customization.

UML/MDA model evolution maintenance requires tedious, repetitive, manual intervention. The modeler must ensure that the UML model reflects changes for every major and minor change.

UML/MDA model implementation involves the time-consuming and error-prone tasks of manually mapping a UML model to platform-specific code.

Java developers sometimes resist the introduction of MDA products because they are often introduced and used by business analysts, thereby putting the position of Java developers within an organization under threat.

[Ilja Preuss]

Take also a look at http://faq.javaranch.com/view?UmlLinks

[Ilja Preuss]

Originally posted by PJ Murray:
UML is an important specification and can be very useful when used to help with the design phase of projects.

I agree that UML is important, though I don't think that the *specification* is that important. (I also think the whole notion of a design *phase* is dangerous.)

UML requires a large amount of write-off in current training investment as programmers become application modelers.

UML doesn't require that. UML is just a language and doesn't require any specific usage. It's quite possible to simply use it as a communication medium on white boards or napkins when discussing issues in the development team.

UML/MDA requires new development routines and practices.

Certainly. UML and MDA are two quite different beasts, though.