The software industry struggles with the problems of producing correct and reliable software. Although many techniques have been proposed to deal with this situation, one is particularly promising: namely, the application of formal methods. Formal methods give software development a rigorous mathematical basis, which permits more precise specifications and earlier error detection. Conventional software development still prevails, but surveys of formal methods projects have increasingly shown that these projects can be completed on budget and on schedule. What's more, software produced by formal methods has proved to be well structured and maintainable. Much research has been conducted to improve the foundations of formal methods. While this is important, equally important for the technology transfer process is practical advice on how these methods can be applied in an industrial setting. While there is no ''silver bullet'' that will solve the software development problem, the authors present 10 practical guidelines for software developers that will help them avoid some of the pitfalls commonly experienced in applying formal methods. The authors discuss specification notations, levels of formal development, cost estimation, documentation, quality standards, and testing. They also offer hard-won advice that may be especially invaluable to developers about the need to be flexible, to retain consultants for unique expertise, and also to retain some of the traditional development techniques that are still effective.
