But the largest software project that utilizes KParts is KOffice.
但利用KParts的最大的软件项目是KOffice。
In an Agile software project usually small (elementary) services are delivered.
在敏捷软件项目里，通常交付的是小(基本)的服务。
Effective software project teams are composed of people fulfilling a variety of roles.
有效的软件项目团队由担当各种角色的人员所组成。
So, just as in a software project, we have a conference call with all the stakeholders.
因此，正如在软件项目中一样，我们与所有的涉众开了一个电话会议。
The failure of a software project becomes more likely as the size of a project increases.
随着项目规模的增长，软件项目越发变得容易失败了。
Functional requirements document: a typical requirements document for a software project.
功能需求文档：软件项目的典型需求文档。
One of the biggest challenges for any software project is to know when to declare victory.
对于任何软件项目，一个最大的挑战是知道何时宣告胜利。
Typically, use cases are elaborated on during the requirements phase of a software project.
通常在软件项目的需求阶段详细描述用例。
The following key ideas will allow teams to manage requirements for their software project.
下面这些观念将帮助团队管理他们软件项目的需求。
Yet, it’s not a software project which has suffered splintering or factionism(factionalism).
然而，它依然不是一个已经裂成碎片或派系丛生的软件项目。
Software project experience has shown time and again that the early phases make or break a project.
软件项目的经验已多次表明，早期阶段决定项目的成败。
The examples presented here are designed to demonstrate how to integrate ODC into a software project.
这里展示的范例是用来论证怎样将ODC整合到软件项目中的。
Ease of testing, documentation, and maintenance should be kept in mind as well in any software project.
还应在任何软件项目中考虑测试、编写和维护的简易性。
But if you have ever managed a software project that way, and I have, you know that it just doesn't work.
但是你用这种方式管理过软件项目的话，你就知道这是行不通的。
In a software project, requirements are explicitly stated expectations that users place on the project team.
在软件项目中，需求是用户对项目团队陈述明确的期望。
Defect management is critical in any software project, and many tools are available to achieve various tasks.
缺陷管理对于任何软件项目都很重要，而且不同的工具负责不同的任务。
Even on a software project, during times of stress and panic, we have a tendency to turn to our comfort zones.
甚至是在软件项目中，在压力和恐慌的时期，我们倾向于求助于我们的舒适地带。
Test teams write and execute hundreds or even thousands of test script documents for a given software project.
测试团队为已知的软件项目书写并执行成百甚至上千的测试脚本文档。
For example, you and a few friends -- who are spread apart around the world -- start a small software project.
假设，您和遍布在世界各地的几位朋友打算开始一个小型的软件项目。
Software project managers do not have to calculate the correlations between projects or sub groups of projects.
软件项目经理不必要计算项目或项目子族之间的关联。
Very often, the almost inevitable delays in a software project get assigned to the already short "testing cycle".
通常情况是，软件工程里本来就很短的“测试周期”总是不可避免地会被耽搁。
An efficient, automated software project measurement program can help project managers cope with these challenges.
一个有效的、自动化的软件项目度量程序能够帮助项目经理应对这些挑战。
Iterative, incremental development already offers a great measure of quality and progress for every software project.
迭代，递增的开发已经为每个软件项目的质量和进展提供了很好的度量手段。
For example, a great deal of effort is put into producing valid and reliable data for software project cost estimates.
例如，大量的工作用来为软件项目成本估算产生有效和可靠的数据。
The software project manager with the help of the management review team updates the software development plan as needed.
在需要之时，软件项目经理会在管理评审小组的帮助下更新软件开发计划。
But I hope the analogy provokes readers to look at software project management techniques from a different frame of reference.
但是我希望这种类比能使读者从不同的参考中来审视软件项目管理技术。
In sum, good documentation at the right level of detail (and not more) increases the chances of success in a software project.
总之，详细程度恰到好处的好文档会提高软件项目成功的几率。
A software project that has a consistently increasing earned value profile is certain to have a pending cataclysmic regression.
一个具有一张价值持续不断增长曲线图的软件项目一定会有一个待解决的很大的回归。
If there is a RUP work product but no counterpart in your software project management process, should you add this work product?
如果在你的软件项目管理过程中存在RUP工作产品中没有副本，你是否应该增加这个工作产品？
Risk in software project management is also well-known, although it is usually expressed qualitatively in a documented risk list.
软件项目管理中的风险也是众所周知的，尽管它通常在质量方面表示于编制的风险列表中。
应用推荐