李彤《软件工程》教学课件ch22.pptVIP

Stages of static analysis Information flow analysis. Identifies the dependencies of output variables. Does not detect anomalies itself but highlights information for code inspection or review Path analysis. Identifies paths through the program and sets out the statements executed in that path. Again, potentially useful in the review process Both these stages generate vast amounts of information. They must be used with care. Use of static analysis Particularly valuable when a language such as C is used which has weak typing and hence many errors are undetected by the compiler, Less cost-effective for languages like Java that have strong type checking and can therefore detect many errors during compilation. 22.4 Verification and formal methods Formal methods can be used when a mathematical specification of the system is produced. They are the ultimate static verification technique. They involve detailed mathematical analysis of the specification and may develop formal arguments that a program conforms to its mathematical specification. Arguments for formal methods Producing a mathematical specification requires a detailed analysis of the requirements and this is likely to uncover errors. They can detect implementation errors before testing when the program is analysed with the specification. Arguments against formal methods Require specialised notations that cannot be understood by domain experts. Very expensive to develop a specification and even more expensive to show that a program meets that specification. It may be possible to reach the same level of confidence in a program more cheaply using other V V techniques. The name is derived from the ‘Cleanroom’ process in semiconductor fabrication （半导体制作）. The philosophy is defect avoidance rather than defect removal. This software development process is based on: Incremental development; Formal specification; Static verification using correctness arguments; Statistical testing to determine program reliability. Cl