jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 50 5 UML Class Diagrams and Object Workbench Java programs usually involve multiple classes, and there can be many dependencies among these classes. To fully understand a multiple class program, it may be necessary to keep track of the interclass dependencies. Although this can be done mentally for small programs, it is usually helpful to see these dependencies in a class diagram. jGRASP provides for the automatic generation of class dependency diagrams based on the Unified Modeling Language (UML). Since a UML class diagram is based on multiple classes, jGRASP utilizes the “Project” to determine which user classes to include. (1) In order to generate a meaningful UML diagram, you must create a jGRASP project file (.gpj) as described in the previous section. You should include all of your source files (.java) in the project, and you may optionally include other files (e.g., .class, .dat, .txt, etc.). (2) The information jGRASP uses to generate the UML is located in the .class files. Recall, .class files are generated when you compile your Java program files. Therefore, you must compile your .java files prior to generating the UML diagram. Note, the .class files do not have to be in the project file, but they should be in the same directory as the .java files. The remainder of this section assumes you have created a project file, and that you have compiled your program files. 5.1 Opening the Project In preparation for generating the UML class dependency diagram for a particular project, you need to open that project. There are two ways to open a project. 1) On the Desktop tool bar, click Project – Open Project, and then select the project from the list of project files displayed in the Open Project dialog as shown in Figure 36. 2) In the Browse pane (tab in the left pane of the Desktop), double-click the project file. Figure 36. Open Project Dialog
DRAFT, February 18, 2003, Page 51 In Windows, the project name will be displayed at the top of the Desktop. You can also click the Project tab in the left pane of the Desktop to see the current project. If you are not in the right project, you can double-click on the project file in the Browse pane to open a project. If you additional help with opening a project, review the previous section. 5.2 Generating the UML In Figure 37 below, the left pane is set to the Project tab. The PersonalLibraryProject file is listed along with source files in the project. To generate the UML class dependency diagram, on the Desktop menu, click on UML, then Generate/Update UML. Figure 37. Generating the UML
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: 4.5 Jar file Creation and Extractio
Page 61 and 62: DRAFT, February 18, 2003, Page 53 j
Page 63 and 64: DRAFT, February 18, 2003, Page 55 M
Page 65 and 66: DRAFT, February 18, 2003, Page 57 a
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:
Page 113 and 114:
22.5 View Menu DRAFT, February 18,
Page 115 and 116:
• CSD Page • Colors Page • Fo
Page 117 and 118:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?