UC知道找明白人翻译计算机反面英文材料(4)!~~
来源：百度知道 编辑：UC知道 时间：2024/06/21 19:07:02
There will always be cases that the specification does not explicitly address. The role
of the robustness requirement is to make sure that if such cases do arise, the system does
not cause catastrophic events; it should produce appropriate error messages, terminate its
execution cleanly, or enter a so-called “graceful degradation” mode.
Software is supposed to be soft, and indeed is in principle; nothing can be easier than to
change a program if you have access to its source code. Just use your favorite text editor.
We need extendibility because at the basis of all software lies some human
phenomenon and hence fickleness. The obvious case of business software (“Management
Information Systems”), where passage of a law or a company’s acquisition may suddenly
invalidate the assumptions on which a system rested, is not special; even in scientific
computation, where we may expect the laws of physics to stay in place from one mont
of the robustness requirement is to make sure that if such cases do arise, the system does
not cause catastrophic events; it should produce appropriate error messages, terminate its
execution cleanly, or enter a so-called “graceful degradation” mode.
Software is supposed to be soft, and indeed is in principle; nothing can be easier than to
change a program if you have access to its source code. Just use your favorite text editor.
We need extendibility because at the basis of all software lies some human
phenomenon and hence fickleness. The obvious case of business software (“Management
Information Systems”), where passage of a law or a company’s acquisition may suddenly
invalidate the assumptions on which a system rested, is not special; even in scientific
computation, where we may expect the laws of physics to stay in place from one mont
也往往会有不规范的情况,明确处理. 发挥稳健的要求是,以确保如果出现这种情况, 该系统并不造成灾难性事件; 它应产生适当的误差信息,终止执行清廉、 或进入所谓婀娜退化模式. 软件理应是软,事实上是在原则; 比什么都好办,如果你要改变一个节目获得其源代码. 刚刚用你最喜欢的文字编辑. 因为我们需要扩展所有软件的基础在于人的现象,因而有些变化无常. 显然对于商业软件(管理信息系统) 凡通过法律或公司开展收购可能突然无效假设一个系统休息、 不是特殊; 即使在科学计算、 我们可以预期的法律物理学留在广场由一个月延长至明年 我们的理解和物理模型系统将会改变. 传统软件工程方法并没有充分考虑到变化 依靠理想而针对软件生命周期分析,初步阶段要求冻结、 其余的用于设计和建设过程中解决. 这是可以理解的: 在第一项任务是发展进步的纪律和良好的技术说明,解决固定问题 如此我们才可以做什么,如果担心的变化而有人忙着解决问题. 如今随着软件工程技术的基本到位,已成为中央必须承认和处理这一 . 变化是无孔不入软件开发:需求的变化,我们的认识到位,对算法 数据的代表性,执行技巧. 支持对象的基本目标是改变技术和管理,通过这本书的主题. 尽管许多改善的技术,可扩展性小例子或介绍介绍课程 相关只有变得清晰大项目. 对于提高可扩展两个原则:? 设计简便:建筑永远是一个简单容易适应变化较复杂. ? 放权:越是自主单元的可能性较高,只有一个简单的改变会影响模块 或少数单元,而非引发连锁反应变动整个系统