Slide 11B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach

Slide 11B.2 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CHAPTER 11 — Unit B CASE

Slide 11B.3 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Continued from Unit 11A

Slide 11B.4 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l Example 1: Class diagram drawn by hand

Slide 11B.5 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l Unfortunately, no CASE tool can draw such a diagram automatically –Instead, the classes are displayed on the screen arranged in some order –The user can then rearrange the classes to his or her personal taste l While classes are moved about on the screen, the CASE tool automatically adjusts the lines connecting them –However, many CASE tools support only straight lines joining the classes

Slide 11B.6 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l The diagram drawn by the CASE tool is clear, but is not as aesthetically pleasing as the hand-drawn one l On the other hand (and these are the major reasons why CASE tools are essential for developing and maintaining information systems): –When changes are made, the hand-drawn version has to be redrawn from scratch—changes can easily be made to the CASE tool version –At any time, every member of the development team knows the current classes of the project, namely, the current version of the CASE tool version

Slide 11B.7 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) –The description stored inside the CASE tool can be used to draw not just the one class diagram, but all the other UML diagrams as well –Some environments can use the stored description of the information system to generate code in C++ or Java l The advantages of CASE tools far outweigh the fact that the resulting UML diagrams are not picture perfect

Slide 11B.8 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l Some UML diagrams can be adjusted by the user until they are aesthetically pleasing l Even then, however, the resulting diagram may still be unsatisfactory

Slide 11B.9 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l The same class diagram drawn using Rational Rose

Slide 11B.10 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l Example 2: Use-case diagram drawn by hand

Slide 11B.11 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l The same use-case diagram drawn using Rational Rose

Slide 11B.12 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l Example 3: Sequence diagram drawn by hand

Slide 11B.13 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CASE and Aesthetics (contd) l The same sequence diagram drawn using Rational Rose

Slide 11B.14 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Continued in Unit 11C