IT职业英语各章重点内容梳理

第一章

1.部分缩写以及重点职位
CEO-首席执行官
CTO-首席技术官
CFO-首席财务官）
COO-首席运营官
R&D Project Leads研发项目经理
Director Of Marketing 市场总监
Customer Service Manager 客户服务经理
2.What is the meaning of Organizational Chart?组织结构图的含义是什么?
An Organizational Chart is a chart which represents the structure of an organization in terms of rank. The chart shows the managers and subordinates that make up an organization, and it also shows relationships between them.
组织结构图是一种按等级表示组织结构的图表。该图表显示了组成组织的经理和下属，还显示了他们之间的关系。
关于组织结构图的举例如下：

3.什么是程序员？
Computer programmers write, test, and maintain __the detailed instructions, called programs , which computers must follow to perform their functions. They also conceive, design, and test logical structures for solving problems by computer . In general, a computer programmer refers to individuals whose main job function is programming; this group has a wide range of responsibilities and educational background. Somebody who practices(or professes) a formal approach to programming may also be known as a software engineer
计算机程序员编写、测试和维护__详细说明，称为项目，计算机必须遵循这些程序来执行它们的功能。他们还设想、设计和测试逻辑结构，用计算机解决问题。一般来说，电脑程序员指的是那些主要工作功能_是编程;这个群体有着广泛的责任和教育背景。实践(或公开)正式编程方法的人也可以称为软件工程师。
4.What is the meaning of feasibility study?可行性研究的意义是什么?
Feasibility study is a preliminary study before the main work of a project starts, which finds out the probability of the project’s success. It is an analysis of all possible solutions to a problem and recommendation on the best solution to use.
可行性研究是在一个项目的主要工作开始之前进行的初步分析，以找出该项目成功的几率。它分析所有可能的解决方案，并推荐最佳方案以备使用。
5.There are five types of feasibility study. They are:可行性研究有五种类型。它们是:
(1)Operational feasibility study:操作可行性研究:
examines how the software interacts with users. 检查软件如何与用户交互。
(2)Technical feasibility study:技术可行性研究:
checks the skills of the group检查小组成员的技能
(3)Schedule feasibility study:计划可行性研究
ensures that all deadlines can be met.确保所有的最后期限都能完成。
(4)Financial feasibility study:财务可行性研究:
examines the costs and benefits.检查成本和收益。
(5)Legal feasibility study:法律可行性研究
examines if the proposed solution have legal issues.检查提议的解决方案是否有法律问题。
6.What is the meaning of feasibility report?可行性报告的含义是什么?
This type of writing studies a project or a plan and then determines whether that project or plan is “feasible”. Not only does it give advice, it also provides the data and the reasoning behind that advice.
这类文章分析一个项目或一个计划，然后得出该项目或计划是否可行。它不仅给出建议，还提供支撑该建议的数据和推理。
7.How many types does feasibility report have?可行性报告有多少种?
(1)The first type studies a situation and a plan for doing something & then determines whether it is feasible, with data and reasoning.
(2)The second type starts with a stated(明确的) need, a selection of choices, or both and then recommend one, some or none.
(3)The third type provides a studied opinion on the value or worth of something.
第一种是研究一种情况和一个做某事的计划，然后用数据和推理来确定它是否可行。
第二种开始陈述(明确的)需求,选择,或两者兼而有之,然后推荐一个,部分或没有。
第三类是对某物的价值或价值的研究意见。
8.What is the requirements analysis?什么是需求分析?
In software engineering, requirements analysis, also known as requirements engineering, is a term used to describe all the tasks that scope and define a new or altered computer system. Requirements analysis is an important part of the software engineering process.
在软件工程中，需求分析，也叫作需求工程，描述一切研究和定义一个新的或更改过的计算机系统的任务。需求分析是软件工程过程中重要的一部分。
9.Who may conduct the feasibility study?
System Analyst 系统分析师
CTO
Project manager 项目经理
10.一些缩写及具体含义
GUI： Graphical User Interface
图形化界面：是指采用图形方式显示的计算机操作环境用户接口。
JVM：Java Virtual Machine（Java虚拟机）
Serial port串行端口：要用于串行式逐位数据传输
SDK软件开发工具包： 一系列程序接口，文档，开发工具的集合
Gantt Chart 甘特图
通过条状图来显示项目、进度和其他时间相关的系统进展的内在关系，随着时间进展的情况

第二章

1.What is the meaning of iteration?迭代的意义是什么?
In the framework of Agile Software Development , iteration is a short time frame which typically lasts one to four weeks. Each iteration includes all the tasks necessary to release the mini-increment of new functionality : planning, requirements analysis, design, coding, testing, and documentation.
在 敏捷软件开发 的框架下，迭代周期是一个通常为时一到四周的 短期时间段。 每个迭代周期包括发布一个新功能的增量所需的 一切任务 。这些任务包括：计划、需求分析、设计、编码、测试和文档编制。
2.What is the meaning of project development plan?项目开发计划的意义是什么?
The purpose of the Project Development Plan is to define and establish the management strategy for achieving the goals of the project. The project development plan is used to: guide project execution, document project planning assumptions and decisions , facilitate communication among stake-holders, define key management reviews as to content, extent, and timing, and provide a baseline for progress measurement and project.
项目开发计划的目的是定义和建立管理策略，以实现项目的目标。项目开发计划用于:指导项目执行，记录项目计划假设和决策，促进利益相关者之间的沟通，定义关键管理评审内容、范围、和时间，为进度度量和项目提供基线。
项目开发计划的目的是定义和建立达成项目目标的管理策略。
3.SDK和API的差别
SDK相当于开发集成工具环境，API就是数据接口。在SDK环境下调用API数据
SDK对指定功能的实现是完全隐藏的，只需要调用接口函数，传进去特定的值即可实现提供商制定好的功能
API可能会包括许多个接口函数，这些函数需要按照提供的规则进行顺序调用，所以在调用不同函数的期间可以插入自己定制化的代码。
4.Project development plan
guide project execution；指导项目执行;
document project planning assumptions and decisions；记录项目计划的假设和决定
facilitate communication among stake-holders;促进利益相关者之间的沟通
define key management reviews as to content, extent, and timing;定义关键管理评审的内容、范围和时间;
provide a baseline for progress measurement and project.
为进度度量和项目提供基线。
5.What does a project plan describe?项目计划描述了什么?
Interim and final deliverables the project will deliver;
Managerial and technical processes necessary to develop the project deliverables;
Resources required to deliver the project deliverables;
Additional plans required to support the project
项目将交付的中期和最终交付成果;
制定项目可交付成果所需的管理和技术过程;
交付项目可交付成果所需的资源;
需要额外的计划来支持这个项目
6.How many phases are mentioned according to project phase plan? What’s the major milestone that marks the completion of each phase?
Four phases and their major milestones:
Inception phase — Business Case Review Milestone
Elaboration phase — Architectural Prototype Milestone
Construction phase — Initial Operational Capability Milestone
Transition phase — R2.0 Release Milestone
四个阶段及其主要里程碑:
初始阶段——业务案例评审里程碑
精化阶段——架构原型里程碑
构建阶段——初始操作能力里程碑
产品化阶段——R2.0发布里程碑

第三章

1.What is the meaning of router?
A router is a computer networking device that forwards data packets across an internetwork toward their destinations , through a process known as routing . Routing occurs at layer 3 ( the Network layer) of the OSI seven-layer model. Routing is most commonly associated with the Internet Protocol, although other less-popular routed protocols remain in use.
路由器是一种计算机网络设备 。通过互联网络，它以一种被称为 路由选择 的方法将数据包发送到它们的 目的地 。 路由选择作用于OSI七层模型中的第三层——网络层。路由选择常常同互联网协议联系在一起，虽然还存在其他一些不太流行的路由协议
2.What is the meaning of geocode?
A location in geographic space converted into computer readable form. This usually means making a digital record of the point’s coordinates.
地理代码一个计算机可读的地理空间位置代码。这通常是指将一个点的坐标数字化。
3.IMEI国际移动设备识别码（International Mobile Equipment Identity number）
俗称“手机串号”、“手机串码”、“手机序列号”，用于在GSM移动网络中识别每一部独立的手机，相当于手机的身份证号码。
大部分终端设备中都可以通过拨号输入*#06#来查询
IMEI是GSM网络制式专用的身份编码
MEID是CDMA网络制式专用的身份识别编码
4.GPRS（General Packet Radio Service通用分组无线服务技术）
是GSM移动电话用户可用的一种移动数据业务，属于第二代移动通信中的数据传输技术。分组交换技术是计算机网络上一项重要的数据传输技术。
5.TCP（Transmission Control Protocol 传输控制协议）
是一种面向连接的、可靠的、基于字节流的传输层通信协议
TCP支持的应用协议：
FTP 文件传送、RLogin 远程登录、SMTP POP3 电子邮件等。
用户数据报协议（UDP）是同一层内另一个重要的传输协议。
6.三类文档目的及意义
商业需求文档（BRD）
进行市场和用户调研、竞品分析，定义用户需求，规划产品轮廓，描述功能点
目的：对产品进行市场层面的全方位阐述，帮助研发产品经理进行产品定位和规划
市场需求文档（MRD）
进行市场和用户调研、竞品分析，定义用户需求，规划产品轮廓，描述功能点
目的：对产品进行市场层面的全方位阐述，帮助研发产品经理进行产品定位和规划
产品需求文档（PRD）
业务规则，制定产品流程、功能描述、界面示意和性能指标
目的：对MRD的内容进行指标化和技术化， 将产品从概念转化为文字/图片
产品原型（prototype）
7.ACK(Acknowledgement，命令正确应答字符）
8.XML（Extensible Markup Language，扩展性标识语言）
XML为了便于不同应用、不同平台之间的数据共享和通信，是一种跨平台的，与软、硬件无关的，处理与传输信息的工具
具体点的作用为：
(1)可作为一种简单的数据库，存储并检索数据；
(2)传输约定格式的文件；
(3)做软件的配置文件。
XML不会做任何事情。XML被设计用来结构化、存储以及传输信息。
XML被设计用来描述数据，其焦点是数据的内容
HTML（超文本标记语言）被设计用来显示数据，其焦点是数据的外观。
xml不是要来取代html的，是对html的补充，用来与html协同工作的语言
9.JMS（Java Message Service，Java消息服务）
JMS是两个应用程序之间进行异步通信的API，它为标准消息协议和消息服务提供了一组通用接口
JMS是异步的，客户端获取消息的时候，不需要主动发送请求，消息会自动发送给可用的客户端
支持两种模型：
点对点或队列模型：发送者、接受者、消息队列
发布/订阅消息传递模型：发布者、接受者、主题

第四章

1.What is the meaning of design & architecture? 软件设计与架构的意义是什么
Software Design& Architecture is how the requirements are met. The requirements specify what properties are needed and software design specifies how these properties are implemented from more general and abstract point of view than the actual implementation.
软件设计与架构是描述如何满足需求的。需求指明需要哪些属性，而软件设计从一个比实际编码更加一般和抽象的角度指明这些属性将如何被实现。
2.Designing a software‘s ’process 设计一个软件的过程
Designing a software is a process which takes requirements as input and produces a description of the architecture of software product that can be easily turned into.
设计一个软件就是这样一个过程：它把需求当做输入，并产生一个便于转换成代码的软件产品构架说明。
3.What does a design specification include?
(1)This includes the architectural features of the system down through details of what operations each code module will perform and database layout .
包括系统的体系结构功能，详细说明每个代码模块将执行的操作和数据库布局。
(2) It also shows how the use cases promised in the SRS will be implemented in the system using this design.
它还显示了如何使用此设计在系统中实现SRS中承诺的用例。
4.UML(Unified Modeling Language统一建模语言)
统一建模语言或标准建模语言， Unified Modeling Language的缩写。
是国际对象管理组织OMG制定的一个通用的、可视化建模语言标准，可以用来描述(specify)、可视化(visualize)、构造(construct)和记载(document)软件密集型系统的各种工件。
UML可帮助我们做软件需求分析和软件设计的工作

第五章

1.Why teamwork? Because it improves
Quality,、Flexibility,、Coordination,、Satisfaction and Development,
Productivity/Cost.
质量、灵活性、协调、满意度和发展、效率/成本。
2.Nature of Teamwork团队合作的性质
Teams aren’t just groups of people.
Teams don’t just happen. You have to build them.
Teamwork means people cooperating to meet common goals.
团队不仅仅是一群人。
团队不会凭空出现。你必须建造它们。
团队合作是指人们为了达到共同的目标而合作。
3.Benefits of Teamwork团队合作的好处
Enhances success、Promotes creativity、Builds synergy、Promotes trade-offs and solves problems、Is fun and reduces tension and conflicts、Helps both large corporations and small groups、Responds to the challenge of change.
提高成功、促进创造力、构建协同作用、促进权衡和解决问题、是乐趣和减少紧张和冲突、帮助大团队和小团队、响应变化的挑战。
4.What is the meaning of architecture design?架构设计意义是什么？
The design process for identifying the sub-systems making up a system and the framework for sub-system control and communication is architectural design. Its objective is to establish the overall structure of a software system.
As an early stage of the system design process, architectural design represents the link between specification and design processes, identifying major system components and their communications.
架构设计是指确定构成系统的各子系统及其控制和通信架构的设计过程。其目标是构建软件系统的整体架构。作为系统设计过程的一个早期阶段，架构设计连接了需求说明和设计过程，说明了主要的系统组件及其通信。
5.What is the meaning of detailed design?详细设计的意义是什么
The software detailed design is developed based on the software architecture. It is the detailed breakdown of all components, including precise information about data structures, objects and storage. It may be expressed using some program descriptive language.
详细设计是在软件架构的基础上进行的。它是对所有组件的详细分解，包括了数据结构、对象和存储的详细信息，也可以通过程序描述语言表述。
6.How many types of UML diagrams are mentioned in the two specifications? What are they?
There are five types.
They are class diagram, use case diagram, sequence diagram, statechart diagram and component diagram.

第六章

1.Code documentation
Also known as software documentation, it is a written text that accompanies computer software. It either explains how the software operates or how to use the software. In software development, code alone is insufficient. There must be some text along with it to describe various aspects of its intended operation. This documentation can be highly technical and is mainly used to define and explain the APIs, data structures and algorithms.
它是计算机软件附带的书面文本。它要么解释软件如何运行，要么解释如何使用软件。在软件开发中，仅代码是不够的。必须随附一些文本来描述其各个方面的预期操作。此文档可以是高度技术性的，主要用于定义和解释API、数据结构和算法
2.Source documentation
Source documentation, also known as citation, is a credit or reference to another document or source that you use to create an intellectual work. A citation provides the information that is needed to find the cited source. It helps back up your work, and gives credit to others for their ideas. Others for their ideas. Otherwise you run the risk of plagiarism—of taking credit for ideas that are not your own.
来源文档，也称为引文，是对另一个文档或源的引用，您可以使用它来创建脑力劳动的作品。引文提供了查找被引源所需的信息。它有助于支撑你的作品，并将别人的想法归功于自己。否则，你将冒着剽窃他人观点的风险
3.思考这几个问题
What is software documentation used for?
Who is responsible for creating software documentation?
How is software documentation created?
软件文档的用途是什么?
谁负责创建软件文档?
如何创建软件文档?
Code documentation is what most programmers mean when using the term software documentation. When creating software, code alone is insufficient. There must be some text along with it to describe various aspects of its intended operation. This documentation is usually embedded within the source code itself so it is readily accessible to anyone who may be traversing it.
His writing can be highly technical and is mainly used to define and explain the APIs, data structures and algorithms. For example, one might use this documentation to explain that the variable m_name refers to the first and last names of a person. It is important for the code documents to be thorough, but not so verbose that to becomes difficult to maintain them.
Often, tools such as doxygen, javadoc, ROBODoc,POD or TwinText can be used to auto-generate the code documents—that is— they extract the comments from the source code and create reference manuals in such forms as text or HTML files. Code documents are often organized into a reference guide style, allowing a programmer to quickly look up an arbitrary function or class.
Many programmers really like the idea of auto-generating documentation for various reasons. For example, because it is extracted from the source code itself ( for example, through comments), the programmer can write it while referring to his code, and can use the same tools with which he created the source code to make the documentation. This makes it much easier to keep documentation up-to-date.
Of course, a downside is that only programmers can edit this kind of documentation, and it depends on them to refresh the output ( for example, by running a cron job to update the documents nightly). Some would characterize this as a pro rather than a con.
代码文档是大多数程序员在使用软件文档这个术语时的意思。在创建软件时，仅靠代码是不够的。必须有一些文本与它一起来描述其预期操作的各个方面。此文档通常嵌入在源代码本身中，因此任何人都可以很容易地访问它。
他的作品技术性很强，主要用于定义和解释api、数据结构和算法。例如，可以使用这个文档解释变量m_name引用一个人的姓和名。代码文档的全面是很重要的，但不要过于冗长以至于难于维护它们。
通常，可以使用doxygen、javadoc、ROBODoc、POD或TwinText等工具自动生成代码文档——也就是说，它们从源代码中提取注释，并以文本或HTML文件的形式创建参考手册。代码文档通常组织成参考指南样式，允许程序员快速查找任意函数或类。
出于各种原因，许多程序员确实喜欢自动生成文档的想法。例如，因为它是从源代码本身提取的(例如，通过注释)，程序员可以在引用代码时编写它，并且可以使用与创建源代码时相同的工具来编写文档。这使得更新文档变得更加容易。
当然，缺点是只有程序员可以编辑这类文档，并且依赖于他们来刷新输出(例如，通过运行cron作业来每晚更新文档)。有些人认为这是好事而不是坏事。
4.Types depending on the information type of the software documentation类型取决于软件文档的信息类型 信息上区分
Basic information about the software’s underlying concepts; often also additional Basic domain knowledge that readers are lacking
Procedures (task descriptions)
Reference information to look up, such as information on particular parameters
有关软件基本概念的基本资料;通常还会增加一些读者缺乏的基本领域知识
过程(任务描述)
要查找的参考信息，如关于特定参数的信息
5.Types depending on the medium of the software documentation 类型取决于软件文档的媒介 媒介上区分
printed or printable manuals with a fixed order of pages (including PDF)
online documentation (online help) as hypertext, usually HTML
有固定页数顺序的印刷或可印刷手册(包括PDF)
在线文档(在线帮助)作为超文本，通常是HTML
5.How many styles of implementation comments are mentioned here? What are they?这里提到了多少种类型的实现注释?他们是什么?
Block Comments、Single-Line Comments、Trailing Comments、Out Comments
块注释、单行注释、批注、输出注释

第七章

1.Critical path（关键路径）
In project management, a critical path is the sequence of project network terminal elements with the longest overall duration, determining the shortest time to complete the project.
在项目管理中，关键路径是指网络终端元素的元素的序列，该序列上最长的持续时间决定了整个项目的最短完成时间。
Critical path（关键路径）
The duration of the critical path determines the duration of the entire project. Any delay of a terminal element on the critical path directly impacts the planned project completion date.
关键路径的持续时间，决定了整个项目的持续时间。任何关键路径上的终端元素的延迟将直接影响项目的预期完成时间。
2.Project work plan
A project work plan is the schedule of tasks, durations ,and dates to accomplish a project. A high level work plan shows the standard deliverables for the process, and a detailed project plan shows the project-specific tasks.
项目工作计划是完成项目的任务、持续时间和日期的进度表。高级工作计划显示流程的标准可交付成果，详细的项目计划显示具体任务。
A project work plan provides a plan of what has to be done, how the work will be organized and who will do it. This will require a calendar or chart that provides a schedule of work outlining the project goals, objectives, strategies, and evaluations.
项目工作计划提供了必须做什么、如何组织工作以及由谁来做的计划。这将需要一个日历或图表，提供概述 项目目的、目标、策略和评估的工作进度表。
The purpose of the project work plan is to describe how the work of the project will be carried out and the goals of the program accomplished. This includes describing the project management; data collection and management; data quality assessment, validation, and usability; and data analysis process.
项目工作计划的目的是描述项目的工作将如何进行以及项目的目标是如何完成的。这包括描述项目管理;数据收集和管理;数据质量评估、验证和可用性;和数据分析过程。

第八章

1.Unit testing单元测试
In computer programming, a unit test is a method of testing the correctness of a particular module of source code. The goal of unit testing is to isolate each part of the program and show that the individual parts are correct.
在计算机程序设计中，单元测试是测试源代码特定模块正确性的一种方法。单元测试的目标是隔离程序的每个部分，并显示各个部分是正确的。
It provides a written contract that the piece must satisfy. Test cases are written for every nontrivial function or method in the module so that each test case is separate from the others if possible. This type of testing is mostly done by the developers.
提供一份满足条款的书面合同。测试用例是为模块中每个有意义的函数或方法编写的，因此如果可能的话，每个测试用例都是独立的。这种类型的测试主要由开发人员完成。
2.软件测试一般分为4个阶段：
单元测试、集成测试、系统测试、验收测试。
一、单元测试Unit Testing
单元测试是对软件中的最小可验证单元进行检查和验证。比如对Java中的类和方法的测试。粒度最小，一般由开发小组采用白盒方式来测试，主要测试单元是否符合“设计”。
二、集成测试Integrated Testing
集成测试是在单元测试的基础上，把软件单元按照软件概要设计规格说明的规格要求，组装成模块、子系统或系统的过程中各部分工作是否达到或实现相应技术指标及要求。
三、系统测试 System Testing
系统测试把已经经过确认的软件纳入实际运行环境中，与其它系统成份组合在一起进行测试。粒度最大，一般由独立测试小组采用黑盒方式来测试，主要测试系统是否符合“需求规格说明书”。
四、验收测试 acceptance testing
是针对用户需求、业务流程进行的正式的测试，以确定系统是否满足验收标准，由用户、客户或其他授权机构决定是否接受系统。主要区别是测试人员不同，验收测试由用户执行。
3.什么是 白盒测试？
主要应用于单元测试阶段，主要是对代码级别的测试，针对程序内部的逻辑结构。测试的手段有：语句覆盖、判定覆盖、条件覆盖、路径覆盖和条件组合覆盖。
4.什么是 黑盒测试？
不考虑程序内部结构和逻辑结构，主要是测试系统的功能是否满足“需求规格说明书”。一般会有一个输入值和一个输出值，和期望值做比较。黑盒测试也被称为功能测试或数据驱动测试，它是通过测试来检测每个功能是否都能正常使用。
5.Test case测试用例
In software engineering, a test case is a set of conditions or variables under which a tester will determine if a requirement upon an application is partially or fully satisfied. It may take many test cases to determine that a requirement is fully satisfied.
在软件工程中，测试用例是一组条件或变量，在这些条件或变量下，测试人员将确定应用程序上的需求是部分满足还是完全满足。可能需要许多测试用例来确定需求是否完全满足。
In software engineering, a test case is a set of conditions or variables under which a tester will determine if a requirement upon an application is partially or fully satisfied. It may take many test cases to determine that a requirement is fully satisfied.
在软件工程中，测试用例是一组条件或变量，在这些条件或变量下，测试人员将确定应用程序上的需求是部分满足还是完全满足。可能需要许多测试用例来确定需求是否完全满足。
6.Unit test plan单元测试计划
A unit test plan is a document describing the unit testing process in terms of the features to be tested, pass/fail criteria and testing approaches, resource requirements and schedules.
单元测试计划是一份描述单元测试过程的文档，它根据要测试的特性、通过/失败标准和测试方法、资源需求和进度表进行描述。
7.Unit testing单元测试
Unit testing is the process of testing the individual sub-programs, sub-routines or procedures in a program.
Unit testing involves testing the smallest possible unit of an application. Unit testing is recognized as an essential component of the software development process. Unit testing practitioners enjoy such benefits as easier error detection, which has the very desirable end result of increasing software quality while reducing development time and cost. Easier error reduction leads to reduced development time, effort, and cost, because less time and resources are consumed in finding and fixing errors.
单元测试是测试程序中单个子程序、子例程或过程的过程。
单元测试包括测试应用程序的最小单元。单元测试被认为是软件开发过程中的一个重要组成部分。单元测试实践者享有这样的好处，如更容易的错误检测，这在增加软件质量的同时减少了开发时间和成本，这是非常理想的最终结果。更容易地减少错误会减少开发时间、工作量和成本，因为在查找和修复错误方面消耗的时间和资源更少。
8.How many types of testing are there in unit testing?
In addition, unit testing involves several complex types of testing:
White box testing: ensures that code is constructed properly and does not contain any hidden weaknesses.白盒测试:确保代码构造正确，不包含任何隐藏的弱点。
Black box testing: ensures that code functions in the way that it is intended to function.黑盒测试:确保代码按照预期的方式运行。
Regression testing: ensures that modifications do not introduce errors into previously correct code.回归测试:确保修改不会将错误引入到以前正确的代码中。
9.一些缩写和全称

第九章

1.Risk风险
Schedule时间表
Technical技术
Management管理
Personnel人员
Requirements需求
2.Documentation文档
Test plan测试计划
Test case测试用例
Test case review测试用例评审
Requirements validation matrix需求验证矩阵
Bug reports错误报告
Final test summary report最终试验总结报告
3.What kinds of risks may the test team encounter throughout the testing phase?
There are schedule, technical, management, personnel and requirement risks.
测试团队在整个测试阶段可能会遇到什么样的风险?
进度风险、技术风险、管理风险、人员风险和需求风险。
4.Test plan
Test plan is a document which defines scope, approach, resource and schedule of a testing activity. It has complete information of what is required to execute the test.
测试计划是定义测试活动的范围、方法、资源和时间表的文档。它包含执行测试所需的完整信息。
A test plan is a flexible document: it can be continually modified to conform to changes during the project.
测试计划是一个灵活的文档:它可以不断地修改以适应项目期间的更改。
5.Testing phase
In many software engineering methodologies, the testing phase is a separate phase which is performed by a different team after the implementation is completed. It is a process used to help identify the correctness, completeness and quality of developed computer software.
在许多软件工程方法中，测试阶段是一个独立的阶段，在实现完成后由不同的团队执行。它是一个用来帮助识别所开发的计算机软件的正确性、完整性和质量的过程。
With that in mind, testing can never completely establish the correctness of computer software. Only the process of formal verification can prove that there are no defects.
考虑到这一点，测试永远不能完全确定计算机软件的正确性。只有通过形式验证的过程才能证明不存在缺陷。
6.Formal Verification（形式验证)
在计算机硬件（特别是集成电路）和软件系统的设计过程中，形式验证的含义是根据某个或某些形式规范或属性，使用数学的方法证明其正确性或非正确性。
形式验证是一个系统性的过程，将使用数学推理来验证设计意图（指标）在实现(RTL)中是否得以贯彻。
主要应用于昂贵的航天器材的操作系统、危险的医疗设备的程序之中。
7.Bug report
Writing a bug report is the first step in getting a bug fixed. The aim of a bug report is to enable the programmers to see how the program fails under certain conditions.
编写bug报告是修复bug的第一步。bug报告的目的是使程序员能够看到程序在某些条件下是如何失败的。
A bug report gives them careful and detailed instructions on how to make it fail. Finding the bug is at least half the work.
Bug报告会给他们详细的指导，告诉他们如何使它失败。找到bug至少完成了一半的工作。
8.workaround
A workaround is a method, sometimes used temporarily, for bypassing a recognized problem when the usual or planned method isn’t working. A workaround is typically a temporary fix that implies that a genuine solution to the problem is needed.
变通方法是一种方法，有时是临时使用的，用于在常规或计划的方法不起作用时绕过已识别的问题。变通方法通常是一个临时的解决方案，它意味着需要一个真正的问题解决方案。
They are considered brittle in that they will not respond well to further pressure from a system beyond the original design. In implementing a workaround it is important to flag the change so as to later implement a proper solution.
他们被认为是脆弱的，因为当之后的压力超过系统原设计时，变通方法无法做出合适的响应。在实现解决方案时，标记更改很重要，以便以后实现正确的解决方案。
9.What is a Software Test Plan?什么是软件测试计划?
It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.
明确正在测试的项目、要测试的特性、要执行的测试任务、每个任务的负责人，以及与计划相关的风险。
10.Why do we need Test Plan?
A software test plan is a document describing the scope, approaches, resources, and schedule of intended testing activities.
测试计划的目的是：规定测试活动的范围、方法、资源和进度。
11.Beta test
α测试是指软件开发公司组织内部人员模拟各类用户对即将面市软件产品（称为α版本）进行测试，试图发现错误并修正。
β测试是由软件的多个用户在实际使用环境下进行的测试，这些用户返回有关错误信息给开发者。测试时，开发者通常不在测试现场。
12.Control procedures
reviews评审
bug review meetings缺陷评审会议
change request变更请求
bug reporting bug报告
bug report form缺陷报告表