业务分析人员和应用程序分析人员不使用同一种语言(例如，UML)来将它们的系统形式化。
Business analysts and application analysts do not use the same language (such as UML) to formalize their systems.
在一个实验中，研究人员开发了一个应用程序来分析白日梦和幸福之间的关系。
For one experiment, researchers developed an app to analyze the relationship between daydreaming and happiness.
随后，研究人员利用一种叫做“因素分析”的复杂统计程序分析受试的饮食习惯。
The researchers then used a complex statistical procedure called "factor analysis" to analyze subjects' dietary habits.
此外，分析人员认识到，使用当前的程序，门卫也可以获得停车位。
In addition, the analyst realizes that a janitor could get a parking space with the current procedure.
这些是OO设计人员用来构成分析、设计和实现的工具，但它们并不是使程序面向对象的主要部分。
These are tools that the oo designer puts to use in order to structure the analysis, the design, and the implementation, but they aren't central to what makes an oo program object-oriented.
研究人员开发了一个计算机的程序，可用来分析符合这种图案的宇宙微波背景（CMB）的观测结果。
The researchers developed a computer algorithm to analyze CMB observations for patterns that would fit.
这种工作的划分模仿了典型应用程序开发中分析人员与开发人员之间的分工。
This division of work mimics the division of work between the analyst and the developer in typical application development.
如您如见，在脚本语言中定义业务规则可以使规则的编写更加轻松，并且更易于程序员之外的人员阅读，比如说业务分析师或规则编写人员。
As you'll see, defining the business rules in a scripting language makes the rules easier to write, and probably easier for a nonprogrammer, such as a business analyst or rule writer, to read.
但是运行时分析则是一种应用于整个应用程序的方法，它可以由测试人员或者开发人员进行，或者二者都进行。
Runtime analysis, on the other hand, is an approach that applies to the entire application, and it can be performed by developers or testers, or both.
当面临一个业务流程方面或者系统资源利用效率低的问题时，每个程序员、系统管理员、数据库分析人员都知道应该怎么做。
Every programmer, systems administrator, database analyst, and so on knows what to do when they face a problem with business process or some inefficiency utilizing systems resources.
进一步的分析有几种选择：研究示例文件、会见用户、创建测试案例，或者——在最好的情况下——和应用程序开发人员交谈。
To continue the analysis, you have many options: study sample files, interview the user, create test cases, or — in the best cases — talk to the application developer.
获取这种计数器随时间的测量可以帮助分析人员发现系统的瓶颈，并且调整系统或应用程序的性能。
Capturing the measurements of such counters over time assists analysts to discover system bottlenecks and fine-tune a system or an application's performance.
如何使各组件去耦是应用程序系统分析员和开发人员们共同面对的一个棘手问题。
One of the most common pains that application architects and developers have to deal with is to achieve decoupling of the components.
让业务分析人员提供其预期应用程序将处理的用例。
Have your business analyst provide the use cases they expect the application will process.
它是否需要有着很多混合能力和技能的工作人员，而不仅仅只是少数分析人员和程序员？
Will it require people with a broad mix of capabilities and skills rather than just a few analysts and programmers?
数学是程序员和分析人员的流行主题，从而导致了大量不同的工具可供选择。
Math is a popular topic with programmer and analyst types, leading to a huge diversity of tools to choose from.
并非所有开发人员都是安全专家，但所有开发人员都应该了解足够多的知识，执行某些基本的网络和流量分析，并在其应用程序内构建基本的安全性。
While not every developer can be a security expert, all developers should know enough to perform some basic network and traffic analysis and to build rudimentary security into their applications.
如果是这样，您可能已经注意到开发人员(或业务分析人员)在IDE中拖动组件来构建应用程序的基本内容的方便性。
If so, you probably noticed the ease with which a developer (or business analyst) can build up the fundamentals of an application by dragging components around the IDE.
WDPE 提供的工具为业务分析师和集成开发人员提供了一个丰富的开发环境来建模、设计和组建应用程序。
The tools provided with WDPE provides a rich development environment for business analysts and integration developers to model, design and assemble applications.
UIMA应用程序可能分析纯文本并识别人员、位置和组织；它也可能识别关系，比如为谁工作或在什么地方工作。
A UIMA application might analyze plain text and identify entities such as persons, places, and organizations; or it might identify relationships, such as works-for or located-at.
软件行业已经长期应用在组织图中将“经理”放在“程序设计人员”和“软件质量保证分析人员”之上的层次。
The software industry has long applied a hierarchy that puts "manager" above "programmer" and "software quality assurance analyst" on the organizational chart.
获得了模型后，分析人员就能够确定进行改进的机会、提出更改建议，并能够预估更改对 COATS应用程序的影响。
With the model in place, the analysts were able to identify opportunities for improvement, propose changes and estimate a projected impact of the changes on the COATS application.
规则外部化使得业务分析人员和其它非技术用户可以更改策略而不需要改变流程逻辑和重新发布应用程序。
Externalizing the rules allows business analysts and other less-technical users to modify policies that have been defined without changing the process logic and without re-deploying the application.
这就意味着一个专家级的程序员——或者测试人员、分析师——可能有一个处于“胜任”阶段，甚至更有可能在“高级初学者”阶段的上司。
This means an expert programmer - or tester or analyst - will have a boss who is at best competent and most likely an advanced beginner.
按位逻辑对于普通程序员和分析人员非常复杂。
Bitwise logic is complex for ordinary programmers and analysts.
如果开发人员需要进一步查看应用程序在运行时是如何交互的，那么他们可以使用运行时分析特性来描绘他们的应用程序。
If developers need to further see how the application reacts at runtime, they can use the runtime analysis feature to profile their application.
在这个场景下，通过使用BuildForge，开发人员在他们的代码或组件中运行分析规则去找到并发现问题，而开发经理可以在基于代码的应用程序系统上运行一组标准的规则集。
In this scenario, developers run analysis rules to find and fix problems in their component code and the development manager runs a standard rule set on the application code base using Build Forge.
业务流程设计人员使用IntegrationEdition指定用于流程中人员分析的MemberManager 人员插件提供程序
The business process designer uses Integration Edition to specify that the Member Manager staff plug-in provider be used for staff resolution within the process
开发迭代产生应用程序的可部署工作版本(应用程序的工作构建)后，业务分析人员可以通过跟踪关键性能指标(Key Performance Indicator,KPI)来监视系统的实时性能。
After a development iteration produces a deployable, working build of the application, business analysts can monitor the live performance of the system by tracking key performance indicators (KPIs).
本文为关注Linux的用户分析了 Linux 2.6的一些重要特性，并且讨论了驱动程序开发人员可能会感兴趣的多方面的变化。
This article analyzes some of the key features of Linux 2.6 for the avid Linux user, and discusses various changes that might be of interest to driver developers.
应用推荐