计算机专业英语第6章

1、Chapter 6 Software Engineering6-1Computer EnglishChapter 6 Software EngineeringChapter 6 Software Engineering6-2 掌握软件的生命周期的基本术语与知识；掌握软件的生命周期的基本术语与知识； 了解软件工程的发展趋势；了解软件工程的发展趋势； 了解软件设计方法；了解软件设计方法； 了解软件安全的有关知识；了解软件安全的有关知识； 掌握复杂定语掌握复杂定语(从句从句)的翻译技巧。的翻译技巧。Requirements:Chapter 6 Software Engineering6-3New W

2、ords & Expressionsmanufactured products 工业产品工业产品 lieu n.场所场所software life cycle 软件生命周期软件生命周期 versus prep. 与与.相对相对nondescriptive adj. 非描述性的非描述性的 community n.团体团体, 社会社会authorized adj.权威认可的权威认可的, 经授权的经授权的leverage n.杠杆作用杠杆作用generic adj. 一般的一般的, 普通的普通的potential adj.潜在的潜在的, 可能的可能的in terms of adv.根据根据, 按照按

3、照, 用用.的话的话terminology n.术语学术语学personnel n.人员人员, 职员职员inventory n.详细目录详细目录, 财产清册财产清册adhere to v.粘附粘附, 粘着粘着, 坚持坚持, 追随追随password n.密码密码, 口令口令specification n.详述详述, 说明书说明书, 规范规范encrypt v.加密加密,将将.译成密码译成密码preprocess vt.预加工，预处理预加工，预处理routine n.程序程序modular adj.模块的模块的, 有标准组件的有标准组件的well-established 充分证实的充分证实的de

4、composition n.分解分解breakdown n. 分解，故障分解，故障pertaining to 与与.有关的有关的maintenance n.维护维护, 保持保持imperative adj.强制性的，命令式强制性的，命令式paradigm n.范例，模式范例，模式approach vt.接近接近,解决解决;n.近似近似,途径途径 conducive adj.有助于有助于.的的evasive adj.逃避的；回避的；推托的逃避的；回避的；推托的framework n.构架构架, 框架框架, 结构结构Chapter 6 Software Engineering6-4New Word

5、s & Expressionstake the form of 采取采取.形式形式 entity n.实体实体; 统一体统一体modular design 标准设计标准设计, 模块化设计模块化设计 object-oriented 面向对象的面向对象的stub n.树桩树桩, 桩模块桩模块give way to 让路让路,让步让步trial-and-error n.试错，反复试验试错，反复试验malfunction n.故障，出错故障，出错waterfall model 瀑布模型瀑布模型analogy n.类似类似, 类推类推after all adv.毕竟毕竟stark adv.完全地完全地t

6、rial-and-creative 试验并创造的试验并创造的nonstructure 非结构性非结构性intuition n.直觉直觉, 直觉的知识直觉的知识contradiction n.反驳反驳, 矛盾矛盾incremental model 增量式模型增量式模型update v.修正修正, 更新；更新；n.更新更新stepwise adj.楼梯式的楼梯式的, 逐步的逐步的prototype n.原型原型evolutionary prototyping 演化式原型演化式原型 in favor of adv.赞同赞同, 有利于有利于throwaway prototyping 抛弃原型抛弃原型i

7、ron out 消除；解决困难等消除；解决困难等documentation n.文件文件debugging n.调试调试spreadsheet n.电子制表软件电子制表软件, 电子数据表电子数据表AbbreviationsCASE (computer-aided software engineering) 计算机辅助软件工程计算机辅助软件工程GUI (Graphical User Interfaces) 图形用户界面图形用户界面Chapter 6 Software Engineering6-56.1 The Software Life Cycle6.1.1 The Cycle as a Who

8、le Use Modifaction Developmen Figure 6-1 The software life cycleThe most fundamental concept in software engineering is the software life cycle.软件生命周期是软件工程中最基本的概念。软件生命周期是软件工程中最基本的概念。Chapter 6 Software Engineering6-66.1.1 The Cycle as a WholeThe software life cycle is shown in Figure 6-1. This figure

9、 represents the fact that once software is developed, it enters a cycle of being used and modified that continues for the rest of the softwares life. Such a pattern is common for many manufactured products as well. The difference is that, in the case of other products, the modification phase is more

10、 accurately called a repair or maintenance phase because other products tend to move from being used to being modified as their parts become worn. 在图在图6-1中展示了软件的生命周期。这个图说明了一个事实：一旦软件开发中展示了软件的生命周期。这个图说明了一个事实：一旦软件开发完成，它就进入了使用和修改的循环，并且这个循环将在软件生命期的剩完成，它就进入了使用和修改的循环，并且这个循环将在软件生命期的剩余时间中不断进行。这样的模式对机器制造的产品而言

11、也是很普通的。不余时间中不断进行。这样的模式对机器制造的产品而言也是很普通的。不同之处在于，对于其他产品，软件工程中的修改阶段要被更精确地称作修同之处在于，对于其他产品，软件工程中的修改阶段要被更精确地称作修理或者维护阶段，因为其他产品由于部件的磨损会有从使用到修改的过程。理或者维护阶段，因为其他产品由于部件的磨损会有从使用到修改的过程。Chapter 6 Software Engineering6-76.1.1 The Cycle as a WholeSoftware, on the other hand, does not wear out. Instead, software moves

12、 into the modification phase because errors are discovered, because changes in the softwares application occur that require corresponding changes in the software, or because changes made during a previous modification are found to induce problems elsewhere in the software. For example, changes in ta

13、x laws may require modifications to payroll programs that calculate withholding taxes, and all too often these changes may have adverse effects in other areas of the program that may not be discovered until some time later.当然，软件不存在磨损的问题。但是，软件进入修改阶段或者是因为错误当然，软件不存在磨损的问题。但是，软件进入修改阶段或者是因为错误被发现，或者是因为要在软件

14、的应用程序中进行修改从而修改了软件，或被发现，或者是因为要在软件的应用程序中进行修改从而修改了软件，或者是因为先前的改变又引起了软件其他地方出现了新的问题。例如，税务者是因为先前的改变又引起了软件其他地方出现了新的问题。例如，税务法案的改变导致对计算扣税的工资程序进行修改，而太频繁的修改则会在法案的改变导致对计算扣税的工资程序进行修改，而太频繁的修改则会在软件的其他地方引起反面的作用，而这些是不会被立即发现的。软件的其他地方引起反面的作用，而这些是不会被立即发现的。Chapter 6 Software Engineering6-86.1.1 The Cycle as a WholeRegard

15、less of why software enters the modification phase, the process requires that a person (often not the original author) study the underlying program and its documentation until the program, or at least the pertinent part of the program, is understood. Otherwise, any modification could introduce more

16、problems than it solves. Acquiring this understanding can be a difficult task even when the software is well-designed and documented. In fact, it is often within this phase that a piece of software is finally discarded under the pretense (too often true) that it is easier to develop a new system fro

17、m scratch than to modify the existing package successfully 不管因为什么原因软件进入了修改阶段，这个过程需要人们（通常不是原不管因为什么原因软件进入了修改阶段，这个过程需要人们（通常不是原始的作者）研究程序及其文档，直到程序或者至少是相关部分的程序能够始的作者）研究程序及其文档，直到程序或者至少是相关部分的程序能够被理解。否则，任何的修改将导致比它所解决问题还要更多的问题出现。被理解。否则，任何的修改将导致比它所解决问题还要更多的问题出现。即使软件有优秀的设计和齐备的文档，理解也是一个很困难的工作。事实即使软件有优秀的设计和齐备的文档，

18、理解也是一个很困难的工作。事实上，常常是在这个阶段，一个有用的软件片段最终就被放弃了（常常是这上，常常是在这个阶段，一个有用的软件片段最终就被放弃了（常常是这样），而开发一个新的系统比成功地修改现有软件更容易。样），而开发一个新的系统比成功地修改现有软件更容易。Chapter 6 Software Engineering6-96.1.1 The Cycle as a WholeExperience has shown that a little effort during Experience has shown that a little effort during the developm

19、ent of software can make a the development of software can make a tremendous difference when modifications in the tremendous difference when modifications in the software are required. software are required. 经验告诉我们经验告诉我们, ,软件开发过程中的一丁点付出，会在软件需要软件开发过程中的一丁点付出，会在软件需要修改的时候带来巨大的不同。修改的时候带来巨大的不同。In turn, mo

20、st of the research in software In turn, most of the research in software engineering focuses on the development stage of engineering focuses on the development stage of the software life cycle, with the goal being to the software life cycle, with the goal being to take advantage of this effort-versu

21、s-benefit take advantage of this effort-versus-benefit leverage.leverage.反过来，大多数软件工程的研究都集中于软件生命周期的开发反过来，大多数软件工程的研究都集中于软件生命周期的开发阶段，它们的目标是要利用这个付出与收益的杠杆作用。阶段，它们的目标是要利用这个付出与收益的杠杆作用。Chapter 6 Software Engineering6-106.1.1 The Cycle as a WholeThe Traditional Development PhaseThe stages within the developm

22、ent phase of the software life cycle are analysis, design, implementation, and testing (Figure 6-2).软件生命周期的开发阶段包括分析、设计、实现与测试等步骤（如图软件生命周期的开发阶段包括分析、设计、实现与测试等步骤（如图6-2所所示）。示）。 Analysis Design Implementation Testing Chapter 6 Software Engineering6-116.1.1 The Cycle as a WholeThe Traditional Development P

23、haseAnalysis The development phase of the software life cycle begins with analysis-a major goal being to identify the needs of the user of the proposed system. If the system is to be a generic product sold in a competitive market, this analysis would involve a broad-based investigation to identify t

24、he needs of potential customers. If, however, the system is to be designed for a specific user, then the process would be a more narrow investigation.分析分析 软件生命周期的开发阶段以分析开始软件生命周期的开发阶段以分析开始主要目标是确定用户对所提主要目标是确定用户对所提出系统的需求。如果系统是一个在竞争的市场上销售的通用产品，这个分出系统的需求。如果系统是一个在竞争的市场上销售的通用产品，这个分析将会包括一个广泛的调查来发现潜在用户的需要。但是

25、，如果系统是为析将会包括一个广泛的调查来发现潜在用户的需要。但是，如果系统是为特殊用户设计的，那么这个过程就是一个更专业的调查。特殊用户设计的，那么这个过程就是一个更专业的调查。Chapter 6 Software Engineering6-126.1.1 The Cycle as a WholeThe Traditional Development PhaseAs the needs of the potential user are identified, they are compiled to form a set of requirements that the new system

26、 must satisfy. These requirements are stated in terms of the application rather than in the technical terminology of the data processing community. One requirement might be that access to data must be restricted to authorized personnel. Another might be that the data must reflect the current state o

27、f the inventory as of the end of the last business day or that the arrangement of the data as displayed on the computer screen must adhere to the format of the paper forms currently in use.当潜在用户的要求被确定之后，要将这些要求汇编成新系统必须满足的需当潜在用户的要求被确定之后，要将这些要求汇编成新系统必须满足的需求。这些需求是从应用的角度来表述，而不是用数据处理界的技术术语来求。这些需求是从应用的角度来表

28、述，而不是用数据处理界的技术术语来表达。一种需求可能是对数据的存取必须限制在有权限的人员，另一种可表达。一种需求可能是对数据的存取必须限制在有权限的人员，另一种可能是当一个工作日结束时，数据必须反映目前的清单状态，或者可能是在能是当一个工作日结束时，数据必须反映目前的清单状态，或者可能是在计算机屏幕上的数据必须按照用户目前使用的格式来显示。计算机屏幕上的数据必须按照用户目前使用的格式来显示。Chapter 6 Software Engineering6-136.1.1 The Cycle as a WholeThe Traditional Development PhaseAfter the

29、system requirements are identified, they are converted into more technical system specifications. For example, the requirement that data be restricted to authorized personnel might become the specification that the system will not respond until an approved eight-digit password has been typed at the

30、keyboard or that data will be displayed in encrypted form unless preprocessed by a routine known only to authorized personnel.系统的需求被确定以后，它们就转化为更具技术性的说明书。例如，关于系统的需求被确定以后，它们就转化为更具技术性的说明书。例如，关于数据须限制在某些有权限的人的需求，就可能转化为以下规范数据须限制在某些有权限的人的需求，就可能转化为以下规范直到从直到从键盘输入一个被认可的键盘输入一个被认可的8位密码，系统才开始响应，或者除非经过只有授权位密码，系统才

31、开始响应，或者除非经过只有授权的人才知道的例程预处理，否则数据将以加密的形式显示在屏幕上。的人才知道的例程预处理，否则数据将以加密的形式显示在屏幕上。Chapter 6 Software Engineering6-146.1.1 The Cycle as a WholeThe Traditional Development PhaseDesign Whereas analysis concentrates on what the proposed system should do, design concentrates on how the system will accomplish th

32、ose goals. It is here that the structure of the software system is established. 设计设计 分析关注这个系统应该做什么，而设计关注这个系统应分析关注这个系统应该做什么，而设计关注这个系统应该怎样来实现目标。正是通过设计建立了软件系统的结构。该怎样来实现目标。正是通过设计建立了软件系统的结构。Chapter 6 Software Engineering6-156.1.1 The Cycle as a WholeThe Traditional Development PhaseIt is a well-establish

33、ed principle that the best structure for a large software system is a modular one. Indeed, it is by means of this modular decomposition that the implementation of large systems becomes a possibility. Without such a breakdown, the technical details required in the implementation of a large system wou

34、ld exceed a humans comprehensive powers. 大型软件系统最好的结构是模块化系统，这是一条被充分证实大型软件系统最好的结构是模块化系统，这是一条被充分证实的原则。确实，正是借助模块化的分解方法，大型系统的实现的原则。确实，正是借助模块化的分解方法，大型系统的实现才成为可能。没有这样的分解，在大型系统实现过程中所需要才成为可能。没有这样的分解，在大型系统实现过程中所需要的技术细节可能会超过一个人的理解能力。的技术细节可能会超过一个人的理解能力。Chapter 6 Software Engineering6-166.1.1 The Cycle as a Whol

35、eThe Traditional Development PhaseWith a modular design, however, only the details pertaining to the module under consideration need be mastered. This same modular design is also conducive to future maintenance because it allows changes to be made on a modular basis. (If a change is to be made to th

36、e way each employees health benefits are calculated, then only modules dealing with health benefits need be considered.)然而，有了这种模块化设计，仅仅需要熟悉与在考虑中的模块然而，有了这种模块化设计，仅仅需要熟悉与在考虑中的模块相关的细节。同样，模块化设计对未来的维护是有益的，因为相关的细节。同样，模块化设计对未来的维护是有益的，因为它允许对基本的模块进行修改。（如果要对每个雇员的医疗福它允许对基本的模块进行修改。（如果要对每个雇员的医疗福利计算方法进行修改，那么仅仅需要考虑

37、处理医疗福利模块。）利计算方法进行修改，那么仅仅需要考虑处理医疗福利模块。）Chapter 6 Software Engineering6-176.1.1 The Cycle as a WholeThe Traditional Development PhaseThere are, however, distinctions regarding the concept of a module. If one approaches the design task in terms of the traditional imperative paradigm, modules consist of

38、 procedures and the development of a modular design takes the form of identifying the various tasks that the proposed system must perform. In contrast, if one approaches the design task from the object-oriented perspective, modules are seen as objects and the design process becomes that of identifyi

39、ng the entities (objects) in the proposed system as well as how these entities should behave.但是，有关模块的概念也是有差别的。如果一个人以传统的命令式语言范但是，有关模块的概念也是有差别的。如果一个人以传统的命令式语言范式的方法来进行设计工作，模块由不同程序组成，而模块化设计则以确定式的方法来进行设计工作，模块由不同程序组成，而模块化设计则以确定有待实现系统的不同任务的方式进行。相反地，如果一个人从面向对象的有待实现系统的不同任务的方式进行。相反地，如果一个人从面向对象的角度来完成设计工作，模块就被看

40、成了对象，而设计过程变成了确定有待角度来完成设计工作，模块就被看成了对象，而设计过程变成了确定有待实现系统中的实体（对象）以及确定这些实体是如何工作的。实现系统中的实体（对象）以及确定这些实体是如何工作的。Chapter 6 Software Engineering6-186.1.1 The Cycle as a WholeThe Traditional Development PhaseImplementation Implementation involves the actual writing of programs, creation of data files, and devel

41、opment of databases. 实现实现 实现包括程序的实际编写、数据文件的建立以及数据库实现包括程序的实际编写、数据文件的建立以及数据库的开发等过程。的开发等过程。Chapter 6 Software Engineering6-196.1.1 The Cycle as a WholeThe Traditional Development PhaseTesting Testing is closely associated with implementation, because each module of the system is normally tested as it i

42、s implemented. Indeed, each module in a well-designed system can be tested independently of the other modules by using simplified versions of the other modules, called stubs, to simulate the interaction between the target module and the rest of the system. Of course, this testing of components gives

43、 way to overall system testing as the various modules are completed and combined.测试测试 测试与实现紧密联系，因为系统中的每一个模块都要在实现的过程中测试与实现紧密联系，因为系统中的每一个模块都要在实现的过程中进行正常测试。确实，通过使用其他模块的简化版本进行正常测试。确实，通过使用其他模块的简化版本有时称为桩模块，有时称为桩模块，来模拟目标模块和系统其他部分的交互，从而使设计良好的系统中的每一来模拟目标模块和系统其他部分的交互，从而使设计良好的系统中的每一个模块都可以被独立地测试。当然，在各种模块都开发完成并且

44、整合在一个模块都可以被独立地测试。当然，在各种模块都开发完成并且整合在一起之后，这个组件的测试将让路给整个系统的测试。起之后，这个组件的测试将让路给整个系统的测试。Chapter 6 Software Engineering6-206.1.1 The Cycle as a WholeThe Traditional Development PhaseUnfortunately, the testing and debugging of a system is extremely difficult to perform successfully. Experience has shown tha

45、t large software systems can contain numerous errors, even after significant testing. Many of these errors may go undetected for the life of the system, but others may cause major malfunctions. The elimination of such errors is one of the goals of software engineering. The fact that they are still p

46、revalent means that a lot of research remains to be done.不幸的是，成功地进行系统的测试和调试是极其困难的。经验表明，大型不幸的是，成功地进行系统的测试和调试是极其困难的。经验表明，大型的软件系统可能包含众多的错误，甚至是经过关键测试之后。许多这样的的软件系统可能包含众多的错误，甚至是经过关键测试之后。许多这样的错误在软件的生命期中一直潜伏着，但是也有一些会导致关键性的错误。错误在软件的生命期中一直潜伏着，但是也有一些会导致关键性的错误。减少这样的错误是软件工程的一个目标。这些错误的普遍存在说明了在这减少这样的错误是软件工程的一个目标。这

47、些错误的普遍存在说明了在这方面还有许多的研究工作要做。方面还有许多的研究工作要做。Chapter 6 Software Engineering6-216.1.1 The Cycle as a WholeRecent TrendsEarly approaches to software engineering insisted on performing analysis, design, implementation, and testing in a strictly sequential manner. The feeling was that too much was at risk d

48、uring the development of a large software system to allow for trial-and-error techniques. 软件工程的早期方法坚持要严格地遵守分析、设计、实现以及软件工程的早期方法坚持要严格地遵守分析、设计、实现以及测试的顺序。在大型软件系统的开发过程中，感觉到采用试错测试的顺序。在大型软件系统的开发过程中，感觉到采用试错法是在冒着很大的风险进行开发的。法是在冒着很大的风险进行开发的。Chapter 6 Software Engineering6-226.1.1 The Cycle as a WholeRecent Tre

49、ndsAs a result, software engineers insisted that the entire analysis of the system be completed before beginning the design and, likewise, that the design be completed before beginning implementation. The result was a development process now referred to as the waterfall model, an analogy to the fact

50、 that the development process was allowed to flow in only one direction.因此，软件工程师坚持应当在设计之前进行完整的系统分析，因此，软件工程师坚持应当在设计之前进行完整的系统分析，同样，设计应该在实现之前完成。这就形成了一个现在称为瀑同样，设计应该在实现之前完成。这就形成了一个现在称为瀑布模型的开发过程，这是对开发过程只允许以一个方向进行的布模型的开发过程，这是对开发过程只允许以一个方向进行的事实的模拟。事实的模拟。Chapter 6 Software Engineering6-236.1.1 The Cycle as a

51、 WholeRecent TrendsYou will notice a similarity between the four problem-solving phases identified by Polya and the analysis, design, implementation, and testing phases of software development. After all, to develop a large software system is to solve a problem. 你将注意到由你将注意到由Polya提出的解决问题的提出的解决问题的4个阶段

52、与软件开发的个阶段与软件开发的分析、设计、实现和测试阶段的类似性。毕竟，开发一个大型分析、设计、实现和测试阶段的类似性。毕竟，开发一个大型的软件系统是去解决一个问题。的软件系统是去解决一个问题。Chapter 6 Software Engineering6-246.1.1 The Cycle as a WholeRecent TrendsOn the other hand, the traditional waterfall approach to software development is in stark contrast to the free-wheeling , trial-an

53、d-creative problem solving. Whereas the waterfall approach seeks to establish a highly structured environment in which development progresses in a sequential fashion, creative problem solving seeks a nonstructured environment in which one can drop previous plans of attack to pursue sparks of intuiti

54、on without explaining why. 另一方面，传统软件开发的瀑布模型法与随心所欲的反复试验并创另一方面，传统软件开发的瀑布模型法与随心所欲的反复试验并创造性地解决问题的方法是完全相反的。瀑布模型法寻求建立一个高造性地解决问题的方法是完全相反的。瀑布模型法寻求建立一个高度结构化的环境，希望在这个环境中的开发可以顺利地进行，而创度结构化的环境，希望在这个环境中的开发可以顺利地进行，而创造性的问题解决要寻找一个非结构化的环境，希望在这个环境中可造性的问题解决要寻找一个非结构化的环境，希望在这个环境中可以抛弃先前的计划，来追逐思维的火花，而不用解释为什么。以抛弃先前的计划，来追逐思维

55、的火花，而不用解释为什么。Chapter 6 Software Engineering6-256.1.1 The Cycle as a WholeRecent TrendsIn recent years, software engineering techniques have begun to reflect this underlying contradiction as illustrated by the emergence of the incremental model for software development. Following this model, the desi

56、red software system is constructed in increments-the first being a simplified version of the final product with limited functionality. 近年来，软件工程技术已经开始反映这种本质的对立了，这可近年来，软件工程技术已经开始反映这种本质的对立了，这可以由软件开发中出现的增量式模型来说明。根据这个模型，所以由软件开发中出现的增量式模型来说明。根据这个模型，所需的软件系统是通过增量模式来构造的需的软件系统是通过增量模式来构造的首先开发最终产品首先开发最终产品的简化版本，它

57、只有有限的功能。的简化版本，它只有有限的功能。Chapter 6 Software Engineering6-266.1.1 The Cycle as a WholeRecent TrendsOnce this version has been tested and perhaps evaluated by the future user, more features are added and tested in an incremental manner until the system is complete. For example, if the system being devel

58、oped is a student records system for a university register, the first increment may incorporate only the ability to view student records. Once that version is operational, additional features, such as the ability to add and update records, would be added in a stepwise manner.一旦这个版本经过测试、并且也许经过了未来用户的评

59、估，更一旦这个版本经过测试、并且也许经过了未来用户的评估，更多的特性就可以添加进去并且进行测试，这样就以一种增量的多的特性就可以添加进去并且进行测试，这样就以一种增量的方式进行，直到完成系统。例如，如果正在开发的系统是为大方式进行，直到完成系统。例如，如果正在开发的系统是为大学登记员设计的学生记录系统，第一次迭代版本仅仅包括浏览学登记员设计的学生记录系统，第一次迭代版本仅仅包括浏览学生记录的功能。一旦这个版本可以运行了，其他特性，诸如学生记录的功能。一旦这个版本可以运行了，其他特性，诸如增加和更新记录的功能，就可以分阶段地添加到系统中了。增加和更新记录的功能，就可以分阶段地添加到系统中了。Ch

60、apter 6 Software Engineering6-276.1.1 The Cycle as a WholeRecent TrendsThe incremental model is evidence of the trend in software development toward prototyping in which incomplete versions of the proposed system, called prototypes, are built and evaluated. In the case of the incremental model these