Do formal methods really work?

L. Zucconi, Greg Royle, K. Reed, J. Staples
{"title":"Do formal methods really work?","authors":"L. Zucconi, Greg Royle, K. Reed, J. Staples","doi":"10.1109/ASWEC.1996.10003","DOIUrl":null,"url":null,"abstract":"\"Formal methods\" is an established but inappropriate name for the use in software engineering of a standard engineering technique: prediction of in-service performance at design time, based on relevant scientific theories and mathematical models. Today, no other branch of engineering would deny the necessity of scientifically based prediction-though such denial was common a century ago. Given the precedents elsewhere in engineering, the author confidently says that the formal methods are really needed if software engineering is to really work! It is also clear that every branch of engineering involves much more than prediction of in-service performance. For example the creation of designs is central and is purely informal, even though it may be interleaved with formal methods. This example is enough to show that formal methods alone cannot make software engineering really work, no matter how good the formal methods are. In the author's view the key questions are these: what is the role of formal methods in making software engineering really work? How capable are existing formal methods of performing that role?.","PeriodicalId":321303,"journal":{"name":"Proceedings of 1996 Australian Software Engineering Conference","volume":"21 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1996-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of 1996 Australian Software Engineering Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ASWEC.1996.10003","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 8

Abstract

"Formal methods" is an established but inappropriate name for the use in software engineering of a standard engineering technique: prediction of in-service performance at design time, based on relevant scientific theories and mathematical models. Today, no other branch of engineering would deny the necessity of scientifically based prediction-though such denial was common a century ago. Given the precedents elsewhere in engineering, the author confidently says that the formal methods are really needed if software engineering is to really work! It is also clear that every branch of engineering involves much more than prediction of in-service performance. For example the creation of designs is central and is purely informal, even though it may be interleaved with formal methods. This example is enough to show that formal methods alone cannot make software engineering really work, no matter how good the formal methods are. In the author's view the key questions are these: what is the role of formal methods in making software engineering really work? How capable are existing formal methods of performing that role?.
形式化方法真的有效吗?
“形式化方法”是在软件工程中使用的一种标准工程技术的一个既定但不恰当的名称:基于相关的科学理论和数学模型,在设计时预测在用性能。今天,没有其他工程分支会否认科学预测的必要性——尽管这种否认在一个世纪前很常见。考虑到工程中的其他先例,作者自信地说,如果软件工程要真正工作,那么形式化方法是非常需要的!同样清楚的是,工程的每一个分支所涉及的远不止对服役性能的预测。例如,设计的创作是中心的,完全是非正式的,即使它可能与正式的方法交织在一起。这个例子足以说明单独的形式化方法不能使软件工程真正工作,无论形式化方法有多好。在作者看来,关键的问题是:形式化方法在使软件工程真正工作中的作用是什么?现有的正式方法执行该角色的能力如何?
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信