Software design architecture based on

 

Software Design (Architecture-Based Software Design, ABSD) based architecture is an architecture-driven approach. This approach has three basic:

(1) separation function. In functional decomposition, ABSD methods of using existing technology based cohesion and coupling modules.

(2) to implement quality and business needs by selecting architectural style.

(3) use the software templates. Use of some software template structure of the software system.

ABSD input method consists of the following components:

(1) abstract functional requirements, including changing needs and requirements of common;

(2) Example (actual functional requirements);

(3) the abstract quality and service requirements;

(4) the quality factor (actual quality and service requirements);

(5) architectural options;

(6) constraints.

Architecture requirements

User demand is the expectation of the target software system in terms of function, behavior, performance, design constraints and the like. Process is mainly needs to obtain the user needs to use the system to identify the member.

Requirements elicitation

Architecture requirements generally from three aspects, namely business objectives business objectives and systems development personnel system quality objectives, system.

Identification member

In FIG. 6-10 belong to the imaginary part of the frame member identification procedure, which generates an initial logical structure of a system, comprising a substantially member.

Needs assessment team organized a different representatives (such as analysts, customers, designers, testers) composed of architectural requirements and related components be carefully scrutinized. The main contents of the review, including whether acquired a true reflection of the needs of the user's requirements, grouping class is reasonable, members merger is reasonable.

Architecture design

Architecture used to stimulate demand and to adjust the design decisions, different views were expressed for information about the quality objectives. Architecture design is an iterative process.

Architecture documentation

Documentation is in the system at every stage of the evolution of communication media system design and development staff, is the basis for the verification architecture and refine or modify the design (if necessary) executed a pre-analysis.

The main output schema document process is the quality of architecture design specification requirements specification and test infrastructure requirements of these two documents. Accurate description of formal requirements model generating member, as between users and developers of a deal.

Architecture review

Architecture design, documentation and review is an iterative process. In this respect, after a major version of the software architecture analysis, to arrange for the participation of external personnel (user representatives and experts in the field) in the review.

复审的目的是标识潜在的风险,以及早发现架构设计中的缺陷和错误,包括架构能否满足需求、质量需求是否在设计中得到体现、层次是否清晰、构件的划分是否合理、文档表达是否明确、构件的设计是否满足功能与性能的要求 。

架构实现

所谓“实现”就是要用实体来显示出一个软件架构,即要符合架构所描述的结构性设计决策,分割成规定的构件,按规定方式互相交互。

虚框部分是架构的实现过程。整个实现过程是以复审后的文档化的架构说 明书为基础的,每个构件必须满足软件架构中说明的对其他构件的责任。

架构演化

在构件开发过程中,最终用户的需求可能还有变动。在软件开发完毕,正常运行后,由一个单位移植到另一个单位,需求也会发生变化。

Guess you like

Origin blog.csdn.net/q947448283/article/details/91953529