您如何能够可靠地度量并比较组件或项目？
How can you reliably measure and compare between components or projects?
另外一些人选择将可能比较频繁变更版本的组件—例如代码列表—放入单独的架构文档中。
Others choose to put components that might be versioned more frequently-for example, code lists-into a separate schema document.
虽然它们都在极其不同的编程和组件模型中运行，但是它们仍然能够比较无缝地与对方进行对话。
Both are running in very different programming and component models but are able to talk to each other relatively seamlessly.
例如，下面这些操作将非常简单：执行验证，在GUI组件中找到一些错误，比较之前运行的代码以发现何时引入了新错误。
For example, it would be a simple matter to perform a validation, find a number of errors in a GUI component, and compare against a previous run to find when the new errors were introduced.
如果希望查明哪个组件的缺陷比较多，只需按照组件名称对所有缺陷进行分组并统计数量。
If you want to figure out which component has more defects, you can simply group all the defects by the component name and do a count.
在实际实现应用程序组件时，每个组件的逻辑都比较陌生。
The logic of each component of your application is freshest when you are actually implementing those components.
让AT阅读器明了这些关系，可以使它增强组件组的表示，从而将比较复杂的信息传递给用户。
By making these relationships apparent to an at reader, you enable it to enhance its presentation of the group, thereby conveying more complex information to the user.
体系结构评估中的一项主要活动就是区分已经完全了解的内容和尚比较模糊的内容——并理清未知组件的潜在复杂性。
A key activity in architectural estimation is differentiating between what's understood completely and what's ambiguous — and to clarify the potential complexity of the unknown components.
尽管在时间压力下，通常情况是用简单的单件来连接各种各样的组件比较容易。
It is often the case, though, under time pressure, that simple Singletons make it easy to bridge large gaps between components.
组件图是比较容易理解的图之一，因此没有很多超越基础的内容。
The component diagram is one of the easier-to-understand diagrams, so there is not much to cover beyond the basics.
本文将KParts与其它组件模型(如CORBA)进行比较，并描述了KParts中使用的主要概念，包括操作、插件、部件管理器和GUI合并。
This article compares KParts with other component models, such as CORBA, and describes the main concepts used in KParts, including actions, plug-ins, part managers, and GUI merging.
集成测试一般比较完整，因为它们覆盖Rails应用程序中各个组件之间的高层交互。
Integration tests are generally more complete as they cover high-level interactions between various components within the Rails application.
sca与ejb组件之间存在三个要记住的重要比较点。
There are three important points of comparison between SCA and EJB components to remember.
“可用性”告诉您一个组件“运行(up)”相比较“停止(down)”的时间的百分比。
"Availability" tells you the percentage of the time that a component is "up" rather than "down".
MLVM中最有趣也是比较成熟的组件——invokedynamic，在刚刚过去的一个秋季中经过了不少横向修改。
MLVM's most interesting and more mature component, invokedynamic, has mostly undergone lateral changes since this past fall.
换句话说，facade可以简化客户端和服务提供者之间比较复杂的接口(甚至多个从属组件)。
In other words, a facade can simplify a more complicated interface between the client and the service provider (or even multiple subordinate components).
iSCSISAN的实现比较简单且便宜，因为它基于常用的标准组件。
The implementation of a iSCSI SAN is relatively simple and cheap because it is based on common standard components.
因为DataCapture andDelivery组件通常运行在用于储存和处理数据的资源比较有限的分布式平台中，所以必须将数据转发到服务器平台中。
Since the Data Capture and Delivery component typically runs in a distributed platform and has limited resources for processing and storing data, the data must be forwarded to a server platform.
对于用Spring框架开发并部署在Geronimo上的组件，比较容易进行单独的测试，因为这些组件与它可能依赖的组件已经去耦了。
Components developed with the Spring Framework and deployed on Geronimo are easier to test independently because they are decoupled from other components on whom they might have a dependency.
安全标签是按组件逐一比较的。
我们还将比较两个使用了EJB组件的方案，并将看到它们是如何被正确或错误地应用于实际的。
We also compare two projects that used EJB components and see how they have been properly, and improperly, applied in practice.
当需要为另一个组件上的某个动作提供静态值时，这个组件比较方便。
This component is handy when you want to provide a static value to an action on another component.
如果用户持有用于比较两个值的规则的豁免权，则不进行比较(换句话说，访问规则没有被应用到那个组件)。
If the user holds an exemption for the rule that is being used to compare two values, then that comparison is not done (in other words, access rule is not applied for that component).
我们对组件概念的定义是相对比较宽松的。
At that point the notion of components is defined relatively loosely.
由呈现程序生成的组件需要和我们迄今为止所讨论过的比较简单的组件一样，对于用户是可访问的，这意味着我们必须能够设置其可访问性值。
Components generated by the renderer need to be as accessible to the user as the simpler components we've discussed so far, which means we have to be able to set their accessibility values.
其能使用声明式服务分离组件以加入新的组件的功能，已被证明是建立连接的一种比较简单的方法。
Being able to decouple components whilst using Declarative Services to join the components proved a simple way to set up the connections.
如果上下文比较简单，将通过一个跨页面连接执行；否则，将使用一个聚合组件和一个页面切换组件执行操作。
If the context is simple, this could be through a cross-page wire; if it is not, an aggregation component could be used with a page-switching component to perform this action.
我比较喜欢的是它支持17种不同的组件，包括菜单、网格、树状结构和日历。
What I like about Lucid Spec is that it supports 17 types of widgets for screen design including Menus, Grids, Trees, and Calendars.
针对这些需求，EJB组件集能够客观地进行比较，从而找到针对实际应用情况的最佳方案。
Within a context of these kinds of requirements, the set of EJB components can be objectively compared; one will turn out to be the best to use for that aspect of the application.
比较老的版本需要各种额外组件。
应用推荐