A Formal Method for the Abstract Specification of Software
Journal of the ACM (JACM)
Software errors and complexity: an empirical investigation0
Communications of the ACM
Advances in software inspections
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
Typestate: A programming language concept for enhancing software reliability
IEEE Transactions on Software Engineering
Functional program testing and analysis
Functional program testing and analysis
Evaluating Software Engineering Technologies
IEEE Transactions on Software Engineering
Software interconnection models
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Principles of information systems analysis and design
Principles of information systems analysis and design
Designing documentation to compensate for delocalized plans
Communications of the ACM
Trace Specifications: Methodology and Models
IEEE Transactions on Software Engineering
Cecil: A Sequencing Constraint Language for Automatic Static Analysis Generation
IEEE Transactions on Software Engineering
Comments Analysis and Programming Errors
IEEE Transactions on Software Engineering
Towards a method of programming with assertions
ICSE '92 Proceedings of the 14th international conference on Software engineering
Aspect: an economical bug-detector
ICSE '91 Proceedings of the 13th international conference on Software engineering
An instrumented approach to improving software quality through formal technical review
ICSE '94 Proceedings of the 16th international conference on Software engineering
ACM Transactions on Programming Languages and Systems (TOPLAS)
Programming with Specifications: An Introduction to Anna, a Language for Specifying ADA Programs
Programming with Specifications: An Introduction to Anna, a Language for Specifying ADA Programs
The specification of process synchronization by path expressions
Operating Systems, Proceedings of an International Symposium
Using assertions about traces to write abstract specifications for software modules
Proceedings of the 2nd Conference of the European Cooperation on Informatics: Information Systems Methodology
An overview of path Pascal's design
ACM SIGPLAN Notices
Aspect: detecting bugs with abstract dependences
ACM Transactions on Software Engineering and Methodology (TOSEM)
Linear and structural event sequence analysis
ISSTA '96 Proceedings of the 1996 ACM SIGSOFT international symposium on Software testing and analysis
Verifiable partial specifications for logic programming
SAC '96 Proceedings of the 1996 ACM symposium on Applied Computing
Automatic Analysis of Consistency between Requirements and Designs
IEEE Transactions on Software Engineering
Software Reflexion Models: Bridging the Gap between Design and Implementation
IEEE Transactions on Software Engineering
Hi-index | 0.00 |
Formal verification of program properties may be infeasible or impractical, and informal analysis may be sufficient. Informal analysis involves the informal acceptance, by inspection, of the validity of program properties or steps in an analysis. Informal analysis may also involve abstraction. Abstraction can be used to eliminate details and concentrate on more general properties. Abstraction will result in informal analysis if it includes the use of undefined properties. A systematic, informal method for analysis called QDA (Quick Defect Analysis) is described. QDA is a comments analysis process based on facts and hypotheses. Facts are used to create an abstract program model, and hypotheses are selected, nonobvious program properties which are identified as needing verification. Hypotheses are proved from the facts that define an abstraction. QDA is hypothesis-driven in the sense that only those parts of an abstraction that are needed to prove hypotheses are created. The QDA approach was applied to a previously well tested operational flight program (OFP). The QDA method and the results of the OFP experiment are presented. The problems of incomplete or unsound informal analysis are analyzed, the relationship of QDA to other analysis methods is discussed, and suggested improvements to the QDA method are described.