The project workbook is not so much a separate document as it is a structure imposed on the documents that the project will be producing anyway.

All the documents of the project need to be part of this ( 1 ). This includes objectives ,external specifications , interface specifications , technical standards , internal specifications and administrative memoranda（备忘录）.

Technical prose is almost immortal. If one examines the genealogy ( Ff ) of a customer manual for a piece of hardware or software , one can trace not only the ideas , but also many of the very sentences and paragraphs back to the first ( 2 ) proposing the product or explaining the first design. For the technical writer, the paste-pot is as mighty as the pen.

Since this is so, and since tomorrow's product-quality manuals will grow from today’s memos, it is very important to get the structure of the documentation right. The early design of the project ( 3 ) ensures that the documentation structure itself is crafted, not haphazard. Moreover, the establishment of a structure molds later writing into segments that fit into that structure.

The second reason for the project workbook is control of the distribution of ( 4 ). The problem is not to restrict information, but to ensure that relevant information gets to all the people who need it.

The first step is to number all memoranda, so that ordered lists of titles are available and h worker can see if he has what he wants. The organization of the workbook goes well beyond this to establish a tree-structure of memoranda. The ( 5 ) allows distribution lists to be maintained by subtree, if that is desirable.

（1） A.structure     B.specification     C.standard     D.objective

（2） A.objective     B.memoranda     C.standard     D.specification

（3） A.title     B.list     C.workbook     D.quality

（4） A.product     B.manual     C.document     D.information

（5） A.list     B.document     C.tree-structure     D.number

参考答案：A、B、C、D、C

参考译文：

项目工作手册与其说是一个独立的文档，倒不如说它是一种加在文档上的一种结构，项目会按照项目工作手册来实施。 项目所有的文档都是项目工作手册的一部分，其中包括目标、外部说明、接口说明、技术标准、内部说明、以及管理备忘录。

技术文档是其中至关重要的部分。如果客户通过用户手册去搜寻硬件或软件的信息，他不止能找到简单的描述还能找到关于项目计划与初步设计方面的建议和解释。对于技术文档工程师来说糊锅跟笔一样重要。

鉴于项目质量手册出自出自于这些备忘录，那么建立正确的文档结构尤为重要。事先将项目工作手册设计好，可以确保文档的结构被精心制作而不是被粗制滥造。更进一步说文档结构的建立也给后续的书写工作提供一个模板。

再者，项目工作手册也能控制信息的分发，它不是严格限制分发而是把信息传递给需要它的人。 第一步要给所有备忘录进行编号，形成一个列表，工作手册再把这些备忘录建立一个树形结构。而且如果需要的话，可以使用树结构中的子树来维护发布列表。

Creating a clear map of where the project is going is an important first step. It lets you identify risks， clarify objectives， and determine if the project even makes sense. The only thing more important than the release plan is not to take it too seriously.

release planning is creating a game plan for your Web project ( 1 ) what you think you want your Web site to be. The plan is a guide for the content， design elements， and functionality of a Web site to be released to the public， to partners， or internally. It also ( 2 ) how long the project will take and how much it will cost. What the plan is not is a functional ( 3 ) that defines the project in detail or that produces a budget you can take to the bank.

Basically you use a release Plan to do an initial sanity check of the project's ( 4 ) and worthiness. Release Plans are useful road maps， but don't think of them as guides to the interstate road system. Instead， think of them as the ( 5 ) used by early explorers--half rumor and guess and half hope and expectation.

It's always a good idea to have a map of where a project is headed

（1） A.constructing     B.designing     C.implementing     D.outlining

（2） A.defines     B.calculates     C.estimates     D.knows

（3） A.specification     B.structure     C.requirement     D.implementation

（4） A.correctness     B.modifiability     C.feasibility     D.traceability

（5） A.navigators     B.maps     C.guidances     D.goals

参考答案：D、C、A、C、B

参考译文：

创建一个清晰的项目进行的地图是一个重要的第一步。它让你识别风险，明确日标，并确定项日是否有意义。唯—比发布计划更重要的是不要太认真。

发布计划正在为你的web项目创建一个游戏计划，概述你认为你想要得到什么样的网站。该计划指导将网站的内容，设计元素和功能发布给公众，合作伙伴，或内部。它还估算了项目将花费多长时间和资源。这个计划不是一个功能性的说明书——详细地定义了项目或者形成一个可以提交到银行的预算。基本上，你使用发布计划来对项目的可行性和价值进行初步的安全检查。发布计划是有用的路线图，但不要认为它们是州际公路系统的指南。相反，把它们看作是早期探险家使用的地图———半是传闻和猜测。—半是希望和期望。

有一个项目走向的地图总是一个好主意。

The development of the Semantic Web proceeds in steps, each step building a layer on top of another. The pragmatic justification for this approach is that it is easier to achieve ( 1 ) on small steps, whereas it is much harder to get everyone on board if too much is attempted. Usually there are several research groups moving in different directions; this ( 2 ) of ideas is a major driving force for scientific progress. However， from an engineering perspective there is a need to standardize. So, if most researchers agree on certain issues and disagree on others, it makes sense to fix the point of agreement. This way, even if the more ambitious research efforts should fai1， there wil1 be at least ( 3 ) positive outcomes.

Once a ( 4 ) has been established ， many more groups and companies will adopt it， instead of waiting to see which of the alternative research lines will be successful in the end. The nature of the Semantic

Web is such that companies and single users must build tools， add content，and use that content. We cannot wait until the full Semantic Web vision materializes-it may take another ten years for it to be realized to its full ( 5 ) （as envisioned today, of course）.

（1） A.conflicts     B.consensus     C.success     D.disagreement

（2） A.competition     B.agreement      C.cooperation     D.collaboration

（3） A.total     B.complete     C.partial      D.entire

（4） A.technology     B.standard     C.pattern     D.model

（5） A.area     B.goal     C.object     D.extent

参考答案：B、A、C、B、D

参考译文：

语义网络的发展是一步一步的，每一步都建立在之前的基础之上。选择这种方法的现实理由就是因为很容易对一小步达成一致，而如果想要一步到位就难得多。通常，很多研究组织都是从不同方向考虑的，这种思想的竞争的方式是科学进步的驱动力。然

而，从工程的角度来说是需要进行标准化的。因此，如果大多数研究者同意某个观点不同意另一个的时候，改正观点是有意义的。这样，即使再宏大的研究努力也会失败，可能会有局部的积极效果。

—日一个标准被建立，许多组织和企业都会采纳，而不是等待并查看其他研究线是否会获得成果。语义网络的性质就是让企业和单个用户必须构建工具，添加内容并使用。我们不会等着整个语义网络被物化——因为实现它的全部内容需要再过十年时间（当然是按照今天所设想）。

You are developing a server-side enterprise application. It must support a variety of different clients including desktop browsers , mobile browsers and native mobile applications. The application might also expose an API for 3rd parties to customer. It might also ( 1 ) with other applications via either web services or a message broker. The application handles requests（HTTP requests and messages）by executing business logic;accessing a database;exchanging messages with other systems;and returning a HTML / JSON / XML ( 2 ) . There are logical components corresponding to different functional areas of the application.

What's the application' s deployment architecture?

Define an architecture that structures the application as a set of ( 3 ) ，collaborating services. This approach corresponds to the Y-axis of the Scale Cube. Each service is;

Flighly maintainable and testable-enables rapid and frequent development and deployment.

Loosely coupled with other services-enables a team to work independently（the majority of time on their servicers）without being impouted by changes to other services and without affecting other services.

( 4 ) deployable-enable a team to deploy their services without having to cortdinate with other teams.

Capable of being developed by a small team-essential for high productivity by avoiding the high communication head of large teams.

Services ( 5 ) using either synchronous protocols such as HTTP/REST or a synchronous protocols

such as AMQP. Services can be developed and deployed independently of one another. Each service has its own database in order to be decoupled from other services. Data consistency between services is maintained using some particular pattern.

（1） A.integrate     B.Coordinate     C.cooperate     D.Communicate

（2） A.request     B.response     C.text     D.File

（3） A.loosely coupled     B.loosely cohesion     C.High coupled     D.Highly cohesion

（4） A.Dependently     B.Independently     C.Coordinately     D.Integratedly

（5） A.interoprate     B.coordinate     C.communicate     D.depend

参考答案：C、D、A、B、C

参考译文：

你们正在开发一个全方位的企业应用系统。它必须支持各种不同的客户机，包括桌面浏览器。移动浏览器和本地移动应用程序。应用程序还可以向客户公开第三方的API。它还可以通过web services或消息代理与其他应用程序协作。应用程序通过执行业务逻辑、访问数据库、与其他系统交换消息以及返回HTML /JSON/XML 响应 来处理请求（HTTP请求和消息）。它有一些逻辑组件对应于应用程序的不同功能区域。

那么这个应用程序有什么样的部署体系结构呢？

将应用程序的体系结构定义为一组松散耦合的协作服务集合，对应于Scale Cube的y轴伸缩。每个服务；

易于维护和测试———支持快速和频繁的开发和部署。

与其他服务的松散耦合——使团队能够独立工作（大部分时间在其服务器上），而不会受到对其他服务的更改的影响，也不会影响其他服务。

独立部署——允许团队部署他们的服务，而不必与其他团队协调。

能够被一个小团队开发，避免了大团队的高交流领导，这对于高生产力是至关重要的。

服务通信使用HTTP/REST等同步原协议或AMQP等同步协议。服务可以彼此独立地开发和部署。每个服务都有自己的数据库，以便与其他服务解耦。服务之间的数据一致性是使用某种特定的模式来维护的。

A project is a [temporary] ( 1 ) of unique, complex, and connected activities having one goal or purpose and that must be completed by a specific time, within budget, and according to ( 2 ).

Project management is the process of scoping, planning, staffing，organizing, directing, and controlling the development of a（n） ( 3 ) system at a minimum cost within a specified time frame.

For any systems development project, effective project management is necessary to ensure that the project meets the ( 4 ) , is developed within an acceptable budget, and fulfills customer expectations and specifications. Project management is a process that starts at the beginning of a project, extends through a project, and doesn’t culminate until the project is completed.

The prerequisite for good project management is a well-defined system development process. Process management is an ongoing activity that documents, manages the use of, and improves an organization’s chosen methodology (the “process”)for system development. Process management is concerned with the activities, deliverables, and quality standards to be applied to ( 5 ) project ( s ).

（1） A.task     B.work     C.sequence     D.activity

（2） A.specifications      B.rules     C.estimates     D.designs

（3） A.perfect     B.acceptable     C.controlled     D.completed

（4） A.deadline     B.specification     C.expectation     D.requirement

（5） A.a single     B.a particular     C.some     D.all

参考答案：C、A、B、A、D

参考译文：

一个项目是一个（临时）独特的、复杂的、相关的活动序列，它有一个目标或目的，必须在特定的时间完成，在预算之内，并且遵循相关说明书。

项目管理是针对在有限时间内以最低成本完成—个可接受系统的开发，其范围.计划.人员.组织，指导和控制的过程。

对于任何系统开发项目而言，有效的项目管理是必要的，以确保该项目在工期截止前，能够以一个可接受的预算开发和实现，并且符合用户的期望和规范。

项目管理是一个从项目开始，到项目结束，贯穿整个项目，直到项目完成才结束的过程。

良好的项目管理的先决条件是定义良好的系统开发过程。过程管理是一种持续的活动，它记录、管理和改进组织为系统开发所选择的方法（"过程"）。流程管理涉及的活动、可交付成果和质量标准适用于所有的项目。