为CRM解决方案收集数据时，公司必须考虑客户对隐私的需要、数据安全以及法律上、文化上的行为规范。
When gathering data as part of a CRM solution, a company must consider the desire for customer privacy and data security, as well as the legislative and cultural norms.
我们需要理解待解决的问题，为一个潜在的解决方案收集需求，将这些需求转换至设计中，构建解决方案，并对方案进行测试。
We need to understand the problem, gather requirements for a potential solution, translate those requirements into a design, build the solution, and test it.
这种工作中非常关键的一个部分是在部署并执行所有测试方案之前收集正确的数据。
A very critical component in this exercise is gathering the right data prior to deployment to execute all the test scenarios.
为了有机会复用，要创建一个或多个分类方案，并且指定要收集的量度，以帮助调整该团体的治理等级。
To aid the opportunistic reuse one or more classification schemas are created and the metrics to be collected are specified, to help justify the level of governance in this community.
存储过程需要将寄存器EXPLSNAP设置为ALL或YES，用以收集存取方案。
The stored procedure needs to set the EXPLSNAP register to ALL or YES in order to collect the access plans.
Sharding是非常合适的解决方案，因为在多数情况下，数据收集会比其它操作要频繁的多，没必要每次都去分配整个数据库。
Sharding collection is preferable because in many cases some data collections tend to be much larger than others, so it would be unprofitable to distribute the entire database.
实际上，您会发现转换工作很少没有麻烦，但是如果您从不熟悉XML的作者那里收集文档，那么它是一个较佳的解决方案。
In practice, you might find that the conversions are seldom trouble-free, but it's a good solution if you collect documents from authors who are not familiar with XML.
注意更多的关于提供可用性解决方案和为了防止失效而付出的代价比较的讨论可以在下面的“收集需求”中找到。
Note that further discussion comparing the costs of providing availability solutions against the costs of the failures against which they protect can be found in Gathering Requirements below.
过程信息应当被不断的收集起来，并且同原始方案和基线进行比较。
In-process information should be collected continuously and compared against the original plan and baseline.
您还能够将它用作一个从解决方案的细节模型中收集图的地方，从而您就能够描述那个解决方案的各种各样的架构的重要观点。
You could also use it as a place to gather diagrams from the more detailed models of a solution, so that you can depict various architecturally significant viewpoints of that solution.
它是一个强大的ETL解决方案，能够收集、集成和转换大量数据，能够处理复杂的数据结构。
It is a powerful ETL solution which collects, integrates and transforms large volumes of data with simple and complex data structures.
因此，随后的开发方法不是典型的“瀑布”方案，在瀑布方案中，收集需求之后进行分析和设计，并进行系统的实现。
Hence, the development approach that is followed is not the classic "waterfall" scenario, where requirements gathering is followed by analysis and design, leading to the implementation of the system.
一旦这25个县的数据收集完毕，较小的县可以根据相应的组织提供的方案，进行更详细与自身相关数据的收集。
Once the data for those 25 counties has been assembled, smaller counties could gather their Numbers using a detailed do-it-yourself kit from the coordinating organization.
本文描述的示例案例管理解决方案自动地把所有相关信息收集到案例中，从而为与索赔相关的业务活动提供上下文。
The sample case management solution described in this article automates the collection of all relevant information into a case to provide context for the business actions taken in regard to the claim.
随着收集到更多关于项目的信息，过程的方向越来越明确，支持设计目标的备选方案的数量也逐渐减少。
As more knowledge about a project is gathered, this informs the process and reduces the number of alternatives that support the design goals.
为了收集与计算雇员活动碳轨迹相关的必要数据，这个解决方案使用简单的用户友好的界面(UI)。
To collect the data necessary to calculate the carbon footprint associated with any employee activity, the solution USES a simple, user-friendly interface (UI).
通过使用现有工具、框架和插件，该解决方案能够更好地了解用户体验，并使收集数据和再现问题变得更容易。
Using this existing tool, framework, and plug-ins, this solution provides better insight to the user experience, making it easier to collect data and reproduce problems.
举个例子，诺基亚的一个提出一个方案，利用手机上的传感器收集空气质量的报告。
For example, Nokia have put forward an idea to attach sensors to phones that could report back on air quality.
团队开始设计解决方案前，必须对需求进行收集。
Before the team begins designing solutions, it must gather requirements.
对于某些情况，比如工作台和代理之间的连接被破坏，代理收集器不能够正常运行，可以使用一个替代解决方案。
For situations when, for example, the agent collector cannot be run because the connectivity between the workbench and agent is compromised, an alternate solution is available.
通过将你的表意识的注意力全心投入于一个复杂问题的解决方案中，你的潜意识收集了所有的必要信息，并且全面将之呈送给你的表意识。
By giving your conscious attention and devotion to the solution of a perplexing problem, your subconscious mind gathers all the necessary information and presents it full-blown to the conscious mind.
任何项目的需求收集过程都应该结合操作方面，它们量化了解决方案的可接受性能标准。
The requirements gathering process of any project should incorporate operational aspects that quantify acceptable performance criteria of the solution.
在大多数情况下，问题归结为组织远在解决方案需求收集之前就分配其预算了，更不用提很好地了解了。
In most cases, the issue comes down to the fact that an organization allocated its budget long before the solution requirements were even collected, let alone well understood.
表面上，众包看上去好像很简单——向公众提出问题，收集他们的点子，然后让他们投票选出给最佳方案。
On the surface,crowdsourcing seems easy – shout a question out to the crowd, get their ideasand allow them to vote on the best.
在开发所有OLAP解决方案时，首先应该收集并分析顾客的业务需求。
All OLAP solutions should begin with collecting and analyzing the customer business requirements.
另外请记住，您所使用的电子邮件解决方案也将影响能够收集到的信息。
Also bear in mind that the E-mail solution that you are using also affects the information that can be gleaned.
解决方案创建过程中另一项重要输入是收集来的现有资产，即先前针对类似客户场景所作的提案。
Another key input to the solution creation is harvesting of existing assets; that is, previous proposals for similar customer scenarios.
在某些情况下，这些决定将包括折衷方案，但是通过收集适当的需求并对其确定优先级，这些选择中的许多都将是明显的、容易证明其合理性。
In some cases these decisions will involve trade-offs, but with proper requirements gathering and prioritization, many of these choices will be obvious and easily justified.
在某些情况下，这些决定将包括折衷方案，但是通过收集适当的需求并对其确定优先级，这些选择中的许多都将是明显的、容易证明其合理性。
In some cases these decisions will involve trade-offs, but with proper requirements gathering and prioritization, many of these choices will be obvious and easily justified.
应用推荐