外文翻译-软件测试的艺术.docx

西安邮电学院 毕 业 设 计（论 文） 外文文献翻译 系 别： 电子与信息工程 专 业： 电子信息工程 班 级： 电子1002班 学生姓名： 起止时间：2014年 3月10日 至 2014年 6月15日 英文原文 The art of software testing Glenford J. Myers When you finish module-testing a program, you have really only just begun the testing process. This is especially true of large or complex programs. Consider this important concept: A software error occurs when the program does not do what its end user reasonably expects it to do. Applying this definition, even if you could perform an absolutely perfect module test, you still couldn’t guarantee that you have found all software errors. To complete testing, then, some form of further testing is necessary. We call this new form higher-order testing. Software development is largely a process of communicating information about the eventual program and translating this information from one form to another. For that reason, the vast majority of software errors can be attributed to breakdowns, mistakes, and noise during the communication and translation of information. This view of software development is illustrated in Figure 6.1, a model of the development cycle for a software product. The flow of the process can be summarized in seven steps: 1. The program user’s needs are translated into a set of written requirements. These are the goals for the product. 2. The requirements are translated into specific objectives by assessing feasibility and cost, resolving conflicting requirements, and establishing priorities and trade-offs. 3. The objectives are translated into a precise product specification, viewing the product as a black box and considering only its interfaces and interactions with the end user. This description is called the external specification. 4. If the product is a system such as an operating system, flight-control system, database management system, or employee personnel system, rather than a program (compiler, payroll pr