In contemporary architecture practice, proficiency in an ever-widening array of architecture software is becoming increasingly important.
在当代建筑实践中，精通一系列不断发展壮大的建筑软件变得越来越重要。
It is a common problem for the designer to exchange data in different layers and use which kind of granularity in multi-layers architecture software system.
在多层架构的分布式软件系统中，如何在层间交换数据，采用何种粒度的对象交换数据，是系统构建时经常遇到的问题。
What do you see as the future of software architecture documentation?
你认为软件架构文档的未来会是什么样？
In this article, you learned about the system context view of software architecture.
在本文中，您了解了软件架构的系统上下文视图。
Architecture in software is one of the most talked about yet least understood concepts that developers grapple with.
软件中的架构是开发人员谈论最多但是最难理解的概念之一。
Enterprise architecture (EA) is not software code.
企业结构(EA)并不是软件代码。
In this new series, learn why and how you should document software architecture.
在这个新的系列中，了解为什么以及应该如何编写软件架构文档说明。
Software architecture can be used recursively.
软件架构可以递归地使用。
Various researchers have interpreted what software architecture is, and they have different viewpoints on how to best represent the architecture of a software system.
不同的研究人员已解释了软件架构是什么，并且他们对有关如何最好地表示软件系统的体系结构具有不同的观点。
An outline description of the software architecture, including major software components and their interactions.
软件架构概要描述，包括主要的软件组件及其之间的交互。
Read a compendium of published software architecture definitions.
阅读已发布的软件架构定义的纲要。
The architecture binds a software component to its external properties.
体系结构将软件组件与其外部属性绑定在一起。
In addition, because the project is focused now on requirements and software architecture, the software project manager is responsible for compiling a risk list.
除此之外，由于项目已进入到关注需求和软件架构的阶段，此时软件项目经理有必要编写一份风险列表。
In this series, you will learn about documenting software architecture.
在本系列中，您将了解如何编写软件架构文档说明。
The activity ends with a review of the resulting architecture, as documented in the Software architecture document.
此活动以最终架构的评审作为结束，在软件架构文档中进行文档化。
In Part 1 of this series you explored the fundamentals of software architecture.
在本系列的第1部分中，我们了解了软件体系结构的基础知识。
This series begins by describing software architecture and defining the place of services within software architecture.
本系列开始将介绍软件架构，并确定服务在软件架构中的位置。
Evaluating software architecture is an important part of enterprise architecture (EA).
软件架构评估是企业架构(EA)中重要的一部分。
The software architecture also ACTS as a record of the decisions made.
软件体系结构还可以作为决策制定的记录。
Address the architecture, infrastructure, software, and related business services as a cohesive unit.
将架构、基础设施、软件以及相关业务服务作为一个内聚单元。
A key goal of business architecture is to demonstrate the business value of the software architecture.
业务体系结构的主要目标是展现软件体系结构的业务价值。
System architecture primarily comprises software elements and the relationships among them.
系统体系结构主要由软件要素和它们之间的关系组成。
Software architecture, as a discipline, is mature.
作为一门学科，软件架构是非常成熟的。
Software architecture has been around for more than 30 years.
软件架构已经存在30多年了。
Reuse is critical to both software architecture and SOA.
重用对软件体系结构和SOA都非常重要。
Layering is probably the simplest way to discuss software architecture.
用来讨论软件架构好坏的最简单的方法要属分层了。
Level Seven: The organization now has dynamically re-configurable software architecture.
第七级：组织现在已经拥有可动态重新配置的软件架构。
Recover the architecture of the software.
恢复软件的架构。
Ideally, these views map to the 4 + 1 views of software architecture outlined in the RUP (see Figure 3) and embodied in the RUP's software architecture Document.
理想情况下，这些视图对应于在RUP中描述的软件体系结构4 +1视图(参见图3)，并且在RUP软件体系结构的文档中有具体表达。
As you expand your architecture, software revision history is critical.
在体系结构的扩展过程中，软件修订历史记录非常重要。
应用推荐