文章目录
- 一、前言
- 二、常用名词
- 三、架构风格
- 四、非功能需求
- 五、应用架构
- 六、软件架构重用
一、前言
笔记目录大纲请查阅：【软考速通笔记】系统架构设计师——导读
二、常用名词
| 名词 | 翻译 |
|---|---|
| architecture | 架构 |
| system | 系统 |
| design | 设计 |
| requirements | 需求 |
| components | 组件 |
| constraints | 约束 |
| models | 模型 |
| properties | 属性 |
| styles | 风格 |
| connector | 连接器 |
| environment | 环境 |
| information | 信息 |
| data | 数据 |
| process | 过程 |
| hardware | 硬件 |
| software | 软件 |
| specifications | 规范 |
| types | 类型 |
| performance | 性能 |
| security | 安全 |
| abilities | 能力 |
| countries | 国家 |
| application | 应用 |
| technologies | 技术 |
| outline | 大纲 |
| construction | 构造 |
| implementation | 实施 |
| details | 细节 |
| logical | 逻辑的 |
| DFD | 数据流图（Data Flow Diagram） |
| ERD | 实体关系图（Entity Relationship Diagram） |
| data flow | 数据流 |
| general | 总体的 |
| standards | 标准 |
| objectives | 目标 |
| feasibility | 可行性 |
| techniques | 技术 |
| physical | 物理的 |
| network | 网络 |
| processors | 处理器 |
| stores | 存储 |
| distribution | 分布 |
| options | 选项 |
| servers | 服务器 |
| tables | 表 |
| database | 数据库 |
| construction activity | 构建活动 |
| elements | 元素 |
| relations | 关系 |
| 名词 | 翻译 |
|---|---|
| defines | 定义 |
| determines | 确定 |
| developed | 发展 |
| refine | 细化 |
| employed | 采用 |
| select | 选择 |
| placed | 放置 |
| decide | 决定 |
| develop | 开发 |
| focus | 聚焦 |
| protect | 保护 |
| specifies | 指定 |
| serves | 服务 |
| include | 包括 |
| distribute | 分发 |
| create | 创建 |
| constrained | 受限 |
| drawn | 绘制 |
| partitioning | 分区 |
| replication | 复制 |
| support | 支持 |
| record | 记录 |
| connect | 连接 |
| involves | 涉及 |
| analyzing | 分析 |
| construct | 构建 |
| converts | 转换 |
| storage | 存储 |
三、架构风格
An architectural style defines as a family of such systems in terms of a pattern of structural organization.
一种架构风格以一种结构化组织模式定义一组这样的系统。
More specifically, an architectural style defines a vocabulary of components and connector stypes, and a set of constraints on how they can be combined.
更具体来说，一种架构风格定义了一个构件和连接器类型的词汇表，以及一组关于它们如何组合它们的约束。
For many styles there may also exist one or more semantic models that specify how to determine s system’s overall properties form the properties of its parts.
对于许多风格来说，可能也存在一个或者多个语义模型，从系统部件的特性来确定系统的整体特性。
Many of architectural styles have been developed over the years.
许多架构风格已经发展很多年了。
The best-known examples of pipe-and-filter architectures are programs written in the UNIX shell.
用UNIX shell编写的管道-过滤器架构就是最出名的例子。
四、非功能需求
The architecture design specifies the overall architecture and the placement of software and hardware that will be used.
架构设计明确规定了需要被使用的软件和硬件和总体架构。
Architecture design is a very complex process that is often left to experienced architecture designer and consultants.
架构设计是非常复杂的过程，往往留给经验丰富的架构师和顾问。
The first step is to refine the nonfunctional requirements into more detailed requirements that are then employed to help select the architecture to be used and the software components to be placed on each device.
第一步去定义非功能性需求细化为更详细的要求，然后用于帮助选择要使用的体系结构和要放置到每个设备中的软件组件。
In a client-based architecture, one also has to decide whether to use a two-tier, three-tier, or n-tier architecture.
基于客户端的架构中，还必须决定是使用两层、三层还是n层架构。
Then the requirements and the architecture design are used to develop the hardware and software specification.
然后使用需求和架构设计来开发硬件和软件规范。
There are four primary types of nonfunctional requirements that can be important in designing the architecture.
在架构设计中有4种主要的非功能性需求可能很重要。
A operational requirements specify the operating environment(s) in which the system must perform and how those may change over time.
操作要求指定系统必须执行的操作环境以及这些环境如何随时间变化。
Performance requirements focus on the nonfunctional requirements issues such as response time, capacity, and reliability.
性能要求主要侧重在非功能性需求问题，例如响应时间、容量和可靠性。
Security requirements are the abilities to protect the information system form disruption and data loss, whether caused by an intentional act.
安全需求是指有能力保护信息系统免受破坏和数据丢失的能力。
Cultural and political requirements are specific to the countries in which the system will be used.
使用该系统的国家明确文化和政治要求。
五、应用架构
An application architecture specifies the technologies to be used to implement one or more information systems.
应用架构说明了实现一个或者多个信息系统所使用的技术。
It serves as an outline for detailed design, construction, and implementation.
它作为详细设计、构造和实现的一个大纲。
Given the models and details, include logical DFD adn ERD, we can distribute data and processes to create a general design of application architecture.
给一个模型和详细资料包括逻辑数据流图和实体联系图，我们可以分发数据和流程，来创建应用程序架构的总体设计。
The design will normally be constrained by architecture standards, project objectives, and the feasibility of techniques used.
这个设计通常会被架构标准、项目目标和被使用的技术的可行性等因素的约束。
The first physical DFD to be drawn is the network architecture DFD.
第一个绘制的物理数据流图是网络架构数据流图。
The next step is to distribute data stores to different processors.
下一步是分发数据到不同的处理器。
Data partitioning and replication are two types of distribution data which most RDBMSs support.
数据分区和复制是大多数关系型数据库支持的两种分布式数据形式。
There are many distribution options used in data distribution.
有许多分配方法用于数据分布。
In the case of storing specific tables on different servers we should record each table as a data store on the physical DFD and connect each to the appropriate server.
在不同服务器上存储特定表的情况下，我们应该将不同表记为物理数据流图中的数据存储，并将其连接到相应的服务器。
六、软件架构重用
Software architecture reconstruction is an interpretive, interactive, and iterative process including many activities
软件架构重用是一个解释性、交互式和反复迭代的过程，包括了多项活动。
Information extraction involves analyzing a system’s existing design and implementation artifacts to construct a model of it.
信息提取需要分析系统现有的设计和实现来构造它的模型。
The result is used in following activities to construct a view of the system.
这个结果用于后续活动构造系统的视图。
The database construction activity converts the elements and relations contained in the view into a standard format for storage in a database.
数据库构建活动将视图中包含的元素和关系转换为标准格式，以存储在数据库中。
若觉得文章对你有帮助，随手『点赞』、『收藏』、『关注』，也是对我的支持。