软件设计教案(级).docVIP

Chapter 1Programming Review and Introduction to Software Design Process Phase Introduced in This Chapter Key Concept: ( Where We’re Headed ( Coding Practices Used in This Book Instance variables may be referred to with “this.” Example: class Car { int milesDriven; … } May use esDriven within methods of Car to clarify Static variables may be referred to with class name. Example: class Car { static int numCarsSold; … } May use Car.numCarsSold within methods of Car to clarify Parameters are given prefix “a” or “an” Example: public … getVolume( int aLength ) {…} Programming Conventions: Method Documentation 1 of 2 Preconditions: conditions on non-local variables that the method’s code assumes Includes parameters Verification of these conditions not promised in method itself Postconditions: value of non-local variables after execution Includes parameters Notation: x denotes the value of variable x after execution Invariants: relationships among non-local variables that the function’s execution do not change (The values of the individual variables may change, however.) Equivalent to inclusion in both pre- and post-conditions There may also be invariants among local variables Programming Conventions: Method Documentation 2 of 2 Return: What the method returns Known issues: Honest statement of what has to be done, defects that have not been repaired etc. (Obviously) limited to what’s known! Key Concept: ( Specifying Methods ( Flowchart Example Pseuodocode Example For an X-ray Controller Advantages of Pseudocode Flowcharts Clarify algorithms in many cases Impose increased discipline on the process of documenting detailed design Provide additional level at which inspection can be performed Help to trap defects before they become code Increases product reliability May decreases overall costs Disadvantages of Pseudocode Flowcharts Create an additional level of documentation to maintain Introduce error possibilities in translating to code May require too