Wrote a few years ago.
See if it's going to work.
1Simple Introduction
This document describes the implementation framework of the T-mobile self-updating system based on ASP and IIS services.
This document focuses on two aspects of technical architecture and business architecture to describe T-mobile 's own initiative to update the system architecture, so that the relevant personnel to understand the structure of the product at a high speed.
1.1Purpose
This document provides a comprehensive overview of T-mobile's own proactive updating system from an architectural aspect. There are many different architectural views, such as use case views, logical views, deployment views, implementation views, that describe various aspects of the system.
These descriptive narratives are used to document and articulate important decisions that have been made on the architecture of the system. At the same time, determine the relationship between the different modules in the system design process, the key modules, and the interface between each module. and documenting the design process to be followed by the design methods and guidelines, coding specifications.
This document is therefore suitable for specific foot colors: Project managers, architects, designers, and developers, testing personnel. This document provides an understanding of the system implementation platform and the basic framework. In addition, various views are presented through the system design process. Understand the system execution mechanism from the aspects of architecture, design, development, deployment and so on, and help related personnel to understand the system at high speed, and design and develop it on this basis.
1.2Range
This document is suitable for t-mobile to proactively update the system, which has an impact on T-mobile 's own proactive updating of the system's profile design, design, and coding implementations.
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 own initiative to update |
|
|
1.4 References
2Schema Representation
3schema goals and Constraints
Objective of this architecture:
L Reuse: It is hoped that this document can be used to analyze reusable functions and code to 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 entire architecture as simple as possible to meet the requirements. Reduce the complexity of future maintenance.
L Efficient: It is hoped that the important decision made by this document analysis can guide the design and development work. The guarantee system can guarantee the performance index under the premise of guaranteeing the function demand.
L Transparency: We hope that through the analysis of this architecture, the interaction of modules can be made transparent. Expose 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 |
Through .net2005 and excellent query performance MySQL implements bs client. Real-time progress bar for large file uploads via R.A.D upload component. via a corresponding multiple ftpserver for load balancing. Support 100 Concurrency:   |
Reliability |
The system uses the queue to realize the file distribution of FTPserver, improve the performance Verify uploaded files via md5 to ensure correct file upload process A hot backup of the standby server ensures that the server is in an unexpected state. Standby server can be put into use right away |
Scalability |
Database design and development reserved interfaces Physically reserving an interface that expands to a driver update for multiple hardware Performance-reserved extension interfaces that enable updates for multi-region multi-server |
Capacity |
Data structures are not complex. The system uses MySQL database, which gives priority to support the retrieval speed on the Web . |
Ease of Use |
User-friendly interface with a unified style |
Portability |
The system is implemented using the C # language, and temporary unsupported systems can be deployed on different platforms. |
Maintainability |
After the server-side software has an exception, the request can be recorded. and send exception information to the system administrator Consistency check for input data |
Test-able |
|
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 number |
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 number |
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 number |
ServerIP |
Hardware configuration |
Database |
Mysql |
Locally established |
|
WebServer |
asp.net1.1,IIS6.0 |
Locally established |
|
FTPServer |
Iis6.0 |
Locally established |
|
|
|
|
|
3.3.4test Environment
Test server |
Software configuration |
Name Version number |
ServerIP |
Hardware configuration |
Test Server A D |
Database |
Mysql |
|
2C /4g |
WebServer |
asp.net1.1,IIS6.0 |
|
2C /4g |
FTPServer |
asp.net1.1,IIS6.0 |
|
2C /4g |
|
|
|
|
3.3.5Production Environment
Production server |
Software configuration |
Name Version number |
ServerIP |
Hardware configuration |
Production server |
Database |
Mysql5.0 |
|
|
Application Server |
asp.net1.1,IIS6.0 |
|
|
WebServer( Shanghai ) |
asp.net1.1,IIS6.0 |
|
|
3.4Development Specifications
Based on the design specifications that meet the IT center standards. Based on the details of this system, a more careful design specification has been developed.
4use Case View
Figure 5.1.1 Global use case diagram
4.1Key Use Cases
4.1.1T-mobileproactively update V2.0
5Logical View
5.1Component Diagrams
。
5.2use case implementations
5.3Implementation Scenario Description
6Data View
See Design module Database design documentation.
7 size 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 system under high-intensity pressure test
Copyright notice: This article blog original articles, blogs, without consent, may not be reproduced.
3g actively update the network card to drive the Web after the schema document