DocumentCode
2947095
Title
Introduction to use of formal methods in software and hardware
Author
Huling, George
Author_Institution
PRC Inc., Pasadena, CA, USA
fYear
1994
fDate
27-29 Sep 1994
Firstpage
48
Lastpage
52
Abstract
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
Keywords
formal specification; safety-critical software; software engineering; formal methods; formal programming language; formal representations; formal specifications; graphical representation; notational; safety critical applications; specification verification; tabular; Application software; Design engineering; Design methodology; Hardware; Logic design; Manufacturing; Mathematics; Partial response channels; Safety; Writing;
fLanguage
English
Publisher
ieee
Conference_Titel
WESCON/94. Idea/Microelectronics. Conference Record
Conference_Location
Anaheim , CA
ISSN
1095-791X
Print_ISBN
0-7803-9992-7
Type
conf
DOI
10.1109/WESCON.1994.403628
Filename
403628
Link To Document