Does the application meet stakeholder requirements?
应用软件满足涉众的需求吗？
Instead, we do the work to fulfill specific stakeholder requirements.
相反，我们做这样的工作来满足具体涉众的需求。
After the stakeholder requirements are imported, a model-based requirements analysis can be performed.
在导入涉众需求之后，就可以执行基于模型的需求分析操作了。
Changing stakeholder requirements demand a flexible, evolutionary, and highly collaborative approach to DW development.
项目涉众(stakeholder)需求的不断变更需要一种灵活、渐进的，且高度协作的DW开发方法。
It is difficult to include stakeholder requirements as they might change due to changing marketing strategies and/or technology conditions.
很难收集相关方面的需求，因为由于市场战略和/或技术条件的变化，需求可能会变化。
In the case of less complex course development, we use fewer iterations because stakeholder requirements are clear, architecture is stable, and the content is obvious.
在不十分复杂的课程的开发中，我们使用较少的迭代，因为涉众的需求很明确，结构很稳定，内容也很清晰。
Remember that this is not a static sequence but requires feedback and iteration between the various models and views all the way back to the stakeholder requirements.
请记住，这不是一个静态的序列，而需要在各种模型和视图之间进行反馈和迭代，直到利益相关者的需求。
Stakeholder requirements are translated into system requirements that define what the system must do (functional requirements) and how well it must perform (quality of service requirements).
涉众需求会转化为系统需求，该需求定义了系统必须执行的操作(功能性需求)，以及必须实现的程度(服务需求的质量)。
Stakeholder participation lets analysts weigh different goal opinions from different stakeholders on formulating requirements in response to changes in SOA constraints and risks.
涉众的参与允许分析人员权衡不同涉众对制定需求(以响应SOA约束和风险方面的变化)的不同目标意见。
Finally, make sure you get the signed agreement of key stakeholders, or representatives of key stakeholder groups, saying that the requirements as presented precisely reflect their needs.
最后确保您所得到的是关键利益相关者、或关键利益相关者小组代表所签署的协议认为这些要求准确地反映了他们的需求。
There will be teams that will be given requirements from a stakeholder and they will interact with that stakeholder to satisfy the requirements.
有项目小组，给定来自利益相关者的需求，小组将和他们交互以满足他们的需求。
Stakeholder concurrence on scope, requirements, constraints, and schedule estimates.
涉众在规模、需求，限制以及进度评估上的合作。
Additional trace relationships can be set up between other levels, such as features to stakeholder requests, supplementary requirements traced to features, and requirements to XDE model artifacts.
可以在其他级别上设计额外的跟踪关系，例如从特性到相关者请求、跟踪的辅助需求到特性、需求到xde模型工件等跟踪关系。
It is foolish to think that one type of requirement will satisfy every stakeholder or that it will be easy to keep requirements synchronized with the code.
认为一种类型的需求可以满足每个涉众，或者认为可以很容易地使代码和需求保持同步是很愚蠢的。
During requirements gathering, stakeholder needs and goals are refined into requirements.
在需求采集期间，涉众需求和目标被提取为需求。
Thus the purpose of the system is to satisfy a set of stakeholder needs — the system requirements.
因此系统的目的是满足一系列投资者的需求，也就是所谓的系统需求。
Once the stakeholder goals document is created, here's how to apply it to the requirements process.
一旦这个涉众目标文档被创建，这里有如何将它运用到需求过程的方法。
Requirement reviews: Progress on requirements and stakeholder reviews.
需求复审：需求和涉众复审的进度。
If a system meets stakeholder goals, it doesn't matter whether you've written down the requirements.
如果一个系统满足了涉众目标，你是否已经写下了需求就无关紧要了。
Rather than sending our programming teams out to attack each element in a requirements list, the first thing we need to do is to understand and prioritize business and stakeholder needs.
我们要做的不是叫我们的程序设计团队攻克需求清单中每一个元素；我们要做的第一件事是理解并排列业务和涉众需要的优先次序。
Interview the various stakeholders, including the sponsor and identified users, and collect the requirements and stakeholder requests.
会见不同的出资方，包括发起人和用户，并且收集他们提出的需求。
Other authors 20 have defined a method for mapping and communicating stakeholder problems to business needs to system features (requirements) used for project scoping.
另外一些作者20已定义了一种方法来映射和交流涉众问题到业务需要再到项目的系统特性(需求)。
Each iteration verifies the system architecture, adherence to requirements and stakeholder needs, and the software quality.
每次迭代都验证系统架构，保证需求和干系人的要求，以及软件质量。
Development teams must be increasingly agile in order to respond to a volatile environment, in which requirements might change even before a system that satisfies stakeholder needs can be deployed.
开发团队为了响应一个易变的环境必须越来越敏捷，在这种环境中，在一个满足涉众需求的系统能够被部署之前，需求可能经常发生变化。
There is one key artifact — a stakeholder goals document — that can be developed to keep track of requirements for our Agile software projects.
有一个关键的架构——涉众的目标文档——它可能非常先进，可以跟踪我们敏捷软件项目的需求。
Instead, the best practice is to allow each stakeholder group to nominate exactly one representative who will be authorized to submit requirements and change requests on behalf of the group.
相反，最好的办法是让每个涉众组正确地任命一个代表，代表全组来负责提交需求和更改需求。
BPM and direct requirements analysis through stakeholder interviews and CBM are an obvious and well-suited way of identifying candidate services.
通过项目相关人员的会谈和CBM来进行BPM和直接需求分析是一个容易理解且非常合适的标识候选服务的方法。
Even in a more informal environment, an Excel spreadsheet with requirements from the business stakeholder will suffice.
即使在一个不太正式的环境中，一个包含业务利益相关者的需求的Excel电子数据表也能够满足我们的要求。
Allow only one representative from each stakeholder group to submit requirements and change requests.
每个涉众组只允许一个代表去提交需求和更改需求。
As engineers, how do we know when we have the right scenario or if we have the right stakeholder when we collect system requirements?
作为工程师，当我们收集系统需求时，我们怎能知道我们得到了正确的场景或是否遇上了正确的涉众？
应用推荐