In a process-centric architecture, the application is developed for the process.
在以流程为中心的体系结构中，应用程序是为过程开发的。
For example, if your SOA entry point is business centric, you can defer loose coupling via the ESB, even though the ESB is included in your reference architecture.
例如，如果SOA入口点以业务为中心，您可以推迟通过ESB实现的松散耦合，尽管您的参考体系结构中包括了ESB。
Software architecture competence is the ability of an individual or organization to acquire, use, and sustain the skills and knowledge necessary to carry out software architecture-centric practices.
软件架构能力是个人或组织获取、使用、胜任对开展以软件架构为中心的实践来说必不可少的技能和知识。
Given its RUP roots, it provides a process that is iterative and incremental, use-case driven, risk-driven, and architecture-centric, which at the same time supports the work habits of agile projects.
有RUP做根基，它能提供迭代式、递增的、用例驱动、风险驱动和以架构为中心的过程，同时也支持敏捷项目的工作习惯。
These patterns are summarized below and considered in the architecture of a business process-centric PaaS framework.
这些模式总结如下，在业务流程为中心的PaaS框架架构中进行考虑。
Part 4 of this series discusses planning for growth in your application architecture by showing you how to focus on customer-centric business strategies using scalable and adaptive thinking.
本系列的 第 4部分讨论了如何规划应用程序体系结构的增长，向您展示了如何使用可伸缩和自适应思想来集中于以客户为中心的业务策略。
In particular, the backbone of RUP, an architecture-centric and iterative development process, is highly consistent with MDA concepts and offers an excellent basis for succeeding with MDA.
特别是，RUP的灵魂，即以体系架构为中心的迭代的开发过程，与MDA概念保持高度一致，并为在MDA方面取得成功提供极好的基础。
The exchange of information is done by using a data-centric publish-subscribe architecture that loosely couples components, thereby enabling anonymous exchange of data between disparate systems.
信息的交换是使用数据中心的结构完成的，该结构有松散耦合的构件，因此支持在分隔系统之间交换数据。
It was essential that the new process be iterative, architecture-centric, and requirements-driven, features that existing systems were short on.
重要的是新的过程具有迭代的、以构架为中心的，以及需求驱动的特征，而这些特性是已有系统所不具备的。
The architecture-centric approach promoted by RUP leads to careful consideration and selection of various applicable architectures.
RUP倡导的以体系架构为核心的方法导致了对各种应用结构的仔细考虑和选择。
An ESB-centric mainframe integration solution leverages these advantages by building on the ESB architecture.
以esb为中心的大型机集成解决方案通过建立在ESB架构之上，充分利用了这些优势。
Siloed approaches were abandoned in favor of an architecture-centric approach supported by SOA principles.
为了支持由SOA原则支持的“以架构为中心”方式，所有的筒仓方式都被抛弃。
This article illustrates an iterative, risk-driven, architecture-centric, and quality-driven approach to method development.
这篇文章描述了一个迭代的、风险驱动的、以构架为中心的，以及面向质量的方法开发的方法。
Figure 3 depicts the architecture of a business process-centric PaaS framework for industry solutions to support all three of the above integration patterns.
图3描述了行业解决方案的业务流程为中心的PaaS框架架构，用于支持上述的三个集成模式。
However, the path toward learning Zachman may strongly benefit from the application of some core RUP principles, such as "requirements-driven," "architecture-centric," "model-driven," and "iterative."
尽管如此，学习Zachman的方法可能主要受益于一些RUP主要原则——例如，“需求驱动”、“以构架为中心”、“模型驱动”和“迭代”——的应用。
In this article we advocate a new, ESB-centric, view of mainframe integration and we introduce LegStar for JBoss ESB, an open source solution that implements such an architecture.
本文中，我们将提倡一种以esb为中心的大型机集成的新观点，同时也将介绍一种实现这个架构的开源解决方案，即在JBossESB中使用LegStar实现大型机整合。
REST-style architecture embraces both SOA and the Web, enabling a component-centric model in which various server-side and client components can be reused in a scalable yet simplistic way.
REST 样式的体系结构同时采用 SOA和Web，支持以组件为中心的模型，其中各种服务器端和客户端组件通过可扩展而简单的方式进行重用。
As a process framework, RUP is iterative, architecture-centric, and use-case driven. This is incorporated into the six RUP principles.
作为过程框架，RUP是迭代的、以架构为中心的，并且是用例驱动的。
According to the traditional PCs defect that the PCI bus forms the bottleneck of system communication, we propose the design of Parallel PC architecture for switching network centric.
针对传统的PCI总线结构形成系统通信瓶颈的缺陷，提出了以交换网络为中心的可扩展并行PC体系结构设计思想。
An open architecture design will add flexibility by shifting the focus of the control systems from being hardware-centric to more software-centric.
采用开放式架构设计将重点从硬件设计转向以控制系统为中心的系统设计，同时也增加了软件设计的灵活性。
A dialogue centric cognitive control architecture is presented, which utilizes both agent-oriented programming and formal methods.
首先给出一个以会话为中心采用面向代理编程和形式化方法的认知控制体系结构。
Key ideas of RUP are use case driving, iteration of architecture-centric and incremental development.
本文归纳了RUP的主要核心思想为：用例驱动，以构架为中心的迭代和增量开发。
Key ideas of RUP are use case driving, iteration of architecture-centric and incremental development.
本文归纳了RUP的主要核心思想为：用例驱动，以构架为中心的迭代和增量开发。
应用推荐