jgrasp handbook

More documents

Recommendations

Info

3.5 Hints on Working with the CSD DRAFT, February 18, 2003, Page 38 The CSD is generated based on the source code text in the CSD Window. When you click View -- Generate CSD (or press F2), jGRASP parses the source code based on a grammar or syntax that is slightly more forgiving that the Java compiler. If your program will compile okay, the CSD should generate okay as well. However, the CSD may generate okay even if your program will not compile. Your program may be syntactically correct, but not necessarily semantically correct. CSD generation is based on the syntax of your program. Enter code in syntactically correct chunks - To reap the most benefit from using the CSD when entering a program, you should take care to enter code in syntactically correct chunks, and then regenerate the CSD often. If an error is reported, it should be fixed before you move on. If the error message from the generate step is not sufficient to understand the problem, compile your program and you will get a more complete error message. “Growing a program” is described it the table below. Although the program being “grown” does nothing useful, it is both syntactically and semantically correct. More importantly, it illustrates the incremental steps that should be used to write your programs. Step Code to Enter After CSD is generated 1. We begin by entering the code for a Java class. Note, the file should be saved with the name of the class, which in this case is MyClass. 2. Now, inside the class, we enter the text for a method called myMethod, and then regenerate the CSD by pressing F2. 3. Next, inside myMethod, we enter a while loop with an empty statement, and then regenerate the CSD by pressing F2. Although this program is not intended to be useful, it does illustrates the process of growing a program, and generating the CSD each step of the way. public class MyClass { } public class MyClass { } myMethod() { } public class MyClass { } myMethod() { } while (true) { } ; ÏÕÖ×public class MyClass ÏÏ§{ ÏÏ©} ÏÕÖ×public class Hello ÏÏ§{ ÏÏ§ÏÞßàmyMethod() ÏÏ§ÏÏ§{ ÏÏ§ÏÏ©} ÏÏ©} ÏÕÖ×public class MyClass ÏÏ§{ ÏÏ§ÏÞßàmyMethod() ÏÏ§ÏÏ§{ ÏÏ§ÏÏ¨¹¹±while (true) ÏÏ§ÏÏ§ÏÏ5{ ÏÏ§ÏÏ§ÏÏ7¹¹Ï; ÏÏ§ÏÏ§ÏÏ°} ÏÏ§ÏÏ©} ÏÏ©}
3.6 Reading Source Code with the CSD DRAFT, February 18, 2003, Page 39 The CSD notation for each of the control constructs has been carefully designed to aid in reading and scanning source code. While the notation is meant to be intuitive, there are several reading strategies worth pointing out, especially useful with deeply nested code. Reading Sequence The visualization of sequential control flow is as follows. After statement s(1) is executed, the next statement is found by scanning down and to the left along the solid CSD stem. While this seems trivial, its importance becomes clearer with the if statement and deeper nesting. Reading Selection Now combining the sequence with selection (if.. else), after s(1), we enter the if statement marked by the diamond. If the condition is true, we follow the solid line to s(2). After s(2), we read down and to the left (passing through the dotted line) until we reach the next statement on the vertical stem which is s(4). If the condition is false, we read down the dotted line (the false path) to the else and then on to s(3). After s(3), again we read down and to the left until we reach the next statement on the stem which is s(4). Reading Selection with Nesting As above, after s(1), we enter the if statement and if cond1 and cond2 are true, we follow the solid lines to s(2). After s(2), we read down and to the left (passing through both dotted lines) until we reach to the next statement on the stem which is s(4). If the cond1 is false, we read down the dotted line (the false path) to s(4). If cond2 is false, we read down the dotted line to the else and then on to s(3). After s(3), again we read down and to the left until we reach to the next statement on the stem which is s(4). Ï¨¹¹Ïs(1); Ï¨¹¹Ïs(2); Ï¨¹¹Ïs(3); Ï Ï§ Ï¨¹¹Ïs(1); Ï¨¹³íf (cond) Ï§Ï6¾¹¹Ïs(2); Ï§Ïöélse Ï§ÏÈ¾¹¹Ïs(3); Ï¨¹¹Ïs(4); Ï§ Ï§ Ï¨¹¹Ïs(1); Ï¨¹³íf (cond1) Ï§Ï6¾¹³íf (cond2) Ï§Ï6ÏÏ6¾¹¹Ïs(2); Ï§Ï6ÏÏöélse Ï§ÏÏÏÈ¾¹¹Ïs(3); Ï¨¹¹Ïs(4); Ï§
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: 3.4 CSD Templates DRAFT, February 1
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 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?