Technical design review summary outline

[TOC]

Technical design review summary outline

Business products vary widely, there is no single methodology can complete architecture design and technical evaluation, system architecture design can only be expressed from some key points. Outline is a tool to help everyone to do architecture reviews to help you organize your thoughts and form a plan can be implemented, so when doing system design, can selectively refer to this outline, done according to the characteristics of a business can achieve effective architecture design.

The requirements specification and project technical research report, profiling software design, through technology seminars, system prototyping and other methods, formation design idea and design modeling software, drawing system design diagrams (including overall system architecture diagram, the system structure is divided in FIG. dynamic exchange relationship diagram, a flowchart of the system, the system design diagrams, schematic diagram of system deployment, system technology architecture diagram), the definition of critical system data structure design system key interfaces. If necessary, the need to develop software prototype system to validate design ideas, and as a basis for subsequent system development.

Overall structure, the external interface, the main components function assignment, appropriate aspects of the interface between the global data structure and main components.

First, the status

Business Background

• project name
• Business Description

technical background

• Architecture Description
• The current system capacity (the average amount of system calls)
• The amount of peak current system calls
• Art heritage

Second, demand

Business needs

• To transform content
• To achieve the new requirements

Business pain points

• Business pain points related to what

Performance requirements

• Estimated system capacity (estimated amount of calls the system average)
• Estimated amount of peak system calls
• Other non-functional quality, such as: security, flexibility and other

Third, the program description

plan 1

Outline

Sentence highlights of the program, such as: double write, separated from the main, sub-library sub-table, expansion and archiving.

Detailed description

Specific description scheme, it is not clear text description may be combined view (FIG any of: the UML, conceptual diagrams, block diagrams, etc.) in the manner described, if the local change of the best projection transformation program, include the following description of several angle:

• Middleware architecture (application servers, databases, caching, message queues etc.)
• Logical architecture (module division, the communication module, information flow, timing, etc.)
• Data architecture (data structures, data distribution, split strategy, cache policy, read and write separation strategy, policy inquiry, data consistency policy)
• Exception handling, disaster recovery strategy, the gray release

Performance Evaluation

Alternatives baseline data, according to performance needs assessment the amount of resources to be used.

• Stand-alone concurrency
• Stand-alone capacity
• According to estimated performance requirements, estimate the amount of resources (application server, cache, store, queue, etc.)
• Telescoping fashion

Program strengths and weaknesses

Lists the advantages and disadvantages of the program, the advantages and disadvantages to have certainty, do not have "certain risks" this description, that is, to quantify.

Scenario 2

Program as a whole need to refer to various indicators technical review of proposed indicators to be considered to meet the system's non-functional quality requirements.

Fourth, the program comparison

Comparative alternative, and given reasons for choosing this approach, the selection tendency scheme.

Fifth, the online program

The above description of the program tend to be more careful

specific plan

How to design specific programs

Chart

How the overall architecture, drawing on the architecture

The key design point

The statements came out a few key points of focus of design ideas, great direction to ensure that the user is OK.

Overall process

The whole process is how to get a whole flow chart

Core processes critical systems is how

Module division

1, Module Description: Indicate the module implements which features; 2, hierarchy module: FIG using software framework to express certain viewing angle; 3, between modules: described inter-module dependent, relationship between the communication mechanisms described; 4 , core interface module: description information, the configuration information transmission module; 5, treatment design: that meet some of the functionality and performance of the algorithm;

[Important] abnormal boundary

By a xmind format to organize related abnormalities border, so they have enough help to control the degree of realization of the time, but also facilitate others to review your plan and specific implementation (such as coding)

Abnormal borders need to be considered:

• What comes to module
• Comes to which procedures
• Each module, the process appeared in a variety of situations possible deal is?
• The underlying causes of system abnormalities caused by the deal is?

Sampling and monitoring

Gray, rollback strategy

• How gray?
• How to roll back?

Disaster recovery plan

Sixth, deployment topology

How to deploy line topology, how the upstream and downstream

Seven, the risk assessment

The risk of identifying the selected program proposed coping strategies to address this risk when it happened, for example: rollback strategy when on-line failure.

potential risks

• What are the risks associated with changes in points
• Incompatible point?
• What are the current problems existing design?
• What are the potential problems

Eight stages of planning Architecture Evolution Plan []

Architecture how evolution

How planning stage

Each stage of the reach what goals

The first stage

second stage

The third stage

Nine, workload assessment

Use the selected program to do a specific job description and evaluation time to develop, test and other tasks needed refinement to form task schedule can be implemented, the task schedule recommended a simple tabular form, reducing the cost of tools and learning.

[ "I welcome the attention of the public micro-channel number: Linux server system development, quality article send back will vigorously by the public micro-channel number"]