Updating of requirements attributes, as well as most of the changes made to requirements, will also take place at Site A. Site B also needs read/write access to requirements.
对需求特性的更新以及大部分对需求的更改也都将在Site A发生。 SiteB也需要对需求的读/写访问。
This access must be not only to the wording of the requirements, but also to the priority, status, and other attributes.
这种接口必须不只是针对需求的描述，也要针对优先级、状态和其他属性。
Requirement attributes contain information about requirements.
需求属性包含需求信息。
Quality attributes requirements need to be specified with good measures.
质量属性需求需要用好的度量方法指定。
You can also add logic in the unit validators that pertains to specific capabilities, requirements, or attributes.
您还可以在拥有特定功能，需求或者属性的单元确认器中添加逻辑。
The services map in Figure 7 shows a typical services and application inventory with some typical attributes gathered to document technical requirements for the integration.
图7中的服务地图显示了典型服务和应用程序库存，它具有为记录集成的技术需求而收集的一些典型属性。
As we also noted earlier, attributes provide supplemental information that helps you understand and use requirements specifications more effectively.
也如我们前面注意到的，属性提供了补充信息，使你更加有效地理解和使用需求规约。
A canonical data model is a common representation of entities, their attributes and relationships based on the business requirements in the SOA project.
规范化数据模型是SOA项目中实体及其属性和基于业务需求的关系的一个公共表示。
Unit validators can check the capabilities, requirements, attributes, and links on the unit and ensure that the unit is properly configured as a whole.
单元确认器会检查单元上的功能，需求，属性以及链接，以确保单元会作为一个整体进行配置。
Similarly, requirements have attributes — information that makes the requirements more understandable or usable.
类似地，需求也有属性——这是使需求更为可读和可用的信息。
For developers who write requirements, the plan describes necessary requirements artifacts, along with requirement types and their respective attributes.
对编写需求的开发人员，该计划描述了必要的需求工件，以及需求类型及相应的属性。
The data model for the data warehouse was based on the attributes identified during the requirements phase.
这个数据仓库的数据模型基于在需求阶段识别出的属性。
As I explain in part 2 of this article, these attributes become particularly handy when requirement relationships are represented outside requirements diagrams.
正如我在本系列的第2部分解释的那样，当需求关系在需求图外被提出时，这些属性将会变的非常便捷。
Non-functional requirements describe the attributes of the portal system.
非实用需求描述门户系统的属性。
The system attributes and services are traced to system requirements.
系统属性和服务被系统需求追踪。
Requirements have a number of derived attributes to store the status of the relationships reviewed in the above paragraphs.
需求拥有大量的源属性以存储上文中提到的关系状态。
Where attributes are mapped, the set of source attributes must be compiled and provided for scoping including identification of any semantic alignment requirements.
当有属性映射时，必须整理源属性集并用于范围界定，包括识别所有语义校准需求。
For example, annotations can specify the attributes of a service's scope, the nature of implementation, plus interaction attributes, constraints, and requirements.
例如，注释可以指定服务范围的属性、实现的本质以及迭代特性、约束和需求。
RequisitePro USES a database to organize and track requirements, and to assign attributes like priority, status, and difficulty level to them.
RequisitePro使用数据库管理并追踪需求，并为它们分配属性例如优先级、状态以及难度级别等。
Microdata has strict requirements about where to place the microdata attributes in the HTML, so each field type in Drupal needs to define where to place the attribute within its formatters.
对于在HTML中放置微数据属性的位置，微数据有严格的要求，因此Drupal中的每种字段类型都需要定义在其格式器中放置属性的位置。
Defining manageability requirements up front along with other architectural quality attributes provides an interesting opportunity: Management facilities can be decoupled from other Web 2.0 artifacts.
提前定义可管理性需求以及其他体系结构的质量属性，这样可以使管理功能与其他Web 2.0构件解耦。
Rational RequisitePro USES a database to assign attributes, such as priority, difficulty, and status, as well as to organize and track requirements.
RationalRequisitePro利用数据库分配属性，如优先级、难度和状态，同时组织并跟踪需求。
Business requirements captured in Rational RequisitePro with priorities, status, and other important attributes.
在RationalRequisitePro中捕获的业务需求，包括优先级、状态及其他重要属性。
By critically reviewing your requirements with these attributes in mind, you'll jump-start your inspection process. According to Patton, our requirements ought to be.
通过仔细地利用这些属性用心地审阅您的需求，您将启动您的检查过程。
Quality requirements have many more attributes; see the IEEE guidelines for more information. 1.
质量需求还有更多的属性，详见ieee的指南。
Activity attributes include activity codes, predecessor activities, successor activities, logical relationships, leads and lags, resource requirements, imposed dates, constraints, and assumptions.
活动属性包括活动编码、先行活动、后续活动、逻辑关系、提前量和滞后量、资源需求、强制日期、约束条件和假设条件等。
The Queuing Service applies scheduling policies, which include matching job requirements to grid resource attributes.
排队服务应用调度策略，将作业的需求和网格资源的属性相匹配。
Quality Attributes are derived from requirements.
从需求可以导出一系列质量属性；
Activity Attributes include Activity Codes, predecessor activities, successor activities, Logical Relationships, Leads and Lags, resource requirements, Imposed Dates, Constraints, and assumptions.
活动属性包括：活动编码、紧前活动、紧后活动、逻辑关系、时间提前量和时间滞后量、资源要求、强制日期、制约因素和假设条件。
Activity Attributes include Activity Codes, predecessor activities, successor activities, Logical Relationships, Leads and Lags, resource requirements, Imposed Dates, Constraints, and assumptions.
活动属性包括：活动编码、紧前活动、紧后活动、逻辑关系、时间提前量和时间滞后量、资源要求、强制日期、制约因素和假设条件。
应用推荐