Formal methods: The very idea - Some thoughts about why they work when they work

Science of Computer Programming

Volumn 42, Issue 1, 2002, Pages 11-27

  Berry, Daniel M ^a  

^a UNIVERSITY OF WATERLOO   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SYSTEMS; COMPUTER SYSTEMS PROGRAMMING; FORMAL LOGIC; SOFTWARE ENGINEERING;

FORMAL METHODS (FM);

REQUIREMENTS ENGINEERING;

EID: 0036131823     PISSN: 01676423     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0167-6423(01)00026-0     Document Type: Article

References (29)

1. Towards a formal basis for the formal development method and the Ina Jo specification language
2. The importance of ignorance in requirements engineering
3. The programmer-client interaction in arriving at program specifications
4. Requirements engineering
5. Specification and prototyping: Some thoughts on why they are successful
6. No silver bullet
7. Model checking large software specifications
8. Social processes and proofs of theorems and programs
9. INATEST: An interactive environment for testing formal specifications
10. Design and code inspections to reduce errors in program development
11. Program verification: The very idea
12. System engineering overview
13. Understanding requirements
14. An introduction to OBJ: A language for writing and testing formal algebraic program specifications
15. Rapid prototyping: Lessons learned
16. Seven myths of formal methods
17. Using formal methods to develop an ATC information system
18. Testing formal specifications to detect design errors
19. Programs, life cycles, and laws of software evolution
20. Guest editor's introduction: Formal methods in software engineering
21. Pitfalls of formality in early system design
22. Calculating with requirements
23. A specifier's introduction to formal methods