When the software is completed, it will have three modules: "Dictionary Maintenance", "Clinic Management" and "Dean's Query", which play an efficient role in the application environment of the software. Efficient role of the software, "dictionary maintenance" module stores drug information and charges for the purchase and storage of drugs to provide data; "outpatient management" module has four sub-functions: outpatient registration, outpatient pricing, outpatient charging, pharmacy drug issuance; The "Dean's Query" module provides a direct query for the hospital's senior leadership to check the hospital's departmental registration and drug inventory at any time.
The development platform of this system is Microsoft Visual Studio 2005, the development tool of Microsoft Corporation, and the combination of the database software - Microsoft SQL Serer as the system used in the system. SQL Serer is used as the support platform for the data sources used in the system.
Keywords: hospital management system; VC++.NET; database; database system
Contents
Introduction 6
1 Introduction 7
2 Feasibility Analysis 8
2.1 Economic Feasibility 8
2.2 Technical Feasibility 8
2.3 Policy Feasibility 8
3 Requirement Analysis 8
3 Requirement Analysis 8
3 Feasibility Analysis 8
3 Feasibility Analysis 8
3 Feasibility Analysis p>
3 Requirements Analysis 9
3.1 Business Process 9
3.2 System Hierarchy Block Diagram 9
3.3 Hierarchy Diagram of the Modules in the System 10
3.3.1 System Dictionary Maintenance 10
3.3.2 Outpatient Registration System 11
3.3.3 Outpatient Price Management 11
< p>3.3.4 Pharmacy Management System 113.3.5 Dean's Comprehensive Query System 12
3.4 System Flow Chart 12
3.5 System Data Flow Chart 13
3.5.1 Top Level Flow Chart 13
3.5.2 Layer 0 Flow Chart 13
3.6 Data Dictionary 14
3.6.1 Data Flow Entries 14
4 Conceptual Structure Design 15
4.1 Global Entity Diagram of the System 15
4.2 Entity Diagrams of the System by Entity 15
4.3 System Tables and Their Uses 17
5 Logical Structure Design 18
5.1 Logical Design Specifications 18
5.2 Logical structure table 18
6 Physical structure design 19
6.1 Data storage 19
6.2 Creating indexes 19
7 Coding 20
7.1 Front-end function design 20
7.1.1 Dictionary maintenance 20
7.1.2 Clinic management 21
7.1.3 Dean's Query 21
8 System Testing 23
8.1 Overview of Software Testing[5] 23
8.2 Common Software Testing Methods[6] 23
8.2.1 Black Box Testing 23
8.2.2 White Box Testing 24
8.2.3 Model-Based Testing 24
8.3 Software Testing Methodology for this System 25
9 Conclusion 26
9.1 Summary of System Functions 26
9.2 Outlook of the System 26
Thanks 27
References 28
Introduction
The hospital management system (Hospital Information System (HIS) has been recognized in the international academic community as an important branch of the emerging Medical Information. Morris Collen, a famous professor in this field in the United States, wrote an article in 1988 for the hospital information system was defined as follows: the use of electronic computers and communication equipment, for the various departments of the hospital to provide the collection of patient diagnosis and treatment information and administrative information, storage, processing, extraction, and data exchange capabilities, and to meet the functional needs of all authorized users.[4] After a long period of time, the hospital information system (HIS) has been recognized by the international academic community as an important branch of the emerging medical information (Medical Information). [4] After years of development, nowadays enterprise-level application software like hospital information system can not only provide static information and interactive dynamic information services, but also provide application program infrastructure services (e.g., security, transaction, transmission, buffering, and survivability management, etc.), and such software is currently built using the N-tier structure, and the advantage of the N-tier structure is that each tier can be altered individually without affecting the other layers, reducing the overhead of deployment and maintenance [11].
In order to satisfy the above mentioned problems, it is crucial to reuse not only old code but also similar analysis and design results and architectures to reduce the cost of constructing a new software system and to improve the reliability of the software. Frameworks are one such domain-oriented reuse technique, and frameworks are considered to be one of the most promising object-oriented techniques because of the strong reuse they provide. Reuse of individual classes, though useful, does not offer a meaningful leap in productivity due to the low level of reuse. Framework-based software development process, the development of software as an assembly process, under the guidance of the software framework to find reusable components (and the development of some new components) and system assembly, this development process is currently a very important research direction. Currently, some solutions have been proposed for enterprise-level applications. Microsoft's .NET framework and SUN's J2EE are two of the most popular and mature can simplify the enterprise application with the development, deployment and management of complex issues related to the architecture. Net was launched by Microsoft in 2000 and is a new generation of Windows development system platform. NET platform contains the following key features:[10]
(1) software-as-a-service
(2) XML-based *** same language
(3) incorporation of a wide range of devices and platforms
(4) next-generation human-computer interfaces
(5) hosted code public *** language runtime libraries
This article references This paper refers to the steps related to the development of a software in software engineering, combined with the knowledge of the database, in accordance with the three steps of software definition, software development, operation and maintenance of the development of software. The software development step is different in that it consists of the design of the conceptual structure of the database, the design of the logical structure, and the design of the physical structure.
1 Introduction
The main goal of the hospital information management system is to establish a new type of social security system that can not only guarantee the fair access to basic health care services for all employees, but also effectively regulate waste and rationally utilize medical resources. With the progress of science and technology, people's lives improve, hospital information management needs to be further systematized, scientifically, the establishment of hospital information management system has been the general trend. At the same time, but also in order to better conscientiously carry out the implementation of the national, provincial and municipal health insurance reform policies, the establishment of normal basic medical care for employees and supplemental medical insurance good operating mechanism, after full conception, research and argumentation, after drawing on a variety of styles of hospital management system, the development of the hospital management system [2].
It is expected that the system will achieve the following six goals after completion:
(1) standardization and development
(2) uniformity and practicality
(3) parametric design and flexibility
(4) security and reliability
(5) universality
The development of China's hospital information system began in the early 1980s. In the early 1980s, hospital information construction roughly experienced a single machine operation, local networking, hospital-wide information networking construction of three stages. According to the Ministry of Health Information Center in 2001, China's application of information management system of hospitals accounted for 31% of the total number of hospitals, including provincial hospitals invested in information management system as high as 84% of the municipal and county hospitals only 37% and 34%. In the country's more than 500 tertiary hospitals and more than 1,000 counties and cities above the second level hospitals, there are nearly 900 large and small hospitals have been implemented or are in the process of implementation of hospital information systems [12].
The future of hospital information management: the construction of hospital information management is a long-term arduous task. Hospital information management system is composed of multi-faceted systems, and constantly improve and expand, so that the construction of information technology to cover the construction of hospital operations. With the development of information technology, the hospital information session construction will pay more attention to human services, optimize and improve the information management system functions, performance, human-machine interface and intelligent construction is the inevitable trend of the development of the medical industry [13].
The fundamental purpose of hospital information construction is to take the patient as the center, to realize the network management of the hospital, for clinical medical treatment, operation and management to provide convenient and effective management means and management mode [8]. The content of hospital informatization construction includes a full range of management modules such as medical behavior, administrative organization, logistics support, etc., which involves registration, charging, drugstore, pharmacy, doctor's workstation, nurse's workstation, surgery, anesthesia, financial settlement, inspection, testing, case processing, medical insurance, self-service information query and other businesses. Only the optimization and restructuring of hospital business processes, further strengthening the processing and mining of information resources can continuously improve the quality of medical services and management level of hospitals in order to achieve satisfactory economic and social benefits [14].
2 Feasibility Analysis
2.1 Economic Feasibility
Given the current price of computer equipment decreases year by year, in the large, medium and small hospitals already have the ability to equip computers and computer operators. In addition, the use of a good hospital management system can not only improve the efficiency of hospital management, to a large extent, to bring a lot of convenience to the public, the most important thing is to enable the use of hospitals in the next two to three years to recover the cost of further profits. In summary, the development of such a hospital information management system is economically feasible.
2.2 Technical Feasibility
Technical feasibility can be further divided into two categories: the technical feasibility of developing the system and the feasibility of the technology of the system users. NET high-level programming language, based on Microsoft Visual Studio 2005 as the development platform, combined with Microsoft SQL Server as the data source provider, so the development of the system is technically feasible; in terms of the technical feasibility of the system user, today's undergraduates are basically able to In terms of the technical feasibility of system users, today's undergraduates are basically able to master the use of WINDOWS operating system, as a medical undergraduate users, as long as the combination of user manuals can skillfully master the use of this management system. It can be said that it is also technically feasible.
2.3 Policy feasibility
The Ministry of Health in 1997 issued and published the "Hospital Information System Basic Functional Specification", for accelerating the construction of information technology infrastructure in hospitals, standardize the management, improve the quality of the hospital information system software, to protect the interests of the user, and to promote the healthy development of the hospital's computer applications play an important role in guiding. With the rapid development of computer network technology, the implementation of the Ministry of Health's major health care reform policy and the transformation of the medical model, to develop this hospital management system provides a strong policy feasibility guarantee [9].
3 Requirements Analysis
3.1 Business Processes
The basic business processes of hospital management are shown in Figure 3.1:
Figure 3.1 Business Processes in Hospital Management
3.2 System Hierarchical Block Diagram
The system consists of the "Dictionary Maintenance", "Outpatient" and "Dictionary Management". "The system consists of three first-level sub-modules: "Dictionary Maintenance", "Outpatient Management" and "Dean's Query". Drug information maintenance", "fee program maintenance" two modules; "outpatient management" sub-module by "registration management", Outpatient management" submodule consists of "registration management", "price management", "fee management", "pharmacy drugs" four modules; "Dean query" submodule consists of "departmental registration", "fee management", "pharmacy drugs" four modules. The module consists of two modules: "departmental registration volume" and "inventory statistics". The hierarchical block diagram is shown in Figure 3.2.
Figure 3.2 Hierarchical block diagram of the hospital management system
3.3 Hierarchical diagram of the modules in the system
3.3.1 System dictionary maintenance
The "System Dictionary Maintenance" module is used to set up the commonly used dictionary information in the hospital management system, including sub-functional modules as shown in Figure 3.3. It includes the sub-modules as shown in Figure 3.3.
Figure 3.3 System Dictionary Maintenance Module
3.3.2 Outpatient Registration System
The Outpatient Registration System functional module is used to establish and maintain the patient's main index information, assign the patient's ID number to ensure the uniqueness of the patient's information, establish the patient's card, and process the registration or appointment number of outpatients. It is used to process the registration or appointment number of outpatients, and provide information for the follow-up activities of outpatients as well as outpatient workload statistics. Patients can apply for IC card, magnetic card, etc. for the first time to realize one card to see a doctor, and card-carrying patients can replace the frequent queuing to pay fees by swiping the card when they visit the doctor, which can greatly improve the efficiency of both the hospital and the patient and reduce the waiting time of the patient. The computer automatically assigns a temporary ID number when registering, and you can choose to enter the patient's name, the type of registration (general, specialist, etc.) and the department and other information, print and generate the outpatient registration form, the barcode number on the registration form will be the basis of the patient's next steps in the medical treatment, which will realize the integration of the price of the charge, the project check, the pharmacy to take medication flow of the operation.
3.3.3 Outpatient pricing management
The "Outpatient pricing and charging system" functional module is used to record the patient's payment information at the outpatient fee collection office and perform the corresponding statistical accounting functions, which includes the self-functional modules as shown in Figure 3.4.
Figure 3.4: "Diagnostic pricing and charging system" function module
"Outpatient pricing" is used to complete the outpatient clinic patients of various prescriptions, examination applications, treatment applications, such as the pricing of the cost of diagnosis and treatment, the price of various medicines, examination information. The price information of various medicines and examinations is maintained in the dictionary management.
"Outpatient Charging" is used to complete the collection of various outpatient treatment costs, can be based on the price list (or other methods) to query the patient pricing information, cost collection, receipt printing process, and save the operation record for query.
"Drug distribution" is used for the pharmacy to pre-print the details of the drugs that need to be shipped and prepare the drugs, so that when the patient picks up the drugs, they can be given directly to the patient, avoiding the doctor to get the patient's bill and then go to look for the corresponding drugs.
3.3.4 Pharmacy Management System
"Pharmacy Management Module" function is used to manage the hospital pharmacy purchasing, warehousing and warehousing operations, including sub-modules shown in Figure 3.5.
Figure 3.5 Pharmacy Management Module
3.3.5 Dean's Comprehensive Query System
"Dean's Comprehensive Query System" functional module is used to process from the hospital information system to deal with the hospital management of the medical, teaching, research and human, financial and material analysis and decision-making information, in order to provide a basis for decision-making for the dean and the administrator. Provide a basis for decision-making.
3.4 System Flow Chart
The system flow chart of the hospital management system is shown in Figure 3.6.
Figure 3.6 System Flow Chart
3.5 System Data Flow Chart
3.5.1 Top Flow Chart
According to the basic business flow chart of hospital management in Figure 3.1, we can firstly come up with the top data flow chart of the system, as shown in Figure 3.7.
Figure 3.7 Top-level flow diagram of the hospital management system
3.5.2 Layer 0 flow diagram
Based on the top-level flow diagram of the hospital management system shown in Figure 3.7, by the knowledge of software engineering: the information continuity must be maintained in the hierarchical refinement of the data flow diagram, i.e., when decomposing a processing into a series of processing, the input/output of the inputs/outputs before and after decomposition data flows must be the same. [3] The top data flow graphs can be mapped to obtain a Layer 0 flow graph for the hospital management system, as shown in Figure 3.8.
Figure 3.8 Layer 0 flow diagram for a hospital management system
3.6 Data Dictionary
3.6.1 Data Flow Entries
Table 3.1 describes most of the data flow entries used in the system, which provides descriptions of the data flow names, where and how they are used, and their contents and supplementary information.
Table 3.1 Table of Data Flow Entries
Name Where and How Used Content Description
Drug Name Drug Information Query, enter name e.g. Penicillin
Drug Code Drug Information Query, enter number e.g. 1001
Item Name Chargeable Item Query, enter name e.g. Liver Functions
Item Code Chargeable Item query, enter the code such as 8000
Start time Department registration query, enter the time such as 1998-7-15
End time Department registration query, enter the time such as 2008-7-15
Stockroom Drug inventory query, enter the name of the stockroom such as Western Pharmacy
Drug number Drug inventory query, enter the name of the drug such as Tetracycline
Type of Registration Outpatient registration, the system has set up the classification of general and specialist
Type of Fees Outpatient registration, the system has set up the classification of public, self-funded, and retirement
The Department of Registration Outpatient registration, the system has set up the classification of traditional Chinese medicine, and other 16
Doctors Outpatient registration, enter the name of the doctor in order to be entered into the records of the name of the doctor in the hospital
Name Outpatient registration, enter the name of the doctor in the records
Doctor
Name p>Name outpatient registration, record the patient's name on the patient's name, such as Zhang San
Gender outpatient registration, record the patient's gender on the patient's gender, such as male
Age outpatient registration, record the patient's age on the patient's age, such as 36
Ethnicity outpatient registration, record the patient's ethnicity on the patient's ethnicity, such as Yao
4 Conceptual Architecture Design
4.1 Global Entity Diagram of the System
The global entity diagram of the system is shown in Figure 4.1.
Figure 4.1 Global Entity Diagram of the System
4.2 Entity Diagrams of the System
Based on the global entity diagram of the system in Figure 4.1, analyzing the system will result in the entity diagrams of the system as shown in the following figures.
Figure 4.2 Patient Entity Diagram
Figure 4.3 Physician Entity Diagram
Figure 4.4 Physician Prescription Entity Diagram
Figure 4.5 Pharmaceuticals Entity Diagram
Figure 4.6 Pharmacy Entity Diagram
4.3 System Tables and Their Uses
The system ****requires 10 tables, the uses of which are shown in Table 4.1 respectively<
Table 4.1 System Tables and Their Uses
Table Name Table Uses
Pharmaceuticals Data Saves basic information about the hospital's pharmaceuticals, including selling prices
Doctor Data Saves information about the doctor, including the department to which the doctor belongs
Department Data Saves information about the department's classification, such as medical, surgical, and so on
Patient Database Saves basic information about the patient, which can be reused later. patient's basic information, which can be reused later
Outpatient registration Save the information of outpatient registration
Outpatient registration type Save the classification information of the type of outpatient registration and its registration price, such as general, specialist, etc.
Outpatient pricing Outpatient pricing information (master table)
Outpatient pricing details Outpatient pricing details (from the table)
Outpatient charges items Save the classification information of the department, such as internal medicine, surgery, etc.
Outpatient charges items Save the classification information of the department, such as internal medicine, surgery, etc. Outpatient Charge Items Save outpatient charge items and their price information, including the name, type, cost, etc.
5 Logical Structure Design
5.1 Logical Design Specification
Database Logical Design is the process of converting the E-R diagram into a relational model, i.e., converting all the entities and relationships into a series of relational schemas. /p>
(1) An entity type is converted into a relational schema.
(2) A one-to-one relational model can be converted into a separate relational schema or merged with the corresponding relational schema at either end.
(3) A one-to-many link can be converted into a standalone relational model or merged with the relational model corresponding to either end of the multiple.
(4) A many-to-many link can be converted into a single relational schema.
5.2 Logical structure table
After the database system analysis and logical design, the structure of the database has been very clear, first of all, in Microsoft SQL Server 2000 to create a database HisBook. then, respectively, to create 10 tables: drug information table, doctor information table, department information table, patient information base table, Outpatient registration table, outpatient registration type table, outpatient pricing table, outpatient pricing details table, outpatient fee program table, drug inventory table, each table with the logical design of a kind of relational schema corresponds to.
Table 5.1 System Logical Structure Table
6 Physical Structure Design
6.1 Data Storage
The database is Microsoft MSSQL Server database, the installed version is: Simplified Chinese Personal Edition, the database file name is: hisbook_Data.MDF and log file hisbook_Log. Log.LDF, respectively, stored in the system's default folder below.
6.2 Creating Indexes
Building indexes is an effective means to speed up queries. Users can create one or more indexes on the basic table according to the needs of the application environment to provide multiple access paths to speed up the search. [7]MSSQL Server's two types of indexes are: Aggregate Indexes and Non-Aggregate Indexes, the advantage of using indexes is: to speed up the query, the disadvantage is: it will take up disk space, and reduce the speed of adding, deleting, and updating rows, so in the use of indexes, need to be carefully considered.
For the database tables involved in this system, the indexes created are:
Table 6.1 Creating Index Fields Table
Table Name Creating Aggregate Fields Creating Non-Aggregate Index Fields
Medication Information MedID MedName
Doctor Information DocID DocName
Department Information OffID OffName
PatientInfoBase PatiID PatiName
OutpatientRegistration PatiRegID PatiRegTime
OutpatientRegistrationType PatiRegKID None
OutpatientRegistration Price PriceKind None
OutpatientRegistrationDetails ListID ListName
Outpatient Charge Items KindID None
Pharmaceutical Inventory MedID MedName
7 Coding
7.1 Front-end Functional Design
There are three main functions in the system: dictionary maintenance, outpatient management, and dean's query. The dictionary maintenance function is mainly responsible for the maintenance of drug information and fee items, which are the two most important services provided by the hospital for patients. Outpatient management has outpatient registration, outpatient pricing, outpatient charging, pharmacy drug issuance of four functions, which is usually go to the hospital to see a doctor in the outpatient clinic when the process is the same, these four functions to deal with the patient from the registration until the medicine to leave the entire function. The dean's query mainly includes the query of the registration quantity and current drug inventory of each department of the hospital, and these two functions are mainly used for the statistics of the overall status of the hospital.
7.1.1 Dictionary Maintenance
Click Dictionary Maintenance | Drug Information command, you can enter the drug information function form, as shown in Figure 7.1. In it, you can manage all the current drug information of the hospital. By clicking the Add, Modify, or Delete buttons on the toolbar, you can add a new drug, modify a drug's specifications, units, or unit price and other information. The editing and inputting of data records are carried out in the text box in the lower panel of the form, except for editing or adding new records, the text box in the lower panel of the form is not editable.
Figure 7.1 Drug Information Management Function Window
After the maintenance of drug information, click the Dictionary Maintenance | Charges command to enter the hospital charges management window, shown in Figure 7.2. This window is very similar to the drug information, it mainly manages the information of all the charge items in the hospital. Also through the toolbar buttons above, you can add, modify, delete and other operations on the table. This table and the drug information table data is connected to the labeling of the number of drugs, drugs, the first four digits of the number of the first from 1 to 7, while the charges for the first item number is the beginning of 8, which is in order to facilitate the handling of the charges in the back, because patients are often prescribed at the same time and undergo a number of tests. Therefore, when adding a new number, the user can determine the first number according to the medical items the patient receives.
Figure 7.2 Charge Item Function Form
7.1.2 Outpatient Management
After completing the dictionary maintenance function, clicking on Outpatient Management allows you to carry out the four functions of outpatient registration, outpatient pricing, outpatient charging, and pharmacy medication issuance, which are also designed in accordance with the basic steps that a patient takes when visiting a hospital.
7.1.3 Dean's Query
In Solution Explorer, add a new form and change the name to "RegQuery", and place controls on it as shown in Figure 7.3.
Figure 7.3 Department Registration Form
Similarly, add a new form named "MedQuery" and place a space on it as shown in Figure 7.4.
Figure 7.4 Medication Inventory Form
8 System Testing
8.1 Overview of Software Testing[5]
Software testing is an important part of the software development process, and is used to confirm that the quality or performance of a program meets some of the requirements that have been set forth prior to development. The purpose of software testing is, firstly, to confirm the quality of the software, where on the one hand it is to confirm that the software does what you expect it to do, and on the other hand it is to confirm that the software does the event in the right way. The second is to provide information, such as feedback to developers or program managers, information prepared for risk assessment. Thirdly after the development of the software product is completed a lot of problems are found which indicates that this software development process is likely to be defective. Therefore the third purpose of software testing is to ensure that the entire software development process is of high quality.
Software quality is measured in several ways: First, doing a job right at the right time and in the right way. Second, in line with the requirements of some application standards, such as different countries of the user's different operating habits and requirements, the project project maintainability, testability and other requirements. Third, quality itself means that the software meets the requirements set at the very beginning, and the beauty of the code or subtle skills does not mean that the software is of high quality. Quality also means that it meets the needs of the customer. As a software testing industry, one of the most important things is to start from the customer's needs, from the customer's point of view to see the product, how customers will go to use the product, what kind of problems will be encountered in the process of use. Only these problems are solved, the quality of software products can be said to go up.
The tasks of testers in the software development process:
(1) Finding Bugs
(2) Avoiding Defects in Software Development
(3) Measuring the Quality of the Software
(4) Paying Attention to the User's Requirements
In a nutshell, the overall goal of testing is to ensure that the software is of a high quality in order to achieve the level of quality required by the user.
8.2 Common Software Testing Methods[6]
8.2.1 Black Box Testing
Black box testing, as the name implies, is to look at the system under test as a black box, taking inputs from the outside world and then outputting them. The entire test is based on the requirements document to see if it can meet the even requirements in the requirements document. Black box testing requires the tester to test without using knowledge or experience related to the internal structure of the system under test and it is suitable for testing the functionality of the system. The advantages of black-box testing include: it is simple and does not require knowledge of the internal code and implementation of the program; it has nothing to do with the internal implementation of the software; from the user's point of view, it is easy to know what functions the user will use and what problems he or she will encounter; based on the software development documentation, it is possible to know what functions the software has implemented in the documentation; it is more convenient to do the automated testing of the software. The disadvantages of black box testing are: it is not possible to cover all the code, the coverage rate is low, probably only up to 30% of the total amount of code; automated testing of the reusability is low.
8.2.2 White-box testing
White-box testing refers to the testing work in which the structure of the object under test is known and the content of the code under test can be accessed. It needs to know the internal design structure of the program and the specific code implementation, and use this as the basis for designing test cases. The following example program code:
HRESULT Save(char* pszFileName)
{
If (NULL = = pszFileName)
Return;
If (STATE_OPEND = = currentState)
{
SaveTheFile();
}
Return;
}
After reading the code, you can see that you have to check if a character is null first, and then perform the appropriate action based on the current state of the file. Design some test cases like this: what happens when the input string is empty; what happens if a file stored at this time has been opened. These are things that are not always possible when doing black-box testing.
The immediate benefit of white-box testing is to know where the designed test cases are ignored at the code level, and it has the advantage of helping software testers increase code coverage, improve the quality of the code, and find hidden problems in the code. The disadvantages of white box testing are: the program will run many different paths, it is impossible to test all the running paths; testing based on the code, can only test the developers to do the right thing or not, but can not know the design of the correct or not, may miss some of the functional requirements; when the system is huge, the testing overhead will be very large.
8.2.3 Model-based testing
Risk-based testing means evaluating the priority of testing, doing high-priority tests first, and if there is not enough time or effort, low-priority tests can be left off for a while. There is the following figure 8.2.3, where the horizontal axis represents the impact and the vertical axis represents the probability, based on the characteristics of a piece of software: if something goes wrong with a feature, how big is its impact on the whole product, and what is the probability that this feature will go wrong? If the probability of a problem is large, and the impact of the problem on the entire product is also large, then the test must be covered. For features that are rarely used by users, the probability of something going wrong is small, and even if something goes wrong the impact is not very large, then if time is tight, you can consider not testing [15].
Figure 8.1 Two Determinants of Risk-Based Testing
The two determinants of risk-based testing are how much of an impact a problem with the feature will have on the user and how likely it is that something will go wrong. Some of the other influencing factors are complexity, usability, dependencies, modifiability, and so on. Testers decide where to focus their testing efforts mainly based on the priorities of the matter.
8.3 Software Testing Methodology for this System
Since this program is for small hospitals, the software is small and the functionality is relatively simple, the software testing methodology used is black box testing. Software in the initial completion, handed over to a third party for testing (here I let the students in the same dormitory for testing), the third party in the actual use of the problems found: such as the need to supplement the function, some errors in the operation, etc., the program developers according to the views of the third party to make modifications until the software function in line with the user (the system user) until.
9 Conclusion
9.1 Summary of system functions
This small hospital management system can simply complete the hospital's outpatient, pharmacy, the director of the query of the basic functions. But there is no invoice printing function, in the outpatient management part is not perfect enough to realize the function of registering patients with magnetic cards. This system has roughly accomplished the main functions mentioned in the requirement analysis. For accomplishing such a database system in the context of a brand new development language, the workload and difficulty are still very great, for example, how to connect to the database in the .NET environment, and there is still the problem of errors in data operation between different modules, and so on.
Because of the high starting point and standards in the design of the system, in a short period of time failed to improve all the sub-functions, sub-modules, but in the establishment of the database table structure, always in accordance with the one-step, do not easily change the principle, because once the structure of the table changes, the corresponding logical structure, the foreground display information must be followed by the change, which brings about the workload is very large.
9.2 Prospects of the system
(1) Data structure problems
As mentioned in the summary of the system's functions: the function of registering patients with magnetic cards has not been realized, and it has not yet been possible to realize the interfaces to connect with hardware devices.
(2) Backup and recovery of data
The data backup function is mainly realized through the SQL statement BACKUP DATABASE, and the data recovery function is mainly realized through the SQL statement RESTORE DATABASE. Due to time rush, I was not able to realize these two functions.
(3)Knowledge of .NET language
Because it is the first time to use .NET language for programming related software, developing such a database system in three weeks gave me a great challenge and difficulty, but under Mr. Xie's encouragement I took the spirit of continuous learning, step by step, I hope that this experience will have a great impact in my future study. I hope this experience will have a great impact on my future studies.
(4) The method of accessing the database in .NET
This system is based on the design and realization of the .NET framework, and the method of accessing the database in .NET I just refer to the method and code given in some reference books to realize, but I am not very clear about the reason of it.
(5) system scalability
The development of the system there are many functions that can be improved, such as monthly or yearly financial settlement, the establishment of the hospital's staff in the information base, which is a perfect hospital management system necessary.