jgrasp handbook

More documents

Recommendations

Info

5.3 Laying Out the UML Diagram DRAFT, February 18, 2003, Page 56 Currently, jGRASP has limited automatic layout capabilities. However, manually arranging the class symbols in the diagram is straightforward, and once this is done, jGRASP remembers your layout from one generate/update to the next. To begin, locate the class symbol that contains main. In our example, this would be the PersonalLibrary class. Remember the project name should reflect the name of this class. Generally, you want this class near the top of the diagram. Left click on the class symbol and then while holding down the left mouse button, drag the symbol to the area of the diagram you want it, and then release the mouse button. Now repeat this for the other class symbols until you have the diagram looking like you want it. Keep in mind that class–subclass relationships are indicated by the inheritance arrow and that these should be laid out in a tree-down fashion. You can do this automatically by selecting all classes for a particular class– subclass hierarchy (hold down SHIFT and left-click each class). Then on UML window menu, click on Layout – Tree Down to perform the operation. With a one or more classes selected, you can move them Figure 42. First cut at laying out the UML
DRAFT, February 18, 2003, Page 57 as a group. Figures 42 shows the UML diagram after the PersonalLibrary class and the legend have been repositioned. For Figure 43, the UML settings (Edit – Settings) have been changed to include the JDK classes, and these have been dragged as a group to the lower part of the diagram. Note, you can experiment with making these external classes visible or not by going to View – Visible Objects – then uncheck External References. Here are several heuristics for laying out your UML diagrams: (1) The class symbol that contains main should go near the top of the diagram. (2) Classes in an inheritance hierarchy of should be laid out tree-down, and then moved as group. (3) Other dependencies should be laid out with the red dashed line pointing downward. (4) JDK classes, when included, should be toward the bottom of the diagram. (5) Line crossings should be minimized. (6) The legend is usually below the diagram. Figure 43. Second cut at laying out UML (with JDK classes included)
Page 1 and 2:
The Table of Contents Index Handboo
Page 3 and 4:
DRAFT, February 18, 2003, Page ii 4
Page 5 and 6:
DRAFT, February 18, 2003, Page iv 1
Page 7 and 8:
DRAFT, February 18, 2003, Page vi 2
Page 9 and 10:
Overview of jGRASP DRAFT, February
Page 11 and 12:
DRAFT, February 18, 2003, Page 3 sp
Page 13 and 14: DRAFT, February 18, 2003, Page 5 Pr
Page 15 and 16: DRAFT, February 18, 2003, Page 7 Co
Page 17 and 18: 11 Control Structure Diagram (CSD)
Page 19 and 20: 1 Installing jGRASP DRAFT, February
Page 21 and 22: 2.1 Creating a New File DRAFT, Febr
Page 23 and 24: In the upper right corner of the CS
Page 25 and 26: 2.2 Saving a File DRAFT, February 1
Page 27 and 28: 2.4 Loading a File DRAFT, February
Page 29 and 30: DRAFT, February 18, 2003, Page 21 4
Page 31 and 32: DRAFT, February 18, 2003, Page 23 O
Page 33 and 34: 2.7 Line Numbers DRAFT, February 18
Page 35 and 36: DRAFT, February 18, 2003, Page 27 T
Page 37 and 38: 2.9 Running a Program DRAFT, Februa
Page 39 and 40: 3 The Control Structure Diagram (CS
Page 41 and 42: DRAFT, February 18, 2003, Page 33 n
Page 43 and 44: Selection (cont’d) switch (when b
Page 45 and 46: 3.4 CSD Templates DRAFT, February 1
Page 47 and 48: 3.6 Reading Source Code with the CS
Page 49 and 50: Consider the fragment at right with
Page 51 and 52: 4 Projects DRAFT, February 18, 2003
Page 53 and 54: 4.2 Adding files to the Project DRA
Page 55 and 56: 4.4 Generating Documentation for th
Page 57 and 58: 4.5 Jar file Creation and Extractio
Page 59 and 60: DRAFT, February 18, 2003, Page 51 I
Page 61 and 62: DRAFT, February 18, 2003, Page 53 j
Page 63: DRAFT, February 18, 2003, Page 55 M
Page 67 and 68: 5.5 Displaying Dependencies Between
Page 69 and 70: 5.8 Saving the UML Layout DRAFT, Fe
Page 71 and 72: DRAFT, February 18, 2003, Page 63 b
Page 73 and 74: DRAFT, February 18, 2003, Page 65 t
Page 75 and 76: DRAFT, February 18, 2003, Page 67 V
Page 77 and 78: DRAFT, February 18, 2003, Page 69 T
Page 79 and 80: Part 2 - Reference DRAFT, February
Page 81 and 82: DRAFT, February 18, 2003, Page 73 i
Page 83 and 84: 9.4 Requirements for the Integrated
Page 85 and 86: 13 Known Bugs DRAFT, February 18, 2
Page 87 and 88: Unicode support - this will require
Page 89 and 90: Section 3. Disclaimer of Warranty D
Page 91 and 92: * . * DRAFT, February 18, 2003, Pag
Page 93 and 94: DRAFT, February 18, 2003, Page 85 A
Page 95 and 96: DRAFT, February 18, 2003, Page 87 S
Page 97 and 98: 17.13 Projects DRAFT, February 18,
Page 99 and 100: 17.18 Jar/Zip Extractor Dialog DRAF
Page 101 and 102: DRAFT, February 18, 2003, Page 93 e
Page 103 and 104: 18.8 Find Dialog / Page DRAFT, Febr
Page 105 and 106: DRAFT, February 18, 2003, Page 97 s
Page 107 and 108: \xnn hexadecimal representation of
Page 109 and 110: DRAFT, February 18, 2003, Page 101
Page 111 and 112: DRAFT, February 18, 2003, Page 103
Page 113 and 114: 22.5 View Menu DRAFT, February 18,
Page 115 and 116:
• CSD Page • Colors Page • Fo
Page 117 and 118:
DRAFT, February 18, 2003, Page 109
Page 119 and 120:
23.2.1.11 View Page DRAFT, February
Page 121 and 122:
Page 123 and 124:
23.4.3 UML Print Settings Page Marg
Page 125 and 126:
File syncing may cause jGRASP to lo
Page 127 and 128:
Page 129 and 130:
flags..............................
show all

jgrasp handbook

Create successful ePaper yourself

Delete template?

Save as template?