Method and device for determining non-functional access check conclusion of banking business system
By automating configuration and real-time calculation of non-functional access check conclusions, the problem of low efficiency in manual push has been solved, achieving efficient and accurate conclusion determination, adapting to multi-version centralized production scenarios, and improving the efficiency of the production process of banking business systems.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA CONSTRUCTION BANK
- Filing Date
- 2025-12-16
- Publication Date
- 2026-05-19
AI Technical Summary
In banking systems, the push of non-functional access inspection results relies on manual operation, resulting in high labor costs, low efficiency, and issues such as omissions and delays, which affect the smooth progress of the production process.
By configuring non-functional access inspection activities and establishing an automatic linkage mechanism, the conclusions of non-functional access inspections are automatically calculated in real time, enabling automatic push and update of the conclusions, and adapting to multi-version centralized production scenarios.
This improved the efficiency and accuracy of determining non-functional access inspection conclusions, reduced human resource costs, and ensured the timely initiation of subsequent inspection activities.
Smart Images
Figure CN122064582A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of banking software testing technology, and particularly relates to a method and apparatus for determining the conclusion of non-functional access inspection of banking business systems. Background Technology
[0002] As the digital transformation of banking business deepens, the number of system deployment versions is increasing year by year. In centralized deployment scenarios, thousands of deployment versions need to be processed every day. The synchronization of non-functional access inspection results and the efficiency of subsequent process initiation have become key factors affecting the deployment progress.
[0003] Currently, the push notification of non-functional access inspection results relies on manual operation: in scenarios with a single or small number of production versions, staff need to manually trigger the push command, and subsequent inspection activities can only begin after the backend platform receives and returns a successful response. However, in scenarios with a large number of concentrated production deployments, the drawbacks of this approach become increasingly prominent: on the one hand, manual push notifications require a significant amount of temporary manpower, and the operation process is cumbersome and time-consuming, making it difficult to complete the push notification of results for a massive number of versions in a short period of time, severely restricting overall production efficiency; on the other hand, over-reliance on manual operation not only leads to high labor costs, but may also result in problems such as push notification omissions and delays due to human negligence, failing to guarantee the timely initiation of subsequent inspection activities after the non-functional access inspection results are passed, thus affecting the smooth progress of the production process. Summary of the Invention
[0004] This invention provides a method for determining the conclusion of non-functional access checks for banking systems. Through sub-activity configuration and check result judgment, it automates the determination of non-functional access conclusions, adapts to multi-version centralized deployment scenarios, improves the efficiency and accuracy of conclusion determination, and provides technical support for improving the quality and efficiency of the deployment process. The method for determining the conclusion of non-functional access checks for banking systems includes:
[0005] Obtain the following information for non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check; the sub-activity status includes enabled status and disabled status.
[0006] Repeat the following steps until all non-functional access check sub-activities are disabled:
[0007] Based on the sub-activity status of the non-functional access check, each sub-activity is executed based on the sub-activity information to obtain the non-functional access check results; the non-functional access check results include the non-functional test evaluation form check results, the non-functional test plan case check results, the non-functional test report check results, and the non-functional test transaction code consistency check results.
[0008] Based on the results of the non-functional access inspection, a non-functional access inspection conclusion is determined; the non-functional access inspection conclusion includes admission and non-admission.
[0009] The non-functional access check results are detected. When the non-functional access check result of any enabled sub-activity is updated, the corresponding sub-activity information is retrieved again.
[0010] This invention provides a device for determining the conclusion of non-functional access checks in a banking system. Through sub-activity configuration and check result judgment, it automates the determination of non-functional access conclusions, adapts to multi-version centralized deployment scenarios, improves the efficiency and accuracy of conclusion determination, and provides technical support for improving the quality and efficiency of the deployment process. The device for determining the conclusion of non-functional access checks in a banking system includes:
[0011] The information acquisition module is used to acquire the following information and status of non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check; the sub-activity status includes enabled status and disabled status.
[0012] The repeat trigger module is used to repeatedly trigger the execution of the following modules until all non-functional admission check sub-activities are disabled:
[0013] The inspection execution module is used to execute each sub-activity based on the sub-activity information according to the sub-activity status of the non-functional access inspection, and obtain the non-functional access inspection results; the non-functional access inspection results include the non-functional test evaluation form inspection results, the non-functional test plan case inspection results, the non-functional test report inspection results, and the non-functional test transaction code consistency inspection results.
[0014] The inspection conclusion determination module is used to determine the non-functional access inspection conclusion based on the non-functional access inspection results; the non-functional access inspection conclusion includes access and non-access.
[0015] The inspection result detection module is used to detect non-functional access inspection results. When the non-functional access inspection result of any enabled sub-activity is updated, the corresponding sub-activity information is re-acquired.
[0016] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method for determining the non-functional access inspection conclusion of the aforementioned banking business system.
[0017] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method for determining the non-functional access control conclusion of the banking system described above.
[0018] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the method for determining the non-functional access control conclusion of the banking business system.
[0019] In this embodiment of the invention, the following are obtained for non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form checks, non-functional test plan case checks, non-functional test report checks, and non-functional test transaction code consistency checks; the sub-activity status includes enabled and disabled states; the following steps are repeated until all non-functional access check sub-activity statuses are disabled: based on the non-functional access check sub-activity statuses, each sub-activity is executed based on the sub-activity information to obtain the non-functional access check results; the non-functional access check results include non-functional test evaluation form check results and non-functional test plans. The system includes case inspection results, non-functional test report inspection results, and non-functional test transaction code consistency inspection results. Based on the non-functional access inspection results, a non-functional access inspection conclusion is determined. The non-functional access inspection conclusion includes admission and non-admission. The system detects non-functional access inspection results, and when the non-functional access inspection result of any enabled sub-activity is updated, the corresponding sub-activity information is re-acquired. This embodiment of the invention achieves automated determination of non-functional access conclusions through sub-activity configuration and inspection result judgment, adapts to multi-version centralized production scenarios, improves the efficiency and accuracy of conclusion judgment, and provides technical support for improving the quality and efficiency of the production process. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:
[0021] Figure 1 This is a flowchart illustrating the method for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention.
[0022] Figure 2 This is a specific example diagram illustrating the non-functional access check results obtained in an embodiment of the present invention;
[0023] Figure 3This is a specific example diagram illustrating the determination of a non-functional access check conclusion in an embodiment of the present invention;
[0024] Figure 4 This is a specific example diagram illustrating the determination of a non-functional access check conclusion in an embodiment of the present invention;
[0025] Figure 5 This is a structural example diagram of the device for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention;
[0026] Figure 6 This is a specific example diagram of the structure of the device for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention;
[0027] Figure 7 This is a specific example diagram of the structure of the device for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention;
[0028] Figure 8 This is a structural diagram of a computer device in an embodiment of the present invention. Detailed Implementation
[0029] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.
[0030] The acquisition, transmission, storage, use, and processing of data in the technical solution of this invention all comply with relevant regulations.
[0031] It should be noted that in the embodiments of the present invention, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of the present invention. However, they do not mean that the applicant has used or necessarily used the solution.
[0032] First, the technical terms appearing in the embodiments of this invention will be explained;
[0033] Non-functional access checks: Non-functional access checks are a key quality audit step before the banking business system is put into production and goes live. The core of this step is to verify the system's compliance with non-business functional aspects such as performance, security, and availability through configurable sub-activities such as non-functional test evaluation form review, non-functional test plan case review, non-functional test report review, and transaction code consistency check. This ensures the stable operation of the system after it goes live and avoids potential risks.
[0034] As mentioned earlier, in the existing technology, the push of non-functional access inspection conclusions relies on manual operation. Staff members need to manually click to push the conclusions to the backend platform after each inspection activity is completed, and the access inspection conclusions cannot be automatically updated after the results of a single inspection activity are updated.
[0035] As the number of production versions increases year by year, thousands of conclusions need to be pushed out every day. The manual method not only requires a lot of human resources and has high labor costs, but also has extremely low efficiency and long time consumption. There is a time lag between the conclusion push and the subsequent inspection activities, which cannot guarantee the timely start of the subsequent inspection activities.
[0036] To address this issue, the inventors discovered that by configuring non-functional access inspection activities and establishing an automatic linkage mechanism, they proposed a device for automatically pushing non-functional access inspection conclusions. When the results of sub-activities such as non-functional test evaluation form inspection, non-functional test plan case inspection, non-functional test report inspection, and transaction code consistency inspection change, the non-functional access inspection conclusion is automatically calculated in real time. When the conclusion is passed, it is automatically pushed in real time without manual intervention, thereby achieving efficient and accurate conclusion pushing and ensuring that subsequent inspection activities are carried out in a timely manner.
[0037] Figure 1 This is a flowchart illustrating the method for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention, as shown below. Figure 1 As shown, the method for determining the conclusion of the non-functional access inspection of the banking business system includes:
[0038] Step 101: Obtain the sub-activity information and sub-activity status for non-functional access checks; the sub-activity information includes non-functional test evaluation form checks, non-functional test plan case checks, non-functional test report checks, and non-functional test transaction code consistency checks; the sub-activity status includes enabled status and disabled status.
[0039] Repeat the following steps until all non-functional access check sub-activities are disabled:
[0040] Step 102: Based on the sub-activity status of the non-functional access check, execute each sub-activity based on the sub-activity information to obtain the non-functional access check results; the non-functional access check results include the non-functional test evaluation form check results, the non-functional test plan case check results, the non-functional test report check results, and the non-functional test transaction code consistency check results.
[0041] Step 103: Determine the non-functional access inspection conclusion based on the non-functional access inspection results; the non-functional access inspection conclusion includes access and non-access.
[0042] Step 104: Detect the non-functional access check results. When the non-functional access check results of any enabled sub-activity are updated, re-acquire the corresponding sub-activity information.
[0043] As shown in Figure 1, in this embodiment of the invention, the method for determining the non-functional access inspection conclusion of the banking business system includes: obtaining sub-activity information and sub-activity status of the non-functional access inspection, wherein the sub-activity information includes non-functional test evaluation form inspection, non-functional test scheme case inspection, non-functional test report inspection, and non-functional test transaction code consistency inspection, and the sub-activity status includes enabled status and disabled status; repeating the following steps until all non-functional access inspection sub-activity statuses are disabled: executing each sub-activity based on the sub-activity information according to the sub-activity status to obtain non-functional access inspection results including non-functional test evaluation form inspection results, non-functional test scheme case inspection results, non-functional test report inspection results, and non-functional test transaction code consistency inspection results; determining non-functional access inspection conclusions including approved and disapproved based on the non-functional access inspection results; detecting the non-functional access inspection results, and when the inspection result of any enabled sub-activity is updated, re-acquiring the corresponding sub-activity information and repeating the above steps.
[0044] Compared with existing technologies that rely on manual push of non-functional access inspection conclusions, this technology allows for the configuration of non-functional access inspection sub-activities that can be flexibly enabled and disabled. It automatically calculates inspection conclusions based on the execution results of each sub-activity and dynamically refreshes the conclusions by detecting and updating the results of enabled sub-activities in real time. This enables automatic push of conclusions when they are passed, which can significantly save human resource costs and improve the efficiency of determining and pushing non-functional access inspection conclusions. This solves the problems of low efficiency, long time consumption, and time lag in manual push in scenarios with a large number of production versions, and ensures that subsequent inspection activities are launched in a timely manner.
[0045] In step 101, the following are obtained for non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check; the sub-activity status includes enabled status and disabled status.
[0046] In a specific embodiment, information on sub-activities including non-functional test evaluation form checks, non-functional test plan case checks, non-functional test report checks, and non-functional test transaction code consistency checks is obtained, along with sub-activity statuses such as enabled and disabled statuses, including:
[0047] Obtaining information about sub-activities:
[0048] Extract the preset core sub-activity information from the non-functional access inspection configuration system, and identify four types of mandatory sub-activities: non-functional test evaluation form inspection, non-functional test plan case inspection, non-functional test report inspection, and non-functional test transaction code consistency inspection. At the same time, it supports reading the extended sub-activity information newly added in the system, such as inspection activities with additional configurations.
[0049] Assign a unique identifier code and inspection content description to each type of sub-activity information. For example, the code corresponding to the non-functional test evaluation form inspection is "JCD-001", and the inspection content description is "whether the evaluation conclusions corresponding to version changes and infrastructure changes in the evaluation form are correct"; the code corresponding to the non-functional test transaction code consistency inspection is "JCD-004", and the inspection content description is "compare the transaction codes in the evaluation form and the operation and maintenance handover form to ensure consistency".
[0050] Obtaining the status of sub-activities:
[0051] Call the non-functional access check activity configuration interface to read the current status configuration of each sub-activity. The status value is only one of two types: enabled or disabled.
[0052] The "Enabled" status indicates that the sub-activity must participate in the calculation of the non-functional access check conclusion, and the check result must be "pass" to form an access conclusion; the "Disabled" status indicates that the sub-activity is not included in the conclusion calculation and does not need to be forced to pass.
[0053] Example status configuration results: Non-functional test evaluation form check (enabled), Non-functional test plan case check (enabled), Non-functional test report check (enabled), Non-functional test transaction code consistency check (enabled); If a certain type of sub-activity is not mandatory in the pilot phase, the status configuration is disabled, such as Non-functional test report check (disabled).
[0054] Information integration and verification:
[0055] The obtained sub-activity information and status are structured and integrated according to the structure of sub-activity identifier code - sub-activity name - inspection content description - status to form a sub-activity information status table.
[0056] Verify that all core sub-activity information is complete and that the status configuration is unique, ensuring that the information is complete and error-free, and then use this information as the basis for executing subsequent sub-activities.
[0057] In this embodiment, before executing each sub-activity based on the sub-activity information according to the sub-activity status of the non-functional access check to obtain the non-functional access check result, the following may also be included:
[0058] For each sub-activity whose status is enabled, retrieve the corresponding delivery data; this includes:
[0059] Non-functional test evaluation forms are checked against the corresponding delivered evaluation forms; non-functional test case studies are checked against the corresponding delivered test case studies; non-functional test reports are checked against the corresponding delivered test reports; and transaction code consistency checks are checked against the corresponding delivered consistency checklists.
[0060] In a specific embodiment, before executing each sub-activity to obtain the non-functional access check results, a process for obtaining corresponding delivery data is also included, including:
[0061] Filter enabled sub-activities: Iterate through the sub-activity information and status obtained in step 101, filter out all sub-activities with the status of enabled, and clarify the scope of sub-activities for which delivery data needs to be obtained, such as non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check.
[0062] Targeted acquisition of various delivery data:
[0063] For non-functional test evaluation form checks: Obtain the non-functional test evaluation form delivered for the corresponding production version through the production version data submission interface. This evaluation form must include version change content, such as transaction changes, batch processing changes, database changes, infrastructure changes, and evaluation conclusions, such as whether non-functional testing is required.
[0064] For non-functional test plan case checks: retrieve the non-functional test plan cases delivered for the corresponding production version from the test plan management system to ensure that the plan includes complete content such as test purpose, test scope, test scenario, test environment, test data and test cases.
[0065] For non-functional test report inspection: Obtain the non-functional test report for the corresponding production version through the test report submission channel. The report must cover key information such as test results, test case execution steps, execution results, and whether they meet expectations.
[0066] For non-functional test transaction code consistency checks: Obtain the delivered evaluation form, which contains the transaction codes, and the operation and maintenance handover form, which contains the delivered transaction codes, from the non-functional test evaluation form and the operation and maintenance handover system respectively, forming the delivery data combination corresponding to the transaction code consistency check.
[0067] Delivery data verification: Check whether all types of delivery data are complete and match the current production version to ensure there are no missing or mismatched data issues.
[0068] If the delivery data for a certain type of enabled sub-activity is missing or mismatched, it will be marked as data to be supplemented and the relevant submitter will be notified to supplement and improve it. After the data is supplemented, the sub-activity will proceed to the execution stage.
[0069] Figure 2This is a specific example diagram illustrating the non-functional access check results obtained in an embodiment of the present invention, such as... Figure 2 As shown, based on the sub-activity status of the non-functional access check, each sub-activity is executed based on the sub-activity information to obtain the non-functional access check results, which may include:
[0070] Based on the delivery data, checks are performed on each sub-activity whose status is enabled, resulting in non-functional access check results, including:
[0071] Step 201: For non-functional test evaluation forms, check the delivered evaluation forms to determine whether non-functional testing is required.
[0072] Step 202: For non-functional test case review, examine the delivered test case to determine whether the test case covers the test requirements.
[0073] Step 203: For non-functional test report review, examine the delivered test report to determine whether the test results meet expectations;
[0074] Step 204: For non-functional test transaction code consistency check, check the delivered consistency check sheet to determine whether the non-functional test transaction codes are consistent.
[0075] In a specific embodiment, checks are performed on each enabled sub-activity based on the delivery data to obtain non-functional access check results, including:
[0076] Non-functional test evaluation form checklist:
[0077] Retrieve the delivered non-functional test evaluation forms and focus on verifying the version changes recorded in the evaluation forms, such as transaction changes, batch processing changes, database changes, infrastructure changes, and basic software changes, and their consistency with the evaluation conclusions.
[0078] If the assessment clearly states that the version has no changes affecting non-functional performance, and the assessment conclusion is "no non-functional testing required", then the inspection result is "passed". If the version has non-functional related changes but the assessment conclusion is "no non-functional testing required", or if there is no clear explanation of the changes but it is determined that "non-functional testing is required", then the inspection result is "failed", and the reason for failure is noted, such as "the version contains database changes, and the assessment conclusion does not match the requirement for non-functional testing".
[0079] Non-functional test plan case review:
[0080] Review the delivered non-functional test plan cases and verify the core contents one by one: whether the test purpose is consistent with the version change requirements in the evaluation form, whether the test scope fully covers the business scenarios involved in the change, whether the test scenario design fits the actual production application scenario, whether the test environment configuration meets the technical requirements of non-functional testing, whether the test data is representative and complete, and whether the test cases fully cover the test requirements.
[0081] If all of the above meet the preset standards and the test cases do not omit any key test points, the inspection result is judged as "passed"; if there are problems such as missing test scope, test scenarios that do not match reality, or test cases that do not cover core requirements, the inspection result is judged as "failed", and the specific problem items are clearly marked, such as "the test scenario does not cover the concurrent scenario after the batch processing changes".
[0082] Non-functional test report review:
[0083] Verify the delivered non-functional test reports, focusing on whether the test results meet the preset non-functional indicator requirements, such as response time, concurrency, stability duration, etc., whether the test case execution steps are complete and standardized, whether the execution results are consistent with the expected conclusions, and whether the report provides reasonable analysis and explanation for any abnormal situations.
[0084] If the test results meet the indicator requirements, the execution steps are standardized, and the execution results are consistent with expectations, the inspection result is judged as "passed"; if the test results fail to meet the standards, key steps are missing, or the execution results contradict expectations without a reasonable explanation, the inspection result is judged as "failed", and the problem type is marked, such as "response time in high-concurrency scenarios does not meet the preset standard".
[0085] Non-functional test transaction code consistency check:
[0086] Extract the transaction codes recorded in the evaluation form from the delivery data, such as the account balance query transaction code and the account information maintenance transaction code, and perform a full comparison with the transaction codes delivered in the operation and maintenance handover form. Verify that the name, code, and function description of the transaction codes are completely consistent to ensure that there are no omissions, mismatches, or newly added unregistered transaction codes.
[0087] If the transaction codes in the two types of documents match perfectly and there are no discrepancies, the inspection result is "passed". If there are missing transaction codes, inconsistent coding, or mismatched function descriptions, the inspection result is "failed". The specific information of the discrepancies in the transaction codes will be listed, such as "the function description of the assessment order transaction code A001 is inconsistent with that of the maintenance handover order transaction code A002".
[0088] Summary of inspection results: The inspection results of the above four categories of sub-activities are summarized according to the type of sub-activity to form a complete non-functional access inspection result, which provides a basis for the subsequent access conclusion.
[0089] Figure 3 This is a specific example diagram illustrating the determination of a non-functional access check conclusion in an embodiment of the present invention, such as... Figure 3 As shown, the conclusions of the non-functional access inspection, based on the results of the non-functional access inspection, may include:
[0090] Step 301: Traverse the non-functional access check results of all enabled sub-activities;
[0091] Step 302: If all non-functional access checks of enabled sub-activities pass, the non-functional access check conclusion is determined to be access.
[0092] Figure 4 This is a specific example diagram illustrating the determination of a non-functional access check conclusion in an embodiment of the present invention, such as... Figure 4 As shown, the conclusions of the non-functional access inspection, based on the results of the non-functional access inspection, may include:
[0093] Step 401: Traverse the non-functional access check results of all enabled sub-activities;
[0094] Step 402: If any enabled sub-activity fails the non-functional access check, the non-functional access check conclusion is deemed as disallowed.
[0095] In a specific embodiment, the non-functional access inspection conclusion is determined based on the non-functional access inspection results, including the access conclusion determination corresponding to Figure 3 and the non-access conclusion determination corresponding to Figure 4, as detailed below:
[0096] I. Determining the non-functional access inspection conclusion as access.
[0097] Traverse the results of enabled sub-activities: retrieve the list of all enabled sub-activities, such as non-functional test evaluation form checks, non-functional test plan case checks, non-functional test report checks, and non-functional test transaction code consistency checks, and verify the non-functional access check results for each sub-activity one by one to ensure that no enabled sub-activities are missed.
[0098] Admission Decision Determination: If, after traversal, all enabled sub-activities pass the inspection with no failed items, the non-functional admission decision is directly determined as admission. Simultaneously, structured conclusion information is generated, including conclusion type (admission), conclusion number, corresponding production version number, a summary of all enabled sub-activities' inspection results, and conclusion generation time, providing complete data for subsequent automatic push notifications.
[0099] II. Determining the non-functional access inspection conclusion as non-access.
[0100] Traverse the enabled sub-activities and check their results: Following the same logic as step 301, traverse all enabled sub-activities and their corresponding non-functional access check results, and check one by one whether there are any failed check results.
[0101] Access Denial Decision: If any enabled sub-activity fails the check during the traversal, the non-functional access check decision is immediately set as "access denied." Simultaneously, key information about the failed sub-activities is automatically compiled, including the sub-activity name, specific reason for failure, and corresponding delivery data anomalies, forming a clear list of reasons for failure. This list is then synchronously linked to the conclusion information, facilitating quick problem identification and correction by relevant personnel.
[0102] Unified storage of conclusions: The final conclusions of admission or disapproval, along with related information, are stored in a non-functional admission inspection conclusion database in a preset format to ensure that the conclusions are traceable and searchable, while also providing data support for subsequent conclusion pushes or problem rectification.
[0103] In this embodiment, after determining the conclusion of the non-functional access check based on the non-functional access check results, it may further include:
[0104] Perform data consistency verification on the non-functional access inspection conclusions. If the verification is successful, store the non-functional access inspection conclusions in the banking business system database.
[0105] In a specific embodiment, after determining the conclusion of the non-functional access check, a data consistency check is performed and the data is stored in the banking business system database, including:
[0106] Data consistency verification content:
[0107] Verification of Conclusion-Related Information: Check whether the production version number, conclusion number, and generation time corresponding to the non-functional access inspection conclusion are complete and formatted correctly, and ensure that they are consistent with the version information in the summary of sub-activity inspection results.
[0108] Conclusion consistency check: If the conclusion is admission, check whether the check results of all enabled sub-activities are all passed and there are no contradictions; if the conclusion is disadvantage, check whether the list of failed sub-activities is consistent with the description of the corresponding check results to ensure that the conclusion and check results are logically closed.
[0109] Data integrity verification: Check whether the conclusion information includes core fields, such as conclusion type, production version, conclusion generation time, summary of sub-activity check results, and list of reasons for failure, and whether there is any missing key information.
[0110] Verification result processing:
[0111] If the verification passes, meaning the associated information is consistent, the logic is consistent, and the core fields are complete, then it proceeds to the database storage stage.
[0112] If the verification fails, for example, due to version number mismatch, failure of sub-activities corresponding to the admission conclusion, or missing core fields, the exception type is automatically marked and a retry mechanism is triggered. The sub-activity check results and conclusion data are retrieved again for verification and correction. After correction, the verification is performed again until the verification passes.
[0113] Database storage: Successfully verified non-functional access inspection conclusions are structured and stored in designated data tables according to the preset storage format of the banking business system database. The stored content includes information such as conclusion number, production version number, conclusion type, conclusion generation time, list of activated sub-activities and inspection results, list of reasons for failure, and verification pass time. At the same time, an index is established to associate the conclusion number with the production version number to facilitate data retrieval during subsequent queries, tracing, and automatic push.
[0114] In step 104, the non-functional access check result is detected. When the non-functional access check result of any enabled sub-activity is updated, the corresponding sub-activity information is re-acquired.
[0115] In a specific embodiment, detecting the non-functional access check result and re-acquiring the corresponding sub-activity information when the enabled state sub-activity result is updated includes:
[0116] Real-time monitoring of inspection results: Activate the dynamic monitoring mechanism for non-functional access inspection results to monitor the inspection result status of all sub-activities that are enabled in real time. The monitoring dimensions include whether the result has changed, such as from failing to passing, or whether the description of the issue associated with the result has been updated.
[0117] Update trigger judgment: If the non-functional access check result of any enabled sub-activity is detected to change, for example, if the original result of the non-functional test evaluation check was failed, but after the problem was corrected, the result was updated to pass after re-checking; or if a new difference item is added to the transaction code consistency check, causing the result to change from pass to fail, then the corresponding sub-activity information re-acquisition process is triggered.
[0118] Retrieve corresponding sub-activity information: Based on the updated sub-activity type, retrieve the complete information of the sub-activity again, including:
[0119] Sub-activity basic information: Sub-activity name, unique identifier code, description of inspection content, current enabled / disabled status;
[0120] Related delivery data: Delivery data updated for the corresponding sub-activity;
[0121] Latest inspection results: Updated pass / fail conclusions for this sub-activity and explanations of the latest issues.
[0122] Information Synchronization and Process Restart: The newly acquired sub-activity information and the latest inspection results are synchronized to the non-functional access inspection system, overwriting the original historical data, and the process of steps 102-103 is restarted. The inspection is performed based on the updated sub-activity information, and the non-functional access inspection conclusion is re-determined to ensure that the conclusion can reflect the latest status of the sub-activity inspection results in real time, and to ensure the accuracy and timeliness of the conclusion.
[0123] The method for determining the non-functional access control conclusion of the banking system according to the embodiments of the present invention has been verified to have the following beneficial effects:
[0124] 1. Automatically updated conclusions ensure real-time performance: When the inspection results of any enabled sub-activity such as non-functional test evaluation form inspection or non-functional test plan case inspection change, the non-functional access inspection conclusion can be automatically recalculated in real time without manual intervention. This solves the problem of the inability to automatically update conclusions after the completion of inspection activities in the prior art, ensuring that the conclusions always reflect the latest inspection status.
[0125] 2. Flexible configuration of inspection activities to adapt to diverse needs: Supports enabling and disabling non-functional access inspection sub-activities. Inspection activities can be flexibly added or reduced according to business scenarios without modifying the core logic. It adapts to diverse needs such as pilot promotion and business adjustments, improving the applicability and scalability of the method.
[0126] This invention also provides a device for determining the conclusion of a non-functional access inspection of a banking system, as described in the following embodiments. Since the principle by which this device solves the problem is similar to the method for determining the conclusion of a non-functional access inspection of a banking system, the implementation of this device can refer to the implementation of the method for determining the conclusion of a non-functional access inspection of a banking system; repeated details will not be elaborated further.
[0127] Figure 5 This is a structural example diagram of the device for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention, as shown below. Figure 5 As shown, the device for determining the conclusion of the non-functional access inspection of the banking business system includes:
[0128] The information acquisition module 501 is used to acquire the following information for non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check; the sub-activity status includes enabled status and disabled status.
[0129] The repeat trigger module 502 is used to repeatedly trigger the execution of the following modules until all non-functional access check sub-activities are disabled:
[0130] The inspection execution module 503 is used to execute each sub-activity based on the sub-activity information according to the sub-activity status of the non-functional access inspection, and obtain the non-functional access inspection results; the non-functional access inspection results include the non-functional test evaluation form inspection results, the non-functional test plan case inspection results, the non-functional test report inspection results, and the non-functional test transaction code consistency inspection results.
[0131] The inspection conclusion determination module 504 is used to determine the non-functional access inspection conclusion based on the non-functional access inspection results; the non-functional access inspection conclusion includes access and non-access.
[0132] The inspection result detection module 505 is used to detect the non-functional access inspection results. When the non-functional access inspection result of any enabled sub-activity is updated, the corresponding sub-activity information is re-acquired.
[0133] Figure 6 This is a specific example diagram of the structure of the device for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention, as shown below. Figure 6 As shown in one embodiment, Figure 5 The device for determining the non-functional access control conclusion of the banking system in the embodiment of the present invention may further include: a delivery data determination module 601.
[0134] In one embodiment, the delivery data determination module 601 is specifically used for:
[0135] Before executing each sub-activity based on the sub-activity information according to the sub-activity status of the non-functional access check and obtaining the non-functional access check results, for each sub-activity whose status is enabled, the corresponding delivery data is obtained; including:
[0136] Non-functional test evaluation forms are checked against the corresponding delivered evaluation forms; non-functional test case studies are checked against the corresponding delivered test case studies; non-functional test reports are checked against the corresponding delivered test reports; and transaction code consistency checks are checked against the corresponding delivered consistency checklists.
[0137] In one embodiment, the inspection execution module 503 is specifically used for:
[0138] Based on the delivery data, checks are performed on each sub-activity whose status is enabled, resulting in non-functional access check results, including:
[0139] For non-functional test evaluation forms, examine the delivered evaluation forms to determine whether non-functional testing is required.
[0140] For non-functional test case review, examine the delivered test case to determine whether the test case covers the test requirements;
[0141] For non-functional test report review, examine the delivered test reports to determine whether the test results meet expectations;
[0142] For non-functional test transaction code consistency checks, examine the delivered consistency checklist to determine whether the non-functional test transaction codes are consistent.
[0143] In one embodiment, the inspection conclusion determination module 504 is specifically used for:
[0144] Iterate through the non-functional admission check results of all enabled sub-activities;
[0145] If all non-functional access checks for enabled sub-activities pass, then the non-functional access check conclusion is deemed as access.
[0146] In one embodiment, the inspection conclusion determination module 504 is specifically used for:
[0147] Iterate through the non-functional admission check results of all enabled sub-activities;
[0148] If any enabled sub-activity fails the non-functional access check, the non-functional access check conclusion is deemed as disallowance.
[0149] Figure 7 This is a specific example diagram of the structure of the device for determining the non-functional access control conclusion of a banking system in an embodiment of the present invention, as shown below. Figure 7 As shown in one embodiment, Figure 5 The device for determining the non-functional access control conclusion of the banking system in the embodiment of the present invention may further include: a data verification module 701.
[0150] In one embodiment, the data verification module 701 is specifically used for:
[0151] After determining the conclusion of the non-functional access inspection based on the results of the non-functional access inspection, a data consistency verification is performed on the conclusion of the non-functional access inspection. If the verification is successful, the conclusion of the non-functional access inspection is stored in the banking business system database.
[0152] Based on the aforementioned inventive concept, such as Figure 8 As shown, the present invention also proposes a computer device 800, including a memory 810, a processor 820, and a computer program 830 stored in the memory 810 and executable on the processor 820. When the processor 820 executes the computer program 830, it implements the method for determining the non-functional access inspection conclusion of the aforementioned banking business system.
[0153] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method for determining the non-functional access control conclusion of the banking system described above.
[0154] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the method for determining the non-functional access control conclusion of the banking business system.
[0155] In this embodiment of the invention, the following are obtained for non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form checks, non-functional test plan case checks, non-functional test report checks, and non-functional test transaction code consistency checks; the sub-activity status includes enabled and disabled states; the following steps are repeated until all non-functional access check sub-activity statuses are disabled: based on the non-functional access check sub-activity statuses, each sub-activity is executed based on the sub-activity information to obtain the non-functional access check results; the non-functional access check results include non-functional test evaluation form check results and non-functional test plans. The system includes case inspection results, non-functional test report inspection results, and non-functional test transaction code consistency inspection results. Based on the non-functional access inspection results, a non-functional access inspection conclusion is determined. The non-functional access inspection conclusion includes admission and non-admission. The system detects non-functional access inspection results, and when the non-functional access inspection result of any enabled sub-activity is updated, the corresponding sub-activity information is re-acquired. This embodiment of the invention achieves automated determination of non-functional access conclusions through sub-activity configuration and inspection result judgment, adapts to multi-version centralized production scenarios, improves the efficiency and accuracy of conclusion judgment, and provides technical support for improving the quality and efficiency of the production process.
[0156] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0157] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0158] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0159] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0160] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for determining the conclusion of a non-functional access inspection of a banking business system, characterized in that, include: Obtain the following information for non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check; the sub-activity status includes enabled status and disabled status. Repeat the following steps until all non-functional access check sub-activities are disabled: Based on the sub-activity status of the non-functional access check, each sub-activity is executed based on the sub-activity information to obtain the non-functional access check results; the non-functional access check results include the non-functional test evaluation form check results, the non-functional test plan case check results, the non-functional test report check results, and the non-functional test transaction code consistency check results. Based on the results of the non-functional access inspection, a non-functional access inspection conclusion is determined; the non-functional access inspection conclusion includes admission and non-admission. The non-functional access check results are detected. When the non-functional access check result of any enabled sub-activity is updated, the corresponding sub-activity information is retrieved again.
2. The method as described in claim 1, characterized in that, Before executing each sub-activity based on the sub-activity information according to the sub-activity status of the non-functional access check and obtaining the non-functional access check result, the process also includes: For each sub-activity whose status is enabled, retrieve the corresponding delivery data; this includes: Non-functional test evaluation forms are checked against the corresponding delivered evaluation forms; non-functional test case studies are checked against the corresponding delivered test case studies; non-functional test reports are checked against the corresponding delivered test reports; and transaction code consistency checks are checked against the corresponding delivered consistency checklists.
3. The method as described in any one of claims 1-2, characterized in that, Based on the sub-activity status of the non-functional access check, each sub-activity is executed based on the sub-activity information to obtain the non-functional access check results, including: Based on the delivery data, checks are performed on each sub-activity whose status is enabled, resulting in non-functional access check results, including: For non-functional test evaluation forms, examine the delivered evaluation forms to determine whether non-functional testing is required. For non-functional test case review, examine the delivered test case to determine whether the test case covers the test requirements; For non-functional test report review, examine the delivered test reports to determine whether the test results meet expectations; For non-functional test transaction code consistency checks, examine the delivered consistency checklist to determine whether the non-functional test transaction codes are consistent.
4. The method as described in claim 1, characterized in that, Based on the results of the non-functional access inspection, the conclusions of the non-functional access inspection are determined, including: Iterate through the non-functional admission check results of all enabled sub-activities; If all non-functional access checks for enabled sub-activities pass, then the non-functional access check conclusion is deemed as access.
5. The method as described in claim 1, characterized in that, Based on the results of the non-functional access inspection, the conclusions of the non-functional access inspection are determined, including: Iterate through the non-functional admission check results of all enabled sub-activities; If any enabled sub-activity fails the non-functional access check, the non-functional access check conclusion is deemed as disallowance.
6. The method as described in claim 1, characterized in that, After determining the conclusion of the non-functional access inspection based on the results of the non-functional access inspection, it also includes: Perform data consistency verification on the non-functional access inspection conclusions. If the verification is successful, store the non-functional access inspection conclusions in the banking business system database.
7. A device for determining the conclusion of a non-functional access inspection of a banking business system, characterized in that, include: The information acquisition module is used to acquire the following information and status of non-functional access checks: sub-activity information and sub-activity status; the sub-activity information includes non-functional test evaluation form check, non-functional test plan case check, non-functional test report check, and non-functional test transaction code consistency check; the sub-activity status includes enabled status and disabled status. The repeat trigger module is used to repeatedly trigger the execution of the following modules until all non-functional admission check sub-activities are disabled: The inspection execution module is used to execute each sub-activity based on the sub-activity information according to the sub-activity status of the non-functional access inspection, and obtain the non-functional access inspection results; the non-functional access inspection results include the non-functional test evaluation form inspection results, the non-functional test plan case inspection results, the non-functional test report inspection results, and the non-functional test transaction code consistency inspection results. The inspection conclusion determination module is used to determine the non-functional access inspection conclusion based on the non-functional access inspection results; the non-functional access inspection conclusion includes access and non-access. The inspection result detection module is used to detect non-functional access inspection results. When the non-functional access inspection result of any enabled sub-activity is updated, the corresponding sub-activity information is re-acquired.
8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1-6.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-6.
10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1-6.