It is not uncommon for the PM to also play a solution architect or technical lead role.
PM担当解决方案架构师或技术领导角色是很常见的。
The Solution Architect considers how to maximize the reuse of it assets in different divisions.
解决方案架构师考虑如何最大化地重用不同部门中的IT资产。
The hardest job for the Solution Architect involves the components supporting the ESB topology.
解决方案架构师最艰巨的任务是提供支持 ESB 拓扑的组件。
Only the solution architect can decide what level of coupling is tolerable for a particular system.
只有解决方案架构师能够决定一个特定的系统能够容忍什么程度的耦合性。
Marc Dutoo is Open Source solution architect at Open Wide, a leading French Open Source portal integrator.
MarcDutoo是OpenWide的开源解决方案架构师，该公司是法国领先的开源门户集成商。
But third, the solution architect must be cognisant of the overarching business and it architecture responsibilities.
而第三，解决方案架构师必须认识到承担的全盘业务与IT体系结构责任。
He gets to wear many hats, from business development manger and evangelist to solution architect and contract negotiator.
他有很多头衔，从业务开发经理和宣传者到解决方案设计师和合同谈判代表。
Slightly afterwards, your software-architect or service-architect starts designing an appropriate solution architecture.
然后，你的软件架构师或服务架构师开始设计一个合适的解决架构。
Architect Responsible for end-to-end solution architecture, which includes ensuring requirements are achievable and deliverable.
架构师对末端到末端的方案结构负责，它可以确保需求是可以达到的及可以交付的。
Even inside the same organization, different departments can use modified interpretations of the roles (for example, solution architect compared with software architect).
即使在同一组织内部，不同的部门对角色的诠释也可能不同(例如解决方案架构师与软件架构师对比)。
The project team (including the project manager, business analysts, solution architect, developers, and testers) should evaluate and validate the development tool being used.
项目团队(包括项目经理、业务分析人员、解决方案架构师、开发人员，和测试人员)应该评估并验证正在使用的开发工具。
Therefore, the Integration Architect responsible for solution design must consider operational differences between endpoint systems, such as availability and concurrent processing capability.
因此，负责解决方案设计的集成架构师必须考虑到端点系统之间的操作差异，比如可用性和并行处理能力。
The software Architect is responsible for dividing the required function between the components that make up a software solution.
软件架构师负责将所需的功能划分为组成软件解决方案的组件。
The design solution that overcomes these incompatibilities and facilitates the synchronization of data is the responsibility of the Integration Architect.
集成架构师需要设计出能够解决这些不兼容性并实现数据同步的解决方案。
On the contrary, an enterprise architect must be involved in helping customers understand their real needs (as opposed to wants) and to work with them throughout the implementation of a solution.
反之，企业架构师必须帮助客户了解他们真正的需求(对照想要的)，并且在解决方案的实现过程中与客户合作。
For example, an architectural overview is used by the software architect to present the solution to users, managers, projects sponsors, or project managers.
例如，软件架构师使用体系结构概述向用户、管理人员、项目赞助商或者项目管理人员展示解决方案。
In cases where choices at the it level conflict with architectural specifications, the developer should negotiate a solution change with the architect.
当IT级别的选择与架构规范发生冲突的时候，开发人员应当与架构师协商对解决方案的修改。
The architect is, clearly, most heavily involved in core architecture activities in terms of defining a solution to the defined requirements.
显然地，架构师涉及最深的核心体系架构活动就是定义一个需求的解决方案。
In this tutorial, Part 2 of the series, we discuss how you can leverage your own custom pattern implementations in Rational Software Architect to automate the design of an SOA solution.
在本教程中，系列的第2部分，我们将讨论您如何能够利用Rational Software Architect中您自己的定制模式实现来自动地设计SOA解决方案。
It shows how you can leverage your own custom templates and profiles in Rational Software Architect to automate the design of an SOA solution.
它向您展示了如何能够利用您自己的定制模板和概要文件，在Rational Software Architect自动地设计SOA解决方案。
We show how you can leverage your own custom templates and profiles in Rational Software Architect to automate the design of an SOA solution.
我们介绍了您可以如何利用RationalSoftware Architect中您自己的定制模板和概要文件，将SOA 解决方案的设计自动化。
The remaining articles in this series provide details regarding how to use Rational Software Architect to automate service solution modeling and development.
本系列文章其余部分将详细介绍如何使用Rational Software Architect进行自动化的服务解决方案建模和开发？
In this tutorial, Part 3 of the series, we discuss how you can leverage your own custom transformations in Rational Software Architect to automate the design of an SOA solution.
在本教程中，也即系列的第3部分，我们会讨论，怎样在Rational Software Architect中，利用我们自定义的转换来自动设计一个SOA方案。
In this tutorial, Part 4 of the series, we discuss how you can use your own custom transformations in Rational Software Architect to automate the design of an SOA solution.
在本篇教程中，系列的第4部分，我们会讨论，怎样在Rational Software Architect中，利用我们自定义的转换，来自动设计一个SOA方案。
Rational Software Architect uses the Reusable Asset Specification (RAS) to provide a standard way to package and consume (use) assets that provide a solution to a problem for a given context.
RationalSoftware Architect利用可复用的资产规范（Reusable Asset Specification，RAS）来提供标准的方法打包并消耗（使用）向已知环境提供问题解决方案的资产。
Article 5 describes how service models built using Rational Software Architect can be used to accelerate the creation of valuable service solution artifacts.
第5篇文章介绍了使用Rational Software Architect构建的服务模型可如何加速有价值的服务解决方案工件的创建。
Part 5, the remaining article in this series, describes how service models built using Rational Software Architect can be used to accelerate the creation of valuable service solution artifacts.
第5部分是本系列的最后一篇文章，其中将介绍使用Rational Software Architect构建的服务模型可如何加速有价值的服务解决方案工件的创建。
Article 5 describes how service models built using Rational Software Architect 8.0 can be used to accelerate the creation of valuable service solution artifacts.
第5篇文章将介绍使用Rational Software Architect 8.0创建的服务模型可以如何用来加速有价值的服务解决方案工件的创建。
This is done by using business models, built using Rational Software Architect and other IBM tools, to drive service discovery and service solution development.
这是通过使用业务模型实现的，通过使用Rational Software Architect和其他IBM工具构建的，旨在促进服务发现和服务解决方案开发。
Rational Rose solution, with models that contain Petal version 47, 48, or 50, which are the only versions that you can import into your Software Architect environment.
RationalRose方案，模型包含了PetalVersion47、48或者50，它是您可以导入到Soft wareArchitect环境的唯一版本。
应用推荐