Software quality integrated management method and system

Abstract

The invention relates to the technical field of software development, in particular to a software quality integrated management method and system. The system comprises a demand management module used for determining a demand and making a test plan; the data processing module is used for collecting quality management data in the software development process and labeling the data; the association relationship module is used for establishing an association relationship between the data; the execution recording module is used for recording operation in software development, test and repair processes and generating an execution log; the quality analysis module is used for constructing a quality evaluation model, calculating a software quality score and judging a software quality grade; the test management module is used for generating and executing a test case according to requirements to obtain evaluation data; and the quality evaluation module is used for integrating and analyzing the evaluation data and comprehensively evaluating the software quality. According to the technical scheme, quality management in the software development process can be efficiently and comprehensively achieved, and quick tracing and positioning of quality problems are achieved.

Description

Technical Field

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

[0002] With the rapid development of information technology, the software development industry is facing unprecedented challenges and opportunities. The complexity of software products continues to increase, and users' requirements for software quality are also increasing. Traditional software quality management methods often rely on manual and decentralized management methods, which leads to low efficiency of quality control in the software development process, difficulty in tracing problems, and inability to timely and accurately evaluate the overall quality level of the software.

[0003] In the existing technology, software quality management is usually divided into multiple independent and relatively fragmented stages, such as requirements analysis, test plan formulation, code development, test execution, defect repair, etc. Although this phased management method helps to standardize the software development process to a certain extent, the information flow between the stages is not smooth, the data island phenomenon is serious, and it is difficult to form a complete quality management closed loop.

[0004] First, in terms of demand management, existing technologies often rely on traditional document management methods, such as Word, Excel, etc. These tools have many inconveniences in demand changes, version control, demand traceability, etc., and it is difficult to ensure the integrity and consistency of requirements.

[0005] Secondly, in terms of data processing and establishing relationships, existing technologies lack efficient means of data collection, organization and analysis, which makes it difficult to fully utilize quality management data in the software development process. At the same time, the relationships between data are often ignored, making it difficult to quickly locate and fix problems when they occur.

[0006] Furthermore, in terms of test management, test cases in the prior art often rely on manual writing, and test plans lack scientificity and systematicity, resulting in low test efficiency and insufficient test coverage. In addition, the maintenance and management of test cases also face many difficulties.

[0007] Finally, in terms of quality assessment, existing technologies often rely on manual and empirical assessment methods and lack objective and comprehensive quality assessment models and methods. This makes the software quality assessment results often subjective and uncertain, making them difficult to use as a basis for decision-making. Summary of the invention

[0008] The purpose of the present invention is to propose a software quality integrated management method and system, which can efficiently and comprehensively realize quality management in the software development process, realize rapid tracing and location of quality problems, and provide objective and comprehensive quality evaluation results, thereby providing strong support for decision-making in the software development process.

[0009] To achieve the above objectives, in a first aspect, an embodiment of the present disclosure provides a software quality integrated management system, including: Requirements management module, used to determine requirements and develop test plans based on them; The data processing module is used to collect quality management data during the software development process and label the quality management data. The labels include defect type, priority, and repair status. The association module is used to establish the association between data; The execution record module is used to record the operations in the software development, testing, and repair processes and generate execution logs; The quality analysis module is used to build a quality assessment model that includes multiple quality elements and their weights; calculate the software quality score based on the actual quality data, and determine the software quality level based on the preset threshold; The test management module is used to generate and execute test cases according to requirements and obtain evaluation data; The quality assessment module is used to integrate and analyze the assessment data and conduct a comprehensive assessment of software quality.

[0010] Beneficial effects of the basic solution: Through the requirements management module, the software development goals can be clarified and a test plan can be formulated accordingly, ensuring the pertinence and effectiveness of the test work. The association module establishes the association between data, so that each link in the software development process can be closely connected, improving the efficiency of collaboration between teams.

[0011] The data processing module collects and labels quality management data, providing a rich information basis for quality analysis. Detailed classification of labels (such as defect type, priority, and repair status) helps to accurately locate problems and optimize resource allocation. The quality analysis module uses this data to build a quality assessment model, calculates software quality scores through actual quality data, and determines quality levels, providing a scientific basis for decision-making.

[0012] The test management module generates and executes test cases according to requirements, ensuring comprehensive verification of software functions. Potential defects can be effectively discovered through a combination of automated testing or manual testing. The quality assessment module integrates and analyzes the assessment data, not only focusing on the repair of individual defects, but also evaluating the software quality as a whole, which helps to discover systemic problems and improve the overall stability and reliability of the software.

[0013] The execution record module records the operations in the software development, testing, and repair processes in detail, generates execution logs, and provides a traceable basis for subsequent audits and improvements. Through continuous quality monitoring and evaluation, bottlenecks and deficiencies in the process can be discovered in a timely manner, promoting process optimization and improving development efficiency.

[0014] The system can regularly evaluate software quality through the quality assessment model of the quality analysis module, and adjust the quality strategy according to the assessment results to achieve continuous improvement. At the same time, through data accumulation and analysis, the trends and laws of quality problems can be discovered, providing early warning and preventive measures for software development.

[0015] As an implementable preferred solution, the data processing module is used to use an API interface or data crawler technology to achieve real-time acquisition and update of data, and use a rule engine to achieve automatic execution of custom rules and automatic labeling of tags.

[0016] As an implementable preferred solution, the association module establishes associations between data through a graph database or a relational database, uses graph algorithms to analyze and mine data associations, and provides a visual tracing interface to display the context and related information of the problem.

[0017] As an implementable preferred solution, the quality analysis module constructs a quality assessment model based on industry standards and internal experience, and regularly updates and optimizes the model based on newly collected data and feedback.

[0018] As an implementable preferred solution, the test management module uses the CI / CD pipeline to automatically execute test cases and collect data during the test process in real time; at the same time, it periodically performs statistical analysis on the test cases to obtain high-risk test cases for key testing.

[0019] As an implementable preferred solution, the requirement management module is connected to a variety of demand communication methods, including video conferencing, email, and online collaboration platforms; the requirement management module is also used to automatically classify and prioritize requirements when formulating test plans.

[0020] As an implementable preferred solution, the requirement management module uses natural language processing technology to identify and analyze the requirements mentioned in the communication, and trains a customized NER model based on existing annotated data, including examples of various functional points, performance indicators and compatibility requirements.

[0021] As an implementable preferred solution, the requirement management module is also used to parse sentence structures, determine dependencies between words, and analyze the contextual relationships between functional requirements and performance indicators, as well as dependencies between requirements through dependency syntax.

[0022] As an implementable preferred solution, the demand management module is also used to construct or adopt an existing sentiment dictionary to perform sentiment polarity judgment and sentiment fine-grained analysis on user feedback. The user feedback is scored for sentiment intensity, and combined with the frequency of occurrence of the needs, the urgency and importance of the needs are comprehensively evaluated, and positive weights are generated to adjust the priority ranking of the needs. At the same time, different positive weights are given to related needs according to the degree of correlation between the dependencies between the needs.

[0023] In a second aspect, the embodiments of the present disclosure also provide a method for integrated software quality management, which utilizes the above-mentioned integrated software quality management system. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 The figure is a schematic diagram of the architecture of an integrated software quality management system.

[0025] Figure 2 FIG. 4 is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to make the technical solution and advantages of the present application clearer, the technical solution of the present invention will be further described in detail below in conjunction with the accompanying drawings. It will be understood that the specific embodiments described herein are only partial embodiments of the present invention, which are only used to explain the present application, rather than to limit the present application. It should be noted that the technical features or combinations of technical features described in the following embodiments should not be considered isolated, and they can be combined with each other to achieve better technical effects. The same reference numerals appearing in the drawings of the following embodiments represent the same features or components, which can be applied to different embodiments.

[0027] In addition, unless otherwise defined, the technical terms or scientific terms used in the description of the present invention should have the common meanings understood by those skilled in the art in the art to which the present invention belongs.

[0028] The present invention is further described in detail below in conjunction with the accompanying drawings: Reference numerals: electronic device 500 , processor 501 , communication interface 502 , memory 503 .

[0029] Embodiment 1 Reference Figure 1 , a software quality integrated management system, including a demand management module, a data processing module, an association module, an execution record module, a quality analysis module, a test management module, an execution analysis module, and a quality assessment module.

[0030] The demand management module includes a target submodule, an archive submodule and a plan submodule.

[0031] The target submodule is used to clarify the functional requirements (such as user interface design, business logic processing), performance requirements (such as response time, load capacity) and compatibility requirements of the software. The target submodule is connected to a variety of demand communication methods, including video conferencing, email, online collaboration platforms, etc.

[0032] The archiving submodule is used to organize the results of demand communication into a structured requirement specification, including detailed information such as functional requirements, performance requirements, compatibility requirements, etc., and use a version control system (such as Git) to manage the version of the requirement specification to ensure that each requirement is clear, traceable and testable.

[0033] The planning submodule develops a testing strategy based on the requirements specification, including test types (unit testing, integration testing, system testing), test methods (such as black box testing, white box testing, etc.), test tools, etc. It automatically classifies and prioritizes requirements, develops a testing plan using project management tools, and specifies detailed information such as test phases, test resources, test environment, test tools, and test milestones.

[0034] The data processing module includes an acquisition submodule and a label submodule.

[0035] The acquisition submodule is used to automatically collect quality management data in the software development process from channels such as project management tools, code repositories, and continuous integration / continuous deployment (CI / CD) platforms, including but not limited to code submission records, defect reports, test coverage, etc., and use API interfaces or data crawler technology to achieve real-time acquisition and update of data.

[0036] The label submodule is used to label the collected data using custom rules or machine learning algorithms, including defect type (such as functional defects, performance defects), priority (high, medium, low), repair status (to be repaired, repaired), etc., to facilitate subsequent analysis and use the rule engine to realize the automatic execution of custom rules and automatic labeling of labels.

[0037] The association module, based on data tags, establishes associations between data through graph databases or relational databases, such as the association between defects and code files, and the association between test cases and requirements, to achieve rapid tracing of quality issues. It uses graph algorithms to analyze and mine data associations to achieve rapid tracing of quality issues, making it easier for developers to quickly locate and fix problems. It also provides a visual tracing interface to display the context and related information of the problem.

[0038] The execution record module is used to automatically record each step of the software development, testing, repair and other processes using scripts or API interfaces, and generate detailed execution logs, including information such as operation time, operator and operation content, to ensure the transparency and traceability of the process.

[0039] The quality analysis module includes a model building submodule and a rating submodule.

[0040] Model building submodule: Based on industry standards and internal experience, build a quality assessment model that includes multiple quality elements (such as code quality, test coverage, user satisfaction) and their weights. Use the data processing library to quantify and calculate the quality elements and determine the weights of the quality elements. Regularly update and optimize the model based on newly collected data and feedback to achieve real-time update and adaptation of the model.

[0041] According to industry standards and internal experience, set quantitative standards for each quality element. Use the data processing library to clean, transform and calculate the collected data. Determine the weight of each quality element through expert scoring, questionnaire surveys, historical data analysis, etc. The weight value should sum to 1 or 100.

[0042] The rating submodule is used to input the actual quality data into the model, automatically calculate the software quality score through the algorithm, and determine the software quality level according to the preset threshold, which are excellent (above 90 points), good (80-89 points), average (70-79 points), and poor (below 70 points).

[0043] The test management module includes a simulation submodule and a cycle submodule.

[0044] The simulation submodule is used to generate test cases that simulate user behavior based on the requirement information in the requirement document using automated testing tools (such as Selenium and JMeter), and to use the script recording function to automatically generate and execute test cases to obtain evaluation data. Determine quality elements, which include code quality (such as the number of lines of code, comment ratio, code duplication rate, code complexity, etc.), test coverage (such as unit test coverage, integration test coverage, system test coverage, etc.), user satisfaction (such as data collected through questionnaires, user feedback, etc.), and other quality elements such as performance, security, maintainability, etc.

[0045] The cycle submodule is used to establish a test case database through project management tools, and to implement tracking management of the entire life cycle of test case design, review, execution, update, and maintenance. It predicts the probability of defect occurrence, optimizes the allocation and priority sorting of test cases, conducts statistical analysis on test cases, and obtains high-risk test cases for key testing.

[0046] The execution analysis module includes an execution submodule and an analysis submodule.

[0047] The execution submodule uses containerization technology to build a test environment consistent with the production environment to improve the reliability of test results. It uses the CI / CD pipeline to automatically execute test cases, collect data during the test process in real time, such as test time, test results, error logs, etc., and generate test reports.

[0048] The analysis submodule is used to combine the test results with the requirements document, analyze the function implementation, performance and compatibility between functions, compare the test results with the expected results, and identify potential defects.

[0049] The quality assessment module includes a comprehensive assessment submodule and a report generation submodule.

[0050] The evaluation submodule is used to integrate and analyze the evaluation data using the data processing library, and to conduct a comprehensive evaluation of software quality by integrating test results, user feedback, historical quality data and other factors.

[0051] The report submodule is used to automatically generate a quality report containing quality scores, a list of major defects, improvement suggestions, and provide a visual display.

[0052] Embodiment 2 The technical feature that distinguishes this embodiment from the above-mentioned embodiment is that the target submodule of the requirement management module is also used to identify and analyze the requirements mentioned in the communication through natural language processing (NLP) technology, and to organize and summarize them to assist in setting target requirements. Named Entity Recognition (NER) is a task of NLP, and key information such as function points, performance indicators, and compatibility requirements can be identified through NER.

[0053] The target submodule trains a customized NER model based on existing annotated data, including examples of various functional points, performance indicators, and compatibility requirements. The results obtained by the NER model form structured demand information by removing duplicate entities and merging similar entities.

[0054] The target submodule can identify specific functional points, such as "users should be able to log in to the system", "the system should support file uploads", etc. The identified functional points will be directly converted into test items in subsequent test cases after confirmation. The target submodule can also identify descriptions related to performance, such as "response time must be within 2 seconds", "the system should be able to withstand 1,000 concurrent users", etc. The identified performance indicators will be used as the basis for performance testing in subsequent test cases after confirmation. The target submodule can directly identify descriptions related to compatibility, such as "support iOS and Android platforms", "compatible with IE11 and above browsers", etc. The identified compatibility requirements will guide the execution of test cases in different test environments after confirmation.

[0055] The target submodule will also parse the sentence structure, determine the dependency relationship between words, and help understand the contextual relationship between functional requirements and performance indicators, as well as the dependency relationship between requirements through dependency syntax analysis. The target submodule first performs preprocessing such as word segmentation and stop word removal on the requirement document or recognized text to improve the accuracy of the analysis, and then extracts the required dependency information by writing parsing code. The analysis results are represented in a tree structure.

[0056] The target submodule can identify the subject-predicate-object structure of functional requirements, so as to understand the specific content of the requirements more accurately. For example, in "users should be able to log in to the system", "user" is the subject, "should be able to log in" is the predicate, and "system" is the object. By analyzing these dependencies, the requirements can be understood more clearly. The target submodule can identify the relationship between performance indicators and functional requirements. For example, in "response time must be within 2 seconds", "response time" is the subject and "must be within 2 seconds" is the condition. By analyzing these dependencies, the constraints of performance indicators on functional requirements can be understood. The target submodule can identify the dependencies between requirements. For example, in "after the file is successfully uploaded, the system should send a notification", "file upload success" is the prerequisite for "sending a notification". By analyzing these dependencies, the logical order and dependencies between requirements can be understood.

[0057] Combined with the above technical features, the target submodule can extract key requirement information and analyze and understand the dependencies between requirements.

[0058] Embodiment 3 The technical feature that distinguishes this embodiment from the above-mentioned embodiments is that the target submodule is also used to construct or adopt an existing sentiment dictionary to judge the sentiment polarity (positive, negative, neutral) of user feedback, as well as fine-grained sentiment analysis (such as joy, anger, sadness, etc.).

[0059] The target submodule will conduct sentiment analysis on the words used in user voice communication or feedback, score the sentiment intensity of user feedback, and comprehensively evaluate the urgency and importance of the requirement in combination with the frequency of occurrence of the requirement, and generate positive weights to adjust the priority of the requirement. At the same time, according to the dependencies between requirements, requirements with associated relationships will also obtain positive weights according to the degree of association, that is, referring to the dependency tree structure diagram, the closer the associated requirements are to the user feedback requirements, the more positive weights they will obtain, and the more distant the associated requirements will obtain lower positive weights than the closer associated requirements. The priority of requirements will also affect the priority of subsequent test cases.

[0060] The target submodule will predict possible future demand hotspots based on the changing trends of each demand priority, and assist in grasping market trends. The prior art generally plans the direction of the software directly based on the number of demands submitted by users. This application overcomes inertial thinking and makes predictions based on the changing trends of demand priorities. Even if the total number of some demands is still small, if the priority weight increases a lot within a certain period of time, even if the number is not large enough, it can be mined and discovered. For example, the urgent needs of some minority groups can be discovered, so that the planning submodule can make subsequent plans in a forward-looking manner. And because of the combination of sentiment analysis, different weights can be given to consumer feedback, so that the priority analysis of demands is not limited to the number of demands.

[0061] Embodiment 4 The technical feature that distinguishes this embodiment from the above-mentioned embodiment is that the requirement management module is also used to perform a detailed analysis on each requirement and identify its pre-requisites (i.e., other requirements that must be met before the requirement is met). If the pre-requisite is not met, the module continues to trace upward until a pre-requisite that has been met is found or the requirement is determined to be the top-level requirement. The hierarchical relationship between each requirement and its pre-requisite is recorded to form a requirement hierarchy diagram.

[0062] According to the requirements hierarchy diagram, calculate the hierarchical depth of each requirement to the top-level requirement (or the implemented predecessor requirement). The hierarchical depth reflects the position of the requirement in the requirements chain and the number of prerequisites that need to be met to implement the requirement.

[0063] Use software usage data, user behavior logs, etc. to count the usage frequency of each implemented prerequisite requirement. The usage frequency reflects the activity and importance of the requirement in actual use.

[0064] The usage importance score of the current requirement is calculated based on the usage frequency of the previous implemented requirements and their hierarchical relationship with the current requirement. The usage frequency of the previous requirements is weighted and summed according to the hierarchical depth.

[0065] Conduct a technical assessment of each requirement, including required technical resources, development time, potential risks, etc., and assign a difficulty level (e.g., low, medium, high) to each requirement based on the assessment results. Convert the difficulty level to a specific score (e.g., low = 1, medium = 3, high = 5). Adjust the difficulty score appropriately based on the depth of the hierarchy to reflect the cumulative difficulty in the requirement chain.

[0066] A composite score is calculated for each requirement using a combination of importance and difficulty. The composite score is obtained by weighted summation, where the weights can be adjusted based on factors such as organizational strategy and resource status.

[0067] Requirements are sorted according to the comprehensive scores. Requirements with higher scores have higher priority. The sorting results should be updated regularly to reflect changes in requirements, technological advances, and changes in resource allocation.

[0068] The above method can be used to obtain more objective urgency and importance, which will not be affected by the frequency of user feedback. This can prevent some niche demands from being mistakenly considered as important demands due to the high frequency of user feedback.

[0069] The disclosed embodiment also provides a software quality integrated management method, which utilizes the above-mentioned software quality integrated management system.

[0070] Those of ordinary skill in the art can understand that all or part of the processes in the software quality integrated management method can be implemented by instructing related hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of various embodiments of the software quality integrated management method. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0071] The embodiment of the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned software quality integrated management method when executing the program. In the embodiment of the present application, the processor is the control center of the computer system, which can be the processor of a physical machine or the processor of a virtual machine.

[0072] Reference Figure 2 , the electronic device 500 includes: at least one processor 501, at least one communication interface 502, at least one memory 503 and at least one bus 504. The bus 504 is used to realize the connection and communication between these components, the communication interface 502 is used to communicate signaling or data with other node devices, and the memory 503 stores machine-readable instructions executable by the processor 501. When the electronic device 500 is running, the processor 501 communicates with the memory 503 through the bus 504, and the machine-readable instructions are called by the processor 501 to execute the steps of the above-mentioned software quality integrated management method.

[0073] The above contents are only embodiments of the present invention. The common sense such as the known specific structures and characteristics in the scheme is not described in detail here. The ordinary technicians in the relevant field know all the common technical knowledge in the technical field to which the invention belongs before the application date or the priority date, can obtain all the existing technologies in the field, and have the ability to apply the conventional experimental means before that date. The ordinary technicians in the relevant field can improve and implement this scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for the ordinary technicians in the relevant field to implement this application. It should be pointed out that for the technicians in this field, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the protection scope of the present invention, which will not affect the effect of the implementation of the present invention and the practicality of the patent. The protection scope required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to explain the content of the claims.

Claims

1. A software quality integrated management system, characterized by: include: Requirements management module, used to determine requirements and develop test plans based on them; The data processing module is used to collect quality management data during the software development process and label the quality management data. The labels include defect type, priority, and repair status. The association module is used to establish the association between data; The execution record module is used to record the operations in the software development, testing, and repair processes and generate execution logs; The quality analysis module is used to build a quality assessment model that includes multiple quality elements and their weights; calculate the software quality score based on the actual quality data, and determine the software quality level based on the preset threshold; The test management module is used to generate and execute test cases according to requirements and obtain evaluation data; The quality assessment module is used to integrate and analyze the assessment data and conduct a comprehensive assessment of software quality.

2. The software quality integrated management system according to claim 1, characterized in that: The data processing module is used to use API interface or data crawler technology to achieve real-time acquisition and update of data, and use the rule engine to achieve automatic execution of custom rules and automatic labeling of tags.

3. The software quality integrated management system according to claim 1, characterized in that: The association module establishes associations between data through a graph database or a relational database, uses a graph algorithm to analyze and mine data associations, and provides a visual tracing interface to display the context and associated information of the problem.

4. The software quality integrated management system according to claim 1, characterized in that: The quality analysis module builds a quality assessment model based on industry standards and internal experience, and regularly updates and optimizes the model based on newly collected data and feedback.

5. The software quality integrated management system according to claim 1, characterized in that: The test management module uses the CI / CD pipeline to automatically execute test cases and collect data during the test process in real time; at the same time, it periodically performs statistical analysis on the test cases to obtain high-risk test cases for key testing.

6. The software quality integrated management system according to claim 1, characterized in that: The maintenance management module is connected to a variety of demand communication methods, including video conferencing, email, and online collaboration platforms; the demand management module is also used to automatically classify and prioritize requirements when formulating test plans.

7. The software quality integrated management system according to claim 1, characterized in that: The requirement management module uses natural language processing technology to identify and analyze the requirements mentioned in the communication, and trains a customized NER model based on existing annotated data, including examples of various functional points, performance indicators and compatibility requirements.

8. The software quality integrated management system according to claim 7, characterized in that: The requirement management module is also used to parse sentence structures, determine dependencies between words, and analyze the contextual relationships between functional requirements and performance indicators, as well as dependencies between requirements through dependency syntax.

9. A software quality integrated management system according to claim 1, 6 or 7, characterized in that: The demand management module is also used to construct or adopt an existing sentiment dictionary to perform sentiment polarity judgment and sentiment fine-grained analysis on user feedback. The user feedback is scored for sentiment intensity, and combined with the frequency of occurrence of the needs, the urgency and importance of the needs are comprehensively evaluated, and positive weights are generated to adjust the priority ranking of the needs. At the same time, different positive weights are given to related needs according to the degree of correlation between the dependencies between the needs.

10. A software quality integrated management method, characterized in that: A software quality integrated management system as described in claims 1-9 is used.

Images