Automatic update of the driver for 3g Internet card Web-side architecture document

Written a few years ago.

See if anyone can use it.

1Introduction

This document details the implementation framework of the T-mobile automatic updating system based on the ASP. NET platform and IIS services.

This document focuses on two aspects of the technical architecture and business architecture to describe the architecture of the t-mobile Automatic Update system, so that relevant people can quickly understand the structure of the product.

1.1Purpose

This document provides a comprehensive overview of the T-mobile Automatic Update system in terms of architecture, which describes various aspects of the system using a number of different architectural views, such as use case views, logical views, deployment views, implementation views, and so on.

These descriptions are used to document and articulate important decisions that have been made on the architectural aspects of the system while determining the relationship of different modules in the system design process, the key modules, and the identification of the interfaces between each module, as well as the design methodology and guidelines for documenting the design process and coding specifications.

This document is therefore suitable for specific foot colors: Project managers, architects, designers, and developers, testers. Through this document can understand the system implementation platform and the basic framework, in addition, through the system design process of various views, from the architecture, design, development, deployment and other aspects of understanding the system operating mechanism, to help relevant personnel quickly understand the system, and on this basis to carry out related design and development.

1.2Range

This document is suitable for the t-mobile Automatic Update system, which has an impact on the design, detailed design, and coding implementation of the t-mobile Automatic Update system.

1.3definitions, acronyms and acronyms

IT The terminology used in the central Software Architecture discipline document is in this document.

Abbreviations	Description
ZTE	ZTE Abbreviation (zhongxing technology equipment)
T-mobile	t-mobile Automatic Updates

1.4References

2Schema Representation

3schema goals and Constraints

Objective of this architecture:

L Reuse: It is hoped that this document can analyze reusable functions and code, achieve reuse, reduce development costs and maintenance costs.

L Concise: Want to determine the implementation technology architecture of the software in the architecture document, make the whole architecture as simple as possible to meet the requirements, reduce the complexity of future maintenance.

L Efficient: I hope that through this document analysis to make important decisions, can guide the design and development work, to ensure that the system in the premise of ensuring functional requirements, can guarantee performance indicators.

L Transparency: We hope that through the analysis of this architecture, the interaction of modules can be made transparent, exposing only the interfaces that need to be exposed for use by other modules.

L Security: Design secure authentication authorization mechanism and other security measures to ensure the security of the system.

3.1Design Goals

Product Features	Design goals
Security	1.
Performance	Excellent MySQL implementation via . net2005 and query performance BS client. Real-time progress bar for large file uploads via R.A.D upload components. Load balancing is achieved through a webserver corresponding to multiple ftpserver . Supports up to four concurrent:
Reliability	The system uses the queue to realize the FTP server file distribution, improves the performance Verify uploaded files via md5 to ensure correct file upload process Standby server can be used immediately by hot backup of the standby server to ensure that the server is in an abnormal condition
Scalability	Database design and development reserved interfaces Physically reserving an interface that can be extended to drive updates for multiple hardware Performance-reserved extension interfaces that can be updated for multi-region multi-server implementations
Capacity	Data structure is not complex, the system uses MySQL database, priority to support the search speed on the Web .
Ease of Use	User-friendly interface with a unified style
Portability	The system is implemented using the C # language and temporarily does not support the ability to deploy on different platforms.
Maintainability	After a server-side software exception occurs, it is required to be able to log and send exception information to the system administrator Consistency check for input data
Testability

3.2unified abbreviation for design coding

The relevant coding abbreviations are defined in strict accordance with the Code specification-c#-rules of the IT center.

3.3Tools and Environment3.3.1Design Tools

Tool Name	Version	Description of Use
Power Designer	9.5	Database modeling tools for database-related object design, customization.
UML(Rose)	1.0	A Unified Modeling Language tool for designing related use cases, views, and more.

3.3.2Coding Tools

Tool Name	Version	Description of Use
Vs.net	2003	Microsoft Visual Studio. NET integrated development environment is the environment and platform for . NET development.
Mysql	6.0	MYSQL Database

3.3.3Development Environment

	Name version	Server IP	Hardware configuration
Database	Mysql	Locally established
Web Server	asp.net1.1,IIS6.0	Locally established
FTP Server	Iis6.0	Locally established

3.3.4test Environment

Test server	Software configuration	Name version	Server IP	Hardware configuration
Test server one D	Database	Mysql		2C /4g
	Web Server	asp.net1.1,IIS6.0		2C /4g
	FTP Server	asp.net1.1,IIS6.0		2C /4g

3.3.5Production Environment

Production server	Software configuration	Name version	Server IP	Hardware configuration
Production server	Database	Mysql5.0
	Application Server	asp.net1.1,IIS6.0
	Web Server ( Shanghai )	asp.net1.1,IIS6.0

3.4Development Specifications

In accordance with the standards of IT center design, based on the specific circumstances of the system to formulate a more detailed design norms.

4use Case View

Figure 5.1.1 Global use case diagram

4.1Key Use Cases

4.1.1T-mobileAutomatic Update V2.0

5Logical View

5.1Component Diagrams

。

5.2use case implementations

5.3Implementation Scenario Description

6Data View

See Design module Database design documentation.

7size and Performance

l Hardware application Environment

2 network environment: LAN

2 database server: MYSQL5.0

2 Web server: PC Server

2 client: IE5 or more, Firefox

l software application Environment

2 server side: asp.net1.1,iis6.0

2 user interface:

2 using IE browser

8Quality

l System expansion performance:

Database performance to meet extended performance requirements

l system reliability:

Real-time effect of the system under high-intensity pressure test

http://qun.t.qq.com/31918264