Architecture Analysis
Architecture (Architecture) process analysis is the process of defining the system architecture of high-level organization structure and mechanism of the core, from the specific activities, architectural analysis mainly includes the following four aspects
- Alternatively, the system architecture is defined to describe high-level organization system to organize subsequent use case model
- Analysis to determine the mechanism to record the common problems in the system
- The core concept extraction system to reveal the key abstractions of the system must be able to handle
- Create use case analysis to achieve start
Alternative architecture
Architecture schema definition: "architectural patterns indicate an infrastructure of software systems"
1. Alternate mode architecture
| Software Category |
Architectural patterns |
Features and Uses |
| system software |
Layer ( Layer ) |
The system is divided into different levels of abstraction, each level of abstraction packaging issues of concern at different levels, in order to deal with different aspects of the system |
| Pipes and filters ( Pipes and the Filters ) |
Follow the system stream processing, data flows through the pipeline different filters, and finally obtaining the processing result |
|
| Blackboard ( the Blackboard ) |
Data structure for handling policy, by the central system data structures and the composition of independent processing means, operated by means of data |
|
| Distributed Software |
Client / server ( Client / Server ) |
In conventional client / server model, the server is responsible for monitoring and responding to client requests, the client actively connected to the server |
| Agent ( Broker ) |
Client and server communicate through an intermediate proxy, the coordination of operations between the client and the server by proxy |
|
| Peer ( the peer to the peer ) |
In equal status between nodes can be connected to each other; a central node is responsible for general management node discovery and resources |
|
| Interactive software |
Model - View - Controller ( the Model-View-the Controller ) |
The software abstraction into the model, view, three control member, which can effectively separate user logic and business logic to changing demands |
| Adaptive Software |
Reflection ( the Reflection ) |
Meta level applications into two portions and substantially level, element level information providing system properties, including the basic level application logic, which implements based on the meta level, which can dynamically change the system configuration to meet the basic level and behavior change |
| 微核（Microkernel） |
The isolated nuclei with minimal functionality and a particular client extension functions out to provide a "plug and play" software environment, so that the user easily connected to the core and extension portion thereof with integrated service systems; mainly used in different platforms have highly adaptable and can be customized to meet the system requirements |
2.BCE three-tier architecture
in
- Boundary class (Boundary Layer) is responsible for the interaction between the system and the participant i.e. UI interface P S: specifically for each class is generated on a boundary with participants and Example
- Control class (Control Layer) i.e. the system logic P S: specifically for each use case to generate at least one control class
- 实体类（Entity Layer ）是对系统业务中低端实体对象的归纳与抽象 即业务实体 PS：具体来说实体类代表了待开发系统的核心概念模型（使用实体类使数据库建立）
分析机制
1.架构机制
根据所关注的阶段和详细程度不同，共有三类架构机制，即分析机制、实现机制、设计机制
- 分析机制 以与实现无关的方式捕获解决方案的关键部分。它们可能表示行为模式或结构模式，或是同时表示这两者。它们主要用于在分析过程中向设计人员提供简短的表述。分析机制通常源于对一个或多个架构模式或分析模式的实例化
- 设计机制
- 实现机制
eg:
分析机制
设计机制
实现机制
持久性
关系型数据库
JDBC
面向对象数据库
Object Store
分布
远程方法调用
JAVA SE 6 MRI
安全性
RBAC身份认证
C++算法实现
2.确定分析机制
| 分析机制 |
特 征 |
含 义 |
| 持久性 |
粒度 |
单个持久对象的大小 |
| 容量 |
所需存储的持久性对象的个数 |
|
| 访问频率 |
对对象进行CRUD等操作的频率 |
|
| 访问机制 |
如何唯一的标识和检索对象 |
|
| 存储时间 |
对象需要保存的时间 |
|
| 分布 |
分布机制 |
分布式访问的方式或协议的约束 |
| 通信方式 |
同步或异步访问 |
|
| 通信协议 |
消息的大小、浏览控制、缓存等相关通信约束 |
|
| 安全性 |
安全规则 |
使用何种安全访问规则 |
| 授权策略 |
CRUD等其他操作权限 |
|
| 数据粒度 |
数据访问权限的粒度，如包级、类级、属性级 |
|
| 用户粒度 |
用户权限的定义级别，如单一用户、角色/分组用户 |
|
| 遗留接口 |
响应时间 |
要求的访问响应时间 |
| 持续时间 |
每次访问遗留系统的持续时间 |
|
| 访问机制 |
访问方式或协议 |
|
| 访问频率 |
访问遗留系统的频率 |
