Article Directory
table of Contents
system design
In the past ten years, my country's automobile industry has developed vigorously, especially the growth of family cars. The size and speed of the car market in developing countries must be synchronized with the urban infrastructure. If you blindly pursue the speed of development, it will inevitably cause serious traffic congestion problems in many large cities, and will also bring a series of negative consequences to the society, such as increasing Socio-economic costs, increased energy consumption, deterioration of urban air, increased traffic accidents and so on. Therefore, while developing our country’s automobile industry, we must pay attention to the significance and role of urban public transportation, increase the country’s investment in public transportation, and make overall planning, overall arrangements, reasonable allocation, and scientific management to make urban roads smooth and convenient. , Safe, effective and reliable.
However, with the rapid development of public transportation, more and more buses and different bus routes will gradually appear, which will make people not very clear about the information of each bus route. The main task of the urban public transport query system is to query the information of each route and manage the information of the entire public transport route. People can find a route that suits them best by using the public transport query system, reducing unnecessary travel time. Therefore, the prospects of the urban public transport query system are very optimistic.
Based on the urban public transport query system and the traditional urban public transport query system are similar and different. The similarity is that the core of the system is the B/S architecture. The B/S architecture does not require a special operating environment. As long as you can access the Internet, you can operate the system anywhere. The difference lies in the different implementation languages. The traditional general language used is ASP+ and its scripting language, which is not object-oriented, while the language used in the urban public transport query system based on this design is .NET, which is object-oriented and oriented. The biggest feature of the object's programming language is that you can write the data types you need. For the traditional urban public transport query system, it is easy to manage and highly reusable.
System implementation
In this system, users can query various routes or stops in the city and learn detailed information about each route or stop. If the user wants to query a certain line or station, he can directly use the corresponding function of the system. The system meets the following requirements:
Simplicity of operation: The urban public transport query system is simple, convenient, and user-friendly to use, and it is easy for users to operate.
System functions: In this system, the following functions are mainly provided: query station information, train number information, station information and station information functions, message messages and system management functions. For example, in the query function, the user enters the information such as the number of trains to be queried to get the results related to it; in the system management function, the administrator can add, edit and delete its information.
3.2 Outline design
3.2.1 System function description
After the user enters the main interface, the relevant line information that meets the user's conditions can be quickly searched through train number query, station query, station query, and station query. The user can also leave a message directly in the guestbook. The content of the message can be inquiries about the line or put forward the user's own opinions on the shortcomings of the system. After the administrator enters the system, he can add, delete and edit the information in the database. He is also responsible for managing the user's message information, by reviewing the message information, and then judging whether to reply or delete the message information.
3.2.2 System functional module division
After understanding the functional requirements of the system, the system can be divided into the following three modules: user query module, guestbook module and system management module as shown in Figure 3-1.
Source File
