要有效地为组织进行设计，您需要获得组织中某种级别的信任。
To effectively design for an organization, you need a certain level of trust in it.
您需要导航到上一个级别才能再次看到流程。
You needed to navigate up one level to see the process again.
在这个级别，您考虑的是通过从应用程序到云的连接传送的实际字节。
At this level, you are concerned with the actual bytes that go across the connection from the application to the cloud.
尽管这种情况并不常见，但您应该注意内核级别的这类潜在问题。
While this is not typical, you should be aware of such potential problems at the kernel level.
可以围绕性能目标构建管理(主要)，但是您需要某种级别的基础设施和工具才能度量性能。
Governance can be built around performance goals (primarily), but you need some level of infrastructure and tooling to measure performance.
此类软件还允许您深入各个粒度级别，以帮助将问题分离出来。
Software like this also lets you drill down to granular levels to help isolate problems.
当您降低抽象级别的时候，表现相同的事物则需要使用更多的元素。
As you move down abstraction levels, you would need more elements to represent the same thing.
在战术级别，您的开发人员可能会绞尽脑汁来保护此表单的安全。
At a tactical level, your developers may do all the smart things to secure this form.
在这个级别，您专注于业务对象。
在您具有内容过滤级别的情况下是可以使用个性化的。
Personalization is possible in the sense that you have content filtering level.
在应用升级时，您需要首先安装基本级别的文件集。
When applying an upgrade, you need the base level of the filesets installed first.
仔细考虑您所需的可靠性级别。
问：您如何确定每个问题的难度级别？
Q: How do you determine the level of difficulty for each question?
从应用程序架构级别而言，您同样要考虑概念和行为。
At the application architecture level, again, you want to think of nouns and verbs.
另一方面，如果这个服务的确需要极其高的运行级别，您需要为您最初的SOA选择一个或者一套不同的服务。
On the other hand, if this service does need that extreme operational level, you may need to choose a different service or set of services for your initial SOA.
主要原因是因为在SIMM级别4，您只关心通过标准化协议和传输公开请求。
This is mostly because at SIMM level 4, you are focused only on exposing requests over standardized protocols and transports.
您要能够为您的服务确定运行级别：应答时间、启动时间，当前用户的平均数量等等。
You need to be able to define operational levels for your services: response time, up time, average number of concurrent users, and so on.
如果您的CFCC级别不同，此值可能会有变化。
您还应该检查您的固件级别，以确保它们是最新的。
You should also check your firmware levels to make sure they are up-to-date.
使用这个级别的时候，您无法知道基础服务是SOAP或REST，仅仅是调用服务。
Working at this level, you have no idea whether the underlying service is SOAP or REST; you simply invoke the service.
无论您选择哪种运行级别，这个文件都会包含在实例引导时运行的命令，因此可用于运行rds。
Regardless of the run level you choose, this file contains commands that are launched at boot time of the instance and therefore can be hooked to launch RDS.
如果需要，还可以使用一个命令将迁移回滚到您选择的以前级别。
Should you need it, it is also possible to rollback a migration to a previous level which you select, again with a single command.
BrokerExplorer允许您设置不同的跟踪级别。
您希望将登录级别更改为trace来提高控制台的输出量。
You'd like to reset the log level to trace to increase the amount of console output.
您还可以让您的日志级别更细粒度一些，仅在某些功能中通过指定想要记录的类别来增加详细程度。
You can also be more granular with your log levels, increasing verbosity only in certain features by specifying which class you want to log. These classes are
比如，V8.2中的HADR功能允许您选择三种级别的数据保护。
For example, the HADR feature in DB2 V8.2 allows you to select three levels of data protection.
如果使用级别在您的应有级别之内，那么不需要做任何事情，您可以继续操作，在下一个季度中提交接下来的使用报告。
If the use level is within your entitlement level, then nothing needs to be done and you go on with operations, submitting the next use report the following quarter.
如果您是应用程序供应商，那么您同时需要支持多种修复级别，以便您的客户能够将您的软件与其他软件一同运行。
If this is you, then you need to support multiple fix levels at the same time so that your customers can run your software in conjunction with other software.
因而对于一次给定的运行，如果您打算改变想要记录的详细级别，那么您只需改变过滤器。
Thus, for a given run, if you change your mind about the level of detail you want, you just have to change your filter.
在这个准备阶段，您开始确定高级别的变化计划。
In this preparation stage, you start to define the high-level change program.
应用推荐