功能需求文档：详细描述SOA将作为业务服务提供的所有业务流程。
Functional requirements document: Describes in detail all the business processes that the SOA will surface as business services.
备注：考虑接口的灵活性以描述不同数量的功能需求。
Comment: Consider the flexibility of the interface to describe a varying number of functional requirements.
尽管服务调用和服务描述通常被认为是SOA的需求，但服务发现也是它的可选功能。
Whereas Service Invocation and Service Description are usually considered to be requirements of SOA, Service Discovery is an optional capability.
如果我们把易访问性需求作为一般的需求，那么它们将和功能与性能需求一起出现在开发人员的任务描述中。
If we treat accessibility requirements as ordinary requirements, then they will appear in developers' task descriptions, together with functional and performance requirements.
它包括了描述用例模型中所确定的功能需求的逻辑实现的类和序列图。
It consists of class and sequence diagrams that describe the logical implementation of the functional requirements that you identified in the use case model.
它可能来自准确描述的服务功能需求，也可能产生于希望规范服务使用的愿望。
They can originate either from requirements necessary for the proper functioning of the service or from the desire to regulate the use of the service.
在设计描述部分逐步讲述项目的需求分析，网站架构设计，功能分析与设计，数据库设计，其中有相应的示意图和表格直观的表达设计意图；
Demand analysis, website structure design, function analysis and design, database design will be shown step by step at the part of design description.
例如，让我们假设您是软件架构师，总是按照软件需求规范（Software Requirement Specification，SRS）来将项目功能需求描述成一列不相干的“应该有”的条目。
For example, let's say you are a software architect who has always described project functional requirements as a list of unrelated "shall have" items in a Software Requirement Specification (SRS).
SV10a系统规则模型描述业务需求或运作任务需求所利用的影响系统功能的约束。
SV10a Systems Rules Model Describes constraints imposed on system functionality by business needs or operational mission requirements.
策略的一个主要用例是描述Web服务提供者的功能或需求。
One main use case for policies is to describe the capabilities or requirements of a Web service provider.
客户要填写详细的问卷，在其中描述他们的需求(吞吐量、用户访问、特殊的应用程序功能等等)。
The customer fills out a detailed questionnaire describing their requirements (throughput, user visits, special application features, and so on).
故事板是一个功能非常强大的技术，可以帮助你描述已经用图形很好表达的信息(比如可用性，用户经验，用户界面标准，以及其它需求)。
Storyboards are a powerful technique to help describe information that is best communicated graphically (such as usability, user experience, user interface standards, and other requirements).
需求描述了所有产品功能，并且定义了实现这些功能的约束条件。
The requirements describe all the product functions, as well as the constraints under which these functions should be realized.
同样在这个时候我们关注系统的非功能需求，这就意味着这些需求不会被系统的功能规格说明描述。
Also at this time we addressed the system's nonfunctional requirements, meaning those not described by the system's functional specifications.
作为描述需求的机制，功能特性必需和额外的环境相结合。
As a mechanism for describing requirements, features must be combined with additional context.
业务分析人员开始编制需求，还利用业务过程模型来描述系统的功能需求。
The business Analyst begins to document requirements, using business process models to describe functional requirements of the system as well.
不适合放在用例中的需求（功能性和非功能性）应当在补充规约中进行详细描述。
The requirements (functional and non-functional) that do not fit appropriately within the use cases should be detailed in the Supplementary Specifications.
功能性的需求用使用用例的术语来描述。
Functional requirements are described in terms of use cases.
非功能需求在需求数据库中进行描述，依附于业务过程模型中的任务或项。
Non-functional requirements are described in a requirements database, attached to tasks and items in the business process model.
在项目过程中，我们可以很容易地将系统功能与提案需求以及工作描述中所设定的所需系统特征相互关联起来。
During the project, we could easily correlate system capabilities to the required system features stated in the request for proposal and statement of work.
从流程的角度而言，您需要让服务提供者描述服务功能和非功能需求。
From a process standpoint, you need to get the service providers to describe the service functionally and nonfunctionally.
这意味着对于功能性的需求(关于系统必须实际上做什么的需求)，我们应当使用用例来描述系统的行为。
This means that for functional requirements (requirements regarding what the system must actually do), we apply use cases to describe the system's behavior.
第三个常见的问题就是需求说明的错误设计，利用技术语言或脚本去描述某个功能是怎么被测试的，而不是去描述系统应该怎么工作。
The third common issue is getting the design of specifications wrong, using technical language and scripts to describe how something is tested instead of what the system is supposed to do.
尽管功能性需求描述产品的功能，非功能性需求描述系统特性，如。
Whereas "Functional" requirements specify the features of the product, "Non-Functional" requirements specify system characteristics such as.
要让文档容易理解，应避免过长的需求说明，避免使用多个较小的需求说明去描述单一功能，寻求更高层的概念，避免技术上的自动化概念。
Easy to understand documentation - avoid long specifications, avoid lots of small specifications for a single feature, look for higher level concepts, avoid technical automation concepts.
来自建筑事务所的描述。该项目设计围绕明确的设计问题：满足功能、审美和语义的需求。
From the architect. The project was designed around a specific design problem: to satisfy functional, aesthetic, and semantic needs.
该系统较好的满足了授权管理的需求，具有资源统一描述、自动收集、资源树生成等功能。
This system has satisfied with privilege management demand, possessing the function of Web resources description, automatical collection and resources tree build and so on.
它描述了应用程序的结构，以及该结构如何实现组织的功能需求。
It describes the structure of an application and how that structure implements the functional requirements of the organization.
在需求分析阶段，以用例来捕获用户需求，描述系统功能。
In the requirement analysis stage, the users 'requirements were captured by use cases, and the system functions were described.
在需求分析阶段，以用例来捕获用户需求，描述系统功能。
In the requirement analysis stage, the users 'requirements were captured by use cases, and the system functions were described.
应用推荐