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

參考譯文：

項(xiàng)目工作手冊(cè)與其說(shuō)是一個(gè)獨(dú)立的文檔，倒不如說(shuō)它是一種加在文檔上的一種結(jié)構(gòu)，項(xiàng)目會(huì)按照項(xiàng)目工作手冊(cè)來(lái)實(shí)施。 項(xiàng)目所有的文檔都是項(xiàng)目工作手冊(cè)的一部分，其中包括目標(biāo)、外部說(shuō)明、接口說(shuō)明、技術(shù)標(biāo)準(zhǔn)、內(nèi)部說(shuō)明、以及管理備忘錄。

技術(shù)文檔是其中至關(guān)重要的部分。如果客戶通過(guò)用戶手冊(cè)去搜尋硬件或軟件的信息，他不止能找到簡(jiǎn)單的描述還能找到關(guān)于項(xiàng)目計(jì)劃與初步設(shè)計(jì)方面的建議和解釋。對(duì)于技術(shù)文檔工程師來(lái)說(shuō)糊鍋跟筆一樣重要。

鑒于項(xiàng)目質(zhì)量手冊(cè)出自出自于這些備忘錄，那么建立正確的文檔結(jié)構(gòu)尤為重要。事先將項(xiàng)目工作手冊(cè)設(shè)計(jì)好，可以確保文檔的結(jié)構(gòu)被精心制作而不是被粗制濫造。更進(jìn)一步說(shuō)文檔結(jié)構(gòu)的建立也給后續(xù)的書寫工作提供一個(gè)模板。

再者，項(xiàng)目工作手冊(cè)也能控制信息的分發(fā)，它不是嚴(yán)格限制分發(fā)而是把信息傳遞給需要它的人。 第一步要給所有備忘錄進(jìn)行編號(hào)，形成一個(gè)列表，工作手冊(cè)再把這些備忘錄建立一個(gè)樹(shù)形結(jié)構(gòu)。而且如果需要的話，可以使用樹(shù)結(jié)構(gòu)中的子樹(shù)來(lái)維護(hù)發(fā)布列表。

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

參考譯文：

創(chuàng)建一個(gè)清晰的項(xiàng)目進(jìn)行的地圖是一個(gè)重要的第一步。它讓你識(shí)別風(fēng)險(xiǎn)，明確日標(biāo)，并確定項(xiàng)日是否有意義。唯—比發(fā)布計(jì)劃更重要的是不要太認(rèn)真。

發(fā)布計(jì)劃正在為你的web項(xiàng)目創(chuàng)建一個(gè)游戲計(jì)劃，概述你認(rèn)為你想要得到什么樣的網(wǎng)站。該計(jì)劃指導(dǎo)將網(wǎng)站的內(nèi)容，設(shè)計(jì)元素和功能發(fā)布給公眾，合作伙伴，或內(nèi)部。它還估算了項(xiàng)目將花費(fèi)多長(zhǎng)時(shí)間和資源。這個(gè)計(jì)劃不是一個(gè)功能性的說(shuō)明書——詳細(xì)地定義了項(xiàng)目或者形成一個(gè)可以提交到銀行的預(yù)算。基本上，你使用發(fā)布計(jì)劃來(lái)對(duì)項(xiàng)目的可行性和價(jià)值進(jìn)行初步的安全檢查。發(fā)布計(jì)劃是有用的路線圖，但不要認(rèn)為它們是州際公路系統(tǒng)的指南。相反，把它們看作是早期探險(xiǎn)家使用的地圖———半是傳聞和猜測(cè)?！胧窍Ｍ推谕?。

有一個(gè)項(xiàng)目走向的地圖總是一個(gè)好主意。

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

參考譯文：

語(yǔ)義網(wǎng)絡(luò)的發(fā)展是一步一步的，每一步都建立在之前的基礎(chǔ)之上。選擇這種方法的現(xiàn)實(shí)理由就是因?yàn)楹苋菀讓?duì)一小步達(dá)成一致，而如果想要一步到位就難得多。通常，很多研究組織都是從不同方向考慮的，這種思想的競(jìng)爭(zhēng)的方式是科學(xué)進(jìn)步的驅(qū)動(dòng)力。然

而，從工程的角度來(lái)說(shuō)是需要進(jìn)行標(biāo)準(zhǔn)化的。因此，如果大多數(shù)研究者同意某個(gè)觀點(diǎn)不同意另一個(gè)的時(shí)候，改正觀點(diǎn)是有意義的。這樣，即使再宏大的研究努力也會(huì)失敗，可能會(huì)有局部的積極效果。

—日一個(gè)標(biāo)準(zhǔn)被建立，許多組織和企業(yè)都會(huì)采納，而不是等待并查看其他研究線是否會(huì)獲得成果。語(yǔ)義網(wǎng)絡(luò)的性質(zhì)就是讓企業(yè)和單個(gè)用戶必須構(gòu)建工具，添加內(nèi)容并使用。我們不會(huì)等著整個(gè)語(yǔ)義網(wǎng)絡(luò)被物化——因?yàn)閷?shí)現(xiàn)它的全部?jī)?nèi)容需要再過(guò)十年時(shí)間（當(dāng)然是按照今天所設(shè)想）。

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

參考譯文：

你們正在開(kāi)發(fā)一個(gè)全方位的企業(yè)應(yīng)用系統(tǒng)。它必須支持各種不同的客戶機(jī)，包括桌面瀏覽器。移動(dòng)瀏覽器和本地移動(dòng)應(yīng)用程序。應(yīng)用程序還可以向客戶公開(kāi)第三方的API。它還可以通過(guò)web services或消息代理與其他應(yīng)用程序協(xié)作。應(yīng)用程序通過(guò)執(zhí)行業(yè)務(wù)邏輯、訪問(wèn)數(shù)據(jù)庫(kù)、與其他系統(tǒng)交換消息以及返回HTML /JSON/XML 響應(yīng) 來(lái)處理請(qǐng)求（HTTP請(qǐng)求和消息）。它有一些邏輯組件對(duì)應(yīng)于應(yīng)用程序的不同功能區(qū)域。

那么這個(gè)應(yīng)用程序有什么樣的部署體系結(jié)構(gòu)呢？

將應(yīng)用程序的體系結(jié)構(gòu)定義為一組松散耦合的協(xié)作服務(wù)集合，對(duì)應(yīng)于Scale Cube的y軸伸縮。每個(gè)服務(wù)；

易于維護(hù)和測(cè)試———支持快速和頻繁的開(kāi)發(fā)和部署。

與其他服務(wù)的松散耦合——使團(tuán)隊(duì)能夠獨(dú)立工作（大部分時(shí)間在其服務(wù)器上），而不會(huì)受到對(duì)其他服務(wù)的更改的影響，也不會(huì)影響其他服務(wù)。

獨(dú)立部署——允許團(tuán)隊(duì)部署他們的服務(wù)，而不必與其他團(tuán)隊(duì)協(xié)調(diào)。

能夠被一個(gè)小團(tuán)隊(duì)開(kāi)發(fā)，避免了大團(tuán)隊(duì)的高交流領(lǐng)導(dǎo)，這對(duì)于高生產(chǎn)力是至關(guān)重要的。

服務(wù)通信使用HTTP/REST等同步原協(xié)議或AMQP等同步協(xié)議。服務(wù)可以彼此獨(dú)立地開(kāi)發(fā)和部署。每個(gè)服務(wù)都有自己的數(shù)據(jù)庫(kù)，以便與其他服務(wù)解耦。服務(wù)之間的數(shù)據(jù)一致性是使用某種特定的模式來(lái)維護(hù)的。

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

參考譯文：

一個(gè)項(xiàng)目是一個(gè)（臨時(shí)）獨(dú)特的、復(fù)雜的、相關(guān)的活動(dòng)序列，它有一個(gè)目標(biāo)或目的，必須在特定的時(shí)間完成，在預(yù)算之內(nèi)，并且遵循相關(guān)說(shuō)明書。

項(xiàng)目管理是針對(duì)在有限時(shí)間內(nèi)以最低成本完成—個(gè)可接受系統(tǒng)的開(kāi)發(fā)，其范圍.計(jì)劃.人員.組織，指導(dǎo)和控制的過(guò)程。

對(duì)于任何系統(tǒng)開(kāi)發(fā)項(xiàng)目而言，有效的項(xiàng)目管理是必要的，以確保該項(xiàng)目在工期截止前，能夠以一個(gè)可接受的預(yù)算開(kāi)發(fā)和實(shí)現(xiàn)，并且符合用戶的期望和規(guī)范。

項(xiàng)目管理是一個(gè)從項(xiàng)目開(kāi)始，到項(xiàng)目結(jié)束，貫穿整個(gè)項(xiàng)目，直到項(xiàng)目完成才結(jié)束的過(guò)程。

良好的項(xiàng)目管理的先決條件是定義良好的系統(tǒng)開(kāi)發(fā)過(guò)程。過(guò)程管理是一種持續(xù)的活動(dòng)，它記錄、管理和改進(jìn)組織為系統(tǒng)開(kāi)發(fā)所選擇的方法（"過(guò)程"）。流程管理涉及的活動(dòng)、可交付成果和質(zhì)量標(biāo)準(zhǔn)適用于所有的項(xiàng)目。