Introduction to use of formal methods in software and hardware
G. Huling · Proceedings of WESCON '94 · 2002
To be formal a method must have a systematic and repeatable process for verifying the consequences of a specification. Verifications can be manual, partially mechanized, or fully mechanized. Formal representations can be tabular, graphical, notational, expressed in a formal (programming) language, or any combination thereof. Barriers to adoption and reasons for adoption are discussed. The examples presented show successful commercial as well as safety critical applications and show that formal specifications can be understood by users.>