满足涉众的变更需求——构建阶段。
Meeting the changing needs of stakeholders — the Construction phase.
您可以为任何类型的变更需求定义独特的工作流。
You can define unique workflows for any type of change request.
建议功能就是从所有干系人那里收集信息并对变更需求快速响应。
The Advising function is associated with the gathering of information from all stakeholders and responding quickly to changing requirements.
巧妙的响应一个变更需求，您需要首先了解变更的原因。
To respond intelligently to a change request, you must first understand the reasons for it.
如果公司决定改变业务方向，随之而来的系统变更需求将令人痛不欲生。
If the business needs to change direction there's often a very painful change request system put in place.
更新变更请求的当前状态以符合在变更需求状态部分的描述。
Update current status of the change request as it moves through the states described in the Change Request Status section.
需求变化：变更需求将会影响交付的时间表并增加软件返工和成本。
Requirements volatility: Changing requirements that impact delivery schedules and increase software rework and cost.
基于全球变更管理流程，管理，控制和执行相关产品的变更需求。
Administer, control and realize changes to the nominated business case baseline definitionon basis of the specific global Change Management processes within the BusinessUnit.
您可以调整scriptassure的实质来满足开发生命周期的变更需求。
You can adjust ScriptAssure Settings to meet changing requirements during the development life cycle.
另外可能的外部因素还包括项目核心人员的离职和客户变更需求说明等。
Other possible external factors include key personnel leaving the project or customers changing the requirements specifications.
因为草图由不同的部件和面板组成，所以可以很容易地为变更需求编辑已经存在的草图。
Because sketches are composed from different parts and panels, it is easy to modify existing sketches for the change requirement.
您可以追踪RationalClearQuestWeb中的缺陷以及变更需求。
You can track defects and change requests in Rational ClearQuest Web.
应该有强烈的商业驱动和迫切的变更需求——其它的建议都不应该考虑，不值得做这样的评估。
There should be strong business drivers and an urgency to change — otherwise the recommendations provided may not be considered and the assessment may be perceived as not worthwhile.
我经常会被问及我们应当在哪个时间点上回顾需求，并且使我们的用户服从正式的变更需求程序。
I am often asked at what point should we lock down the requirements and subject our users to formal change request procedures.
在一个大的系统中，可能有许多需求，数量多得使我们很难在适当的时候记得去变更需求。
In a large system, there may be many requirements, more than we easily can remember to change at the appropriate time.
有了对意图的这种层次的理解，过程的一致的演进可以维持在有时候的变更需求和解释的混乱冲击之下。
With such a tiered understanding of intentions, a consistent evolution of process can be maintained under the sometimes chaotic onslaught of changing needs and interpretations.
如果任何与项目有关的人都能够提交新的需求和/或变更需求，那项目会很快地陷入一片混乱并失去控制。
Things can quickly get out of control if anyone associated with the project is able to submit new requirements and/or change requests.
在一个开发的生存周期中，一个健壮的解决方案也会自动执行一个提交，分配，解决和校验变更需求的过程。
A robust solution will also enforce a common process for submitting, assigning, resolving, and verifying change request resolutions throughout the development lifecycle.
对于每一个包含从现在到将来多种必要状态的需求，需求分析师打开一个变更需求记录就代表着一个评审活动。
For each requirement that contains multiple necessary states from now and into the future, a requirements analyst opens a change request record representing a review activity.
这个变更控制管理器创建了一个变更请求记录类型，它包含了与变更需求相关的活动，而不是创建一个新的需求属性。
Instead of creating a new requirement attribute, the change-control manager creates a change request record type containing activities related to the need to change a requirement.
开发、实施单元测试以确保在发布给客户之前变更需求都被解决；支持测试团队进行测试并根据需求变更来修改程序。
Develop and implement unit tests to ensure required changes are solved before release to the client, support the testing team for testing and modify the program based on the change requirements.
项目涉众(stakeholder)需求的不断变更需要一种灵活、渐进的，且高度协作的DW开发方法。
Changing stakeholder requirements demand a flexible, evolutionary, and highly collaborative approach to DW development.
项目涉众(stakeholder)需求的不断变更需要一种灵活、渐进的，且高度协作的DW开发方法。
Changing stakeholder requirements demand a flexible, evolutionary, and highly collaborative approach to DW development.
应用推荐