鉴于这个劳动力供给和劳动力需求特性的简短调查，对失业有什么观点吗？
In the light of this brief survey of the characteristics of the labor supply and the probable demand for labor, what is the outlook for unemployment?
高科技企业拥有大量知识员工，其需求特性往往有别于传统工人。
There are many knowledge employees working in the high-tech enterprises; their needs are different from the traditional workers.
本课题以我国烟草行业为研究载体，以消费者需求特性为研究对象。
The topics to study in China tobacco industry carrier to consumer demand characteristics in this study.
如早先详细的介绍，RationalQuality Manger有许多帮助您管理需求覆盖率的需求特性。
As described in detail earlier, Rational Quality Manger has several requirements features that help you manage requirements coverage.
对需求特性的更新以及大部分对需求的更改也都将在Site A发生。 Site B也需要对需求的读/写访问。
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.
这两种方法都通过一种简单的原则来描写这些需求，只包括产品的基本特性。
Both work through a straightforward discipline in writing the requirements involving only the basic features of the products.
下面的表总结了这些DB 2特性如何解决各种客户需求。
The table below summarizes how these DB2 features address each customer need.
可能的原因是业务需求或特性功能发生了变化，因此也要求更改数据库架构。
There might be changes in business requirements or feature functionality that require changes to the database schema as well.
因此，当讨论需求、特性和产品定位的时候，每个人都处于同一页面。
Thus, everyone is on the same page when discussing requirements, features, and product positioning.
另外一些作者20已定义了一种方法来映射和交流涉众问题到业务需要再到项目的系统特性(需求)。
Other authors 20 have defined a method for mapping and communicating stakeholder problems to business needs to system features (requirements) used for project scoping.
特性可以将此需求精化为："系统应当使用一个关系数据库"。
The feature can refine this requirement to be: "System should use a relational database".
根据过去的经验，我们知道通过模糊的需求定义，特性和系统缺陷会大量出现在测试结果里。
Based on past experience, we knew that most feature and system defects we discovered in testing resulted from ambiguous requirement definitions.
随着时间的推移，DB2继续添加和增强特性，以解决这些需求。
Over time, DB2 continues to add and enhance features to address these needs.
这避免了“特性蔓延”——需求工作保持不变甚至增加的情况。
This avoids "feature creep," in which requirements work remains constant or even increases.
业务分析员可以使用此特性来满足需求。
The business analyzer could leverage this feature to fulfill the requirement.
正如我们前面看到的，需求类型可能包括业务需要、特性以及功能性和非功能性的软件需求。
As we saw earlier, requirement types might include business needs, features, and functional and non-functional software requirements.
那些代表产品整体特性的非功能性需求是个例外。
Nonfunctional requirements that represent product-wide properties are the exception to this rule.
每一个需求通常映射到几个特性，然后这几个特性映射到用例和补充需求。
Every need usually maps to a couple of features, and then features map to use cases and supplementary requirements.
如果你花费大量时间说明暂时不会实现的特性需求，那么就说明你的流程并不顺畅。
If you spend a lot of time elaborating requirements for features you are not going to work on for a while your process isn't streamlined enough.
这个特性可以满足以下的需求。
其中的一个特性就是根据用户需求，能够同步提供法语和英语的服务。
One of the custom features envisioned is providing services in French and English simultaneously, based on user preference.
可以在其他级别上设计额外的跟踪关系，例如从特性到相关者请求、跟踪的辅助需求到特性、需求到xde模型工件等跟踪关系。
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.
客户必须将业务需求转换成非常具体的特性需求。
Customers have to translate business need into feature stories that are very specific.
竞争因素、公司规定的安全遵守特性，以及其他经常的需求可能迫使我们生成最终用户从不使用的特性。
Competitive factors, corporate-mandated security-compliance features, and other overhead requirements may force us to generate features that the end-user never USES.
例如，注释可以指定服务范围的属性、实现的本质以及迭代特性、约束和需求。
For example, annotations can specify the attributes of a service's scope, the nature of implementation, plus interaction attributes, constraints, and requirements.
确保开发人员不会“镀金”(增加超出需求的特性)。
Ensure that developers aren't "gold plating" (adding features beyond the requirements).
根据需求和业务模型跟踪特性。
图5B.分析师活动：跟踪到用例的需求或特性。
Figure 5b. Analyst activities: Requirements or features traced to use cases.
在RequisitePro中一些需求类型的例子是涉众需求，特性，用例，参与者，和术语条款。
Some examples of requirement types in RequisitePro are stakeholder needs, features, use cases, actors, and glossary terms.
在RequisitePro中一些需求类型的例子是涉众需求，特性，用例，参与者，和术语条款。
Some examples of requirement types in RequisitePro are stakeholder needs, features, use cases, actors, and glossary terms.
应用推荐