它们挂在枝头（由此而得“巫婆的灯笼裤”之名），需要数百年才能分解，它们助长石油需求，正是石油用于制造塑料。
They get caught in trees (hence the epithet "Witches' Knickers"), take hundreds of years to decompose and push up demand for oil, used to make plastics.
在60岁左右，“肌肉真的开始分解，”一位研究衰老的研究员凯瑟琳·斯塔尔说，“也正因为如此，老年人对蛋白质的需求实际上增加了。”
At around age 60, "muscles really start to break down," say Kathryn Starr, an aging researcher, "and because of that, the protein needs of an older adult actually increase."
您现在可以使用流程分解结构来驱动需求指定的方式。
You can now use the process decomposition structure to drive how requirements are specified.
然后需求可以分配给迭代，并分解成开发团队可以实施的任务。
The requirements can then be assigned to iterations and decomposed into tasks for the development team to implement.
必须将安全需求封装或分解为将在SOA实现中以渗透方式工作的一组安全服务。
You must look to encapsulate or decompose security requirements into a set of security services that will act pervasively throughout the SOA implementation.
在系统分解过程中，业务分析人员将确定新服务的需求。
During system decomposition, business analysis identifies the requirements for new services.
每个分解级别都强制进行设计决策，提供正在进行的合成，连接需求和设计规格说明，并增加系统详细内容。
Each level of decomposition forces design decisions, providing ongoing synthesis, coupling of requirements and design specifications, and increasing system detail.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
Through separation of concerns, integration requirements are decomposed into more granular services.
需求的创建来自于需要，工作状态，以及对工作分解结构(WBS)中的工作的估计。
The creation of demand comes from the requirements, statement of work, and by estimating the effort by the work breakdown structure (WBS).
可以通过识别为支持业务需求而定义的特定功能来实现这种分解，如图1所示。
This decomposition is accomplished through the identification of the specific functions that need to be defined to support business requirements, as shown in Figure 1.
塑料袋的确危害很大，它们挂在枝头(由此而得“巫婆的灯笼裤”之名)，需要数百年才能分解，它们助长石油需求，正是石油用于制造塑料。
And quite right, too. They get caught in trees (hence the epithet "Witches' Knickers"), take hundreds of years to decompose and push up demand for oil, used to make plastics.
分解系统，而不是需求(技术的)。
如果已经选择了分解，那么接着选择一种最适合查询和报告需求的目标关系模式。
If you have decided to shred, pick a relational target schema that best fits the query and reporting requirements.
我们将在功能上分解系统，分解成需求层级中的功能（需求分解）。
We would functionally decompose the system to break out functions in a hierarchy of requirements (requirements decomposition).
使用此分解方式，我们能够跨业务领域、行业、特定于客户端的需求、上下文或环境提取共性和差异。
With this decomposition, we are able to extract commonality and variations across business domains, industries, and client specific requirements, contexts or environments.
分解成这些设计决策是出于对补充需求和由位置所表示的分布的考虑。
Factored into these design decisions are considerations for supplementary requirements and distribution represented by the localities.
单个需求也许可以分解为十个用户描述，但是，如果开发团队完成了其中五个最关键的描述，那么也许就足以满足客户的需求了。
One requirement may break down into ten user stories, but if the development team completes the five most critical stories, that may be sufficient to meet the customer requirement.
域分解是通过源自业务组件设计的业务需求规范实现的。
Domain decomposition results from the specification of business requirements originating from the business component design.
模块能够选择完全人造的主键——在拒绝所有数据表示角色时分解出唯一性需求的那些主键。
Instead, the modules are able to choose wholly artificial primary keys — ones that isolate the uniqueness requirement while refusing any data-representation role.
将XML数据分解到关系表仍然是常见的一种需求。
Shredding XML data to relational tables is still a common requirement.
另外，类似于CWM,ODM提供了可以在业务功能模型分解，业务信息需求以及组织分解中使用的实体关系。
In addition, like CWM, ODM provides an entity relationship that could be used to model business functions decomposition, business information needs, and organization, decomposition.
所需的软件被分解为给定名称的特征(需求、故事等)，它们组成了需要交付的整个系统。
The desired software is broken down into named features (requirements, stories) which are part of what it means to deliver the desired system.
然而，业务需求可能随着时间的推移而变化，这使得管理员难以决定应该将哪些xml值分解到关系列中。
However, business needs can vary over time, making it difficult for administrators to determine which XML values should be shredded into relational columns.
首先，被显示在我们的工作状态（SOW）中的需求本质上是一系列被分解的规格说明，这些规格说明不能引导清晰的工作分解，或者甚至不能会产生许多架构的线索。
For one thing, the requirements as stated in our SOW were essentially a set of decomposed specifications that didn't lead to a clear breakdown of the work or even yield many architectural clues.
正如我在本系列的第2部分解释的那样，当需求关系在需求图外被提出时，这些属性将会变的非常便捷。
As I explain in part 2 of this article, these attributes become particularly handy when requirement relationships are represented outside requirements diagrams.
关注点分离建议将业务需求分解为多个服务；合并表示业务流程的现有服务以及新的服务的组合。
Separation of concerns suggests decomposing business needs into services; and composing combinations of existing and new services that represent business processes.
根据您的需求，您可以将您的环境分解或者瓦解成单个或者多个可以引用的拓扑。
Depending on your needs, you may dissect or collapse the contents of your environment into single or multiple topologies that can be referenced.
最后，产品特性被分解成系统用例以及能够被进一步分析并作为系统组件的低级需求细化的补充需求。
Finally, the product features are broken down into system use cases and supplementary requirements that can be further analyzed and detailed as low-level requirements for the system components.
较之传统的发酵工序，这种“双槽系统”能够产生更多的沼气，因为分解排泄物的细菌种类有所不同，于是适合它们分解废物的温度需求也有所不同。
This two-tank system produces more methane than conventional methods because different strains of bacteria, which chew up different components of faeces, work better at different temperatures.
在需求分析阶段(例如，分解与细化)，依据来源创建新的需求。
During requirement analysis (e.g., decomposition and flow-down), new requirements are created by derivation.
应用推荐