Classification number_______________ Classification_______________
UDC _______________ Student Number_ ___
Graduation Design (Thesis)
Graduation design (thesis) task statement
page 1
| Graduation project (thesis) topic: Design and implementation of the management system of nursing home based on java Graduation project (thesis) requirements and original data (materials): 1. Summarize the actual needs and development environment of nursing home operation management;2. In-depth understanding of related technologies for developing nursing home operation management system; 3. Briefly describe the functions to be realized by the nursing home operation management system; 4. Design and implement these functions; 5. Test each function and realize the whole system test; 6. 7. Train the ability to retrieve and utilize literature information; Train the ability to write technical documents and dissertations. |
|---|
page 2
| Graduation project (thesis) main contents: 1. Summarize the actual needs and development environment of nursing home operation management;2. Understand the related technologies of developing nursing home operation management system; 3. Familiar with the development environment of nursing home operation management system; 4. Briefly describe the workflow of the operation management system of nursing homes; 5. In-depth analysis, design and realization of the functions of the operation management system of nursing homes; 6. Perform functional testing as well as testing of the entire system. The design documents (thesis) that students should submit: 1. Graduation project thesis with complete content, clear hierarchy, smooth narrative, and standard typesetting; 2. Graduation design electronic documents and other related materials including graduation design thesis, source program, etc. |
|---|
Page 3
| Main references (data): Xiong Jie. Design of Hotel Accommodation Management System [J]. China Science and Technology Expo, 2015(29). Meng Xiaofeng, Zhou Longxiang, Wang Shan. Development Trend of Database Technology [J]. Journal of Software, 2004, 15(12). Lu Haoyin. Introduction to JSP technology[J]. Journal of Longdong University: Natural Science Edition, 2007(2). Zhang Liangyin. On C/S and B/S Architecture[J]. Engineering Geological Computer Application, 2006(4). Shen Jue. MVC Design Pattern [J]. Science and Technology Square, 2009, 2009(9). Li Fudi. Introduction to Feasibility Study [J]. Southwest Finance, 1984(12). Tian Min, Jin Xing. Technology A Preliminary Study on Design Principles and Methods of Archives Database Management System[J]. Computer and Modernization, 2007(4).Xu Jing. Research on Web-based Information Management System Framework under J2EE Architecture[J]. Silicon Valley, 2015(1).Wang Hua. Exploring the Operation Principle of Java Database Connection Pool[J]. Fujian Computer, 2010, 26(8). Lu Lu, Wang Wenli. Talking about Software Testing Technology[J]. Journal of Zhengzhou Railway Vocational and Technical College, 2007, 19(2). Wang Ping. The Importance of Software Testing[J]. Software Guide, 2009(4).Jacob K. Hotel inventory management system and method: US, US20070075136[P]. 2007.Xia C. The realization of MyEclipse and database connection [J]. Journal of Wuhan Engineering Institute, 2013.Gray J. Notes on Data Base Operating Systems[C]// Operating Systems, An Advanced Course. Springer-Verlag, 1978:393-481.Xia XX, Xin B Y. Compare B/S mode with C/S mode[J]. Journal of Yanbian University,2002. Roth R R. SOFTWARE TESTING: US, US 20080010539 A1[P]. 2008. Yan Hao, a student in class 1304 of professional software class, required design (thesis) work starting and ending dates from March 13, 2017 to June 25, 2017 for guidance The teacher's signature, the date of Xu Song's review, the signature date of the department head's approval and signature date |
|---|
Design and Implementation of Java-based Nursing Home Management System
Summary
Since the new century, with the rapid development of the Internet and computer technology, my country has also entered the era of networked and integrated information big data. For the general public, stand-alone applications have long been a thing of the past, and the traditional model can no longer meet the needs of various fields such as office life. There are very few software that are not connected to the Internet on a computer, and they are replaced by interconnected software systems. information big data society. Fast-paced living environment, data information flying all over the sky, microelectronics technology is not as good as before, backward and inefficient office methods are gradually being eliminated, and information management has been pushed to a new climax by the times. However, information is a new type of resource that cannot be seen or touched, but it is particularly important. Management and manipulation of information has become a new discipline, and information management systems were born in the United States. The nursing home management system uses IT technology to provide an interface for nursing homes to manage information, store personal information and other information of the elderly, and search and update information in nursing home files, which saves labor time of employees and greatly reduces costs.
The nursing home management system used in this design is developed based on the JAVA platform, and the system uses JSP as a programming language. The establishment of background data server utilizes MySQL database. This paper mainly introduces the development environment of the system (background at home and abroad, software introduction, demand analysis), functional module design ideas and development process. Emphatically explain the technical problems encountered in the development of system errors and the final solutions.
Keywords Nursing home; jsp; information management system
Design and implementation of gerocomium management system based on Java
Abstract
Since the new century and as the rapid development of internet and computer technologies, China has also entered into the big data era. For the common, the standalone application has passed by and no longer can satisfy people’s diversified requirements. At present, there is little software that didn’t need to access to network. On the contrary, the connected software system constitutes the big data society. As the popularization of fast pace of life, increasing data information and upgrading micro-electronic techniques, the backward office means are eliminated gradually and information management rise sharply. Information is invisible but also a vital new resource. Management and controlling of information was derived from America and has become a new subject. By utilizing IT technology, the gerocomium management system could provide an interface for information management, such as storage of elder’s information, look up and update information, which could save the working hours of staff and reduce the cost.
The development of the gerocomium management system that this design adopted is based on JAVA platform and the system is JSP programming language. The establishment of background data server is based on MySQL database. This paper mainly introduced the development environment (domestic and international backgrounds, brief introduction of software, demand analysis), design thought of function module as well as introduction of development process. Moreover, this paper emphasize on technical problems and final solutions in the process of system development.
Keywords Nursing Homes; jsp;MIS
Table of contents
Summary 11
Abstract22
Chapter 1 Introduction 66
1. The basis and significance of topic selection 66
2. Research on current situation at home and abroad 66
3. Research purpose 77
Fourth, the main content of this study77
V. Arrangement of chapters in this article 77
6. Summary of this chapter 88
Chapter 2 Design Technology and Development Environment 99
1. Introduction of Related Technologies 99
(1) Introduction to JSP 99
(2) B/S mode analysis 1010
(3) MVC design pattern 1010
2. Introduction to development tools 1111
(1) Introduction to Myeclipse 1111
3. Development environment introduction 1111
(1) Introduction to Tomcat 1111
(2) Introduction to JDK 1111
Four. Summary of this chapter
Chapter 3 System Requirements Analysis 1313
1. Feasibility study 1313
(1) Economic feasibility1313
(2) Technical feasibility1313
(3) Operational feasibility
(4) Time Feasibility 1313
(5) Legal feasibility1414
Second, demand analysis 1414
(1) Application Requirements Analysis 1414
(2) Analysis of operational requirements 1414
(3) Other needs analysis 1515
3. Functional requirements 1515
Fourth, system use case analysis 1616
(1) Overall use case analysis of the system
(2) Analysis of administrator identity use cases
(3) Use Case Analysis of Nursing Worker Identity 1919
V. Summary of this chapter
Chapter 4 System Design 2222
1. Overall system design 2222
(1) User Information Management 2222
(2) Login 2323
(3) Nursing leave management 2424
(4) Additions, deletions, modifications and inquiries of the elderly 2525
(5) Addition and deletion of accident records 2626
2. System development steps 2727
3. Outline design 2727
4. Data dictionary 2828
(1) Data structure 2828
(2) Data flow 2929
(3) Data Storage 2929
(4) Process 3030
(5) External entities 3232
5. Database conceptual structure design 3232
6. Database logical structure design 3333
7. Summary of this chapter
Chapter 5 Detailed Design and Implementation 3636
1. Program flow chart 3636
(1) Data addition flow chart 3636
(2) Data modification flow chart 3737
(3) Data deletion flowchart 3737
(4) Data search flow chart 3838
Second, the system class diagram 3838
3. System login module 3939
4. Realize 4040 on the home page of the system
5. The password management module realizes 4040
6. User information management module 4040
Seven, the elderly information management module realizes 4141
Eight, the accident record management module realizes 4141
Chapter 6 Program Testing and Evaluation 4343
1. Program debugging 4343
2. Program test 4343
(1) The purpose and importance of the test 4343
(2) Test steps 4444
(3) Main content of the test 4444
(4) Test case 4646
3. Test results and analysis 4848
(1) Statistical Analysis of Test Situation 4848
(2) Functionality 4848
(3) Ease of use 4848
(4) Compatibility 4949
(5) Defect Summary 4949
Four. Summary of this chapter
Conclusion 5050
Thanks 5252
Chapter One Introduction
With the sudden advent of the information age, great changes have taken place in our lives. The rapid changes can be seen in all fields of society. This is all due to the innovation of information technology. The combination of medical care and medical care is the call of the country and the trend of the times. Competitiveness needs to start from itself Development, so as to strengthen the nursing management capabilities of nursing homes, and grow into modern nursing homes to adapt to the changing needs of the elderly in our country. The needs of nursing homes continue to expand, and the need for information is already essential. The daily work of nursing homes is inseparable from computers and networks. The modern management model that integrates is the only way to provide convenience for the elderly and medical staff. In order to show that it has more competitive advantages than ordinary nursing homes, this system designs a software that conforms to the management mode of modern nursing homes according to the particularity and universality of nursing homes, so as to respond to the national call for medical care and speed up the construction of modern nursing homes.
1. Basis and significance of topic selection
With the development of information technology, the information management of nursing homes has also ushered in opportunities and challenges. Because, in the future, the Internet will be an open environment, and the traditional management operation is a management model that separates object maintenance and medical treatment. It has many limitations in the current environment where living conditions are constantly improving, and it is difficult to adapt to it. At present, the management of nursing homes can only be called nursing homes or community outpatient clinics. It can be said that the traditional management model is far from being able to adapt to the current well-off society where people's living standards have been greatly improved. In the early stage of Internet technology, it has not been widely used in processing, communication, and home care management information systems before nursing homes. The information is all manually operated and requires multiple procedures. Management, if the traditional model is adopted, will cause a large loss of human, material and financial resources. The emergence of different statistical methods to query and duplicate information problems, such a process promotes the realization of information technology, and an efficient and easy-to-operate information system is urgently needed to improve the current situation. Therefore, under the premise of the development of the great era, the management system of nursing homes And born. Therefore, as a modern nursing home, it is necessary to establish a new information management model to deal with these new forms. The nursing home management information system is a representative work of the combination of medical care and has the function of promoting the development of the labor force, which is of innovative significance. As a powerful driving force, the construction of information system not only promotes the innovation of management mode and system innovation of nursing homes. At the same time, in the high-speed information age, the nursing home management system has become the core of a modern nursing home that combines medical care.
2. Research on current situation at home and abroad
Switzerland has been hailed as a "retirement paradise" many years ago. The reason why the pension system is developed is that it is a well-known country with an aging population. Compared with other countries, the pension system is more complete, otherwise it would not be able to support the current situation in the country. There are four aspects of the Swiss pension system: old apartments, nursing homes, elderly care homes and family elderly care. The advanced pension model that Switzerland currently relies on is mainly led by the state and plays a major role. It is composed of three parts except a small part of funds for individuals and units. A large part of the credit for Switzerland's social stability does not depend on the pension system. And they discovered very early that nursing homes must be combined with information management as soon as possible to improve the management of nursing homes and follow the trend. The Swiss pension system is famous for its complete functions, high efficiency and completeness.
At present, the nursing home industry in our country has not been recognized by the public. The traditional idea of raising children to protect the elderly has appeared in almost everyone's mind. They think that only the elderly who have no children go to nursing homes. Many elderly people are ashamed to go to nursing homes. There are also news reports that black-hearted nursing homes abuse the elderly, and the pension industry in our country only stops at pensions, and the elderly without pensions can only rely on their children. Following the call of the country, it is urgent to build a modern nursing home, adopting a new management model that combines medical care and close contact with the family. It has been recognized in the open area in the south of our country, and gradually spread to all parts of the country to deal with a series of unnecessary troubles caused by our country's aging society. The information management realized in early nursing homes in our country has always been relatively backward, and it is still using software that is not connected to the Internet. In the application of software, various nursing information management systems have been developed by Chinese software development and information companies, but most of the MIS are based on function applications. At present, the information management system of nursing homes in China has not realized the combination of various types of medical care and modern nursing homes. The requirements and functions are even more lacking, and the international standards are far higher than our level. To achieve international recognition, we need continuous efforts. In order to meet the requirements of international development, the nursing home management system will be a difficult problem that our country will solve at present. In recent years, the speed of the rise of my country's IT industry is not what we can imagine. It is just around the corner to catch up with Europe and the United States. In the information management of nursing homes, a large amount of information records and updates are required. The traditional manual management mode can no longer be relied on. Using IT technology to manage information is a Overwhelming, it was a labor liberation. At present, my country's economic level has always been at the forefront of the world, and the living standards of ordinary people are greatly different from those in the past. The information industry is a new scientific and technological innovation that is applicable to all walks of life. Therefore, the information industry not only improves the means of office work, but also popularizes modern office work, improves its working environment and reduces working pressure. This is a symbol of my country's technological progress and an important manifestation of the improvement of people's livelihood.
The purpose of this project is to make the information management of nursing homes clear, transparent, easy to operate and easy to manage. Through the study of foreign language materials, each functional module has been optimized, and more attention has been paid to modern management details. In the management process, automation and informatization have become the most important office means as much as possible. The reliability of automation lies in the fact that automatic completion is simple and cumbersome. It is a happy thing for the staff to remember the wrong work and automatically repair the manual operation. Compared with the traditional nursing home management mode, the error rate is reduced and its own competitive advantage is improved. For the managers , The cost is reduced, and more importantly, the nursing home can better serve the elderly. This is the purpose of the development of information management.
For developers and designers, how to develop a practical nursing home management system that meets the current situation is the real challenge. Through the in-depth investigation and research on the nursing home management system, this paper elaborates in detail from the aspects of demand analysis, feasibility analysis, system overall design, module function design, data format, test and evaluation, and provides a theory for the design and implementation of the nursing home management system. in accordance with.
4. The main content of this research
This paper first summarizes the research background and significance of the nursing home management system, and analyzes the related technologies. Further optimize and upgrade the relevant technologies involved in the system, thus establishing a complete nursing home management system. This paper focuses on the following explanations:
(1) Under the premise of building a new system, conduct a detailed analysis and summary of the background and research status, and introduce the main technologies and technical difficulties that will be adopted in system development.
(2) Use software engineering thinking to conduct requirements analysis on the basis of distinguishing functional requirements from non-functional requirements; use the requirements to analyze the business flow design of the system; then design a system use case diagram and describe the system based on the above content designing process.
(3) This article adopts B/S architecture and uses the MVC three-tier design pattern to build this system.
(4) After the system design is completed, the performance of the system is tested accordingly. During the test, both the white box test method and the black box test method are used, including compatibility test, through a combination of various tests way to ensure the security and effectiveness of the system.
5. Arrangement of chapters in this article
This article includes 7 chapters in total, and the specific arrangements of each chapter are as follows:
The first chapter: Introduction, in this chapter mainly analyzes the research background and research significance of this paper, and summarizes the main research content of the paper, and finally gives the chapter arrangement of the paper.
The second chapter: the basis of related technologies, in this chapter, the related technologies that will be adopted in the system construction are introduced in detail and fully, laying the foundation for the realization of the system.
Chapter Three: System Feasibility Study and Requirement Analysis, discusses from two angles of system non-functional requirements and functional requirements. Combined with the actual needs of the system, a detailed use case analysis of the key modules of the system is carried out.
Chapter 4: System Design, starting from the overall system architecture design, and analyzing the system design situation step by step.
Chapter Five: System Realization, which shows some interfaces of the important functional modules in the system.
Chapter 6: System testing, this chapter studies the related technologies, testing methods and testing tools of system testing, and conducts a detailed system testing of the system.
Chapter Seven: Conclusion, summarizing the work, and describing the key content that needs to be improved in the future.
6. Summary of this chapter
With the popularization of the Internet and the development of related network technologies, the development of my country's information management system has entered a new stage. In this paper, by understanding the development status of information management in our country, aiming at the design and implementation of nursing home management system, the overall functional structure of the system is summarized.
two
The nursing home management system mainly uses MyEclipse development environment, with JSP, JAVA as the main programming language, Tomcat as the operating environment, and MYSQL database management technology for development. The following is an introduction to related development tools and technologies.
(1) Introduction to JSP
JSP was first proposed by Sun Microsystems. After its promotion, many computer and software companies gradually participated in the development. It is mainly implemented by embedding Scriptlet and JSP tags in HTML files (*.htm, *.html). In this way, the embedded Java program can take effect, make a request to the database, or enable E-mail, etc. JSP probably appeared at the end of the last century. Sun Microsystems hopes to use it to build dynamic websites and use its compatibility and scalability to expand platform applications. Judging from the actual effect, the appearance of JSP technology makes the construction and design innovation of Web continue. [9] Its characteristics are roughly as follows:
Relying on JSP technology, engineers and technicians can use XML or HTML tags to modify or overturn the design of web pages. The content on these pages can also be designed or implemented based on JSP. [3] In addition, the content in the web server will be stored in Servlet and JavaBean, and also reflected in the script. In this way, the information and requirements sent by the content of the server designed using the JSP programming language can be interpreted through the JSP index, or designed or established according to its script. Of course, these final contents will also be fed back to the browser in the form of HTML or XML. In this way, the source code writers can maintain their own patents and rights, and the compatibility and scalability of web pages can also be guaranteed. [3]
Generally speaking, a single JSP page does not undergo complex data analysis and processing, and is generally used for crawling or index extraction to grab data.
JSP is based on the Java programming language. It has tags and scriptlets inside, which can be used to store a set of program methods needed for dynamic page operation. In addition, JSP separates a set of program methods required for dynamic page operation from static web page design. Such module division makes JSP compatible and extensible, and has higher development. After all, JSP (JavaServer Pages) can realize dynamic page control, and can separate the page operation program from the static page.
A JSP page consists of two parts, HTML and Java code. Generally speaking, if the upstream server receives an external request or information, it will analyze or process the Java code, and then feed back to the web browser in the form of HTML. Java Servlet is its foundation, and the development of large-scale JSP projects generally relies on both Java Servlet and JSP. Technically, JSP has the unique characteristics of Java, such as easy to understand, easy to use, wide applicability, no choice of platform, and high security. These advantages ensure its widespread use throughout the Internet. After its appearance at the end of the last century, many companies now use its servers, such as the more famous IBM, Oracle, and Bea, which have gradually become the "darling" of e-commerce software development. ,
Specifically, JSP has the following advantages:
1. It has the advantages of multiple use. Generally speaking, coded programs can be nested and used in various systems without rewriting the code. This is its advantage over PHP.
2. In addition, its compatibility is relatively good. Basically do not choose the platform, common platforms can be compatible and developed, applied, extended. This just complements PHP's non-extensibility.
3. Wide applicability. Whether it is a small war file or a multi-level platform and server, it can be compatible and run. It can perform data analysis, processing, and feedback on various platforms of different sizes, showing strong adaptability.
4. It can rely on tools with rich types and excellent functions. After nearly 20 years of development, JSP now has a lot of development tools. These tools are powerful, covering almost all aspects of program development and design, and can be obtained at almost no cost, providing developers with convenience.
(2) Analysis of B/S mode
The C/S mode is composed of Client, Server and middleware. Among them, Client is mainly used for the interaction and transfer of information between customers and standard components. The server mainly manages database resources in a centralized manner. When multiple requests need a certain resource at the same time, it can be optimized and allocated. Middleware acts as a third-party connection between the user and the server. Through its connection, requests and information can flow smoothly between the user and the server.
The biggest difference between B/S and C/S mode is the client side. From the perspective of external use, B/S generally does not need to install a dedicated client on the computer, and does not need to connect to the server through a dedicated program. Its connection is generally realized through a browser with standardized settings. This can avoid the cumbersome installation of the client, free up the user's hard disk space, make the user's computer interface more beautiful and clear, and the use effect is better.
In terms of operating experience, in the C/S mode, if users want to operate familiarly and interact with the server for requests and information, they need to have a certain grasp of the installed client and be familiar with its interface and basic operations. For the B/S mode, since the interface of the browser is standardized, the operation methods and buttons are similar, and users can easily get started without spending too much time and cost. In terms of system security and daily maintenance, B/S is undoubtedly easier.
Judging from the current development, B/S already has the function of disclosing information online, which is developed from MIS. And C/S can't realize this function for the time being. In the application of appointment registration software, using this online announcement and release function can reduce the printing and distribution of hospital paper materials and improve its operational efficiency.
From the above comparison of B/S and C/S, it can be found that B/S has incomparable advantages in the MIS platform. Therefore, the B/S structure is selected in the design of this project.
(3) MVC design pattern
MVC is the abbreviation of Model View Controller in English, which means: model-view-controller, the MVC design pattern separates the business logic layer and the data layer separately, solves the problem of system input, control and display, and helps the development of the system And maintenance, the MVC design pattern is currently the most commonly used and most suitable design pattern for system development. The functions of each layer are described in detail below.
(1) Model layer. This layer is the core part of the application. A model often corresponds to many views. The purpose of this design is for the reusability and portability of the application. It only needs to modify the specific business information and does not need to rewrite the same code. Thereby improving the function of the system and facilitating the maintenance of the system. This layer connects the system business layer and data processing layer, and the application program reads and stores data from the database through the model layer. If the business information of the application is changed, the model layer will issue instructions to both the business layer and the view layer.
(2) View layer. This layer mainly presents the data processed in the application to the user through a friendly interface, and the user can only interact with the system through the view layer. The view layer does not perform any processing or operation on the data, but is only used to receive user information and present the information to the user, and to transmit the update of the model to the data to the user in real time. Usually, the view layer is generally designed by code composed of HTML, plus some markup languages such as Flash and XML, and Web Services.
(3) Controller. This layer is mainly used to solve the related requests of the system business. It is usually responsible for invoking the model according to the user's input to execute the user's needs. At the same time, it can control how the data in the model is displayed to the user through the view. The execution process of the controller is: the user inputs the relevant request and notifies the view layer, the controller receives the request from the view layer and sends instructions to the model layer through a certain algorithm, the model layer returns the data, and finally passes it to the view layer, and sends the data presented to the user.
We describe the MVC design model in detail through the server (controller, model, and routing) and browser (page structure, style, and behavior), as shown in the following table:
The characteristics and advantages of MVC mainly include the following points:
The MVC design pattern is generally used in ERP and office systems with strong interactivity and many users;
The MVC design pattern can display multiple data models with one view, and can also support multiple views to access the code of the same server;
The MVC design pattern is convenient for building models, and it is easy for users to interact and express with applications.
The MVC design pattern is divided into three levels. Relative to the division of responsibilities of developers at each level, the developers at each level only need to focus on the development of the corresponding level, thereby improving the development speed and shortening the delivery time of the application.
2. Introduction of development tools
(1) Introduction to Myeclipse
MyEclipse is a commonly used development software in an IDE environment, and is widely used in the development of J2EE and Java. Its functions are very powerful, and it can debug the development software to improve the efficiency of debugging or development. It can directly translate source files, which is very worry-free and labor-saving, and basically supports all kinds of source files. In addition, it can also automatically generate some more standard codes for easy use. From a practical point of view, its coverage is wide, almost including source file compilation and development on the market. [1] In the design of this topic, after the java is structured, some development tools are needed to use it, and here we use Myeclipse.
3. Development environment introduction
(1) Introduction to Tomcat
Tomcat is a commonly used web server. Because its source code is free, the market is relatively wide. It can support users to access a small number of scenarios at the same time, and belongs to a small-scale server. It is also a common server in JSP design and development. Generally speaking, information interaction or communication can be directly performed on HTML pages through tomcat. It is worth noting that tomcat is separated from Apache at work, as an independent operation and analysis process.
When tomcat and Apache work at the same time, if everything is in a normal state, then Apache will return the request to the HTML page. Of course, the actual work behind it is the Tomcat JSP page and Servlet. When Tomca works independently, it also has the function of processing HTML. But this function is not as good as Apache.
- Introduction to JDK
Simply put, JDK is an SDK for developers, which provides a Java development environment and operating environment. SDK is Software Development Kit, which generally refers to software development kits, which can include function libraries, compilers, etc.
JDK stands for Java Development Kit
JRE is the Java Runtime Environment, which refers to the Java runtime environment, and it is for users of Java programs, not developers.
If JDK is installed, it will tell you that your computer has two sets of JRE, one is located in \jre and the other is located in C:\Program Files\Java\j2re1.4.1_01 directory, the latter set has less Server than the former set Java virtual machine on the server side, but just copy the Java virtual machine on the server side from the previous set. And when installing JDK, you can choose whether to install this JRE located in the C:\Program Files\Java directory. If you only install JRE, not JDK, then only one set of JRE will be installed in C:\Program Files\Java directory.
The status of JRE is like a PC. The Win32 application programs we write need the operating system to run for us. Similarly, the Java programs we write must also require JRE to run. So after you install JDK, if you install two sets of JRE in two different places on the hard disk, then you can imagine that your computer has two virtual Java PCs, both of which have the function of running Java programs. So we can say that as long as your computer has JRE installed, you can run Java applications correctly.
4. Summary of this chapter
This chapter makes a detailed introduction to the relevant technologies used in system development, and finally chooses B/S to develop this system; in addition, it introduces the MVC design module and development environment.
Requirements analysis is to analyze the needs of users. It is the last life stage of software definition. The result it must obtain is to accurately answer the question "what must the system do?" Requirements analysis is also the starting point of database design. Whether the final result of requirements analysis can accurately reflect the actual requirements of users will completely affect the subsequent design stages and whether the design results are reasonable and practical.
1. Feasibility study
Many nursing homes now use paper and pen for manual management. This kind of management has no advantage at all. It does not meet the requirements of modernization, and the cost is extremely high and the error rate is extremely high. Therefore, we should continue to learn, constantly absorb advanced foreign experience, use science to prove everything, and move towards technology to improve efficiency and reduce costs towards modern nursing homes.
(1) Economic feasibility
Economic feasibility mainly refers to the cost and budget of the initial investment, or the good news brought by the government's preferential policies, and there is also an aspect of later investment and later recovery costs. Since the system is a self-developed graduation project, there is almost no economic investment. After the future pension system is completed, it will bring staff a different experience in information management, reduce labor costs, and save capital costs. , Greatly improved people's working conditions, more convenient to process information, shortened working hours, developed office automation, improved information management efficiency, reduced error rates, simpler user operations, simpler and easier-to-operate interface, function template distribution More reasonable, management costs are no longer a concern for managers. The development of the project is almost zero in terms of economic cost, and the system greatly improves the work efficiency of the staff and saves money. All costs are almost free, so it is absolutely passable economically.
(2) Technical feasibility
Technical feasibility is mainly through the research on the technology required by the project, and the comparison with the technical analysis that can be achieved at present, and whether the economic benefits obtained after the project is put into use and whether it will affect the environment after it is put into use. From the analysis of the second chapter, we know that this article mainly uses JSP programming language in the design process to make HTML dynamic pages. It is convenient and quick to debug. In terms of software: B/S software development mode is adopted. This mode is very mature at present, and there are no major technical problems, so the software development platform is technically feasible.
(3) Operation feasibility
The development of this system program is the crystallization of modern nursing homes. It is a typical system combining information management and medical care. It is mainly used for information processing, including information collection, information search, and information storage.
After the new system is in operation, we need to consider the impact of the existing system on the working environment, management, and organization. At the same time, we should pay attention to the aspects after the system is put into use, for example: simply train the users to prevent damage to the system and information management mistakes, and at the same time, check whether the tasks are completed and whether the tasks are completed within the specified time. Difference.
Judging from the current technology in our country, the staff should have the ability to use the system. Although there are different difficulties for different users, this is not something that developers should worry about, nor is it a problem. So the system operation is feasible.
(4) Time feasibility
In terms of time, fresh graduates have a good foundation in their undergraduate studies, plus three months of study and investigation, reading papers related to information management systems through the library, and an in-depth understanding of nursing homes, basically Finishing the project was no problem either.
(5) Legal feasibility
1. All technical information used is legal.
2. In the process of developing nursing home management, it is all done behind closed doors, and there is no intellectual property issue.
3. There is no copying of the current nursing home system, so there is a problem of infringement. So there is no infringement issue.
In short, everything is completely reliable in terms of the development of the economic system, technology, time, and law.
2. Demand Analysis
With the advent of the information age, people have passed from the era when they knew nothing about the information industry. The public cannot live without the Internet, and yearn for a life of office automation. We can proudly say that this is no longer a dream, and the information is complicated. The chaos has brought a lot of problems to the staff, not only is it difficult to sort out, it takes a lot of time, and it is easy to make mistakes if you are not careful. At present, the nursing home management system has adapted to the current era background, and it cannot satisfy the existing use for the staff. The inefficient and backward means need to be improved, and it is prone to errors and has a bad impact. In order to help information management personnel manage information in nursing homes, improve work efficiency, free up more time, and provide better services for the elderly, the developer has made full use of the current booming information industry resources to develop a complete set of A fully functional modern nursing home management system.
In the design of this topic, B/S architecture is used, and certain database knowledge is used for design. In the development and design, the JSP programming language is selected. The main purpose is to solve the backward and inefficient office means of information management in traditional nursing homes, and replace them with a new modern management model. This system combines the standard nursing home management information system with the modern complete nursing home information management steps to realize a complete virtual reality. At the same time, realizing the functions of the nursing home management information system can improve the working efficiency of the management personnel, improve the living environment, and the business operation is simple, which can actually solve the incomplete management of the hospital's patient information.
(1) Analysis of Application Requirements
The performance requirements of the system usually refer to the system's ability to process information and issues such as reliability, utilization, and ease of use. System hardware environment: Core 5600, 1G MB (RAM), 120GB (HD). In order to increase the momentum during the development period, there are no particularly strict requirements on information security, let alone encryption operations on data. In addition, and more importantly, the system program is robust, the system is an independent system, and its ability to run autonomously is good, and it does not need to depend on other applications. The details are shown in Table 3-1.
Table 3-1 System performance table
Figure 3-1 System Performance Table
| server | hardware | Processor: Intel Core Memory: 512M or greater Hard Disk: 120G or greater |
|---|---|---|
| software | Microsoft Windows XPMicrosoft mysqlMicrosoft tomcat 6.0 or higherMicrosoft Office 2003 | |
| Client computer | hardware | No special requirements, as long as you can connect to the Internet |
| software | Microsoft Windows XP Microsoft Internet Explorer 6.0 or later |
(2) Analysis of operational requirements
Hardware conditions: CPU, 1G RAM, PC requires 10G hard disk or above; printer.
Software conditions: Windows 7, IE8.0 or above.
(3) Other demand analysis
Proceeding from reality, the design of this project should take into account issues such as efficiency, ease of operation, and ease of later maintenance. Users can learn how to operate the system and how to manage information more easily. At present, our understanding of maintainability is temporarily stuck on readability and testability. We found in the development and design of the system that the biggest problem is the contradictory point of the goal, so it is particularly important to weigh the pros and cons during the development process, not only from the system function modules but also from the system hardware requirements. If you are not careful, you will cause even greater losses.
3. Functional requirements
Through research and analysis, this system is mainly designed for the staff of nursing homes.
From the perspective of the administrator, that is, the person in charge of the nursing home, he urgently hopes that after using the system, it will be more convenient to manage the nursing home, including the management of employees, the management of the occupancy of the elderly, and the check of bed occupancy information; Personnel management can be performed more conveniently, including modifying old employee information and adding new employee information; financial management can be performed more conveniently, that is, salary management based on employee leave records and payment records for elderly people when they move in.
From the perspective of nurses, they urgently hope that after using the system, they can modify personal details more conveniently; check the information of the elderly they are responsible for more conveniently; and manage bed occupancy more conveniently.
According to the analysis of the above role requirements, the main functions of this system include: login, user information management, elderly information management, accident records, leave records, bed allocation, occupancy fees, nurse salary and nurse leave.
The main functional requirements of the system are as follows:
- Login: User login is the basic function of the system. Users can only perform other operations after logging in to the system. This is also fully considered and authenticated from the perspective of system security. There is only one administrator in this system, he is the person in charge of the nursing home, and new employees can be added through him. Administrators and employees enter their corresponding names and passwords and select the corresponding identity to log in to the system.
- Elderly information management: After logging into the system, employees can modify the personal information of the elderly on the corresponding interface, including personal ID number, name, password, age and phone number.
- Bed allocation management: mainly the administrator manages the occupancy status.
- User information management: It is mainly for the administrator to add, delete, modify and check the personal information of the entire hotel staff.
- Accident records: mainly for administrators to check the additions, deletions, and modifications of services related to accidents of the elderly.
- Leave record: mainly for the administrator to check the additions, deletions, changes and inquiries of related services for the elderly to ask for leave.
- Nursing staff salary management: mainly the person in charge adds, deletes, modifies and checks the nursing staff's salary information and the nursing staff checks their own salary information.
- Nursing worker's leave management: mainly for the person in charge to add, delete, modify and check the nurse's leave record and the nurse's check of his salary information.
- Check-in fee: It mainly records the payment record and payment amount of the elderly when they check in.
The specific system function diagram is shown in Figure 3-1:
Figure 3-1 Structural diagram of nursing home management system
Figure 3-1 Structure of the nursing home management system
4. System use case analysis
On the basis of the above requirements analysis, this section will conduct a use case analysis for the functional requirements proposed by the two roles of administrators and employees.
This system is mainly designed for nursing home staff, that is, administrators and employees. Its main functions include: user administrator, employee login, elderly information management, bed allocation management, nurse salary management, nurse leave records, elderly leave records, and occupancy fees and accident record management. Therefore, the overall use case diagram of the nursing home management system is shown in Figure 3-2:
Figure 3-2 Overall use case diagram of the system
Figure 3-2 System overall use case diagram
(2) Analysis of administrator identity use cases
From the perspective of the administrator, that is, the person in charge of the nursing home, he urgently hopes that after using the system, it will be more convenient to manage the nursing home, including the management of employees, the management of the occupancy of the elderly, and the check of bed occupancy information; Personnel management can be performed more conveniently, including modifying old employee information and adding new employee information; financial management can be performed more conveniently, that is, salary management based on employee leave records and payment records for elderly people when they move in. In this regard, some functions are displayed, and the overall use case diagram of the administrator identity is shown in Figure 3-3:
Figure 3-3 Overall use case diagram of administrator identity
Figure 3-3 Administrator status Overall use case diagram
1. User management use case analysis
According to the administrator's functional requirements description, for personnel management, they hope that they can easily modify the existing employee information, and can also easily add new employee information to the system, so the personnel management use case analysis diagram is shown in Figure 3-4 Shown:
Figure 3-4 Personnel management use case analysis diagram
Figure 3-4 Personnel Management Use Case Analysis Chart
(1) Administrators can modify personal information of in-service nurses.
(2) The administrator can delete the personal information of the resigned nurse from the system.
(3) The administrator can enter the personal information of the new nurse into the system.
2. Use Case Analysis of Nursing Salary
According to the administrator's functional requirements description, for financial management, they hope that the administrator can make reasonable arrangements for the nurse's salary based on the nurse's leave record. Therefore, the use case analysis diagram of the nurse's salary is shown in Figure 3-5:
Figure 3-5 Use Case Analysis Diagram of Nursing Salary
Figure 3-5 Analysis of use cases for nursing workers
- The administrator can check the salary information of the nurses, mainly including salary, deductions, distribution status, detailed information, actual payment.
- Administrators can modify and delete their salary information according to actual needs.
3. Use Case Analysis of Elderly Information Management
The main function of the information management module for the elderly is to add, delete, modify and query old information. This is the administrator, adding information about the elderly, modifying the information of the elderly, deleting old personal information, and querying the information of the elderly.
Therefore, the personnel management use case analysis diagram is shown in Figure 3-6:
Figure 3-6 Personnel management use case analysis diagram
Figure 3-6 Personnel management use case analysis chart
(1) The administrator can modify the personal information of the elderly.
(2) The administrator can delete the expired elderly personal information from the system.
(3) The administrator can enter the personal information of the new residents into the system.
4. Use Case Analysis of Elderly Leave Management
The main function of the leave information management module for the elderly is to add, delete, modify and query old information. This is the administrator, adding the leave information of the elderly, modifying the leave information of the elderly, and querying the leave information of the elderly.
Therefore, the personnel management use case analysis diagram is shown in Figure 3-7:
Figure 3-7 Personnel management use case analysis diagram
Figure 3-8 Personnel management use case analysis chart
(1) The administrator can modify the leave for the elderly.
(2) The administrator can check the leave information of the elderly.
(3) The administrator can update the leave information of the elderly and enter it into the system.
(3) Use Case Analysis of Nursing Worker Identity
From the analysis of the functional requirements of the employees above, it can be seen that the employees hope to use the system to modify their personal passwords more conveniently; to view the information of the elderly they are responsible for, their salary status and leave records more conveniently. In this regard, the overall use case diagram of employee identity is shown in Figure 3-8:
Figure 3-8 Overall use case diagram of employee identity
Figure 3-9 Employee identity Overall use case diagram
1. Use case analysis of password information management
According to the employee's functional requirements description, for information management, they hope that they can easily modify their new passwords. Therefore, the use case analysis diagram of password information management is shown in Figure 3-9:
Figure 3-9 Information Management Use Case Analysis Diagram
Figure 3-9 Information management use case analysis chart
(1) The employee enters the corresponding account number and password, and selects the employee identity to log in to the employee system interface.
(2) When employees log in to the system, they can modify the password information to a new password.
2. Elderly information viewing use case analysis
According to the description of the functional requirements of employees, for the information of the elderly, they hope that they can easily view the detailed information of the elderly they are responsible for. Figure 3-10 shows the analysis diagram of the old customer’s information use case:
Figure 3-10 Elderly Information Use Case Analysis Diagram
Figure 3-10 Use case analysis of elderly information
(1) Employees check the relevant information of the elderly in charge, mainly including number, name, gender, age, physical condition, household registration, ID card, contact person, contact number, home address, bed number, nurse number, check-in date, and discharge date .
(2) Employees can query the corresponding information according to the name of the elderly.
3. Leave information view use case analysis
According to the employee's functional requirements description, for checking leave information, they hope to have a better understanding of their own leave records, mainly including the time of occurrence and detailed information. Therefore, the leave record view analysis diagram is shown in Figure 3-12:
Figure 3-11 Item Management Use Case Analysis Diagram
Figure 3-11 Item management use case analysis chart
4. Use case analysis of nurse salary check
According to the employee's functional requirement description, for customer information, they want to be able to view their salary details. Therefore, the use case analysis diagram of nurse salary is shown in Figure 3-12:
Figure 3-12 Use Case Analysis Diagram of Nursing Salary Check
Figure 3-12 Career Salary View Use Case Analysis Chart
Employees can view their salary status, mainly including salary, deductions, payment status, detailed information, actual payment.
(2) Non-functional requirements
1 function
Accuracy and timeliness of system processing are a must. The system should be able to respond and jump in a timely and accurate manner according to user permissions and information entered. The train ticket query is the core system of this system. According to the data given by the system, the accuracy and timeliness of whether the user chooses to buy a ticket determines the success or failure of the system to a large extent. In the process of system development, the accuracy and timeliness of the system must be guaranteed.
2 Reliability
Other users cannot see the passenger list and orders of their own users. I can't see the information of other users. For the data privacy information involved in the online ticketing system, the system needs to ensure the privacy of users. At the same time, the system also needs to update the database in time to ensure data consistency.
3 robustness
For the input beyond the standard requirements, it can be judged that the input does not meet the standard requirements, and there is a reasonable way to deal with it.
4 Interoperability
Different computer systems, networks, operating systems and applications can work together and share information.
5 Scalability
Database scalability, by adding resources to meet ever-increasing demands on performance and functionality.
5. Summary of this chapter
This chapter first analyzes the feasibility of the system from four aspects: economic feasibility, technical feasibility, operational feasibility, and legal feasibility, then describes the non-functional requirements and functional requirements of the system in detail, and summarizes the needs of users, and finally Convert user functional requirements into use case diagrams for analysis.
Chapter 4 System Design
From the analysis stage, the development formally enters the actual software development stage. At this stage, the general design of the system is completed and the data structure and software structure of the system are clarified. At this stage, on the basis of system demand analysis, system design has been done for the computer accessories online sales system. It mainly solves the problem of program module design to realize the system requirement. Including how to divide the system into several modules, determine the interface between modules, the information transmitted between modules, and the design of data structure and module structure, etc. In the following chapter of system design, all the functional structure, database design, development environment and tools made to the system in this stage will be described in detail.
1. Overall system design
The system requires not only powerful functions, but also an intuitive and easy-to-operate interface. Therefore, we focus on the design of module functions during the development of the system, which is required by an excellent system. Since this system can be implemented in general nursing home information management systems, the system we developed should meet the needs of various nursing homes, and its functions also meet the information management of nursing homes for daily nursing homes. As shown in Figure 4-1.
Figure 4-1 System function module diagram
Figure 4-1 System Function Block Diagram
The nursing home management system should have the following functions:
(1) User information management
The administrator logs in to the administrator system interface, and clicks the Add System User button to add users. If the operation is successful, return to the system user management interface; if the operation fails, return a reminder failure message.
Actors: Admin users.
Permissions: Add User Actions
Output items (such as Table 4-1):
Table 4-1 OutputTable 4-1 Output
| output (unit) | illustrate | Remark |
|---|---|---|
| registration success | ||
| registration failed | User already exists |
Input items (such as Table 4-2):
Table 4-2 Input Table 4-2 Enter
| Input item (unit) | Input | Is it required? | Remark |
|---|---|---|---|
| username | Input box | √ | |
| password | Input box | √ | |
| Telephone | Input box | √ | |
| Name | Input box | √ | |
| gender | Input box | √ | |
| age | Input box | √ | |
| address | Input box | √ |
UI design (as shown in Figure 4-2):
Figure 4-2 Add system user UI
Figure 4-2 Add the system user UI
(2) Login
After the user is added, log in and select the nurse option. If the login is successful, it will jump to the management interface of the system user. If the login fails, it will jump to the page, prompting that the login information is wrong.
Participants: nurses
Permissions: Login
Input items (such as Table 4-3):
Table 4-3 Input Table 4-3 Enter
| Input item (unit) | Input | Is it required? | Remark |
|---|---|---|---|
| username | Input box | √ | |
| password | Input box | √ | |
| login button | button | √ | |
| User ID | button | √ |
Output items (such as Table 4-4):
Table 4-4 OutputTable 4-4 Output
| output (unit) | illustrate | Remark |
|---|---|---|
| Authenticating the user successfully - jump to the page | ||
| Login failed - ERROR | username or password is incorrect |
UI design (as shown in Figure 4-3):
Figure 4-3 Login UI
Figure 4-3 login UI
(3) Nursing leave management
After the administrator logs in to the system, click on Nursing Leave Management, all the nursing leave information will be displayed, and there are two items in the operation column: edit and modify. Edit can modify personal information, and delete can delete all information of the user. Click on Nursing Worker Leave Query, enter the account number, and the corresponding nursing staff information will be displayed. If there is no such person, it will not be displayed.
Participants: Administrator admin
Permissions: Manage system users
Input items (such as Table 4-5):
Table 4-5 Input Table 4-5 Enter
| Input item (unit) | Input | Is it required? | Remark |
|---|---|---|---|
| Nursing account | Input box | √ | |
| submit | button | √ | |
| Revise | button | ||
| delete | button |
Output items (such as Table 4-6):
Table 4-6 OutputTable 4-6 Output
| output (unit) | illustrate | Remark |
|---|---|---|
| account | ||
| Time of occurrence | ||
| details |
UI design (as shown in Figure 4-4):
Figure 4-4 System user management UI
Figure 4-4 System User Management UI
What really needs to be managed is the elderly in the nursing home. Therefore, the nursing user needs to add the elderly. There is an elderly information query button on the elderly information management page. Click on the elderly information management, and there is a button to modify the elderly information. People page to add.
At the same time, the caregiver user enters the elderly list page, and can select unnecessary elderly people to delete their information. Users can also enter the elderly list, click the modify button, and modify the information of the elderly.
After the modification is completed, return to the elderly list. Return the modified information to the list.
Actor: user
Permissions: additions, deletions, modifications and inquiries of the elderly
Output items (such as Table 4-7):
Table 4-7 OutputTable 4-7 Output
| output (unit) | illustrate | Remark |
|---|---|---|
| Add elderly information | ||
| Elderly information management | ||
| Elderly information inquiry | ||
| Delete elderly information |
Input items (as shown in Table 4-8):
Table 4-8 Input Table 4-8 Enter
| Input item (unit) | Input | Is it required? | Remark |
|---|---|---|---|
| old man's name | Input box | √ | |
| ID card for the elderly | Input box | √ | |
| Physical Condition of the Elderly | Input box | √ | |
| add button | Input box | √ | |
| enter page button | single button | √ | |
| delete button | button | √ | |
| back button | button | √ | |
| 修改按钮 | 按钮 | √ | |
| 老人信息管理按钮 | 按钮 | √ |
UI设计（如下图4-5，4-6）：
图4-5 增加老人UI
Figure 4-6 increase the old UI
图4-6 老信息人查询UI
Figure 4-6 old information person query UI
（五） 事故记录的增删查
老年人的事故记录管理模块的主要功能是旧信息的增删改查操作，这是管理员，增加老年人的事故信息，修改了老年人的事故信息，删除旧的信息，快速查询老人事故记录。
参与者：用户
权限：事故记录的增删改查
输入项（如表4-9）：
| 输入项（单位） | 输入方式 | 是否必填 | 备注 |
|---|---|---|---|
| 老人姓名 | 文本框 | √ | |
| 确认按钮 | 按钮 | √ | |
| 查询 | 按钮 | √ | |
| 删除 | 按钮 | √ | |
| 修改 | 按钮 | √ | |
| 详细信息 | 文本框 | √ |
输出项（如表4-10）：
表4-10 输出 Table 4-10 Output
| 输出项（单位） | 说明 | 备注 |
|---|---|---|
| 老人姓名 | ||
| 详细信息 |
UI设计（如下图4-7,4-8）：
图4-7 事故记录管理界面 UI
Figure 4-7 Incident Record Management Interface UI
图4-8 增加事故记录页面UI
Figure 4-8 Add Incident Record Page UI
二、 系统开发步骤
一般说来，信息管理系统在开发的过程中又可以分为三个不同的阶段：系统的开发，系统的宏观规划和操作开发了的系统。在严格的开发阶段中，总是一个接一个的任务的完成，每个任务的完成对上一个阶段又有依赖作用你对下一个阶段又起到了帮助作用，每一个发展阶段的完成，都会生成指导审查处理文档，从而在指导接下来的阶段，凭我的感觉，完成某个阶段后，下一个阶段的执行过程中，不想应该改变上一个阶段的评价。刚刚描述的开发方法是最有利于管理和组织的系统程序的设计和开发工作。从过去完成的优秀的系统中不难发现，这是一个非常不错的开发管理方法。
三、 概要设计
在需求分析阶段，我们的主要任务是明确这个系统的主要作用，通熟一点就是“做什么”。接下我们做的便是将需求分析完成的逻辑模型转换成物理模型。
整体结构的关系模式：
用户管理（用户ID，登录账号，密码，用户姓名，性别，电话，地址）
老人信息（序号，姓名，性别，年龄，身体状况，户籍，身份证，联系人，联系
电话，家庭住址，床位号，护工编号，入住日期，出院日期）
事故记录（序号，姓名，发生时间，详细信息）
请假记录（序号，姓名，发生时间，详细信息）
床位分配（姓名，性别，年龄，身体状况，户籍，身份证，联系人，联系电话,
家庭住址，床位号，护工编号，入住时间，操作)
入住费用（姓名，入住费用，扣除费用，缴费状态，详细信息）
护工薪资（护工ID，工资，扣除费用，发放状态，详细信息）
护工请假（序号，护工ID，发生时间，详细信息）
四、 数据字典
数据字典，即定义数据流图中所含元素的集合，存储了系统所有的数据信息。数据字典能够更细致的说明和补充数据流程图的逻辑内容，并且能够供人查阅。
（一） 数据结构
数据结构主要是用来反映数据之间的组合关系
| 数据结构条目 |
|---|
| 数据结构名称：admin |
| 含义说明：主要定义了系统管理员姓名，ID，联系方式等相关信息 |
| 组成：编号，管理员ID，管理员密码，增加时间，性别，年龄，地址，电话 |
| 数据结构条目 |
|---|
| 数据结构名称：lr |
| 含义说明：主要定义了敬老院老人的姓名，ID，联系方式等相关信息 |
| 组成：编号+姓名+性别+年龄+身体状况+户籍+身份证+联系人+联系电话+家庭住址+床位号+护工编号+入住日期+出院日期 |
| 数据结构条目 |
|---|
| 数据结构名称：Fy |
| 含义说明：主要定义了敬老院老人缴费相关信息 |
| 组成：编号，姓名，费用，扣除，状态 |
| 数据结构条目 |
|---|
| 数据结构名称：Hgqj |
| 含义说明：主要定义了敬老院内护工请假记录，登记的相关信息 |
| 组成：编号，姓名，时间，事情缘由，状态 |
| 数据结构条目 |
|---|
| 数据结构名称：Qj |
| 含义说明：主要定义了养老院内老人的请假记录登记的相关信息 |
| 组成：编号，姓名，时间，事情缘由，状态 |
| 数据结构条目 |
|---|
| 数据结构名称：Xz |
| 含义说明：主要定义了敬老院内护工工资发放，以及扣除的相关信息 |
| 组成：编号，姓名，费用，扣除，状态 |
| 数据结构条目 |
|---|
| 数据结构名称：Cw |
| 含义说明：主要定义了敬老院内老人入住所要登记的床位相关信息 |
| 组成：编号，姓名，入住时间，床位号 |
| 数据结构条目 |
|---|
| 数据结构名称：Sgjl |
| 含义说明：主要定义了敬老院内老人发生事故的详细信息 |
| 组成：编号，姓名，事故详细记录，时间 |
（二） 数据流
数据流是系统内部的路径，用于传输数据结构
admin =编号+管理员ID+管理员密码+增加时间+性别+年龄+地址+电话
Lr= 编号+姓名+性别+年龄+身体状况+户籍+身份证+联系人+联系电话+家庭住址+床位号+护工编号+入住日期+出院日期
Fy =编号+姓名+费用+扣除+状态
Hgqj =编号+姓名+时间+事情缘由+状态
Qj =编号+姓名+时间+事情缘由+状态
XZ =编号+姓名+费用+扣除+状态
Cw =编号+姓名+入住时间+床位号
Sgjl =编号+姓名+事故详细记录+时间
（三） 数据存储
以下是数据存储的具体说明。
| 数据存储条目 |
|---|
| 文件名：管理员信息表 |
| 组成：编号+管理员ID+管理员密码+增加时间+性别+年龄+地址+电话 |
| 组织方式：索引方式 |
| 数据存储条目 |
|---|
| 文件名：老人信息 |
| 组成：编号+姓名+性别+年龄+身体状况+户籍+身份证+联系人+联系电话+家庭住址+床位号+护工编号+入住日期+出院日期 |
| 组织方式：索引方式 ，以姓名为关键 |
| 数据存储条目 |
|---|
| 文件名：费用记录 |
| 组成：编号+姓名+费用+扣除+状态 |
| 组织方式：索引方式 ，以姓名为关键 |
| 数据存储条目 |
|---|
| 文件名：护工请假 |
| 组成：编号+姓名+时间+事情缘由+状态 |
| 组织方式：索引方式 ，以护工账号为关键 |
| 数据存储条目 |
|---|
| 文件名：老人请假 |
| 组成：编号+姓名+时间+事情缘由+状态 |
| 组织方式：索引方式 ，以姓名为关键 |
| 数据存储条目 |
|---|
| 文件名：护工薪资 |
| 组成：编号+姓名+费用+扣除+状态 |
| 组织方式：索引方式 ，以护工账为关键 |
| 数据存储条目 |
|---|
| 文件名：老人床位 |
| 组成：编号+姓名+入住时间+床位号 |
| 组织方式：索引方式 ，以姓名为关键 |
| 数据存储条目 |
|---|
| 文件名：事故记录登记 |
| 组成：编号+姓名+事故详细记录+时间 |
| 组织方式：索引方式 ，以姓名为关键 |
（四） 处理过程
以下是具体的处理过程说明。
| 处理过程条目 |
|---|
| 处理过程名称：用户登录（P1） |
| 输入数据：用户名、密码 |
| 输出数据：登录是否成功的信息 |
| 处理逻辑：系统主界面进入可以选择管理身份，分为系统管理员和普通管理员（护工）两种身份，输入账号和密码，正确就会跳转到相应身份系统功能界面中。账号密码错误则会提示登录信息错误 |
| 处理过程条目 |
|---|
| 处理过程名称：系统管理员设置（P2） |
| 输入数据：编号+管理员ID+管理员密码+增加时间+性别+年龄+地址+电话 |
| 输出数据：管理员设置成功 |
| 处理逻辑：当用户输入完信息后，点击确定，系统管理员列表立即显示所有包括刚刚录入的管理员身份信息。 |
| 处理过程条目 |
|---|
| 处理过程名称：老人信息（P3） |
| 输入数据：编号，姓名，性别，年龄，身体状况，户籍，身份证，联系人，联系电话，家庭住址，床位号，护工编号，入住日期，出院日期 |
| 输出数据：显示录入的信息 |
| 处理逻辑：当用户输入完信息后，点击确定，系统立即存储刚刚录入的记录。 |
| 处理过程条目 |
|---|
| 处理过程名称：护工请假信息（P4） |
| 输入数据：编号+姓名+时间+事情缘由+状态 |
| 输出数据：显示录入的信息 |
| 处理逻辑：当用户输入完信息后，点击录入，系统立即显示数据库中的记录。 |
| 处理过程条目 |
|---|
| 处理过程名称：老人事故登记（P5） |
| 输入数据：编号+姓名+事故详细记录+时间 |
| 输出数据：显示录入的信息 |
| 处理逻辑：当用户输入完信息后，点击确定，系统立即存储刚刚录入的记录。 |
| 处理过程条目 |
|---|
| 处理过程名称：护工薪资信息（P6） |
| 输入数据：编号+姓名+费用+扣除+状态 |
| 输出数据：显示录入的信息 |
| 处理逻辑：当用户输入完信息后，点击录入，系统立即存储刚刚录入的记录。 |
| 处理过程条目 |
|---|
| 处理过程名称：床位更换（P7） |
| 输入数据：编号+姓名+入住时间+床位号 |
| 输出数据：显示修改后的老人床位信息 |
| 处理逻辑：根据输入的姓名在数据库中查询到相应的安咯人信息，修改完床号后点击确定，立即显示修改完的结果。 |
| 处理过程条目 |
|---|
| 处理过程名称：老人信息统计（P8） |
| 输入数据：无 |
| 输出数据：显示本敬老院内所居住老人的姓名，性别，身体状况等个人信息 |
| 处理逻辑：根据数据库中的表、lr表 、cw表中查询到相应的信息，然后显示出来。 |
| 处理过程条目 |
|---|
| 处理过程名称：老人信息查询（P10） |
| 输入数据：姓名 |
| 输出数据：显示本敬老院内满足查询条件的老人信息 |
| 处理逻辑：根据输入的姓名在数据中的老人信息表中查询相应的老人个人信息 |
| 处理过程条目 |
|---|
| 处理过程名称：床位查询 （P11） |
| 输入数据：床位号 |
| 输出数据：显示符合查询条件的学老人信息 |
| 处理逻辑：根据输入的查询关键字床位号显示指定床位中所居住的老人个人信息 |
| 处理过程条目 |
|---|
| 处理过程名称：护工薪资查询（P12） |
| 输入数据：护工账号 |
| 输出数据：显示敬老院内该护工的薪资状态 |
| 处理逻辑：根据输入的查询关键字护工账号显示该护工的薪资发放及将罚金的状态 |
（五） 外部实体
外部实体是数据的来源和去向。
| 外部实体条目 |
|---|
| 名称：管理员admin |
| 说明：后台管理的主要实体 |
| 输入数据流：P1-P12 |
| 输出数据流：各种提示信息 |
| 外部实体条目 |
|---|
| 名称：系统用户 |
| 说明：前台应用层面的主要实体 |
| 输入数据流： 除P2、P4、P6 |
| 输出数据流：各种查询、修改、删除结果 |
五、 数据库概念结构设计
对于实现一个实用性系统，有一个优秀的数据库的设计就是成功一半，在这阶段，选择一个适合本系统的数据库都是极为重要的。该数据库将设计和管理使用MySQL。虽然本数据库对信息安全没有做特别严格的要求，基本的数据库安全还是有必要的。信息保密功能在一个系统出现，主要是为了防止不法分子窃取个人信息，对老人造成骚扰，有损敬老院的声誉。还放置有人对数据库进行恶意的修改删除，造成养老院的损失。所以我们选择的数据库管理系统保证不会出现上述问题。之前所述需求分析和概要设计已经非常详细，根据前文说述，我们得出了各个实体之间的联系图。实体E-R图如图4-2所示：
图4-9 系统实体E-R图
Figure 4-9 System entity E-R diagram
六、 数据库逻辑结构设计
模式设计的目的是确定物理数据结构。它的主要问题是处理具体的数据库管
理系统中各种实体之间的结构约束。在设计过程中，会涉及有关范式的概念。范式从第一范式到第五范式，大致分为五个等级，级别越高表示范式水平越高，也就表示冗余数据的程度是越低的。不过并不是级别越高越好，因为级别的提高需要更多表来支持，表的数量太多会直接导致数据库进行运行速度的降低。如何在性能和数据冗余程度之间进行选择，要根据实际情况来决定，在一般的设计工作中，选取第三范式的居多。在数据库系统大致架构完成后，还需要设计数据库中的内容以及表的内容，这是一个非常重要的步骤，这直接作用在开发系统的数据性能上，如何设计数据库的内容和里面的表，也需要统筹考虑，不仅要满足之前决定的范式规则，还需要考虑数据使用人员使用该数据库该表的方便度。考虑了以上的各个方面，并基于前文给出的E-R模型，建立了以下的系统逻辑数据结构。
数据库表的主要设计如下：
表4-11 admin管理员信息表
Table 4-11 admin admin information table
| 列 名 | 数据类型 | 长度 | 说 明 |
|---|---|---|---|
| id | int | 4 | 编号 |
| name | varchar | 50 | 管理员ID |
| password | varchar | 50 | 管理员密码 |
| Realname | varchar | 50 | 增加时间 |
| Sex | varchar | 50 | 性别 |
| age | varchar | 50 | 年龄 |
| address | varchar | 50 | 地址 |
| tel | varchar | 50 | 电话 |
表4-12 Lr信息表
Table 4-12 Lr Information Table
| 列 名 | 数据类型 | 长度 | 说 明 |
|---|---|---|---|
| id | int | 4 | 编号 |
| name | varchar | 50 | 姓名 |
| Sex | varchar | 50 | 性别 |
| age | varchar | 50 | 年龄 |
| address | varchar | 50 | 地址 |
| tel | varchar | 13 | 电话 |
| condition | varchar | 100 | 身体状况 |
| register | varchar | 50 | 户籍 |
| linkman | varchar | 50 | 联系人 |
| idcard | int | 18 | 身份证 |
| bednum | int | 5 | 床位号 |
| hgid | int | 10 | 护工编号 |
表4-3 Fy费用信息表
Table 4-3 Fy cost information table
| 列 名 | 数据类型 | 长度 | 说 明 |
|---|---|---|---|
| id | int | 4 | 编号 |
| Lr | varchar | 50 | 姓名 |
| Fy | varchar | 50 | 费用 |
| Kc | varchar | 50 | 扣除 |
| Zt | varchar | 50 | 状态 |
表4-4 Hgqj护工请假信息表
Table 4-4 Hgqj caregiver leave information form
| 列 名 | 数据类型 | 长度 | 说 明 |
|---|---|---|---|
| id | int | 4 | 编号 |
| Lr | varchar | 50 | 姓名 |
| Fy | varchar | 50 | 时间 |
| Kc | varchar | 50 | 事由 |
| Zt | varchar | 50 | 状态 |
表4-5 qj请假信息表
Table 4-5 qj leave information table
| 列 名 | 数据类型 | 长度 | 说 明 |
|---|---|---|---|
| id | int | 4 | 编号 |
| Lr | varchar | 50 | 姓名 |
| Fy | varchar | 50 | 时间 |
| Kc | varchar | 50 | 事由 |
| Zt | varchar | 50 | 状态 |
表4-6 Xz薪资信息表
Table 4-6 Xz Salary Information Table
| 列 名 | 数据类型 | 长度 | 说 明 |
|---|---|---|---|
| id | int | 4 | 编号 |
| Lr | varchar | 50 | 姓名 |
| Fy | varchar | 50 | 费用 |
| Kc | varchar | 50 | 扣除 |
| Zt | varchar | 50 | 状态 |
七、 本章小结
本章详细描述了系统的设计过程，从概要设计到详细设计，并以会员管理为例进行了深入阐释，最后还给出了系统数据库的主要设计情况。
一、 程序流程图
本系统使用自顶向下的分层模块设计方法，由于宾馆入住管理系统分为：信息管理，宾馆管理，人员管理，物品设置，客户信息管理，财务管理，我们在设计过程中按其功能把它分成不同的模块。系统的程序流程图如图5-1所示：
图5-1系统的程序流程图
Figure 5-1 system program flow chart
（一） 数据增加流程图
添加信息，表格前列的编号会有所开发的系统后台自动生成，编号后的数据全部由管理员手动输入，经过系统后台的判断，符合要求的则保存数据，不符合则系统提示重新输入。
例如：添加老人请假信息，系统会自动生成编号，请假时间和详细信息会有管理员手动添加。如未填写完整，系统会提示需要重新填写。所有模块的增加功能流程图如图5-2。
图5-2 增加功能流程图
Figure 5-2 to increase the function flow chart
（二） 数据修改流程图
在修改信息的过程中，每次只能修改一条记录，首先要选择需要修改的记录，然后由管理员手动输入修改后的信息，经过系统后台的判断，符合要求的则保存数据，不符合则系统提示重新输入。
例如：修改老人事故记录，首先要选择该条记录，点击修改，手动输入需要修改的项目，点击保存，系统会自动检测，非法需要重新输入，合法系统会保存，再打开会看到新信息。数据修改流程图如图5-3.
图5-3数据修改流程图
Figure 5-3 Flow chart for data modification
（三） 数据删除流程图
在删除信息的过程中，每次只能删除一条记录，首先要选择需要删除的记录，然后由管理员手动点击删除，系统会直接跳转页面，显示操作成功。
例如：选择护工请假记录，点击删除，系统提示操作成功，再打开记录已经不会出现。数据删除流程图如图5-4。
图5-4数据删除流程图
Figure 5-4 Data deletion flowchart
（四） 数据查找流程图
当用户选择查找时，手动输入关键信息，页面跳转道查找信息页面。
例如：选择查找老人信息，手动输入老人姓名张三丰，系统跳转页面，显示张三丰老人个人信息。数据查找流程图如图5-5.
图5-5数据查找流程图
Figure 5-5 Data look up flow chart
二、 系统类图
系统中主要有一下几个类DBO类，common类，Adminservlet类，ComBean类，系统类图如下图5-6：
图5-6系统类图
Figure 5-6 System class diagram
三、 系统登陆模块
该模块将实现用户登录功能。进入系统主界面可以选择管理身份，分为系统管理员和普通管理员（护工）两种身份，输入账号和密码，正确就会跳转到相应身份系统功能界面中。账号密码错误则会提示登录信息错误。
图5-7系统登录流程图
Figure 5-7 System Login Flowchart
图5-8系统登陆界面
Figure 5-8 System login interface
主页提供的是一个导航的功能，左边栏是各信息管理的功能链接，
图5-9 系统首页界面
Figure 5-9 system home page interface
密码的管理和新口令的设置往往有利于系统的安全和信息的安全。
图5-10 密码管理模块界面
Figure 5-10 Password Management Module Interface
六、 用户信息管理模块
管理员信息的增删改查运行结果如图5-11、5-12所示：
图5-11管理员信息管理界面
Figure 5-11 Administrator Information Management Interface
图5-12用户信息管理界面
Figure 5-12 User information management interface
老年人的信息管理模块的主要功能是旧信息的增删改查操作，这是管理员，增加老年人的信息，修改了老年人的信息，删除旧的个人信息，查询老人信息。
老人信息管理的运行结果如图5-13、5-14、5-15所示：
图5-13老人信息管理界面
Figure 5-13 elderly information management interface
图5-14用户信息管理界面
Figure 5-14 User Information Management Interface
图5-15用户信息管理界面
Figure 5-15 User information management interface
八、 事故记录管理模块实现
老年人的事故记录管理模块的主要功能是旧信息的增删改查操作，这是管理员，增加老年人的事故信息，修改了老年人的事故信息，删除旧的信息，快速查询老人事故记录。
老人事故记录信息管理的运行结果如图5-16、5-17所示：
图5-16用户信息管理界面
Figure 5-16 User Information Management Interface
图5-17用户信息管理界面
Figure 5-17 User Information Management Interface
九、 本章小结
本章介绍了该系统的详细设计，我们可以对系统设计进行详细全面的了解。介绍用户信息管理，老人信息管理，入住费用管理等模块的设计和实现过程。系统详细设计的原理是利用设计方法的结构来提高控制结构，降低程序的复杂性，从而提高程序的可读性，可测试性和可维护性。
第六章 程序测试与评价
为提高系统的安全性和响应速度，本系统是基于B/S结构的敬老院管理系统，通过该系统可对老人信息进行管理。通过测试系统中的各个功能模块是否满足用户要求，并测试是否存在bug，预期能够达到使系统进行快速的改进和系统的提高。为了在软件投入生产性运行之前，尽可能地发现软件的错误。
为了保证敬老院管理系统的各项功能可靠的实现，特编写了此测试计划，对所开发软件的各功能模块和事例系统进行测试。
一、 程序调试
对于软件开发设计师来说，错误难免，孰能无过，这是很正常的事情。最常见的就是在代码编写过程中，系统会提示有语法错误，立即更正就可以了，因此，语法错误只是很小的错误，这样的错误不会对系统造成严重的损伤，只要仔细一点都没有什么问题。然而，另一种错误是逻辑错误，这种错误隐藏性强，常常发现不了，一旦出现往往是大的事故。因此，调查这种不宜发现的致命的错误调是非常必要的。
二、 程序测试
（一） 测试的目的和重要性
1、 测试的重要性
软件测试从来都是大家口中的非常重要，实践起来，却不认真。其实测试不论在开发还是维护的过程中都占有机器重要的地位而且耗时是尽次于维护，位于，如同瀑布模式一般，在传统的开发模式中软件测试的工作是在运维阶段之前，在软件真正发售给用户之前，软件测试保证了软件的质量和用户体验。不过因为这种方式耗时长，灵活度不够，容易卡开发的节奏，近些年来，软件工程师们有了新的思路，就是对软件生命周期的各个阶段都应包括测试、检查阶段成果，然后尽快找到并改正错误，这样的话可以更容易接近预期的结果，也为后期测试降低了难度，降低了成本。如果在早期是工作中只是一味的完成项目，没有进行测试检查，危险遍随之而到，错误往往随着时间的不断推移越发不可收拾，最后在测试阶段再返回来重新查找错误会加剧成本的浪费，这才是正真的大难题。
在软件方面，事实上，在系统中总是会有错误，无论任何方法或技术都解决不了。但是矛盾总是能解决的，在开发过程中我们应该秉着认真的态度，这是首要，采用一些先进的技术，尽可能的让误差消失，这些误差只能通过软件测试进行测试，估计误差密度。统计表明，在软件开发的总成本中，用于测试的成本占百分之三十到百分之五十。如果维修阶段的考虑，讨论了软件测试的全生命周期成本的比例可能会减少，但是维护阶段的工作量相当于开发阶段的两倍以上工作量，甚至重复开发重复测试，这也将包含大量的测试工作。
实际上，软件测试是工作人员的一大难题，这是因为测试一直在程序员心中不受重视，不用心去感受测试的内涵，这是一种对测试的偏见，而不是正确的态度，这包括：
（1）测试工作相对于开发来说比较枯燥，没有成就感。
（2）测试本身的目的就是发现软件错误，这种带有批判性的，非建设性的否定对于开发人员来说会有一种抵触情绪，从而影响工作顺利展开。
（3）测试工作往往需要耐心，要在细致又艰苦中进行下去。
（4）有时候因为对开发的程序过于自信，在错误被测试出时害怕别人对自己开发能力的否定。
（5）有时候测试的结果无法确定是测试方法的问题还是软件本身就有错误。
以上的几个情况从测试人员的心态，测试技术等多方面描述了测试工作中会碰到的挫折困难，所以我们必须正视测试，认清本质，才可以通过测试提高软件的质量。
2、 测试的目的
测试程序的目的一直以来都是，最大程度的去寻发现系统中的漏洞，那么我们必须在软件最容易出错，而又危害比较的大位置首先展开排查，接下来就应该是软件深层次的更为复杂逻辑错误容易犯的地方。
（1）系统的测试是一个动态的过程，错误就是程序运行的过程中不断的被发现；
（2）测试的目标总是被人误解，发现错误永远是最主要的，证明这个系统没有错误只能说此次测试是失败的；
（3）每一个好的测试用例都用来检查尚未发生的错误；
（4）一个非常成功的测试是检查迄今为止没有发现的错误。
这个想法是提醒人们把重点放在寻找错误，而不是证明正确的软件功能。然而，大家却又容易误解这个意思，虽然发现错误是最主要的任务，很多时候又会找不到错误，大家又要垂头丧气，其实事实并非如此，找不到错误并非价值全无。
首先，测试不只是为了找出错误。大家通过测试找出错误的过程是一个不断提高自己能力的过程，发现问题，解决问题，下次注意，以防再犯。同时，我们需要通过测试来发现软件中的缺陷，以方便下次的改进，就如同医生于病人，测试对于软件是软件走向完善，完美必不可少的必经之路。
（二） 测试的步骤
测试的开发过程中，脚踏实地的走完测试过程中的每一个步骤，测试也分为若干个线性阶段，然后让每个阶段依次的去实现和完成。
此次测试的步骤分为以下三个阶段：
测试模块：对各个模块以及其子模块进行功能和其他方面的测试，主要发现细节设计和编码上的错误。
测试系统：对整体系统进行测试，主要目的发现软件设计和需求说明中出现的错误
验收测试：常在验收程序的系统要求说明书中找到。
（三） 试验的主要内容
为了系统功能的完整，不出现较大的错误，在这次测试过程中，主要把测试工作内容分成以下几部分：
1、单元测试
单元测试就是按照测试最小的单位，通过测试主要是为了发现功能模块设计不合理的问题，千里之堤毁于蚁穴，所以最小的问题往往最不容易发现，造成的危害也往往是最大，所以一定要认真仔细，将错误扼杀在襁褓之中。
2、集成测试
我们可以把若干个模块组装在一起，接下来再进入集成测试阶段。假设由于疏忽造成的有害影响可能发生在功能模块和其它模块上；集成阶段更重要的是测试各个模块之间的接口，单元测试没有问题之后，接口问题显得尤为重要，接口出现问题，整个系统无法相互连接，子功能完好，而主功能却达不到子功能组装起来的效果。
3、验证试验
确认测试的功能就是保证确定软件的可工作性。在集成测试完成之后，已经表明各个功能模块是可以工作的，这时就需要把大的模块组装成完整的系统，并确认系统能否和预期的一样正常工作，如果这个时候出现问题，那就是系统架构的方向错误了。
4、系统测试
系统开发完之后，还要对系统的独立性进行测试，主要通过以下三个方面进行：（一）功能测试：系统被开发的目的就是为了完成客户所要求的需求。因此在系统完成时必然要检验是否需求都得到了满足，各个功能模块是否达到了用户的指标。同时这个时候通常也会进行功能文档的撰写，方便用户较为轻松的上手软件，实现功能需求。
5、测试的性能和强度：一个质量优良的软件应该可以在一定强度的环境下进行工作，通过对软件的强度和性能测试，可以得到软件对各种性能指标的上限和下限。
6、安全测试：除了性能和强度对软件的影响，在使用过程中逻辑上对系统的影响，比如错误的数据，无效的数据，非法的操作，在这些情况的冲击下，系统是否还可以安全稳定的进行工作，这就需要测试系统的安全保护机制了。
经过之前那么长时间的需求分析，开发，测试的过程，毕业设计也随之该结束了。是时候该进行功能模块的测试，是否满足设计任务书中的要求，能否达到预期的效果。在软件的开发过程中，错误总是不是时候的出现，一点也让人开心不起来，一点点小问题就会让系统的功能无法实现当初的目标，甚至让系统崩溃，目前虽然已接近尾声但是还不能掉以轻心，认真对待最后的测试，站好最后一班岗。
| 测试个案的内容 |
|---|
| 测试时间域。 |
| 测试水平。 |
| 类别：测试类别。 |
| 系统：测试系统。 |
| 子系统：测试子系统。 |
| 模块：测试模块。 |
| 平台：测试环境。 |
| 试题描述与描述。 |
| 目的：测试目标和期望。 |
| 测试案例及脚本 |
|---|
| 检查集成测试策略 |
| 开发测试数据目标和性能目标 |
| 确定关键测试条件 |
| 检查现有在线测试脚本 |
| 输入或抓取在线测试脚本 |
| 检查现有数据进行测试 |
| 生成测试数据 |
| 检查的重要数据 |
| 执行测试数据和测试脚本 |
（四） 测试用例
1、 用户登录测试
表6-1 用户登录测试表
Table 6-1 User Login Test Table
| 测试ID | 模块 | 输入 | 输出 | 要表达的结果是否正确 |
|---|---|---|---|---|
| 1 | 界面登录 | 用户名：1密码：a在护工或者管理员选项下 | 登录信息错误 | 正确 |
| 2 | 界面登录 | 用户名：admin密码：111在管理员选项下 | 页面跳转，进入系统管理员界面 | 正确 |
| 3 | 界面登录 | 用户名：111密码：111在护工选项下 | 页面跳转，进入普通管理员界面 | 正确 |
| 4 | 界面登录 | 用户名：admin密码：111在护工选项下 | 登录信息错误 | 正确 |
| 5 | 界面登录 | 用户名：111密码：111在管理员选项下 | 登录信息错误 | 正确 |
图6-1 用户登录测试
Figure 6-1 User Login Test
2、 信息查询测试
表6-2 信息查询测试表
Table 6-2 Information Query Test Table
| 测试ID | 模块 | 输入 | 输出 | 要表达的结果是否正确 |
|---|---|---|---|---|
| 1 | 系统用户 | 111（护工） | 页面跳转，显示111信息 | 正确 |
| 2 | 系统用户 | 123 | 页面跳转，没有信息 | 正确 |
| 3 | 老人查询 | 张三丰 | 页面跳转，显示张三丰信息 | 正确 |
| 4 | 老人查询 | 李白 | 页面跳转，没有信息 | 正确 |
| 5 | 事故记录 | 张三丰 | 页面跳转，显示张三丰事故记录 | 正确 |
测试ID1
图6-2 信息查询测试 图6-3 信息查询测试
Figure 6-2 Information Query Test Figure 6-3 Information Query Test
测试ID2
图6-4 信息查询测试 图6-5 信息查询测试
Figure 6-4 Information Query Test Figure 6-5 Information Query Test
测试ID3
图6-6 信息查询测试 图6-7 信息查询测试
Figure 6-6 Information Query Test Figure 6-7 Information Query Test
测试ID4
图6-8 信息查询测试 图6-9 信息查询测试
Figure 6-8 Information Query Test Figure 6-9 Information Query Test
测试ID5
图6-10 信息查询测试 图6-11 信息查询测试
Figure 6-10 Information Query Test Figure 6-11 Information Query Test
3、 后台管理登录测试
后台管理登录测试过程如表6-3所示：
表6-3 后台管理登录测试
Table 6-3 Background Management Login Test
| 测试目的 | 操作流程 | 测试用例 | 预测结果 | 测试结果 |
|---|---|---|---|---|
| 后台管理登录 | 点击首页填写用户名密码，点击首页【登录】按钮 | 用户名：123密码：111 | 登录失败 | 提示错误信息 |
| 用户名：admin密码：111 | 登录成功 | 登录成功 |
三、 测试结果及分析
（一） 测试情况统计分析
合格率 = 100%
测试完成率 = 100%
测试覆盖率 = 100％
（二） 功能性
敬老院管理系统实现了员工信息和入住老人信息的录入，查询和删除。用户自己可以进行密码的更改，并对其所拥有的权限进行修改和查询。只有拥有管理员权限才能修改和删除护工用户的数据。普通用户只能根据所分配的权限进行操作。严格控制对数据的修改，只能数据录入的用户才有权对数据进行修改。
（三） 易用性
本系统目前实现的是如下易用性：
查询信息，管理员添加信息，删除记录，修改操作相关提示信息的保持一致，可理解；
输入框限制的条件正确性；
输入限制提示信息是否正确，是否可理解，是否具有一致性；
本系统目前仍存在的易用性缺陷：
界面排版不美观，整洁，现代化；
输入，输出字段的不具备很好的可理解性；
输入缺少解释性说明；
（四） 兼容性
现有系统兼容谷歌，IE8以上内核浏览器，其他浏览器未做兼容性测试。
（五） 缺陷汇总
1、床位的编号没设置上限，这是设计上面的的失误。当会员点击购买产品时，如果未登录就会只显示头部信息
2、左边栏索引画面不友好，使用起来总觉得别扭。会员使用投诉建议功能时，未填写标题也可以提交建议
四、 本章小结
本章主要对系统的部署与测试情况进行了系统性的描述，重点描述了系统的功能测试和性能测试情况，并给出了典型测试用例。
结论
在完成毕业设计的这段时间里，不管是构思、框架设计还是实践体会，我都深有体会。在之前的学习中，我对基础的专业设计有过一些经验，但仅仅是对小模块和小系统的设计。因此，在面临养老院管理信息系统的设计时，我得到了很多老师和同学的帮助和指导，在此深表感谢。同样，在设计思考以及操作的过程中，我的独立思考能力、动手操作能力以及思维整合能力也得到了一定的锻炼。在今后的学习中，我也一定会更加注重对自我能力的培养和锻炼，为迈入社会奠定一定的基础。
虽然项目的设计与开发已经取得了一定的成果，但由于用户的需求而不断更新，在未来的发展，丰富和完善制度是必要的，以下三个方面具体阐述我的设计开发项目思想的前景：
1系统的通用性
目前可以通过该系统实现对养老院的信息化管理。为了增加软件的通用性，我们可以通过系统的开发考虑到养老院的二次开发，使整个养老院管理信息系统的管理更加规范和完善。
2制度的完善
虽然该系统实现了对一般的审批流程疗养院信息管理，但材料的审查，也只能依靠申请人的审计信息，真实性无法在第一时间获得准确的反馈信息，所以申请信息在线验证是一个未来的方向。
3相对于其他部门制度
如何有效管理养老院管理信息系统和养老院管理系统等相关系统，实现信息共享是未来发展的重点。
系统的特点和优点
本次设计开发的养老院管理系统吸取很多养老制度体系完整度高的国家的经验，例如瑞士，也学习了很多管理系统的功能，界面等方面，主要是从管理员的角度出发，方便操作，降低操作难度，以下是系统的主要优点特点：
该系统在我认为最满意的一点就是，用户界面。我们用最简单的，最直观的界面来设计，简单大方，管理员使用起来一点难度都没有，仅仅是培训一下，以防止对系统的不良操作造成数据的丢失。对于养老院的管理者而言，人工成本的降低，实际工作时间的减少，对老人老说也是一种变相的福利。
因为使用的是JAVA进行编程，开发环境选择的是MyEclipse+JDK1.6，鉴于该语言的兼容性，因此本系统也有很好的兼容可移植性。JAVA在大多数的操作系统上都有一个对程序员透明的虚拟机，以便用JAVA开发出的程序可以非常方便的在各种操作系统上运行。并且软件还可以根据用户的需求进行相应的移植改编，适应各种不同的条件。
对于本软件的业务能力也非常的全面完整，老人的信息录入，显示都非常的直观。同时用户体验也非常人性化，因为在手动录入数据的时候有可能会出现失误，这是难免，造成数据逻辑上的错误，对以后的管理造成很大的不方便，因此我们的录入方式都采用的是选择框鼠标选择的方式，大大减少了错误录入的情况发生，带来方便的同时也增加了工作效率。
系统中存在的不足：
该系统对于传统养老院来说，基本的管理功能是没有问题的，包括老人信息，员工信息，同时信息的查询修改删除功能也是可以实现的。然而，毕竟第一次做这样的系统，时间，经验都非常的欠缺，系统的不足主要体现在以三个方面：
1、UI界面因为时间经验不足的关系设计的过于简单单调，虽然对整体不造成什么影响，但是和国内外先进的管理系统相比，设计方面有很大的差距。
2、 在编码和数据库设计的过程中，因为经验不足，代码的架构能力不强，造成了代码的冗余，运行性能不够好。项目从程序员的角度看不够完美，继续扩展功能的能力也不高。
3、对于后台的管理，功能上还并不是非常完善，仅仅是简单的功能完成，数据库能力也比较差，入住老人达到一定人数，系统很可能会崩溃，有一些功能还未能完全完美的实现。
改进方案：
对于以上系统的欠缺，我会做出如下的改进方案：
1、对于系统界面的简单单一，我会通过PS处理照片，让系统不漂亮的界面，增添一点色彩，还会重新设计边栏，看起来不那么单一，在系统主界面加入一些链接，链接到国内各大养老机构，时刻了解养老方面的新闻，还会增添本养老院的信息，搞活动时候老人们开心的照片。
2、对代码和数据库进行优化，功能相同的类或者方法以共享，复用，继承等代码技巧进行整合处理，并且利用数据库连接池技术提高性能。
3、后台的功能在代码优化之后，可以进一步的去开发和完善，拓展整个软件的业务能力。
致谢
于时间无涯的荒野里，走了一段自己心心念念的求学路。在这个阳光灿烂的时节里，我们又迎来了曲终人散的宴席。似乎连校园里的花草树木都通晓这离别的愁绪与滋味，不约而同地在风中摇曳着想要挽留。尽管离别近在眼前，心中是道不尽的话。但在论文即将结束之时，对我本次论文的指导老师孙静宇和李洪涛致以最为真挚的感谢。
正是由于我才能在犹豫不决的选题中发现新的立意，让我的论文有了全新的研究方向，同时在收集资料时老师给了我较为明确的方向指引，对我的构思和框架进行了肯定，论文得以圆满的成功得益于老师的悉心指导。能够遇到像您一样责任心极强的导师是我的荣幸，也是命运对我的垂青。师有较为丰富的论文指导，在与老师的交流沟通的过程里我获得较为有用的指导性意见，老师的建议就像是指路明灯一样照亮了通往学术象牙塔之路，还在路途中的我也在不断完善自己。老师除了给我的论文进行了指导外，在实际生活中也用其严谨的生活作风为我树立了一个好榜样，他将是我此生都需要学习和尊重的人。
除此以外，还想在大学接近尾声之时，对我的专业课老师道谢，谢谢他们孜孜不倦的教会，感谢老师全身心投入的栽培。在这大学期间，我们收获的不仅仅是知识，还懂得了体味生活，感悟人生，使得自己的价值观念得到了进一步升华。时光白驹过隙般在指尖溜走，多希望可以按下暂停键，多希望还能再听一听老师讲课，再去体会一下那段幸福时光。
不仅如此，我还要对院系的学工办老师以及其他老师表示感谢，是你们给予我们生活上的关心与帮助，还为我们举办了丰富多彩的活动；是你们偶尔路过时的点头与微笑，温暖了脆弱的心灵；是你们营造了温馨的环境，让我学会爱与被爱、付出与接受。当然这几年的匆匆岁月，我也特别感谢一路相随的室友以及其他同学，他们的热情善良、无私帮助，让我完美舒适地过完了整个在职生生活，如梦一场。那些一起逃课旅行的日子，那些一起占座复习迎考的日子，那些一起手工打造梦幻宿舍的日子，都成为了这一生都难以忘怀的记忆。谢谢你们出现在我生命里，丰满了我对青春的想念。感恩之情难以用言语度量，谨以我最朴实的语言传递此刻最真切的心意。
感谢郭浩老师和许歌老师在毕业设计工作中给予的帮助。
感谢我的学友和朋友对我的关心和帮助。
参考文献
- 熊杰. 宾馆住宿管理系统的设计[J]. 中国科技博览, 2015(29):77-77.
- 孟小峰, 周龙骧, 王珊. 数据库技术发展趋势[J]. 软件学报, 2004, 15(12):1822-1836.
- 吕浩音. JSP技术介绍[J]. 陇东学院学报:自然科学版, 2007(2):29-31.
- 张良银. 浅论C/S和B/S体系结构[J]. 工程地质计算机应用, 2006(4):20-23.
- 沈珏. MVC设计模式[J]. 科技广场, 2009, 2009(9):249-250.
- 李福弟. 可行性研究内容介绍[J]. 西南金融, 1984(12):28.
- 田敏, 金星. 技术档案数据库管理系统设计原则及方法初探[J]. 计算机与现代化, 2007(4):69-71.
- 徐敬. J2EE架构下基于Web的信息管理系统框架研究[J]. 硅谷, 2015(1):84-85.
- 王华. 探析Java数据库连接池运行原理[J]. 福建电脑, 2010, 26(8):92-93.
- 陆璐, 王文莉. 浅谈软件测试技术[J]. 郑州铁路职业技术学院学报, 2007, 19(2):41-42.
- 王萍. 软件测试的重要性[J]. 软件导刊, 2009(4):20-21.
- Jacob K. Hotel inventory management system and method: US, US20070075136[P]. 2007.
- Xia C. The realization of MyEclipse and database connection[J]. Journal of Wuhan Engineering Institute, 2013.
- Gray J. Notes on Data Base Operating Systems[C]// Operating Systems, An Advanced Course. Springer-Verlag, 1978:393-481.
- Xia X X, Xin B Y. Compare B/S mode with C/S mode[J]. Journal of Yanbian University, 2002.
- Roth R R. SOFTWARE TESTING: US, US 20080010539 A1[P]. 2008.
译文
1.Old Dogs and New Tricks: Keep BBS from Rolling Over and Playing Dead
作者： Mathis, Terry L. Galloway, Shawn M.
来源：[J] EHS Today
At a recent conference, the No. 1 problem reported by mature behavior-based safety (BBS) process teams was observer burnout. So, why do processes falter and why do observers burn out? The answer to both of these issues lies in the strategy for observations. Most BBS teams were taught an observation strategy that simply blanketed observations evenly across the site. They quickly learned that there was a direct correlation between the number of observations and the impact on accident reduction. The goal of the process became to hit the target number of observations. As the process matured, it increasingly became more difficult to accomplish the goal. Additionally, hitting the same number of observations began to have a diminishing impact on accident rates. But, since the process was successful, it was continued. Leaders of mature BBS processes who have revised this strategy for observations have recognized additional gains and have created a more resourceefficient, sustainable approach. The challenge is to modify the perceptual goal of BBS from the quantity of observations to the quality of observations. WHAT TRIGGERS AN OBSERVATION? The answer to this question, at most sites with mature behavioral approaches, has more to do with process than results. When we ask, “Why do you perform observations?” we often hear answers like: “Because we have a numbers goal,” “Because we have to” and “Because I’ll get in trouble.” The goal of a behavioral approach to safety should not be to simply accomplish observations. The goal should be to improve safety by providing simple strategies that easily can be internalized and by identifying influences on safe performance.
People do things for a reason. If you want to improve performance, you need to first identify what is influencing the current performance. Is it a perception, habit, obstacle or barrier? (See “Understanding Influences on Risks: A FourPart Model,” EHS TODAY, February 2010.) If you can eliminate or mitigate the influencer on risk, you are enabling a sustainable behavioral change. Observations that do not gather insight into the reasons for risk are functioning solely as antecedents, activators or triggers that remind and refocus people on certain precautions. This is the most expensive activator you can use. What triggers an observation should be used in a strategic response to previous observations, not simply a numbers goal. A STRATEGY EMERGED Four advanced observation strategies have been identified which have resulted in significant returns on little internal investment. Self-Observations – This approach is ideal for isolated workers and where traditional observations are not an option. It also can be used to supplement traditional observations and further reinforce a change strategy. However, there are limitations to self-observations that must be considered. Workers often are blind to their own habits, so selfobservations need to be supplemented by outside observations, at least periodically. Also, reflection can be grossly inaccurate, so workers cannot simply ask themselves, “How did I do today?” Self-observations need a reminder mechanism that indicates when to start and stop, and this often requires some innovative thinking to design. Aimed Observations – Many organizations analyzing their observation data identify visible trends in risk, such as time of day, day of week, task, weather,etc. The observations can be aimed at these exposure targets, rather than blanketed. If insight into influences (asking why) is not collected during observation, the ability to address the risk exposure is limited. Blitz Observations – Like aimed observations, a blitz is a focus on a target. But, rather than asking observers to aim individual observations at the target, blitzes send groups of observers to the targets to do multiple, simultaneous observations. Blitzes concentrate a lot of attention and can result in quick improvements. SWEEP Observations – SWEEP is an acronym that stands for seeing without explaining to every person. SWEEP observations cannot be used alone to accomplish behavioral change since there is no feedback component. SWEEPs simply are an ongoing way to aim other types of observations at the targets where they can do the most good. Some organizations use SWEEPs to determine a more accurate percent-safe. Other types of observations give workers notice before the observation begins, which often results in an artificially high percentsafe. Caution: SWEEP observations only should be used when the culture and employees have developed a high level of trust in the BBS process. CAREFUL CONSIDERATIONS TO PROGRESS Mature behavior-based safety processes often are doing the right things. Further improvement lies in doing those things a better way. This same principle will apply to how you choose to help your BBS team improve their process. Involve the steering team and the union, if applicable, in selecting the new strategies. (See “Unions and Behavior-Based Safety: The 7 Deadly Sins,” EHS TODAY, October 2009.) Prior to implementing new processes or changing existing ones, it is critical to discuss with the work force the purpose and details of the new observation strategy. Join the many other sites that have found that a different observation strategy can breathe new life and energy into an old BBS process.
在最近的一次会议上，成熟的基于行为的安全（BBS）流程团队报告的第一个问题是观察员倦怠。那么为什么流程变得不稳定，为什么观察者烧掉了？这两个问题的答案在于观察战略。大多数BBS团队被教授了一种观察策略，可以在整个网站上均匀地覆盖观察结果。他们很快了解到观察次数与对事故减少的影响之间存在直接的相关性。这个过程的目标就是达到目标数量的观察值。随着过程的成熟，越来越难以实现目标。另外，同样数量的观察开始对事故率的影响减小。但是，由于这个进程是成功的，所以继续下去。成熟的BBS流程的领先者已经修改了这一观察策略，已经获得了更多的收益，并且创造了一种更具资源效率的可持续的方法。挑战是将BBS的感知目标从观察量改为观察质量。什么是触发观察？在大多数具有成熟行为方式的网站上，这个问题的答案与结果有关。当我们问：“为什么要进行观察？”我们经常听到这样的答案：“因为我们有数字目标”，“因为我们必须”和“因为我会陷入困境”。行为方法的目标安全不应该简单地完成观察。目标应该是通过提供易于内部化的简单策略，并通过识别对安全性能的影响来提高安全性。
人们为事情做事情如果要提高性能，您需要先确定影响当前性能的内容。它是一种感知，习惯，障碍或障碍？ （见“了解风险影响：四部分模式”，EHS今天，2010年2月）如果您可以消除或减轻影响者的风险，您将实现可持续的行为改变。不了解风险原因的观察仅仅作为提醒和重新聚焦人们某些预防措施的前提，激活者或触发器。这是您可以使用的最昂贵的激活剂。应该在对以前观察的战略反应中使用触发观测的内容，而不仅仅是数字目标。战略重组已经确定了四个先进的观察策略，这些战略在很少的内部投资上取得了显着的回报。自我观察 - 这种方法对于孤立的工作者来说是理想的，传统观察不是一种选择。它也可用于补充传统观察结果，进一步加强变革策略。然而，必须考虑自我观察的局限性。工人经常对自己的习惯无视，所以自我观察需要由外部观察来补充，至少定期进行。此外，反思可能是非常不准确的，所以工人不能简单地问自己：“我今天怎么做”？自我观察需要一个提醒机制，指出何时开始和停止，这通常需要一些创新的思维来设计。目标观察 - 许多分析其观察资料的组织识别风险的可见趋势，例如时间，星期几，任务，天气等。观察结果可以针对这些暴露目标，而不是覆盖。如果在观察期间未收集影响因素（询问为什么），则处理风险暴露的能力有限。闪电观察 - 像目标观察一样，闪电战是对目标的关注。但是，不是要求观察员将个人观察目标瞄准目标，而是将观察员派到目标群体进行多次同时观察。 Blitzes集中了很多的关注，可以快速改进。 SWEEP观察 - SWEEP是一个缩写，代表看不到每个人的解释。 SWEEP观察不能单独用于完成行为变化，因为没有反馈组件。 SWEEP只是将其他类型的观察目标瞄准目标的持续方式，他们可以做最好的事情。一些组织使用SWEEP来确定更准确的百分比安全。其他类型的观察在观察开始之前给予工作人员通知，这通常导致人为的高百分点。注意：当文化和员工在BBS流程中发挥了高度的信任时，SWEEP观察只能使用。认真考虑进步成熟的基于行为的安全过程往往正在做正确的事情。进一步的改善在于做这些事情更好的办法。同样的原则将适用于您如何选择帮助您的BBS团队改进其流程。参与指导小组和工会，如果适用，选择新的战略。
2.THE TECHNIQUE DEVELOPMENT HISTORY OF JSP
作者： Kathy Sierra and Bert Bates
来源： Servlet&JSP
The Java Server Pages( JSP) is a kind of according to web of the script plait distance technique, similar carries the script language of Java in the server of the Netscape company of server- side JavaScript( SSJS) and the Active Server Pages(ASP) of the Microsoft. JSP compares the SSJS and ASP to have better can expand sex, and it is no more exclusive than any factory or some one particular server of Web. Though the norm of JSP is to be draw up by the Sun company of, any factory can carry out the JSP on own system.
The After Sun release the JSP( the Java Server Pages) formally, the this kind of new Web application development technique very quickly caused the people's concern. JSP provided a special development environment for the Web application that establishes the high dynamic state. According to the Sun parlance, the JSP can adapt to include the Apache WebServer, IIS4.0 on the market at inside of 85% server product.
This chapter will introduce the related knowledge of JSP and Databases, and JavaBean related contents, is all certainly rougher introduction among them basic contents, say perhaps to is a Guide only, if the reader needs the more detailed information, pleasing the book of consult the homologous JSP.
1.1 GENERALIZE
The JSP(Java Server Pages) is from the company of Sun Microsystems initiate, the many companies the participate to the build up the together of the a kind the of dynamic the state web the page technique standard, the it have the it in the construction the of the dynamic state the web page the strong but the do not the especially of the function. JSP and the technique of ASP of the Microsoft is very alike. Both all provide the ability that mixes with a certain procedure code and is explain by the language engine to carry out the procedure code in the code of HTML. Underneath we are simple of carry on the introduction to it.
JSP pages are translated into servlets. So, fundamentally, any task JSP pages can perform could also be accomplished by servlets. However, this underlying equivalence does not mean that servlets and JSP pages are equally appropriate in all scenarios. The issue is not the power of the technology, it is the convenience, productivity, and maintainability of one or the other. After all, anything you can do on a particular computer platform in the Java programming language you could also do in assembly language. But it still matters which you choose.
JSP provides the following benefits over servlets alone:
• It is easier to write and maintain the HTML. Your static code is ordinary HTML: no extra backslashes, no double quotes, and no lurking Java syntax.
• You can use standard Web-site development tools. Even HTML tools that know nothing about JSP can be used because they simply ignore the JSP tags.
• You can divide up your development team. The Java programmers can work on the dynamic code. The Web developers can concentrate on the presentation layer. On large projects, this division is very important. Depending on the size of your team and the complexity of your project, you can enforce a weaker or stronger separation between the static HTML and the dynamic content.
Now, this discussion is not to say that you should stop using servlets and use only JSP instead. By no means. Almost all projects will use both. For some requests in your project, you will use servlets. For others, you will use JSP. For still others, you will combine them with the MVC architecture . You want the appropriate tool for the job, and servlets, by themselves, do not complete your toolkit.
1.2 SOURCE OF JSP
The technique of JSP of the company of Sun, making the page of Web develop the personnel can use the HTML perhaps marking of XML to design to turn the end page with format. Use the perhaps small script future life of marking of JSP becomes the dynamic state on the page contents.( the contents changes according to the claim of)
The Java Servlet is a technical foundation of JSP, and the large Web applies the development of the procedure to need the Java Servlet to match with with the JSP and then can complete, this name of Servlet comes from the Applet, the local translation method of now is a lot of, this book in order not to misconstruction, decide the direct adoption Servlet but don't do any translation, if reader would like to, can call it as" small service procedure". The Servlet is similar to traditional CGI, ISAPI, NSAPI etc. Web procedure development the function of the tool in fact, at use the Java Servlet hereafter, the customer need not use again the lowly method of CGI of efficiency, also need not use only the ability come to born page of Web of dynamic state in the method of API that a certain fixed Web server terrace circulate. Many servers of Web all support the Servlet, even not support the Servlet server of Web directly and can also pass the additional applied server and the mold pieces to support the Servlet. Receive benefit in the characteristic of the Java cross-platform, the Servlet is also a terrace irrelevant, actually, as long as match the norm of Java Servlet, the Servlet is complete to have nothing to do with terrace and is to have nothing to do with server of Web.
Java服务器页面（JSP）是一种根据脚本褶距离技术的网络，类似于携带的Java在Netscape的公司服务器端的JavaScript（SSJS）的服务器脚本语言和的Active Server Pages（ASP ）微软的。 JSP比较SSJS和ASP有更好的可扩展性，它并不比任何工厂或网站的某一个特定的服务器更加独特。尽管JSP规范是由太阳公司的拟定，任何工厂可以进行JSP自己的系统上。
在日晒后释放JSP（Java服务器页面）正式挂牌，在这种新的Web应用开发技术很快引起了人们的关注。 JSP提供的是建立了高动态Web应用程序的一个特殊的开发环境。根据太阳的说法，JSP能够适应包括Apache网络服务器，IIS4.0在市场上85％的服务器产品的内部。
本章将介绍JSP和数据库，以及JavaBean的相关内容的相关知识，是所有肯定其中粗糙介绍基本内容，说的也许是一个指南而已，如果读者需要更详细的信息，取悦征询书同源JSP。
1.1概括
该JSP（Java服务器页）与Sun Microsystems公司的发起，众多企业参与到构建起来的一种动态状态的Web页面技术标准的同时，在它有它的建设在动态状态的网页强，但不把特别的功能。 JSP和Microsoft的ASP技术非常相似。双方都提供了一定的程序代码混合并利用语言引擎解释HTML的代码执行程序代码的能力。下面我们简单的介绍吧矣。
JSP页面转换成Servlet。所以，从根本上讲，任何任务JSP页面可以执行也可以通过servlet的实现。然而，这种底层的等同性并不意味着servlet和JSP页面对于所有的情况都等同适用。问题不在于技术的力量，这是方便，工作效率和一种或另一种的可维护性。毕竟，任何你可以在Java编程语言中的特定的计算机平台上做的，你也可以做汇编语言编写。但它仍然很重要，你选择。
JSP提供了单独的servlet以下好处：
•它更容易编写和维护的HTML。您的静态代码是普通的HTML：没有额外的反斜杠，没有双引号，也没有暗含的Java语法。
•您可以使用标准的网站开发工具。即使HTML工具一无所知JSP可以使用，因为它们会忽略JSP标签。
•您可以将您的开发团队。 Java程序员可以对动态代码。在Web开发人员可以集中表现层。对于大型的项目，这种划分是非常重要的。根据您的团队的大小，及项目的复杂程度，可以对静态HTML和动态内容进行或强或弱的分离。
现在，这种讨论并不是说你应该停止使用servlets，只使用JSP来代替。绝不。几乎所有的项目将同时使用。对于项目中的一些要求，你会使用servlet。对于其他人，你将使用JSP。对于另外一些人，你会用MVC架构将它们合并。你要作业的合适的工具和servlet，本身并不能完成你的工具包。
Sun公司的JSP的技术，使得网页的页面开发人员可以使用HTML标记也许XML的设计与格式打开尾页。使用JSP标记的或许小脚本今后的生活变得页面内容的动态状态。（根据索赔内容的变化）
在Java Servlet是JSP的技术基础，以及大型Web应用到需要Java Servlet来匹配与JSP，然后才能完成这个过程的发展，Servlet的这个名字来自于小程序，当地的翻译方法现在是为了很多，这本书不是误会，决定直接采用Servlet的，但不做任何转换，如果读者愿意，可以称之为“小服务程序”。该Servlet是类似于传统的CGI，ISAPI，NSAPI等的Web程序开发实际上工具的功能，在使用以后了Java Servlet，客户不必再使用效率的CGI卑微的方法，也不必只用该能力的API，某一固定Web服务器平台循环的方法来动态的网络的诞生页面。网站所有的多台服务器支持Servlet，即便不直接支持Web的Servlet的服务器，也可以通过附加应用服务器和模件支持Servlet。