jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 102 Watches: Fields can be watched for access or modification if the target JVM supports it. To create a watchpoint, select a field and then right click. A popup menu will allow you to set a modification or access watchpoint, or to remove them if they are set. A "Watch All" will set a watchpoint on all fields of the same signature as the selected field (including those in subclasses and superclasses of the field's object type). A simple "Watch" will set a watchpoint only for the selected field's object. Fields that are being watched for modification are shown with a black triangle pointing up in the center of the icon, those with an access watch are shown with the triangle pointing down, while those with both will have a black square. Setting a lot of watches can slow down debugging. 19.6 Breakpoints Breakpoints can be set in the CSD windows using the "View" / "Breakpoints" menu, or the context menu. Only breakpoints in CSD Windows are active (when a CSD Window is closed, the breakpoints will go away, when one is opened, the breakpoints will become active. Breakpoints can be added or removed while the debugger is running. While the debugger is running, invalid breakpoints (breakpoints set on lines that do not contain executable code) are shown crossed out. If the class files for a particular source file can not be found, the breakpoints are shown with a slash through them. In order for this mechanism to work, the source file and associated class files must be located in the same directory. 20 Complexity Profile Graph (CPG) The Complexity Profile Graph, or CPG, is a statement-level complexity or comprehensibility metric. Each segment, which corresponds roughly to a program statement, is assigned a complexity that is a weighted sum of: Reachability - the number of conditions that must be evaluated to reach the segment from outside of the enclosing method, function, or other top-level statement block. This is the traditional definition of reachability. Content - the log of the number of significant tokens in the segment. Some punctuation, such as block-enclosing braces or a statement-ending semicolon, is not considered significant. A pair of parenthesis is counted as one token. Breadth - the number of statements, methods, etc. in the innermost block containing the segment. Inherent - value assigned based on the inherent complexity of the innermost enclosing structure. For example, segments in switch or case statements are assigned an inherent complexity of 3.0. This reflects the view that some structure types are inherently more complex than others. The CPG window "Data Sets" menu allows any combination of these values and the total complexity to be viewed. Currently, the CPG is implemented only for Java and Ada. 21 CPG Window The main section of this window shows the complexity values for the currently selected data sets. If the source is unedited, selecting segments in the CPG window will select the corresponding text in the source CSD window, and vice versa. The selection in the CPG window is shown as a yellow background. If the source is unedited, a black rectangle shows the segments that are currently visible in the CSD Window.
DRAFT, February 18, 2003, Page 103 Each data set value is scaled in the display, by the weight used in computing the total complexity, unless there is only one data set, in which case it is shown unscaled. The label at the top of the CPG window shows the complexity values of the segment under the mouse cursor. If the weight of a particular data set is not 1.0, the value and weight are displayed. The scale button allows the graph to be scaled, from two-pixel wide bars to screen-width bars. If "Scroll Lock" is on, the CPG window and the CSD window from which it was generated will scroll as one. This option is not available if the source has been edited. A scrollbar at the bottom of the window allows the CPG to be scrolled if it does not fit in the window. • File Menu • Data Sets Menu • View Menu 21.1 File Menu Save Data - allows CPG complexity values to be saved in a straightforward text format. Escape From Virtual Desktop / Enter Virtual Desktop - takes the CPG window in and out of the virtual desktop. Disconnect From Source - dissociates the CPG window from the source CSD window. A second CPG window can then be generated from the same source. Exit This Window - closes the CPG window. 21.2 Data Sets Menu This menu allows each data set to be turned off or on. 21.3 View Menu Vertical Orientation - if on, the segments axis is vertical, and the complexity horizontal. Show Key - if on, a key that shows the color for each data set is shown (if there is more than one active data set). Show Axis Labels - if on, the segment and complexity axes are labeled. If there is only one active data set, the complexity axis is labeled with the name of that data set, otherwise it is labeled with "complexity". Show Number Labels - if on, segment and complexity axes have value labels. The labels are evenly spaced based on a minimum inter-label separation. 22 UML Class Dependency Diagrams jGRASP can produce a UML diagram for Java code. The diagram is generated for classes in the source, class, and jar files in the current project. These diagrams are generated directly from the class (or jar) files, so source files must first be compiled.
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 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: DRAFT, February 18, 2003, Page 101
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 123 and 124: 23.4.3 UML Print Settings Page Marg
Page 125 and 126: File syncing may cause jGRASP to lo
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?