We recommend a presentation on "architecture" (PPT)

Recently, I got a presentation from a friend. The center is about "Architecture Design", which mentionsArchitecture,Business ModelingAndDesign Guidelines. Instances are also provided for instructions.

Title: Application System Architecture Overview

Page number: 31

Download the repaired document (*. Zip compressed document)

Note: The animation effect used in the document must be fully supported by Microsoft Office PowerPoint 2003.

From the document, we can see that the speaker has a deep research on the design of ASP. NET presentation layer. For more information, see.

In order not to be too short in this article, the key points and valuable theories are extracted:

Definition of "architecture"

"The basic structure of the system is embodied in components, the relationship between components, the relationship between components and the running environment, and the principle of managing their design and evolution ."

The hierarchical software design proposed by Microsoft. NET is not designed for distributed applications. It is essentially different from the traditional "three-layer structure. For application systems on the Microsoft. NET platform, the client-server-database three-tier structure is not generally comparable. The "architecture" here is essentially different from the above "structure ". The architecture is based on the system design of applications. It is for system analysis, software-only, and compiling.ProgramN-layer architecture. Each layer is a software layer.

Business modeling is different from database design.

Business modeling only defines the data format (schema). The application model does not correspond to the tables in the relational database. Although sometimes they are similar. The business model represents data definitions in a logical sense, such as the project start date, building area, or construction company. The design principles of relational databases are different from those of data definitions. When an object in a business model persists to a relational database, it may occupy two or more tables. This requires the logic of the data access layer.

In addition, the data changes in the business model do not fully correspond to the "read/write deletion" Operation of the relational database. Therefore, it is wrong to design a model in the form of "read/write deletion and modification ".

ASP 3.0 or ASP. NET

ASP. NET is not prepared for "programmers" who "read/write deletions. When the team's technical level is not high or the company's actual technical accumulation is not enough, blindly turning to. NET will only write ASP. NET according to ASP's habits and ideas. In this way, although products can be produced, this approach is fast, short-sighted, and not rigorous. When the demand changes or the system needs to be upgraded, it will face a series of unmanageable situations. Compared with ASP 3.0, development costs increase.

ASP. NET is prepared for enterprise-level applications. ASP. NET is used to satisfy its basic features, namely flexibility, reusability, logical separation and centralization.

The architecture can be both advanced and small, depending on the needs of the project. However, it is not necessary to reduce the flexibility and reusability of the system due to a small amount of coding workload, or to spend less effort on design. A well-designed system, the workload for coding, art design, and database design is very small compared with system analysis. An architecture may be unreasonable, unscientific, or difficult to use at first, and can gradually become perfect as the number of projects increases. However, the architecture must follow the established specifications. Otherwise, it cannot be called "architecture ".