01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Session 30—<strong>UML</strong> Modeling <strong>To</strong>ols 309<br />

sizes. Costs range from free to over $5,000. As with any product, you often get what you<br />

pay for. But the fact is that not all of us need the best or the most expensive or the most<br />

popular. Frankly, some of the low-end products are really worth taking a close look at. So<br />

I’ve provided some evaluation criteria to assist you in your discussions with vendors and in<br />

your own evaluations of the products you want to investigate.<br />

The basics<br />

First I cover the features that should pretty much be provided by every modeling tool. The<br />

distinctions come in how they implement them. Modeling tool vendors will usually give you<br />

access to an evaluation copy of their software. Often, it is as simple as downloading it from<br />

their site. I’ll provide you a convenient site to gain access to most of the existing tools at<br />

the end of this session.<br />

Type and version of the <strong>UML</strong> supported<br />

As of this printing, the current <strong>UML</strong> version is 1.4. <strong>UML</strong> 1.5 is due to be completed by OMG<br />

sometime in 2002, with <strong>UML</strong> 2.0 to follow after that. Since there are generally schedule<br />

delays with updates to the <strong>UML</strong> spec, <strong>UML</strong> 2.0 will probably not be official until sometime<br />

in 2003.The real question is whether the tool really supports 1.4. A substantial number of<br />

changes exist between 1.3 and 1.4. Many tools seem to have a blend of both.<br />

Use the diagram notations in this book to help you verify the support. Get an evaluation<br />

copy of the product and create one of each of the diagrams to try out the modeling features<br />

and check out the standard. You can even duplicate the diagrams created in this book as a<br />

benchmark.<br />

Platform support<br />

You need to run the tool on your operating system(s). Verify that the tool is supported on<br />

each platform you require. Beware that the versions for different platforms are not always in<br />

sync. Some of the vendors bypass this problem by writing the tool in Java. Even so, differences<br />

in virtual machines may surprise you.<br />

Printing<br />

One of the primary reasons you will create the <strong>UML</strong> diagrams is to share your ideas. Check<br />

out the printing capabilities. Some tools require add-ins to get all the features you need.<br />

Many of these diagrams can be very large, so the print features should support either plotters<br />

or easy-to-use multi-page layouts. A print preview feature can also be a great time<br />

saver when preparing presentations.<br />

HTML documentation<br />

Most of the time, there will be a limited number of people actually using the tool, but a much<br />

larger number of people who need to see what is being produced. Printed output is good for<br />

meetings but impractical for wide and frequent dissemination. Many of the current tools support<br />

the generation of reports and diagrams in HTML format so that they may be published on<br />

the Web. Again, some tools build this in as a standard feature while others use add-ins.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!