Quality evaluation method and system for software engineering development

Abstract

The invention discloses a quality evaluation method and system for software engineering development, and relates to the technical field of quality evaluation for software engineering. The system efficiency of the evaluation process is ensured; comprising an evaluation plan module, an index design module, an actual measurement module and an analysis module. The evaluation plan module lists items, needing to be evaluated, of the software in advance in a static state, including functions of the software, namely functions and effects which can be specifically realized by the software in an actual operation process, and whether the user meets various function requirements required by the user in the software using process; when the software is used, whether the linkage interaction capability between the software and a peripheral system is obstructed to influence the use of the software or not is judged. According to the method, the items needing to be evaluated are classified and divided in advance before software is evaluated, and the situation that during evaluation, due to the fact that the number of evaluation items is large, confusion is generated or the evaluation items are complex, and the time needed by evaluation is prolonged is avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of quality evaluation for software engineering, and in particular to a quality evaluation method and system for software engineering development. Background Art

[0002] In the existing technology, various software are needed in life, and different software has different specific functions to meet various needs in life. Therefore, the quality of the software is directly related to the final user experience. The primary purpose of software quality evaluation is to ensure that the software product can accurately and completely meet the needs of users. Through evaluation, the deficiencies of the software in terms of function, performance, security, etc. can be discovered to ensure that the software product truly complies with the user's business processes and operating habits. High-quality software can bring better user experience, thereby improving user satisfaction and loyalty. Software quality evaluation can help developers examine the software from the user's perspective, improve the software's ease of use, compatibility, stability, etc., and encourage users to have positive evaluations of software products;

[0003] After searching, the Chinese patent application number 202011311518.9 discloses a software quality evaluation method and system based on process evaluation and test results. The method includes: a software acquisition step for acquiring the software to be evaluated; a software quality evaluation model establishment step for constructing a software quality evaluation model based on the software development process evaluation and test results; a software quality evaluation step for quantitatively scoring the development process evaluation and test results of the software to be evaluated based on the software quality evaluation model, and calculating the total evaluation score of the quality of the software to be identified.

[0004] A software quality evaluation method and system in the above patent has the following deficiencies: before the software is evaluated, there is a lack of classification and division of the items that need to be evaluated, which leads to confusion due to a large number of items in the evaluation process or the evaluation items are complicated, which prolongs the time required for evaluation. Summary of the invention

[0005] The purpose of the present invention is to solve the shortcomings of the prior art and to propose a quality evaluation method and system for software engineering development.

[0006] In order to achieve the above object, the present invention adopts the following technical solutions:

[0007] A quality evaluation system for software engineering development, comprising an evaluation plan module, an indicator design module, a measurement module and an analysis module;

[0008] The evaluation plan module statically lists the items that need to be evaluated for the software, including:

[0009] Functionality of software: that is, the functions and effects that the software can achieve in actual operation;

[0010] Software security: the software's ability to protect data security;

[0011] Software reliability: that is, whether the various subsystems and ports of the software can identify whether the transmitted data is misaligned in the first place;

[0012] Software usability: When users are operating the software, are the instructions they provide to users clear and easy to understand?

[0013] Preferably: the indicator design module includes a durability measurement module, which evaluates the defect density, failure rate and time required to fix bugs in the software, and performs performance measurement on the response time and resource utilization of the software during operation, and maintains the cohesion and coupling between modules.

[0014] Further: the measurement module specifically includes:

[0015] Code review: manually review the source code to eliminate obvious misalignments and potential defects;

[0016] Functional testing module, after the software unit is coded, evaluates whether the functionality of each port of each software unit is complete;

[0017] The integration evaluation module integrates multiple software units and evaluates the maximum load bearing of the software after the unit evaluation module evaluates the functionality of each port to be normal;

[0018] The performance testing module tests the software's running speed, server occupancy, client resource occupancy, and network resource occupancy.

[0019] Coverage analysis module, which evaluates the effectiveness of testing by measuring the proportion of program parts covered by test cases;

[0020] The fault injection test module simulates abnormal conditions to detect the fault tolerance of the entire system.

[0021] Furthermore: the analysis module is based on inspection, team review, and peer review, and utilizes mutual suggestions among team members to audit and analyze whether the software is compliant and meets the requirements of laws and regulations. The analysis module performs quality management on the quality level of the software based on CMMI and TQM.

[0022] As a preferred solution of the present invention: the functionality of the software ensures whether the various functional requirements of the user are met during the use of the software, and whether the linkage and interaction capabilities between the software and the surrounding systems are hindered when the software is in use, affecting the use of the software.

[0023] As a further solution of the present invention: the specific safety assessment items of the software include:

[0024] User identity authentication: login password verification, IP address access restriction;

[0025] User access rights: Differentiate user levels so that users of different levels do not overlap with each other;

[0026] User data privacy: Hide, encrypt and back up passwords for system files.

[0027] As a further solution of the present invention: the reliability of the software needs to avoid failure problems caused by erroneous transmission, the time required for the port to recover to a normal operating state after receiving erroneous data, and the degree of recovery relative to the initial state.

[0028] On the basis of the above scheme: the usability of the software is whether the software has detailed instructions and a guide to getting started, so that users who have not been exposed to related types of software can get started with the software in the shortest time, reducing the difficulty of learning.

[0029] On the basis of the above-mentioned scheme: the functional testing module verifies whether the various functions are realized according to the actual needs of the demand group, including the convenience, accuracy and safety of user operation; evaluates the error-proof ability of the software, including the fault tolerance rate and whether the software page is prone to freezing; evaluates the functionality of the software, including the difficulty of page learning and whether the operation page is attractive; evaluates the compatibility of the software, such as whether the software is easy to install on different operating platforms after being put into use, and whether it runs smoothly after installation; evaluates the security of the software, including the defense capability against external network attacks and the performance of preventing user information leakage.

[0030] A quality evaluation method for software engineering development comprises the following steps:

[0031] S1: Coordinate the contents of each project that needs to be evaluated for software quality evaluation, and clarify the setting parameter range of each evaluation indicator in the actual evaluation process;

[0032] S2: Evaluate the software in static and dynamic environments respectively, and conduct test evaluation on the software code, functions, integration and coverage analysis modules;

[0033] S3: After the test is completed, the test indicators and test results are audited through team review and peer review to determine whether they meet the requirements under various standards.

[0034] The beneficial effects of the present invention are:

[0035] 1. A quality evaluation method and system for software engineering development, which classifies and divides the items that need to be evaluated before the software is evaluated, ensures that the items that need to be evaluated are presented more clearly, and avoids confusion caused by a large number of evaluation items or prolonged evaluation time due to complicated evaluation items.

[0036] 2. A quality evaluation method and system for software engineering development, which evaluates the functionality, security, reliability and usability of the software, making the entire evaluation process more systematic and comprehensive, and enabling the software to be evaluated both dynamically and statically.

[0037] 3. A quality evaluation method and system for software engineering development, which evaluates the quality of the software by integrating various modules, facilitates a comprehensive evaluation of the quality status of the software, and can find out where the software needs to be improved and the smoothness of the software during operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is an overall schematic diagram of a quality evaluation system for software engineering development proposed by the present invention;

[0039] Figure 2 The present invention is a flowchart of a quality evaluation method for software engineering development. DETAILED DESCRIPTION

[0040] The technical solution of this patent is further described in detail below in conjunction with specific implementation methods.

[0041] The embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0042] Embodiment 1:

[0043] A quality evaluation system for software engineering development, such as Figure 1 As shown, it includes evaluation plan module, indicator design module, measurement module and analysis module;

[0044] The evaluation plan module statically lists the items that need to be evaluated for the software, including:

[0045] The functionality of the software, that is, the functions and effects that the software can achieve in actual operation, whether the software meets the various functional requirements of users when using the software, and whether there are any obstacles in the interaction between the software and the surrounding systems when using the software, which affects the use of the software;

[0046] Software security refers to the ability of the software to protect data security, that is, unauthorized users cannot access the software to obtain relevant information within the software. Specific evaluation items include:

[0047] User identity authentication: login password verification, IP address access restriction;

[0048] User access rights: Differentiate user levels so that users of different levels do not overlap with each other;

[0049] User data privacy: Hide, encrypt and back up passwords for system files;

[0050] When a user logs in, the user's ability to resist external attacks is evaluated. For example, an illegal user may use an automated application script in an infinite loop to seize the IP address resource pool, or an illegal user may use a while infinite loop to make a query request.

[0051] Whether the software meets the regulatory requirements in terms of functionality, i.e. national standards, international standards and industry standards;

[0052] Software reliability, that is, whether the various subsystems and ports of the software can identify whether the transmitted data is misplaced in the first place, and avoid failures caused by erroneous transmission. When the port receives erroneous data, the time required for it to recover to the normal operating state and the degree of recovery relative to the initial state;

[0053] The usability of the software. During the operation of the software, are the instructions fed back to the user clear and easy to understand, so that the user can continue to operate the next instruction according to the instructions after feedback? Does the software have detailed instructions and a guide to getting started, so that users who have not been exposed to related software can get started with the software in the shortest time possible, reducing their learning difficulty?

[0054] The indicator design module includes a durability measurement module, which evaluates the defect density, failure rate and time required to fix bugs in the software, and performs performance measurement on the response time and resource utilization of the software during operation, and maintains the cohesion and coupling between modules;

[0055] The measurement module specifically includes:

[0056] Code review: manually review the source code, eliminate obvious misalignments and potential defects, evaluate the consistency and completeness of design documents and test documents, and quantify the structural complexity of software modules to determine the complexity of the structure;

[0057] Functional testing module: after the software unit is coded, evaluate whether the functionality of each port of each software unit is complete; verify whether the various functions are realized according to the actual needs of the demand group, including user operation convenience, accuracy and safety of use; evaluate the error ability of the software, including fault tolerance and whether the software page is prone to freezing; evaluate the functionality of the software, including the difficulty of page learning and whether the operation page is attractive; evaluate the compatibility of the software, such as whether the software is easy to install on different operating platforms after being put into use, and whether it runs smoothly after installation; evaluate the security of the software, including the defense capability against external network attacks and the performance of preventing user information leakage;

[0058] The integration evaluation module integrates multiple software units and evaluates the maximum load bearing of the software after the unit evaluation module evaluates the functionality of each port to be normal;

[0059] The performance testing module tests the software's running speed, server occupancy, client resource occupancy, and network resource occupancy.

[0060] This embodiment is designed for the actual scenario during performance testing:

[0061] 1: When the software is logged in by a single user, the time required for a single user to open the software login interface, enter the password and log in to the software is tested;

[0062] 2: When the software has multiple users logging in, when multiple users log in to the software at the same time, test the time required for each independent user to open the software login interface, enter the password and log in to the software;

[0063] The test items include the time required for dynamic response, the time required for uploading files, and the time required for downloading files;

[0064] By testing and evaluating the above items, the software load and performance index distribution rules are judged;

[0065] Coverage analysis module, which evaluates the effectiveness of testing by measuring the proportion of program parts covered by test cases;

[0066] Fault injection test module simulates abnormal conditions to detect the fault tolerance of the entire system;

[0067] The analysis module audits and analyzes the compliance of the software and the requirements of laws and regulations based on inspection, team review, and peer review, using mutual suggestions among team members. The analysis module manages the quality level of the software based on CMMI and TQM.

[0068] Integrating the above modules to evaluate the quality of the software facilitates an all-round evaluation of the quality status of the software, and can identify where the software needs to be improved and the smoothness of the software during operation.

[0069] Embodiment 2:

[0070] A quality evaluation method for software engineering development comprises the following steps:

[0071] S1: Coordinate the contents of each project that needs to be evaluated for software quality evaluation, and clarify the setting parameter range of each evaluation indicator in the actual evaluation process;

[0072] S2: Evaluate the software in static and dynamic environments respectively, and conduct test evaluation on the software code, functions, integration and coverage analysis modules;

[0073] S3: After the test is completed, the test indicators and test results are audited through team review and peer review to determine whether they meet the requirements under various standards.

[0074] The above is a preferred specific implementation manner of the present invention, and the protection scope of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by any technician familiar with the field within the technical scope disclosed by the present invention in combination with the prior art or public common sense, within the spirit and principle of the present invention, shall be covered by the protection scope of the present invention.

Claims

1. A quality evaluation system for software engineering development, characterized in that: It includes evaluation plan module, indicator design module, measurement module and analysis module; The evaluation plan module statically lists the items that need to be evaluated for the software, including: Functionality of software: that is, the functions and effects that the software can achieve in actual operation; Software security: the software's ability to protect data security; Software reliability: that is, whether the various subsystems and ports of the software can identify whether the transmitted data is misaligned in the first place; Software usability: When users are operating the software, are the instructions they provide to users clear and easy to understand? 2. A quality evaluation system for software engineering development according to claim 1, characterized in that: The indicator design module includes a durability measurement module, which evaluates the defect density, failure rate and time required to fix bugs in the software, and performs performance measurement on the response time and resource utilization of the software during operation, and maintains the cohesion and coupling between modules.

3. A quality evaluation system for software engineering development according to claim 2, characterized in that: The measurement module specifically includes: Code review: manually review the source code to eliminate obvious misalignments and potential defects; Functional testing module, after the software unit is coded, evaluates whether the functionality of each port of each software unit is complete; The integration evaluation module integrates multiple software units and evaluates the maximum load bearing of the software after the unit evaluation module evaluates the functionality of each port to be normal; The performance testing module tests the software's running speed, server occupancy, client resource occupancy, and network resource occupancy. Coverage analysis module, which evaluates the effectiveness of testing by measuring the proportion of program parts covered by test cases; The fault injection test module simulates abnormal conditions to detect the fault tolerance of the entire system.

4. A quality evaluation system for software engineering development according to claim 3, characterized in that: The analysis module is based on inspection, team review, and peer review, and utilizes mutual suggestions among team members to audit and analyze whether the software is compliant and meets the requirements of laws and regulations. The analysis module performs quality management on the quality level of the software based on CMMI and TQM.

5. A quality evaluation system for software engineering development according to claim 4, characterized in that: The functionality of the software ensures whether the various functional requirements of the user are met during the use of the software, and whether there are any obstacles in the linkage and interaction capabilities between the software and the surrounding systems when the software is in use, affecting the use of the software.

6. A quality evaluation system for software engineering development according to claim 5, characterized in that: The specific security assessment items of the software include: User identity authentication: login password verification, IP address access restriction; User access rights: Differentiate user levels so that users of different levels do not overlap with each other; User data privacy: Hide, encrypt and back up passwords for system files.

7. A quality evaluation system for software engineering development according to claim 6, characterized in that: The reliability of the software needs to avoid failures caused by erroneous transmission, the time required for the port to recover to a normal operating state after receiving erroneous data, and the degree of recovery relative to the initial state.

8. A quality evaluation system for software engineering development according to claim 7, characterized in that: The usability of the software refers to whether the software has detailed instructions and a user guide, so that users who have not been exposed to related software can get started with the software in the shortest time possible, reducing the difficulty of learning.

9. A quality evaluation system for software engineering development according to claim 8, characterized in that: The functional testing module verifies whether various functions are realized according to the actual needs of the demand group, including the convenience, accuracy and safety of user operation; evaluates the error-proof ability of the software, including the fault tolerance rate and whether the software page is prone to freezing; evaluates the functionality of the software, including the difficulty of page learning and whether the operation page is attractive; evaluates the compatibility of the software, such as whether the software is easy to install on different operating platforms after being put into use, and whether it runs smoothly after installation; evaluates the security of the software, including the defense capability against external network attacks and the performance of preventing user information leakage.

10. A quality evaluation method for software engineering development, based on the quality evaluation system for software engineering development according to any one of claims 1 to 9, characterized in that: The following steps are involved: S1: Coordinate the contents of each project that needs to be evaluated for software quality evaluation, and clarify the setting parameter range of each evaluation indicator in the actual evaluation process; S2: Evaluate the software in static and dynamic environments respectively, and conduct test evaluation on the software code, functions, integration and coverage analysis modules; S3: After the test is completed, the test indicators and test results are audited through team review and peer review to determine whether they meet the requirements under various standards.

Images