Discussions of the role of mathematics in software engineering are common and have probably not changed much over the last few decades. There is now much discussion about the "intuitive" nature of software construction and analogies are drawn (falsely) with graphic design, (conventional) architecture, etc. The conclusion is that mathematics is an unnecessary luxury and that, like these other disciplines, it is not needed in everyday practice. We attempt to refute these arguments by recourse to ideas from the Philosophy of Science developed over the past century. We demonstrate why these ideas are applicable, why they establish a framework (in the sense of Carnap) in which many central ideas in software engineering can be formalised and organised, why they refute the simplistic recourse to "intuition", and why they provide a scientific/engineering framework in which contributions to the theory and practice of software engineering can be judged.
关于数学在软件工程中的作用的讨论很普遍,在过去的几十年中可能没有太大变化。现在,关于软件构建的“直觉”性质进行了很多讨论,并通过图形设计,(传统)体系结构等(错误地)得出了类推。结论是数学是不必要的奢侈,并且像其他学科一样,数学也是如此。在日常练习中不需要。我们试图依靠上个世纪发展起来的科学哲学的思想来驳斥这些论点。我们将说明为什么这些思想适用,为什么它们建立了一个框架(就Carnap而言),在该框架中可以对软件工程中的许多中心思想进行形式化和组织化,为什么它们反驳了对“直觉”的简单求助,以及为什么它们提供了一种科学/工程框架,可以判断对软件工程的理论和实践有何贡献。 I> P>
testing, analysis, and verification;
机译:务实问答:一种博弈论方法
机译:务实的试验“现实世界”问题的实际答案
机译:对日本全国心理健康服务的务实评估提出了更多的问题而不是答案。
机译:科学严谨,一个务实问题的答案:软件工程的语言框架
机译:法庭语用学:墓抢劫帕培里的问题和答案分析
机译:引言部分回答为什么科学伦理很重要?的问题
机译:事物的科学:未解决的科学问题和毫无疑问的材料研发中的科学答案