With the maturity of computer science and technology, people have deeply realized the powerful functions of computers. Computers have entered various fields of human social development and played a very important role. The property management of each community is a systematic and complex work, which requires a team to cooperate with each other and cooperate with each other. In this field, the traditional manual access or the management of properties with the help of some software often cannot track and manage various information of the property in real time. , More effective service in the process of software development, so this property management system was developed.
In view of the large scale of various data in the property, property managers and owners need to manage some information related to the property, the framework of the property management system is designed, the overall design of the property management system is given, and the property management system The architecture of the system and the implementation process of key modules are discussed in detail. Using PHP technology and MySQL database technology, a complete system design is realized based on B/S mode, and a good property management system is provided for large users.
Keywords: property management; PHP; MySQL; B/S mode
With the maturity of computer science and technology, people have deeply realized the powerful functions of computers, and computers have entered various fields of human society development and play a very important role. The property management of each community is a systematic and complex work, which requires a team to cooperate and cooperate with each other. In this field, traditional manual access or management of properties with the help of some software often cannot track and manage various information of properties in real time. , To serve the software development process more effectively, so develop this property management system.
In view of the large scale of various data in the property and the need for property managers and owners to manage some information related to the property, the thesis designs the framework of the property management system, gives the overall design of the property management system, and provides an overview of the property management system. The architecture and implementation process of key modules are discussed in detail. Using PHP technology and MySQL database technology, a complete system design is realized based on B/S mode, providing a good property management system for large users.
Keywords: Property management; PHP; MySQL; B/S mode
1.1 Background of topic selection
1.2 Significance of the subject research
1.3 Arrangement of paper structure
Chapter 2 Requirements Analysis of Property Management System
2.1 System Feasibility Analysis
2.1.1 Technical Feasibility Analysis
2.1.2 Economic Feasibility Analysis
2.2 System requirements analysis
2.2.1 Analysis of Functional Requirements
2.2.2 Non-functional requirements analysis
Chapter 3 Overall Design of Property Management System
3.1 System function module design
3.2.1 Database concept structure design
3.2.2 Database logical structure design
Chapter 4 Design and Implementation of Key Modules
4.1.2 Owner registration interface
4.1.4 Property information interface
4.1.5 Community service interface
4.1.7 Community service management interface
4.1.8 Utility bill payment interface
4.1.9 Property fee payment interface
4.2.2 User Management Interface
4.2.3 Community service interface
4.2.4 Real estate information interface
4.2.5 Parking space information interface
4.2.6 Stranger registration interface
4.2.7 Warehouse information interface
4.2.8 Utility bill payment interface
4.2.9 Property fee payment interface
At present, many properties across the country have already shifted the software in their properties towards intelligence, especially in the direction of expanding towards the web page that fits the characteristics of their properties. The property management system used in the previous property management company is a stand-alone version, and it needs to be expanded towards the web version, so I decided to open a property management system [1]. By using the current popular browsers for browsing management, the property management system can become more humanized, and it can also improve the intelligent management of your property [2].
In recent years, with more and more property-related information, such as repair and maintenance, payment, parking spaces, visitors and other information, the demand for property management is getting higher and higher, and we need to use more and more aspects in our work The management system on the webpage side is used for management, and all kinds of information processing operations we need can be completed by using the webpage system. With the system on the webpage side, it is convenient to query and maintain various information [3].
Therefore, it is necessary to realize the electronicization of property management and improve property management efficiency and use efficiency. With the rapid development of computer application technology, various WEB-based systems have been welcomed by enterprises and users. Based on this background, a property management system is designed to take advantage of the convenience of WEB page management to improve the work of the property management system. Efficiency, so that owners and managers can enjoy more convenient and efficient services [4].
The thesis will be arranged in layers, except for the abstract acknowledgments and references, the main text will also analyze the requirements of the website, explain the general design and implemented functions, and finally list some commissioning records. The main structure of the thesis is as follows:
Chapter 1 explains the background and current situation of the project.
Chapter 2 analyzes the requirements of the system.
Chapter 3 explains the general design of the website.
Chapter 4 clarifies the realization of the detailed functions of the property management system, mainly based on the functional realization of technical functional modules.
Chapter 5 lists some records of system debugging and testing.
Chapter 6 presents the conclusion of property management system.
The use of the mysql database used for storage in the property management system and the development tools such as Dreamweaver, HTML, and Apache used in development can bring a lot of convenience to our writing work. The system uses B/S mode for development, which makes the system more scalable and maintainable, reduces system configuration code, and simplifies programming code. Currently, B/S mode is the most popular mode.
The development software used in the development of the property management system, such as Dreamweaver development tools, Apache server, MySQL5.7 database, HTML, Photoshop image processing software, etc., are all open source and free, and the property management system is designed and coded by ourselves , the database uses the popular mysql for data storage, and the use of open source mysql and other technologies reduces system development costs.
The design and implementation of the property management system is to make it easier for property users to manage some information related to the property . At the same time, there are also reasons for owners to view property information through the web system and submit property services such as repairs and repairs online. Their own water and electricity bills and property fees can save users a lot of time and energy when searching for a certain information, and effectively reduce unnecessary search time.
The purpose of studying the design and implementation of the property management system is to have an intelligent one-stop property management method with simple and friendly interface, simple operation and stable operation. System requirements mainly come from property managers and owners.
The property management system chooses PHP combined with Dreamweaver, HTML and other technologies to develop, uses mysql database to store data, and is divided four parts: owner side, property employee side , property manager side and administrator side.
Owner side:
(1) System information: When the owner enters the front desk of the property management system, the navigation bar, carousel map, bulletin board and other information are first displayed in front of the owner, and the owner can view it according to his personal needs;
(2) Registration and login: There are login + registration + search and view buttons in the upper right corner of the system. If the owner wants to log in to the system, he can click the "login" button, then fill in the username + password, and click the "login" button. The system will check your username and password. If it is correct, you will be logged in successfully. If you do not have an account, you can click the "Register" button in the upper right corner, and then enter the user information according to the prompts to get the account and password;
(3) Community service: After the owner logs in to the system, click on the menu "Community Clothing", the system will automatically generate the owner, name, repair date, the owner only needs to fill in the phone number, service type, status, service information, click Just submit;
(4) My account: When the user clicks the "My" button in the upper right corner, a submenu will appear, click "My Account" to set the personal information and the password to log in to the system;
(5) Personal Center: When the user clicks the "My" button in the upper right corner, a submenu will appear, and clicking "Personal Center" will enter the background management of the owner, where the submitted community services can be managed and carried out. Inquire about personal utility bills and property fees, and make online payments;
Admin side:
The administrators of the property management system include administrators, property managers and property employees. Among them, administrators have the highest authority and can control user information, system information and property service information.
(1) Owner users: administrators, property managers and property employees can view the owner's information in the background, but only the administrator can add, delete, modify, and query the owner;
(2) Property staff: administrators and property managers can add, delete, modify and check property staff in the background;
(3) Property manager: the administrator can add, delete, modify and check the property manager in the background;
(4) Community service: After the administrator, property manager, and property staff click the "Community Service" button, the property service information submitted by the front desk owner will be displayed. Choose a piece of property service information and click the "Edit" button. The status of the property service will be set. If it has been processed, it can be set as processed. If the processing is not completed, it can be set as pending;
(5) Real estate information: After clicking the "real estate information" button, all real estate information will be displayed, and operations such as adding, editing, deleting and querying can be performed;
(6) Parking space information: After clicking the "Parking space information" button, all parking space information will be displayed, and operations such as adding, editing, deleting and querying can be performed to set the owner of the parking space;
(7) Registration of Strangers: After clicking the button of "Registration of Strangers", all the registration information of strangers will be displayed, and the operation of adding, deleting, modifying and checking is supported;
(8) Warehouse Information: After clicking the "Warehouse Information" button, all warehouse storage information will be displayed, and operations of adding, deleting, modifying and checking are supported;
(9) Warehouse Information: After clicking the "Warehouse Information" button, all warehouse storage information will be displayed, and operations such as adding, deleting, modifying, and checking are supported. Users can find the information they need more quickly;
(10) Payment of water and electricity fees: After clicking the button of "Payment of Water and Electricity Fees", all the payment information of water and electricity fees will be displayed, and the operation of addition, deletion, modification and query is supported, and payment can also be made by clicking "Payment";
(11) Property fee payment: After clicking the "Property fee payment" button, all property fee payment information will be displayed, and it supports addition, deletion, modification and query operations, and you can also click "Pay" to pay;
The non-functional requirements of the property management system , such as the security, reliability, performance, and scalability of the property management system, etc. Specifically, it can be expressed in the following table 3-1:
Table 2.1 Property Management System Non-functional Requirements Table
| safety |
It mainly refers to the installation of the property management system database, the use of the database and the setting of the password must comply with the norms. |
| reliability |
Reliability means that the property management system can be operated according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for the property management system to occupy the market, so it is better to have good performance. |
| scalability |
For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system. |
| ease of use |
Users only need to follow the page display content of the property management system to operate. |
| maintainability |
The maintainability of property management system development is very important, after testing, there is no problem with maintainability |
The use case diagram of the role of the owner in the property management system is shown in Figure 2.1:
Figure 2.1 Owner Role Use Case Diagram
The use case diagram of the administrator role in the property management system is shown in Figure 2.2:
Figure 2.2 Administrator role use case diagram
The use case diagram of the property manager role in the property management system is shown in Figure 2.3:
Figure 2.3 Property Manager Role Use Case Diagram
The use case diagram of the role of property staff in the property management system is shown in Figure 2.4:
Figure 2.4 Use Case Diagram of Property Staff Role
In the previous chapter, the functional requirements of the property management system were analyzed, and the use cases in the property management system were analyzed according to the requirements. Then the next step is to start the design of the property management system architecture, main functions and database.
After the overall structure of the system is determined, let's look at the main functional module diagram of the property management system . The overall functional module includes three modules: administrator + property manager + property staff + owner. The realized modules mainly include user management, community service, real estate information, parking space information, stranger registration, warehouse information, utility fee payment, property fee payment wait.
Figure 3.1 Functional block diagram of property management system
Database design generally includes three major processes: requirements analysis, conceptual model design, and database table establishment. Requirements analysis has been explained in the previous chapters, and conceptual model design includes two parts: ER model and logical structure design.
The following is the ER entity relationship diagram of the main database tables in the entire property management system.
Figure 3.2 The overall ER relationship diagram of the property management system
According to the total ER relationship diagram of the database of the property management system, it can be concluded that the property management system needs a lot of ER diagrams, and some main database ER model diagrams are listed here.
Figure 3.3 Warehouse information ER relationship diagram
Figure 3.4 ER relationship diagram of registration information of strangers
Figure 3.7 Real estate information ER relationship diagram
Figure 3.5 ER relationship diagram of utility bill payment information
Figure 3.6 ER relationship diagram of property fee payment information
Figure 3.7 ER relationship diagram of parking space information
Figure 3.8 ER relationship diagram of community service information
Figure 3.9 ER relationship diagram of property information information
Figure 3.10 Owner Information ER Relationship Diagram
A total of many data tables need to be created through the previous ER relationship diagram. The relational models of these main database tables are listed here as follows:
(1) The table warehouse_information entity is used to store the storage number, storage name, quantity, storage time, remarks, etc. in the submitted warehouse information;
Table 3.1 warehouse information warehouse_information table
| serial number |
database field |
Field Type |
field length |
storage content |
Remark |
|||||
| 1 |
warehouse_information_id |
int |
11 |
primary key |
primary key |
|||||
| 2 |
storage_number |
varchar |
64 |
storage number |
empty |
|||||
| 3 |
storage_name |
varchar |
64 |
storage name |
empty |
|||||
| 4 |
number |
varchar |
64 |
quantity |
empty |
|||||
| 5 |
storage_time |
datetime |
storage time |
empty |
||||||
| 6 |
remarks |
text |
Remark |
empty |
||||||
| 7 |
recommend |
int |
11 |
Intelligent Recommendation |
empty |
|||||
| 8 |
create_time |
datetime |
creation time |
empty |
||||||
| 9 |
update_time |
timestamp |
update time |
empty |
||||||
(2) The stranger_registration entity is used to store the name, gender, phone number, address, registration date, etc. in the registration information of strangers;
Table 3.2 Stranger registration information stranger_registration table
| serial number |
database field |
Field Type |
field length |
storage content |
Remark |
|||||
| 1 |
stranger_registration_id |
int |
11 |
primary key |
primary key |
|||||
| 2 |
full_name |
varchar |
64 |
Name |
empty |
|||||
| 3 |
gender` |
varchar |
64 |
gender |
empty |
|||||
| 4 |
telephone |
varchar |
64 |
Telephone |
empty |
|||||
| 5 |
address |
varchar |
64 |
address |
empty |
|||||
| 6 |
date_of_registration |
date |
Registration Date |
empty |
||||||
| 7 |
recommend |
int |
11 |
Intelligent Recommendation |
empty |
|||||
| 8 |
create_time |
datetime |
creation time |
empty |
||||||
| 9 |
update_time |
timestamp |
update time |
empty |
||||||
(3) The table real_estate_information entity is used to store the house type, unit number, floor, house number, owner, etc. in the real estate information;
Table 3.3 Real estate information real_estate_information table
| serial number |
database field |
Field Type |
field length |
storage content |
Remark |
|||||
| 1 |
real_estate_information_id |
int |
11 |
primary key |
primary key |
|||||
| 2 |
layout_of_a_house_or_an_apartment |
varchar |
64 |
room type |
empty |
|||||
| 3 |
unit_number |
varchar |
64 |
unit number |
empty |
|||||
| 4 |
floor |
varchar |
64 |
floor |
empty |
|||||
| 5 |
room_number |
varchar |
64 |
Room No |
empty |
|||||
| 6 |
owner |
date |
owner |
empty |
||||||
| 7 |
recommend |
int |
11 |
Intelligent Recommendation |
empty |
|||||
| 8 |
create_time |
datetime |
creation time |
empty |
||||||
| 9 |
update_time |
timestamp |
update time |
empty |
||||||
(4) The table payment_of_utilities entity is used to store the owner, name, unit number, house number, water fee, electricity fee, total, payment status, payment; type, etc. in the utility fee payment information in the system;
Table 3.4 Payment_of_utilities table of utility fee payment information
| serial number |
database field |
Field Type |
field length |
storage content |
Remark |
|||||
| 1 |
payment_of_utilities_id |
int |
11 |
primary key |
primary key |
|||||
| 2 |
owner |
varchar |
64 |
owner |
empty |
|||||
| 3 |
full_name |
varchar |
64 |
Name |
empty |
|||||
| 4 |
unit_number |
varchar |
64 |
unit number |
empty |
|||||
| 5 |
house_number |
varchar |
64 |
house number |
empty |
|||||
| 6 |
charge_for_water |
int |
11 |
water fee |
empty |
|||||
| 7 |
electricity_fees |
int |
11 |
electricity bill |
empty |
|||||
| 8 |
total |
varchar |
64 |
total |
empty |
|||||
| 9 |
pay_state |
varchar |
16 |
Payment status |
empty |
|||||
| 10 |
pay_type |
varchar |
16 |
Payment Types |
empty |
|||||
| 11 |
recommend |
int |
11 |
Intelligent Recommendation |
empty |
|||||
| 12 |
create_time |
datetime |
creation time |
empty |
||||||
| 13 |
update_time |
timestamp |
update time |
empty |
||||||
(5) The table yaopinguanliyuan entity is used to store the owner, name, unit number, house number, property fee, payment status, payment type, etc. in the property fee information in the system, and is used for drug administrator login;
Table 3.5 Property fee information payment_of_property_fee table
| serial number |
database field |
Field Type |
field length |
storage content |
Remark |
|||||
| 1 |
payment_of_utilities_id |
int |
11 |
primary key |
primary key |
|||||
| 2 |
owner |
varchar |
64 |
owner |
empty |
|||||
| 3 |
full_name |
varchar |
64 |
Name |
empty |
|||||
| 4 |
unit_number |
varchar |
64 |
unit number |
empty |
|||||
| 5 |
house_number |
varchar |
64 |
house number |
empty |
|||||
| 6 |
property_fee |
int |
11 |
Property costs |
empty |
|||||
| 7 |
pay_state |
varchar |
16 |
Payment status |
empty |
|||||
| 8 |
pay_type |
varchar |
16 |
Payment Types |
empty |
|||||
| 9 |
recommend |
int |
11 |
Intelligent Recommendation |
empty |
|||||
| 10 |
create_time |
datetime |
creation time |
empty |
||||||
| 11 |
update_time |
timestamp |
update time |
empty |
||||||
（6）表parking_space_information实体用来存放系统中车位信息中车位号、所属人、业主名字、车位位置、备注等；
表3.6车位信息parking_space_information表
| 序号 |
数据库字段 |
字段类型 |
字段长度 |
存储内容 |
备注 |
|||||
| 1 |
parking_space_information_id |
int |
11 |
主键 |
主键 |
|||||
| 2 |
parking_space_number |
varchar |
64 |
车位号 |
可空 |
|||||
| 3 |
owner |
int |
11 |
所属人 |
可空 |
|||||
| 4 |
owner_name |
varchar |
64 |
业主名称 |
可空 |
|||||
| 5 |
parking_space_location |
varchar |
64 |
车位位置 |
可空 |
|||||
| 6 |
parking_space_status |
int |
11 |
车位状态 |
可空 |
|||||
| 7 |
remarks |
varchar |
16 |
备注 |
可空 |
|||||
| 8 |
recommend |
int |
11 |
智能推荐 |
可空 |
|||||
| 9 |
create_time |
datetime |
创建时间 |
可空 |
||||||
| 10 |
update_time |
timestamp |
更新时间 |
可空 |
||||||
（7）表community_service实体用来存放系统社区服务信息中的业主、姓名、业主电话、服务类型、保修日期、服务信息、物业回复等；
表3.7社区服务信息community_service表
| 序号 |
数据库字段 |
字段类型 |
字段长度 |
存储内容 |
备注 |
|||||
| 1 |
community_service_id |
int |
11 |
主键 |
主键 |
|||||
| 2 |
owner |
varchar |
64 |
业主 |
可空 |
|||||
| 3 |
full_name |
varchar |
64 |
姓名 |
可空 |
|||||
| 4 |
owner_telephone |
varchar |
64 |
业主电话 |
可空 |
|||||
| 5 |
service_type` |
varchar |
64 |
服务类型 |
可空 |
|||||
| 6 |
warranty_date |
int |
11 |
保修日期 |
可空 |
|||||
| 7 |
state |
varchar |
16 |
状态 |
可空 |
|||||
| 8 |
service_information |
varchar |
16 |
服务信息 |
可空 |
|||||
| 9 |
property_reply |
varchar |
64 |
物业回复 |
||||||
| 10 |
recommend |
int |
11 |
智能推荐 |
可空 |
|||||
| 11 |
create_time |
datetime |
创建时间 |
可空 |
||||||
| 12 |
update_time |
timestamp |
更新时间 |
可空 |
||||||
（8）表article实体用来存放系统物业资讯信息中的标题、分类、封面图、标签、正文、描述等，用于前台用户浏览使用；
表3.8物业资讯信息article表
| 序号 |
数据库字段 |
字段类型 |
字段长度 |
存储内容 |
备注 |
|||||
| 1 |
article_id |
mediumint |
8 |
主键 |
主键 |
|||||
| 2 |
title |
smallint |
5 |
标题 |
可空 |
|||||
| 3 |
type |
mediumint |
8 |
分类 |
可空 |
|||||
| 4 |
hits |
varchar |
16 |
点击数 |
可空 |
|||||
| 5 |
praise_len |
int |
10 |
点赞数 |
可空 |
|||||
| 6 |
create_time |
datetime |
创建时间 |
可空 |
||||||
| 7 |
update_time |
timestamp |
更新时间 |
可空 |
||||||
| 8 |
source |
varchar |
255 |
来源 |
可空 |
|||||
| 9 |
url |
varchar |
255 |
来源地址 |
可空 |
|||||
| 10 |
tag |
varchar |
255 |
标签 |
可空 |
|||||
| 11 |
content |
varchar |
255 |
正文 |
可空 |
|||||
| 12 |
img |
varchar |
255 |
封面图 |
可空 |
|||||
| 13 |
description |
longtext |
描述 |
可空 |
||||||
（9）表owner_user实体用来存放系统前台业主注册信息中的药品类别；
表3.7业主信息owner_user表
| 序号 |
数据库字段 |
字段类型 |
字段长度 |
存储内容 |
备注 |
|||||
| 1 |
owner_user_id |
int |
11 |
主键 |
主键 |
|||||
| 2 |
user_name |
varchar |
64 |
用户名 |
可空 |
|||||
| 3 |
unit_number |
varchar |
64 |
姓名 |
可空 |
|||||
| 4 |
gender |
varchar |
64 |
性别 |
可空 |
|||||
| 5 |
unit_number |
varchar |
64 |
单元号 |
可空 |
|||||
| 6 |
house_number |
varchar |
64 |
门牌号 |
可空 |
|||||
| 7 |
parking_space_number |
varchar |
64 |
车位号 |
可空 |
|||||
| 8 |
examine_stat |
varchar |
16 |
审核状态 |
可空 |
|||||
| 9 |
user_id |
int |
11 |
用户id |
可空 |
|||||
| 10 |
recommend |
int |
11 |
智能推荐 |
可空 |
|||||
| 11 |
create_time |
datetime |
创建时间 |
可空 |
||||||
| 12 |
update_time |
timestamp |
更新时间 |
可空 |
||||||
物业管理系统的详细设计与实现主要是根据前面的物业管理系统的需求分析和物业管理系统的总体设计来设计页面并实现业务逻辑。主要从物业管理系统界面实现、业务逻辑实现这两部分进行介绍。
当进入物业管理系统的时候，首先映入眼帘的是系统的导航栏、轮播图以及公告信息，在左上角能够看到导航栏，其主界面展示如下图4.1所示。
图4.1 首页界面图
不是物业管理系统中业主的是可以在线进行注册的，当用户点击右上角“注册”按钮的时候，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号后等信息再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可业主注册成功。其用业主注册界面展示如下图4.2所示。
图4.2 业主注册界面图
物业管理系统中的前台上注册后的业主是可以通过自己的username和password进行登录的，当会员输入完整的自己的username和password信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的username和password在数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到物业管理系统的首页中；否则将会提示相应错误信息，业主登录界面如下图4.3所示。
图4.3 业主登录界面图
当访客点击物业管理系统中导航栏上的“物业资讯”后将会进入到该“物业资讯”列表的界面，然后选择想要看的物业资讯，点击进入到详细界面，物业资讯界面如下图4.4 所示。
图4.4物业资讯界面图
当访业主击物业管理系统中导航栏上的“社区服务”后将会进入到该社区服务提交的界面，系统会自动生成业主、姓名、报修日期，业主只需要填写好电话、服务类型、状态、服务信息，点击提交就可以了，社区服界面如下图4.5所示。
图4.5社区服务界面图
当业主点击右上角“我的”这个按钮，会出现子菜单，点击“我的账户”可以对个人的资料以及登录系统的密码进行设置，我的账户界面如下图4.6所示。
图4.6我的账户界面图
当业主点击右上角“我的”这个按钮，会出现子菜单，点击“个人中心”就会进入到业主的后台管理中，在这里可以对提交的社区服务进行管理，社区服务管理界面如下图4.7所示。
图4.7社区服务管理界面图
当业主在后台点击 “水电费缴纳”这个按钮，会出现自己的水电费信息，支持在线支付，水电费缴纳界面如下图4.8所示。
图4.8水电费缴纳界面图
当业主在后台点击 “物业费缴纳”这个按钮，会出现自己的物业费信息，点击“支付”按钮，选择支付方式进行缴纳，物业费缴纳界面如下图4.9所示。
图4.9水电费缴纳界面图
物业管理系统的管理员人员包括了管理员，物业经理以及物业员工三部分，其中管理员拥有最高的权限，可以对用户信息、系统信息以及物业服务信息进行管控。
管理员，物业经理以及物业员工在登录界面输入账号+密码，点击“登录”按钮，系统在用户数据库表中会对管理员，物业经理以及物业员工的账号进行匹配，账号+密码正确的话，就会登录到系统中各个用户的主管理界面，否则提示对应的信息，返回到登录的界面，如果管理人员忘记密码的话，点击“忘记密码”根据提示可以找回密码，然后再进行登录其主界面展示如下图4.10所示。
图4.10登录界面图
用户管理模块包含了管理员、业主用户、物业经理、物业员工四个部分，管理员、物业经理和物业员工在后台都可以查看到业主的信息，但是只有管理员可以对业主进行增删改查操作；管理员和物业经理可以对物业员工进行增删改查。这里以业主用户为例，界面如下图4.11所示。
图4.11 用户管理界面图
管理员、物业经理、物业员工点击“社区服务”这一按钮后会显示出前台业主提交的物业服务信息，任选一条物业服务信息，点击“编辑”这一按钮后，会对物业服务的状态进行设置，如果已经处理，可以设置成已处理，没有完成处理的话，可以设置成为待处理；社区服务界面如下图4.12所示。
图4.12 社区服务界面图
点击“房产信息”这一按钮后会显示出所有的房产信息，在房产信息界面可以添加新的房产信息，可以对房产信息进行修改、删除，也可以按照房型或者单元号或者房号对房产查询，房产信息界面如下图4.13所示。
图4.13 房产界面图
点击“车位信息”这一按钮后会显示出所有的车位信息，在车位信息界面可以添加新的车位信息，可以对车位信息进行修改、删除，也可以按照车位号或者所属人或者业主名字或者车位状态对车位查询，同时可以对车位的所有人进行设置，车位信息界面如下图4.14所示。
图4.14 车位信息界面图
点击“陌生人员登记”这一按钮后会显示出所有的陌生人员的登记信息，在陌生人员登记信息界面可以添加新的陌生人员登记信息，可以对陌生人员登记信息进行修改、删除，也可以按照名车或者登记日期对陌生人员登记信息进行查询，陌生人员登记界面如下图4.15所示。
图4.15 陌生人员登记界面图
点击“仓库信息”这一按钮后会显示出所有的仓库储物信息，在仓库信息界面可以添加新的仓库信息，可以对仓库信息进行修改、删除，也可以按储物名称或者储存时间对仓库信息进行查询，仓库信息界面如下图4.16所示。
图4.16仓库信息界面图
点击“水电费缴纳”这一按钮后会显示出所有的水电费缴纳信息，在水电费缴纳界面可以添加新的水电费缴纳信息，可以对水电费缴纳信息进行修改、删除，也可以按业主或者姓名或者单元号或者门牌号对水电费缴纳信息进行查询，同时支持支付操作，水电费缴纳界面如下图4.17所示。
图4.17 水电费缴纳界面图
点击“物业费缴纳”这一按钮后会显示出所有的物业费缴纳信息，在物业费缴纳界面可以添加新的物业费缴纳信息，可以对物业费缴纳信息进行修改、删除，也可以按业主或者姓名或者单元号或者门牌号对物业费缴纳信息进行查询，同时支持支付操作，物业费缴纳界面如下图4.18所示。
图4.18 物业费缴纳界面图
系统的前台、后台、数据库完成以后，这个系统才算是完成了一半，我们在这之后要对系统进行最后的一个阶段，那就是测试了，测试对一个系统来说是非常重要的，有的时候开发完一个系统，如果测试不合格的话，这个系统是没有办法进行投入使用的，所有我们要用测试对系统的功能进行检验，把不完善的功能尽量完善，把出现的bug解决掉，然后给用户呈现出一个完美的系统。通过对系统最后一步的测试，使得开发人员对自己的系统更加有信心，更加积极的为后期的系统版本的更新提供支持。
用户登录功能测试：
表5.1 用户登录功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 用户登录模块测试 |
用户登录成功的情况 |
点击前台首页左上角“登录”链接后账号和密码分别输入yonghu1和123456后点击“登录”按钮。 |
登录成功并调整到用户界面 |
正确 |
物业费信息添加功能测试：
表5.2 物业费信息添加功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 物业费添加模块测试 |
物业费添加成功的情况 |
在物业费缴纳的页面中将点击添加，选择业主+输入姓名+单元号+门牌号+物业费，输入正确的信息后然后点击“提交”按钮。 |
提示添加成功 |
正确 |
| 物业费添加模块测试 |
物业费添加失败的情况 |
在物业费建安页面中不填写的业主，其他信息正常输入“提交”按钮。 |
提示“添加失败，业主不能为空” |
正确 |
查询业主信息功能模块测试：
表5.3 查询业主信息功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 查询业主信息功能测试 |
查询成功的情况 |
菜单栏中点击用户管理菜单下的子菜单业主用户，输入入用户名或者姓名对业主用户进行查询 |
查询成功 |
正确 |
查询物业资讯信息功能模块测试：
表5.4 查询物业资讯信息功能测试表
| 测试名称 |
测试功能 |
操作过程 |
预期结果 |
测试结果 |
| 查询物业资讯信息功能测试 |
查询成功的情况 |
在系统的首页点击菜单栏中物业资讯这个按钮，查看物业资讯列表，对物业资讯进行查询 |
查询成功 |
正确 |
通过对物业管理系统的调试，能够检测物业管理系统的稳定性，为物业管理系统正式运行、稳定运行提供了可预测性的维护备案。能够帮助使用者熟悉整个物业管理系统，并对物业管理系统可能出现的错误有所了解。本章节提供了部分调试用例及调试日志，可以帮助使用者解决简单的错误问题，也加深了开发者对于此框架下的物业管理系统编写的了解度，为后期开发者顺利完成物业管理系统、发布物业管理系统提供了非常大的帮助。
本次物业管理系统的开发中我学会了例如良好的编程思想和完善的规划思想。在着手编程之前需要罗列出程序框架的大概，脑海中构建出程序的主题框架。做好这一步我们才能胸有成竹的经行开发项目。当设计框架了熟于心之后，需要思考本次编程所需的主要知识点和技术点，并充分学习。如此一来项目的开发才能循序渐进、如丝般顺滑，长久以往就能养成良好的开发习惯。一个程序好不好还要看出的bug多不多，如果在项目完成前做好bug的查验与预防可能发生的事故才能保证程序的稳定长久性运行。如果项目在完工后出现各种问题自己，那么在进入社会后，不仅会给公司团队带来麻烦和增加不必要的工作，还会导致客户流失，公司对自己的评价下降。
在本次项目中我也暴露了诸多问题。对于PHP相关的编程知识有所欠缺，环境配置和算法上出现诸多问题，时常导致项目运行出错，或者目标的实现有问题。或者实现想法时算法未优化，使得代码冗长，程序运行不顺畅。
[1]网页设计与网站建设从入门到精通[M]. 化学工业出版社.张翔.2012
[2]Java Web应用开发教程[M]. 北京邮电大学出版社.于静.2010
[3]互联网+时代PHP动态网站开发技术[J].周黎宁.科技风.2019(04)
[4] PHP Web程序设计与项目案例开发[M]. 清华大学出版社.马石安. 2019
[5]网站建设与管理基础及实训[M]. 清华大学出版社.吴代文.2013
[6] The Comparison Firebase Realtime Database and MySQL Database Performance using Wilcoxon Signed-Rank Test[J]. Margaretha Ohyver，Jurike V. Moniaga，Iwa Sungkawa，Bonifasius Edwin Subagyo，Ian Argus Chandra.Procedia Computer Science.
[7] 基于PHP的简单网页设计[J]. 李秋锦.科技经济导刊.2019(16)
[8]网络数据库连接技术及运用之研究[J]. 赵辉，熊文俊.电脑知识与技术. 2019(17)
[9] Evgeny A. Antipov， Elena B. Pokryshevskaya.Rank-sales relationship in electronic commerce: Evidence from publicly available data on 11 product categories[J].2016.16
[10] Rapid software integration using structured methods[J]. Mark J. Bennett.Journal of Systems Integration.1992(1)
[11]胡锋.基于PHP及MySQL数据库的行业网站建设[J].电脑知识与技术，2016.
[12]陈云芳，潘利华，陈瑞，刘小清，吴丽.基于PHP语言访问MySQL数据库的实现[J].中国新通信，2015.
[13]李年安.基于PHP的网站编程设计与实现[J].电脑开发与应用，2014.
[14]（美）W Jason Gilmore.PHP与MySQL程序设计[M].人民邮电出版社，2011.
[15]（澳）威利，（澳）汤姆森.php和mysql web开发(第4版) [M].机械工业出版社，2009.
致谢
至此论文结束，感谢您的阅读。在此我要感谢我的导师，虽然我在实习期间很忙，论文撰写总是停停改改，但是导师依然十分负责，时不时的询问我的任务进展情况，跟进我的论文进度。虽然我在实习期间很忙，以至于很晚才开始进行论文撰写和编写程序的工作，但是在指导老师的帮助下，我逐步完成了自己的论文和程序，从导师身上也学习到很多知识，和经验，这些知识和经验令我受益匪浅。也从导师身上看到了自己的不足，不论是在即使层面上还是在对待工作的态度上，倒数如同明镜一般照出了我的缺点我的不足。此外，我还要感谢在我实习期间在论文和程序上帮助过我的同学和社会人士，此前我对于PHP方面的一些知识还不了解，是他们在我编写程序过程中给了我很多的启发和感想，也帮助了我对于程序的调试和检测。没有他们我是不能顺利完成本次毕业设计的。至此，我的毕业设计就花上了一个圆满的句号了。
点赞+收藏+关注 → 私信领取本源代码、数据库