Design and Implementation of the Construction Scheme of the Campus All-in-One Card System
[ad_1]
Shantou Vocational and Technical College is composed of the headquarters, Jinyuan campus, Xinjin campus and Dongdun campus. There are more than 1.5×104 students of various types and more than 700 faculty members. According to the college’s informatization development plan and system deployment process arrangement, the headquarters of the college and the Jinyuan campus shall realize network interconnection in the same city and initiate the construction project of the all-in-one card system. The project is divided into two phases, the first phase and the latter phase. The first phase of the project includes: the canteen selling system, intelligent water control system, book borrowing system, etc. Later projects include: extension and access of educational administration system, computer management system, access control and attendance management system, intelligent power control system, bank transfer system, etc., to truly realize the sharing of information and resources, and realize the comprehensive all-in-one card application. According to the construction goals and requirements of the college campus card system, this paper designs and implements the technical solutions of the system.
1 Overview of system construction goals and demand analysis
“Campus All-in-One Card” refers to the use of cards to complete all situations involving cash or identification within the school. The card integrates student ID, work ID, ID card, library card, wallet, etc., and achieves the electronic and intelligent management of fees and management of ID and consumption.
The construction of the one-card system should realize: 1) Form a unified information platform, promote the standardization of education information, and build an excellent digital space and information sharing environment; 2) Realize a unified electronic payment and fee collection management throughout the school to solve various campus fees collection Trouble, miscellaneous, difficult and other issues; 3) Integrate and drive the construction of various management information systems to improve school management efficiency and management level; 4) Promote the construction of school network application platforms, and gradually complete the upgrade of the school’s application system architecture.
The requirements of the system are mainly investigated from the perspectives of business, function, technology, etc. The following author only discusses the analysis of technical requirements. The technical requirements mainly include: 1) Identity information comes from a unified identity management center, and the data synchronization mechanism is based on a unified identity center and data center; 2) Building a one-card private network to improve system security and maintainability; 3) Integrating existing differences 4) The card structure design needs to have an identity authentication information area, an electronic wallet information area, a custom information area, and multiple electronic wallets with sufficient redundancy; 5) Support offline payment; 6) Provide a common development interface, Facilitate expansion and upgrade; 7) Integration, development, operation and management tools that meet various applications must be provided.
The main requirements for campus cards are as follows: use non-contact radio frequency cards; the terminal’s sensing distance range can reach 5~10cm; the data area in the card stores identity information and e-wallet information, and the card adopts directory management; the personal identity information in the card includes Cardholder’s name, gender, school/work number, ID number and other information.
2 System overall design
The overall design of the system includes: overall system framework, software architecture, data flow and database, etc.
2.1 Overall system framework
The system consists of three parts: data center, all-in-one card platform, and interface server. Among them, the all-in-one card platform uses COM+ technology to integrate card application systems, self-service systems and management systems; the interface server uses COM/DELL interface technology to connect library management, educational administration systems, access control systems, etc. As shown in Figure 1.
COM+ is a programming based on binary components and interfaces. By using a transparent RPC layer, remote method calls can be made across process and computer boundaries. COM+ components can be upgraded and extended in finished products without affecting the client applications that use them. COM+ promotes COM components to the application layer. It shields the low-level details of all components through various supports of the operating system.
The use of good interface technology makes the architecture good scalability, low coupling, and easy to upgrade and expand.
2.2 Software Architecture
The software architecture is shown in Figure 2. The system adopts the .NET development environment and provides a three-tier structure with COM+ as the intermediate communication component. The software system architecture consists of a data layer, a business layer and a presentation layer. Among them, the business layer (ie, the middle layer) is mainly responsible for business rules, data access, and legality verification. The biggest advantage of an application using a three-tier system is that it separates the business logic. The client does not directly interact with the database, but establishes a connection with the middle layer through COM/DCOM communication, and then the middle layer interacts with the database. When the business logic needs to be changed, the presentation layer and the back-end data service layer are not affected. Therefore, it can meet the scalability or expansibility requirements of the campus all-in-one card application. At the same time, the system provides standard interfaces, APIs, dynamic libraries, third-party agents, etc. for financial systems, educational management systems and other systems, and processes business requests from other systems in real time to achieve integration with other systems.
2.3 Data flow diagram
The main user groups of the system are students, faculty and staff. Therefore, when analyzing the data flow of the system, the author focuses on the data flow of system users. Due to the huge functions of the system and the many levels of data flow, in order to briefly explain the operating mechanism of the system, only the most important top-level data flow diagram will be analyzed here. The data flow diagram is shown in Figure 3 and Figure 4. The external entities of the system mainly include students, faculty, temporary staff, and administrators; the system’s data processing mainly includes cardholder information management, card user management, system management, transaction processing, bank front-end computers, and accounting processing, etc.; Data storage mainly includes historical transaction tables, account settlement tables, daily and monthly settlement detailed reports, and statistical reports.
3 database model design
The system uses SQLServer2000 database management system. There are many tables used for different functions in the system database, and there are mainly two types of tables:
1) Basic function table. The main function of this type of table is to record some basic auxiliary information needed by other tables. Including user password, student personal information, teacher personal information corresponding table, consumption record information table, etc.;
2) Function operation table. This type of table is used to record the data generated by the operation of each system function.
The design of the database is of great importance to the ultimate success of the system, and the definition of each table and its fields will directly affect the effect of users. Especially the design of data tables related to user consumption records, system accounting records, etc., is the most important thing. Therefore, the use of a database management platform with good performance will play a key role in the stability of the system and the security of the underlying data.
[ad_2]