2011年上半年上午卷
Ravi, like many project (71)
m
a
n
a
g
e
r
s
\color{red}{managers }
managers, had stdied the waterfall model of software development as the primary software life-cycle (72)
p
r
o
c
e
s
s
\color{red}{process }
process. He was all set to use it for an upcoming project, his first assignment. However, Ravi found that the waterfall model could not be used because the customer wanted the software delivered in stages, something that implied that the system had to be delivered and built in (73)
p
a
r
t
s
\color{red}{parts }
parts and not as (74)
a
\color{red}{a}
a
w
h
o
l
e
\color{red}{whole}
whole.
The situation in many other projects is not very different. The real wold rarely presents a porblem in which a standard process, or the process used in a previous project, is the best choice. To be the most suitable, an existing process must be (75)
t
a
i
l
o
r
e
d
\color{red}{tailored }
tailored to the new problem. A development process, even after tailoring, generally cannot handle change requests. To accommodate change requests without losing control of the project, you must supplement the development process with a requirement change management process.
与许多项目（71）经理一样，Ravi将软件开发的瀑布模型作为主要的软件生命周期（72）过程。 他已准备好将它用于即将开展的项目，这是他的第一个任务。 然而，Ravi发现瀑布模型无法使用，因为客户希望分阶段交付软件，这意味着系统必须交付和内置（73）部分而不是（74）整体。
许多其他项目的情况并没有太大差异。 真正的世界很少会出现一个问题，在这个问题中，标准流程或之前项目中使用的流程是最佳选择。 为了使其成为最合适的，现有流程必须针对新问题量身定制。 即使在剪裁之后，开发过程通常也无法处理变更请求。 为了适应变更请求而不失去对项目的控制，您必须通过需求变更管理流程来补充开发过程。
(71)
A. customers 顾客
B.
m
a
n
a
g
e
r
s
\color{red}{managers }
managers 经理
C. users 用户
D. administrators 管理员
(72)
A. activity 活动
B. procedure 程序
C.
p
r
o
c
e
s
s
\color{red}{process }
process 处理
D. progress 进展
(73)
A.
p
a
r
t
s
\color{red}{parts }
parts 部分
B. modules 模块
C. software 软件
D. a whole 整个
(74)
A. parts 部分
B. modules 模块
C. software 软件
D.
a
\color{red}{a}
a
w
h
o
l
e
\color{red}{whole}
whole 整个
(75)
A. modified 修改的
B. used 用过的
C. suited 合适的
D.
t
a
i
l
o
r
e
d
\color{red}{tailored }
tailored 量身定制
2011年上半年下午卷
Extreme Programming (XP) is a discipline of software development with (71)
v
a
l
u
e
s
\color{red}{values }
values of simplicity, communication, feedback and courage. Successful software development is a team effort-not just the development team, but the larger team consisting of customer, management and developers. XP is a simple process that brings these peolpe together and helps them to succeed together. XP is aimed primarily at object-oriented projects using teams of a dozen or fewer programmers in one location. The principles of XP apply to any (72)
m
o
d
e
r
a
t
e
l
y
−
s
i
z
e
d
\color{red}{moderately-sized}
moderately−sized project that needs to deliver quality software rapidly and flexibly.
An XP project needs a(an) (73)
f
u
l
l
−
t
i
m
e
\color{red}{full-time }
full−time customer to provide guidance. Customers, programmers, managers, are all working (74)
t
o
g
e
t
h
e
r
\color{red}{together }
together to build the system that’s needed. Customers-those who have software that needs to be developed-will leran simple, effective ways to (75)
c
o
m
m
u
n
i
c
a
t
e
\color{red}{communicate }
communicate what they need, to be sure that they are getting what they need, and to steer the project to success.
极限编程（XP）是一个软件开发学科，具有简单性，通信，反馈和勇气的价值。 成功的软件开发是一项团队工作 - 不仅仅是开发团队，而是由客户，管理层和开发人员组成的更大团队。 XP是一个简单的过程，将这些人们聚集在一起并帮助他们共同成功。 XP主要针对面向对象的项目，在一个位置使用十几个或更少程序员的团队。 XP的原则适用于需要快速灵活地提供高质量软件的任何（72）中等规模的项目。
XP项目需要（73）全职客户提供指导。 客户，程序员，经理们都在一起工作（74），以构建所需的系统。 客户 - 那些拥有需要开发的软件的人 - 将利用简单有效的方式（75）传达他们需要的东西，确保他们得到他们需要的东西，并引导项目取得成功。
(71)
importance 重要性
keys 关键
roles 角色
v
a
l
u
e
s
\color{red}{values }
values 价值
(72)
small-sized 小型
m
o
d
e
r
a
t
e
l
y
−
s
i
z
e
d
\color{red}{moderately-sized}
moderately−sized 中等规模
large-sized 大规模
huge-sized 巨大的规模
(73)
part-time 兼职
casual 随便
seldom 很少
f
u
l
l
−
t
i
m
e
\color{red}{full-time }
full−time 全职
(74)
t
o
g
e
t
h
e
r
\color{red}{together }
together 一起
by themselves 通过他们自己
separately 分别
alone 单独
(75)
tell 告诉
know 知道
c
o
m
m
u
n
i
c
a
t
e
\color{red}{communicate }
communicate 沟通
feedback 反馈
326
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
