Table of contents
Abstract 2
ABSTRACT 3
1 Introduction 6
1.1 Research background 6
1.2 Current situation at home and abroad 8
1.3 Main research content 10
1.4 Research significance 10
2 Related technologies 12
2.1 Microsoft .NET 12
2.2 Web server IIS 14
2.3 Introduction to Visual Studio 2013 14
2.4 C# development language 15
2.5 SQL Server technology 15
2.6 System development mode 16
3 System analysis 19
3.1 Requirement analysis 19
3.1.1 Requirement background analysis 19
3.1.2 Functional requirement analysis 19
3.1.3 System function structure 20
3.1.4 System use case diagram 21
3.2 System construction Model 22
3.2.2 System Sequence Diagram 24
3.2.3 System State Diagram 26
3.3 System Architecture Design 27
4 Database Design 29
4.1 Data Flow Diagram Design 29
4.1.1 Data Dictionary 29
4.1.2 Business Flow Chart 31
4.2 Conceptual Structure Design 35
4.3 Database Physical Design 37
5 System Implementation 41
5.1 Development environment41
5.1.1 System logic architecture design41
5.1.2 Network architecture design43
5.1.3 Operating environment44
5.2 System design46
5.2.1 Development process design46
5.2.2 Code design48
5.2.3 Input and output design50
5.3 Realization of system functions 51
5.3.1 Realization of user password management module 51
5.3.2 Realization of user information management module 53
5.3.3 Realization of campus card information management module 57
5.3.4 Realization of consumption information management module 58
5.3.5 Realization of information query module 60
6 System Test 61
6.1 Test Process 61
6.2 Typical Functional Test Cases 62
6.3 Performance Test 64
6.4 Test Result Analysis 65
Conclusion 67 References
68
Acknowledgments 71
3 System Analysis
3.1 Requirements Analysis
3.1.1 Requirements Background Analysis
With the vigorous development of the information industry and With the enhancement of people's awareness of office automation, colleges and universities are paying more and more attention to publicity and improving their own image. The original campus card system can no longer fully meet the needs of daily use. In order to strengthen the management of information, improve work efficiency, and make full use of the existing resources of the information industry, it is imperative to develop a better campus card system.
The system to be developed this time is relatively high in efficiency, comprehensibility, reliability and maintainability. It is easy for users to understand and learn to operate. Maintainability includes two meanings, namely readability and testability. Reliability generally refers to the robustness and correctness of a program. In the process of developing this system, it is necessary to weigh multiple contradictory goals, and under the constraints (time, funds, possible hardware and software resources, etc.) to maximize the various requirements mentioned above satisfy.
3.1.2 Analysis of functional requirements
The overall task of campus card system development is to realize the systematization, standardization and automation of university information management. The system solves the tedious work of various information registration management for administrators, reduces the workload of administrators, and improves efficiency. The system has the following main functional modules.
Campus card information management module: This module is mainly responsible for managing the registration of campus card information and the maintenance of campus card information by administrators. It is the core part of this management system. The maintenance of campus card information includes adding campus card information, deleting campus card information, Modify the campus card information function.
Consumption management module: This module is mainly responsible for managing the registration of consumption information and the maintenance of consumption information by the administrator. The maintenance of consumption information includes functions such as adding consumption information, deleting consumption information, modifying consumption information, and information query.
User information management module: This module is mainly responsible for managing the registration of user information and the maintenance of user information by administrators. The maintenance of user information includes functions such as adding user information, deleting user information, and modifying user information.
3.1.3 System Functional Structure
According to the requirement analysis above, the functional structure of the system is designed. The campus card system is divided into five functional modules: system setting management, user information management, campus card management, consumption information management, and book borrowing and returning management. As shown in Figure 31.
Figure 31 System function structure diagram
(1) System setting management
This module provides the user's account information management setting and password modification and maintenance functions. In addition, it also provides system interface information, modification and maintenance of website configuration parameters, and this function is limited to administrator operations.
(2) User information management
This module is operated by the administrator. The administrator can modify the account information of the entire system, including modifying user information, adding user information and deleting user information. User information includes: login account, login password, email, status, etc.
(3) Campus card management
This module is operated by administrators. Mainly complete the maintenance of campus card information, including adding campus card information, deleting campus card information, modifying campus card information and querying campus card information. Campus card information includes: campus card number, type, user, gender, class, phone number, balance and card status, etc. Administrators can complete the search and query of campus card information in this function, and can also modify and delete any record.
(4) Consumption information management
This module is operated by administrators. The main function of the consumption information management sub-module is that the administrator can add, delete, modify and check the consumption information, that is, add consumption information, modify consumption information, delete consumption information, and query consumption information. The operation of modifying consumption information and adding consumption information needs to judge whether the input content is standardized, and then it can be submitted to the database. After the submission is successful, the consumption information table is refreshed.
(5) Borrowing and returning books management
This module realizes the management of student users' borrowing records and returning books records. Including modification of borrowing and returning information, deletion of borrowing and returning information, and addition of borrowing and returning information.
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="SysManage_Login" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title></title>
<style type="text/css">
body
{
margin:0;
background:url(images/ecard.jpg);
background-size:100%;
font-size:14px;
color:#fff;
}
.textbox
{
border:1px solid #A7CAE8;
margin-left:2px;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<table style="WIDTH:465px; HEIGHT:100%" align="center">
<tr>
<td style="height:100px;"><br /><br /></td>
</tr>
<tr>
<td valign="top" align="center" style="background:url(images/loginbg.gif) no-repeat; height:283px;">
<table style="WIDTH:465px; margin-top:120px;">
<tr>
<td style="height:24px" align="right">登录帐号：</td>
<td align="left"><asp:TextBox ID="Txtuid" runat="server" CssClass="textbox" Width="160px"></asp:TextBox></td>
</tr>
<tr>
<td style="height:24px" align="right">登录密码：</td>
<td align="left"><asp:TextBox ID="Txtpwd" runat="server" CssClass="textbox" TextMode="Password" Width="160px"></asp:TextBox></td>
</tr>
<tr>
<td align="right" style="height:24px">登录类型：</td>
<td align="left">
<asp:DropDownList ID="ddltype" runat="server">
<asp:ListItem Value="1">管理员</asp:ListItem>
<asp:ListItem Value="2">学生</asp:ListItem>
</asp:DropDownList>
<asp:ImageButton ID="btnLogin" runat="server" ImageUrl="images/btn_login.gif" OnClick="imbtnSubmit_Click" />
<input onclick="javascript:window.location.href='login.aspx';" type="image" src="images/btn_reset.gif">
</td>
</tr>
<tr>
<td></td>
<td style="padding-top:10px;" align="left">
</td>
</tr>
<tr>
<td></td>
<td style="color:#db0000;" align="left">
<asp:Literal ID="ltlMess" runat="server"></asp:Literal></td>
</tr>
</table>
</td>
</tr>
</table>
</form>
</body>
</html>
