To do this, we will treat the business process as a Service Requirements contract.
为了完成这一步，我们将会把业务过程当作一个ServiceRequirements契约。
Figure 1 shows the business services requirements contract that our solution must fulfill.
图1显示了我们的解决方案所必须满足的业务服务需求合同。
These are the services that are capable of playing the roles in this Business services Requirements contract.
这些是能够在这一业务服务需求合同中扮演角色的服务。
What this diagram does show, however, is how these services fulfill the service Collaboration requirements contract.
然而，该图所显示的是这些服务如何完成了ServiceCollaboration需求契约。
By architecturally neutral, we mean that the requirements contract specifies what the solution has to do but not how.
所谓与体系结构无关，是指该需求契约只是指定了解决方案必须做什么，但是并没有指定如何去做。
We then used this requirements contract to help identify the required services and the potential relationships between them.
然后，我们使用该需求契约来识别所要求的服务以及它们之间的潜在关系。
We then used that requirements contract to help identify the required services and the potential relationships between them.
然后，我们使用该需求契约来帮助我们识别它们被要求的服务及它们之间的潜在联系。
This service collaboration represents a requirements contract derived from a business process that specifies what the service solution must do.
这一服务协作反映了一个需求契约，该契约来自一个指定服务解决方案必须做什么的业务过程。
This maintains the link between the service requirements contract, business processes, the business use case, and the business goals and objectives.
在这个过程中会一直保持服务需求契约、业务流程、业务用例及业务目标和目的之间的联系。
This is to be expected, because you are defining the specification in a Service Requirements contract for how a service consumer and provider interact.
您将在涉及服务消费者和提供者如何进行交互的ServiceRequirements契约中定义该规范。
Essentially, we are building (buying, reusing, adapting) services that are capable of playing the roles in this business services requirements contract.
本质上讲，我们正在建造(购买、复用、适应)能够在这一业务服务需求合同中扮演角色的服务。
Next, we viewed the business process as a service collaboration that represents a business service Requirements contract that must be fulfilled by our eventual solution.
接着，我们将业务过程视作反映我们的最终解决方案所必须满足的业务服务需求契约的一种服务协作。
Then we viewed the business process as a service collaboration that represents a business Services Requirements contract that must be fulfilled by our eventual solution.
接着，我们将业务过程视作反映BusinessServicesRequirements契约的一个服务协作，该契约必须通过我们最终的解决方案来完成。
It shows, specifically, what parts of the service provider play roles in the service requirements contract and how constraints on the component fulfill business constraints.
它特定的显示服务提供者的各个部分在服务需求契约中扮演什么角色，以及合成元素完成业务的约束。
The next section treats the business process as a Requirements contract and shows how to identify services in an SOA solution for the intended business operational requirements.
下一小节将业务过程作为一个Requirements契约进行处理，并且显示如何在一个业务操作需求的SOA解决方案中识别服务。
We also see that the parts taken together will interact in a manner that fulfills the Process Purchase Order requirements contract. Thus, Order Processing summarizes two things.
我们还看到这些被放在一起的部分将会以一种满足processPurchaseOrder需求契约的方式相互作用。
Its parts represent order processing participants that will provide or require services (or both) that are necessary to fulfill the process Purchase order requirements contract.
它部分反映了将要提供或者需求服务(或者既提供又需求)的必须满足processPurchaseOrder需求契约的顺序处理参与方。
Recall that this service collaboration represents a requirements contract, which is potentially derived from a business process that represents what our service solution must do.
回想这个服务协作反映了一个需求合同，它潜在来源于一个反映我们的服务解决方案所必须做的事情的业务过程中。
Showing how the SOA solution fulfills the business requirements takes a little extra work to specify the contract and role bindings, but it provides a big advantage for managing change.
显示SOA解决方案如何完成业务需求要花费额外的工作来指定契约和角色绑定，但是它提供了一个管理变化的有利条件。
This is, perhaps, because the business service contract is incomplete or that there is only an informal sketch of the business requirements.
也就是说，或许因为业务服务契约不完全，或者只有业务需求的概略信息。
A variation on this theme uses contract interfaces for a client to declare its requirements.
这个方案的一个变体采用合约接口，由客户端声明它的要求。
These requirements are viewed as a service contract, indicating the roles that participate in the business process, the tasks that they are expected to perform, and the rules for how they interact.
这些需求被视作一个服务契约，指出参与到业务过程中的角色，希望它们这行的任务，以及它们之间相互作用的规则。
You have to abide by all the requirements listed in this contract for Party a.
你必须遵从本合同中列出的对甲方的所有要求。
And, If you wrote the requirements into the contract, agile techniques may not be much help.
同时，如果你把需求写进合同，敏捷方法也不一定能帮到你。
Applicants also needed to sign a contract with the company after passing the interview, which had strict requirements regarding eyesight, heart rate and blood pressure.
同时，求职者通过面试之后，需要和公司签定一份合同，其中，对于视力、心率、血压都有严格要求。
Both of these features support a site's requirements, and the design of an appropriate contract model.
这两种功能都支持站点的要求和合适的契约模型的设计。
For example, the way you choose to manage change to requirements in a GDD environment could differ greatly for a new system project compared to a legacy maintenance contract involving a third party.
例如，对于一个新系统项目而言，你在GDD环境中所选择的管理需求变更的方法，与关联于第三方的遗留维护合同的管理需求变更方的法将有很大的不同。
With Design by Contract, you can use programmatic expressions to specify the requirements on inputs to a component, as well as on the returned results.
使用契约式设计，可以用可编程表达式指定对于组件输入和返回结果的要求。
He then goes into Design by Contract principles, and requirements management.
接着谈到契约式设计(Designby Contract)原则和需求管理。
He then goes into Design by Contract principles, and requirements management.
接着谈到契约式设计(Designby Contract)原则和需求管理。
应用推荐