• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>World multiconference on systemics, cybernetics and informatics >Neither a perpetuum mobile nor a perfect software: Sincerity in the relationship between the manufacturer and the client with respect to software defects
【24h】

Neither a perpetuum mobile nor a perfect software: Sincerity in the relationship between the manufacturer and the client with respect to software defects

机译：既不是长期移动也不是完美的软件：诚信在制造商与客户之间的关系方面的软件缺陷

获取原文
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

Certain mechanical shortcomings in engines cannot be ascribed to errors in design or defects in construction. They are due to the fact that it is impossible to design and construct engines in a way that completely eliminates friction between its parts. Friction causes wear and tear that is proportional to the amount of use. Likewise, when it conies to software one should not expect it to behave any differently. One must expect a set of errors in the software that cannot be attributed to faulty design or construction. A set of errors will materialize as a function of the equally unavoidable logical "friction" between, on the one hand the necessary but hardly specifiable complexity of software, and on the other hand the following two requirements: 1) The necessity to observe strict limits of the cost and time of development, and 2) The necessity to offer a maximum simplicity of operation. In other words, just as mechanical deficiencies will be proportional to the amount of use to which an engine endures, the user of a software application will experience informational flaws (bugs) that are proportional in number to the use that s/he makes of the product. Once this is shown, we argue that the proper way to approach these software defects is neither via innumerable rounds of trial and error in laboratories, nor with mathematical algorithms that try to demonstrate correctness to 100%. Instead, we believe that the right way would be -analogous to mechanical systems- to deliver the product to the user with a minimal standard of quality but with a certifiable plan of preventive and corrective maintenance. Such a plan would assure the user that any errors that emerge are looked upon in due time, and that the manufacturer will try to keep the downtime as short as possible. All this leads us 1) to discuss the concept of complexity up to the point where we can show that it is possible to contrast it quantitatively with the limitation of cost and time of development, as well as with operational simplicity; the purpose being to establish a clear distinction between defects which can be attributed to complexity, and those which cannot; 2) to show how the occurrence of defects due to complexity is a function of use of the software in the same way as defects due to wear and tear are a consequence of the use of the engine; 3) to show the viability of the concept of a minimum standard quality in software; 4) to sketch the model of preventive and corrective maintenance of defects due to complexity and use of software, analogous or at least as effective as the preventive and corrective model of maintenance of mechanical wear and tear; 5) identify successful experiences in the software industry which resemble the above mentioned model; or elements that may contribute to its implementation; and 6) to propose and promote a culture of information system maintenance which would make it foreseeable for the user, acceptable, and finally budgetable, in a similar manner as the maintenance of an automobile. All of these should bring about a sincere relationship between producer and client, and reduce the level of discord between them.
机译：发动机中的某些机械缺点不能归因于施工中的设计或缺陷中的错误。它们是因为无法以完全消除其部件之间的摩擦的方式设计和构建发动机。摩擦导致磨损与使用量成正比。同样，当它对软件锥体时，一个人不应该指望它表现得不同。人们必须期望在无法归因于故障设计或施工的软件中的一组错误。一组错误将作为同样不可避免的逻辑“摩擦”之间的函数，一方面是必要但几乎不可指定的软件复杂性，另一方面，以下两个要求：1）必须观察严格限制的必要性成本和时间的发展，2）必须提供最大的操作简单。换句话说，就像机械缺陷一样与发动机恢复的使用量成比例，软件应用程序的用户将遇到数字漏洞（错误），其数量与S / HE所做的使用成比例产品。一旦显示了这一点，我们认为接近这些软件缺陷的正确方法既不通过实验室中的无数轮次试验和错误，也没有尝试向100％展示正确性的数学算法。相反，我们认为，正确的方法是对机械系统的途径 - 以最小的质量提供产品，但具有可证式的预防和纠正性维护计划。这样的计划会向用户保证在常年时代浏览出现的任何错误，制造商将尽量保持停机时间。所有这一切都会导致我们1）讨论复杂性的概念，达到我们可以证明可以通过限制成本和发展时间的限制以及操作简单来对比它的概念。目的在于在可以归因于复杂性的缺陷之间建立清晰的区别，以及不能的缺陷; 2）为了展示由于复杂性导致的缺陷的发生是如何使用该软件的功能，以与磨损引起的缺陷相同的方式是发动机的使用; 3）显示软件中最低标准质量概念的可行性; 4）根据复杂性和使用软件，类似的或至少与机械磨损的预防和纠正模型一样有效，以绘制缺陷的预防性和纠正缺陷的模型; 5）确定类似于上述模型的软件行业的成功经验;或可能导致其实施的元素; 6）提出并促进信息系统维护的文化，这将使您可以预见到用户，可接受和最终的预算，以与汽车的维护类似的方式。所有这些都应带来生​​产者和客户之间的真诚关系，并减少它们之间的不和谐程度。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱：kefu@zhangqiaokeyan.com

京公网安备：11010802029741号 ICP备案号：京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有

  • 客服微信

  • 服务号