Function must measure business scope preservation method and system, electronic equipment, storage medium

Abstract

The application provides a function must measure business range preservation method and system, electronic equipment and a storage medium, and the method comprises the following steps: acquiring important business activities, business modeling assets and demand management assets; updating a business range baseline according to the important business activities, the business modeling assets and the demand management assets; performing statistical analysis on the business range baseline, updating a test range and a case; the business range baseline is used as a basis for the test range and the case analysis, and the coverage of the test range on the business range is analyzed through statistical analysis; the baseline of the business range is formed, so that the business range can be updated and maintained; statistical analysis is supported, the business range is used as a basis for the test range and the case analysis, and the coverage of the test range on the business range is analyzed through statistical analysis; the business range is updated, the timeliness, correctness and coverage of the compared business range are improved, and the latest basis is provided for the analysis and update of the subsequent test range and test case.

Description

Technical Field

[0001] This invention belongs to the field of system parameter update technology, and more specifically, it relates to a method and system for preserving the scope of essential functional tests, electronic devices, and storage media. Background Technology

[0002] To ensure the safe and stable operation of the production system and to effectively implement the important directive regarding "ensuring sufficient testing and comprehensive verification," and to precisely and effectively improve the business risk coverage of mandatory test cases, testers regularly conduct re-examinations of mandatory functional regression test cases, establishing a routine working mechanism to ensure the quality of functional regression testing and guarantee the normal operation of important business processes. The current re-examination process uses important business activities with varying levels of business impact, business modeling assets, and requirements management assets as upstream criteria to determine the business scope and test cases for functional regression testing.

[0003] Currently, the system cannot keep the scope of business during the re-inspection process fresh. Once the business department / project team updates important business activities, business modeling assets, or requirements management assets, testers need to manually check them again, which consumes a lot of manpower and has a high error rate. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a method and system, electronic device and storage medium for keeping the functional mandatory test business scope fresh, so as to simplify the business scope baseline update, improve the timeliness, accuracy and coverage of the business scope after comparison, and provide the latest basis for the subsequent sorting and updating of test scope and test cases.

[0005] The first aspect of this application discloses a method for preserving the scope of functions requiring mandatory testing, including:

[0006] Acquire key business activities, business modeling assets, and requirements management assets;

[0007] Update the business scope baseline based on the aforementioned key business activities, the aforementioned business modeling assets, and the aforementioned demand management assets;

[0008] Statistical analysis is performed on the business scope baseline to update the test scope and cases; wherein, the business scope baseline serves as the basis for sorting out the test scope and its cases, and the coverage of the business scope by the test scope is determined through statistical analysis.

[0009] Optionally, in the above-mentioned method for keeping the scope of mandatory functional testing fresh, updating the scope baseline based on the important business activities, the business modeling assets, and the demand management assets includes:

[0010] Determine whether the aforementioned important business activities have changed;

[0011] If not, then compare the differences between business modeling assets and demand management assets;

[0012] If a business function / user workflow exists in the business scope baseline but does not exist in the business modeling asset and / or the requirement management asset, it is displayed as not existing, and the business function / user workflow is deleted to form a new business scope baseline.

[0013] If a business function / user workflow exists in the business scope baseline and in the business modeling asset and / or the requirement management asset; or if a business function / user workflow does not exist in the business scope baseline and does not exist in either the business modeling asset or the requirement management asset, it will be displayed as unchanged and remain at the current business scope baseline.

[0014] If a business function / user workflow does not exist in the business scope baseline but exists in the business modeling asset and / or requirement management asset, it will be displayed as a new function / user workflow, forming a new business scope baseline.

[0015] Optionally, in the above-mentioned method for keeping the scope of mandatory functional tests fresh, statistical analysis is performed on the baseline of the scope of tests to update the test scope and cases, including:

[0016] If it is displayed as not present, the project team will no longer be required to provide the corresponding test scope and cases;

[0017] If it is displayed as a new addition, the project team is required to provide the corresponding test scope and cases, and to cover the test scope and cases accordingly.

[0018] Optionally, in the above-mentioned method for maintaining the validity of mandatory business scope, deleting business functions / user workflows to form a new business scope baseline includes:

[0019] Remind the administrator to manually delete it;

[0020] And after confirming that the administrator has completed the manual deletion, update the business scope baseline.

[0021] Optionally, in the above-mentioned method for keeping the scope of mandatory functional testing fresh, before updating the scope baseline based on the important business activities, the business modeling assets, and the demand management assets, the method further includes:

[0022] Based on key business activities, business modeling assets, and demand management assets, determine the initial business scope baseline.

[0023] The second aspect of this application discloses a functionally required business scope preservation system, comprising:

[0024] The acquisition module is used to acquire important business activities, business modeling assets, and requirements management assets.

[0025] The update module is used to update the business scope baseline based on the important business activities, the business modeling assets, and the demand management assets;

[0026] The case module is used to perform statistical analysis on the business scope baseline and update the test scope and cases; wherein, the business scope baseline serves as the basis for sorting out the test scope and its cases, and statistical analysis is used to determine the coverage of the test scope on the business scope.

[0027] Optionally, in the aforementioned mandatory business scope preservation system, when the update module updates the business scope baseline based on important business activities, business modeling assets, and demand management assets, it is specifically used for:

[0028] Determine whether the aforementioned important business activities have changed;

[0029] If not, then compare the differences between business modeling assets and demand management assets;

[0030] If a business function / user workflow exists in the business scope baseline but does not exist in either the business modeling asset or the requirements management asset, it will be displayed as non-existent, and the business function / user workflow will be deleted to form a new business scope baseline.

[0031] If a business function / user workflow exists in the business scope baseline and in the business modeling asset and / or the requirements management asset; or if a business function / user workflow does not exist in the business scope baseline and does not exist in either the business modeling asset or the requirements management asset, it will be displayed as unchanged and will remain the current business scope baseline.

[0032] If a business function / user workflow does not exist in the business scope baseline but exists in the business modeling asset and / or requirement management asset, it will be displayed as a new function / user workflow, forming a new business scope baseline.

[0033] Optionally, in the aforementioned mandatory testing business scope preservation system, the case module is used to perform statistical analysis on the business scope baseline. When updating the test scope and cases, it is specifically used for:

[0034] If it is displayed as not present, the project team will no longer be required to provide the corresponding test scope and cases;

[0035] If it is displayed as a new addition, the project team is required to provide the corresponding test scope and cases, and to cover the test scope and cases accordingly.

[0036] A third aspect of this application discloses an electronic device, comprising:

[0037] One or more processors;

[0038] A storage device on which one or more programs are stored;

[0039] When one or more programs are executed by one or more processors, the one or more processors perform the functions described in any one of the first aspects of this application, including the method for preserving the business scope.

[0040] The fourth aspect of this application discloses a storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the functional requirements of the preservation method described in any one of the first aspects of this application.

[0041] As can be seen from the above technical solution, the present invention provides a method for keeping the functionally required test scope fresh, including: acquiring important business activities, business modeling assets, and requirement management assets; updating the business scope baseline based on the important business activities, business modeling assets, and requirement management assets; performing statistical analysis on the business scope baseline, and updating the test scope and cases; wherein, the business scope baseline serves as the basis for sorting out the test scope and its cases, and statistical analysis is used to determine the coverage of the test scope to the business scope; that is, forming a business scope baseline facilitates management work such as updating and maintaining the business scope; supporting statistical analysis, the business scope serves as the basis for sorting out the test scope and its cases, and statistical analysis is used to determine the coverage of the test scope to the business scope; it can simplify the updating of the business scope baseline, improve the timeliness, accuracy, and coverage of the compared business scope, and provide the latest basis for the subsequent sorting and updating of the test scope and test cases. Attached Figure Description

[0042] 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 some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 This is a flowchart of a method for preserving the scope of mandatory functional tests provided in an embodiment of the present invention;

[0044] Figure 2 This is a flowchart of another method for preserving the scope of mandatory functional tests provided in an embodiment of the present invention;

[0045] Figure 3 This is a flowchart of another method for preserving the scope of mandatory functional tests provided in an embodiment of the present invention;

[0046] Figure 4 This is a schematic diagram of a functionally mandatory testing business scope preservation system provided by an embodiment of the present invention;

[0047] Figure 5 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0049] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0050] This application provides a method for keeping the scope of business that must be tested fresh, which solves the problem that the existing technology cannot keep the scope of business during the retesting process fresh. Once the business department / project team updates important business activities, business modeling assets or requirements management assets, testers need to manually check them again, which consumes a lot of manpower and has a high error rate.

[0051] See Figure 1 This function requires testing of the following business scope preservation methods:

[0052] S101. Acquire key business activities, business modeling assets, and requirements management assets.

[0053] Specifically, the process of acquiring important business activities, business modeling assets, and requirements management assets can be as follows: after importing important business activities, requirements management assets, and business modeling assets, the system can map them through the "three-level activity" field shared by the three documents, thereby enabling the acquisition of important business activities, business modeling assets, and requirements management assets.

[0054] Of course, other methods can also be used, which will not be elaborated here. They can be determined according to the actual situation and are all within the scope of protection of this application.

[0055] Important business activities, business modeling assets, and requirements management assets can be the names of three separate documents. These will not be elaborated here, but can be determined according to the actual situation, and are all within the scope of protection of this application.

[0056] S102. Update the business scope baseline based on key business activities, business modeling assets, and demand management assets within the business scope.

[0057] It should be noted that the business scope baseline is determined by important business activities, business modeling assets, and requirements management assets. Therefore, updating and maintaining the business scope baseline also needs to be achieved through these three parameters: important business activities, business modeling assets, and requirements management assets.

[0058] Specifically, the baseline of this business scope can change with the changes in three parameters: important business activities, business modeling assets, and demand management assets. Of course, it is not limited to these, and will not be elaborated here. It depends on the actual situation, and all of them are within the scope of protection of this application.

[0059] In other words, after updating the business scope baseline, a new version of the business scope baseline is formed.

[0060] S103. Perform statistical analysis on the business scope baseline and update the test scope and cases.

[0061] Among them, the business scope baseline serves as the basis for the testing scope and its case analysis, and the coverage of the testing scope to the business scope is determined through statistical analysis.

[0062] In other words, it supports statistical analysis of the business scope baseline and updates the test scope and cases.

[0063] Specifically, the business scope serves as the basis for defining the test scope and case studies. Statistical analysis is used to determine the coverage of the business scope by the test scope. When it is necessary to update the business scope baseline, the project team is required to provide corresponding test scopes and cases for coverage. For example, if any item in the business scope is deleted, the project team is no longer required to provide corresponding test scopes and cases; if a corresponding item is added to the business scope, the project team is required to provide corresponding test scopes and cases for coverage.

[0064] Of course, the scope of testing and cases for updates are not limited to this, and will not be elaborated here. They can be determined according to the actual situation, and all are within the scope of protection of this application.

[0065] In other words, this device establishes a business scope baseline using upstream assets such as key business activities, business modeling assets, and demand management assets, and updates, maintains, and statistically analyzes this baseline. Previously, there were no tools for maintaining the business scope; updates and saves could only be done manually. If key business activities, business modeling assets, or demand management assets changed, manual comparison was required again. In this implementation, after identifying the changed content, the old business scope is deleted from the document, and the new business scope is added.

[0066] In this embodiment, key business activities, business modeling assets, and requirement management assets are acquired; the business scope baseline is updated based on these assets; statistical analysis is performed on the business scope baseline to update the test scope and test cases; the business scope baseline serves as the basis for reviewing the test scope and test cases, and statistical analysis reveals the coverage of the test scope with the business scope; that is, a business scope baseline is formed, facilitating management tasks such as updating and maintaining the business scope; statistical analysis is supported, with the business scope serving as the basis for reviewing the test scope and test cases, and statistical analysis revealing the coverage of the test scope with the business scope; this simplifies the process of updating the business scope baseline, improves the timeliness, accuracy, and coverage of the compared business scope, and provides the latest basis for subsequent review and updates of the test scope and test cases.

[0067] In addition, before step S102, which updates the business scope baseline based on key business activities, business modeling assets, and demand management assets within the business scope, the following steps are also included:

[0068] Based on key business activities, business modeling assets, and demand management assets, determine the initial business scope baseline.

[0069] It should be noted that the business scope import process involves first creating a business scope baseline using key business activities, business modeling assets, and requirements management assets, and then importing the business scope.

[0070] In other words, after important business activities, requirements management assets, and business modeling assets are imported, the system can map them through the "Level 3 Activities" field shared by the three documents, ultimately forming a business scope baseline, which can serve as the initial business scope baseline.

[0071] Establishing a baseline for the business scope facilitates management tasks such as updating and maintaining the business scope; transforming offline baseline management into online baseline management improves efficiency and accuracy.

[0072] Existing technologies lack corresponding online platforms / systems for support, relying solely on manual maintenance. Manual processing suffers from high error rates and is time-consuming; any changes to assets necessitate further time for re-comparison and analysis, compromising accuracy and timeliness. This embodiment, however, establishes a baseline for the business scope, facilitating updates and maintenance. It also supports statistical analysis, using the business scope as the basis for testing and case analysis to determine the coverage of the business scope by the testing scope.

[0073] In practical applications, see Figure 2 Step S102: Update the business scope baseline based on key business activities, business modeling assets, and requirements management assets within the business scope, including:

[0074] S201. Determine whether significant business activities have changed.

[0075] It should be noted that the way to determine whether the important business activity has changed is to determine whether the current important business activity is consistent with the previous important business activity. If they are consistent, then there is no change; if they are inconsistent, then there is a change.

[0076] Of course, other methods can also be used to determine whether the important business activity has changed. These will not be elaborated here, but will be determined according to the actual situation, and are all within the scope of protection of this application.

[0077] Significant business activities are assessed by the Internal Control and Compliance Department in conjunction with the business departments, typically on a three-year cycle, though other cycles are also possible (details omitted here, all within the scope of this application). Therefore, significant business activities change infrequently. When changes occur, the new significant business activity document is imported into the system. The system then uses the "Level 3 Activity" field to map and associate it with requirements management assets and business modeling assets, generating a new version of the business scope baseline.

[0078] If not, proceed to step S202; if yes, a new version of the business scope asset needs to be acquired, and then the new important business activities, the business modeling asset, and the demand management asset need to be imported. This version of the business scope can be determined manually based on important business activities, or it can be determined using a corresponding algorithm. Details will not be elaborated here; the choice depends on the actual situation and is within the scope of this application.

[0079] S202. Compare the differences between business modeling assets and demand management assets.

[0080] To obtain asset discrepancies, the scope of business data entering the database is used as a benchmark. The discrepancies are regularly compared with business functions / user workflows / level 4 tasks in the business architecture management platform and the demand management asset platform. When business functions / user workflows / level 4 tasks change, the asset discrepancies can be displayed on the platform.

[0081] The asset difference can be a comparison between the current business modeling asset and the previous business modeling asset; or a comparison between the current demand management asset and the previous demand management asset.

[0082] When business modeling assets or requirements management assets change (and these changes are frequent and can occur at any time), it is necessary to perform asset discrepancy comparisons periodically. The business modeling asset platform, the requirements management asset platform, and the business scope preservation device have interfaces. If business modeling assets or requirements management assets change, the system will send relevant notification messages. After receiving the notification, the business scope preservation device will perform asset discrepancy comparisons.

[0083] Of course, other methods can be used to compare asset differences, which will not be elaborated here. The method depends on the actual situation and is within the scope of protection of this application.

[0084] To identify asset discrepancies, the scope of business operations included in the database is used as a benchmark. These discrepancies are periodically compared with business functions, user workflows, and level 4 tasks in the business architecture management platform and the requirements management asset platform. When business functions, user workflows, or level 4 tasks change, the platform displays the asset discrepancies. The scope of functional testing and test cases are strongly dependent on the business scope; only by keeping the business scope up-to-date can the timeliness of the testing scope and test cases be guaranteed.

[0085] S203. If a business function / user workflow exists in the business scope baseline but does not exist in either the business modeling asset or the requirements management asset, it will be displayed as non-existent, and the business function / user workflow will be deleted to form a new business scope baseline.

[0086] Specifically, if a business function exists in the business scope baseline, then delete the business function; if a user workflow exists in the business scope baseline, then delete the user workflow; if both a business function and a user workflow exist in the business scope baseline, then delete both the business function and the user workflow.

[0087] In practical applications, removing business functions / user workflows creates a new business scope baseline, including:

[0088] The administrator is prompted to manually delete the data; and the business scope baseline is updated after the administrator has completed the manual deletion.

[0089] The scope of business operations forms the basis for the test scope and test cases, and requires rigorous management and maintenance. All content that the system determines should be deleted must be manually confirmed to prevent accidental deletion.

[0090] In other words, business functions / user workflows are implemented to form a new business scope baseline; of course, other methods can also be used, which will not be elaborated here, and all are within the protection scope of this application.

[0091] It should be noted that this function, which requires testing the business scope freshness, will save the documents of the business modeling assets, the documents of the requirements management assets, and the business scope baseline. The system will periodically check the "business function" or "user workflow" fields in the requirements management asset documents, business modeling asset documents, and business scope baseline. If a certain "business function" or "user workflow" does not exist in the business modeling assets and requirements management assets, then it is determined that the "business function" or "user workflow" needs to be deleted from the business scope.

[0092] S204. If a business function / user workflow exists in the business scope baseline and in the business modeling asset and / or the requirements management asset; or if a business function / user workflow does not exist in the business scope baseline and does not exist in either the business modeling asset or the requirements management asset, it will be displayed as unchanged and will remain as the current business scope baseline.

[0093] In other words, if a certain "business function" or "user workflow" appears in the business scope and also in the business modeling asset document or the requirements management asset document (either document is acceptable), it means that the "business function" or "user workflow" has not changed and needs to be retained in the business scope baseline.

[0094] In other words, if a business function / user workflow exists in the business scope of the database and also exists in any asset in the modeling or requirements, it will be displayed as "unchanged" and no action is required.

[0095] S205. If a business function / user workflow does not exist in the business scope baseline but exists in the business modeling asset and / or requirement management asset, it will be displayed as a new addition, and a new business function / user workflow will be added to form a new business scope baseline.

[0096] Specifically, if a business function exists in the business scope baseline, then a new business function is added; if a user workflow exists in the business scope baseline, then a new user workflow is added; if both a business function and a user workflow exist in the business scope baseline, then both a new business function and a new user workflow are added.

[0097] Of course, the specific methods for adding new business functions / user workflows will not be elaborated here, but can be determined according to the actual situation, and are all within the scope of protection of this application.

[0098] The scope of business to be re-examined mainly comes from important business activities. By selecting business areas of A1 and A2 categories and third-level activities, important business areas and third-level activities are determined. Then, business modeling assets and demand management assets are mapped to user workflows and business functions to form a unified business scope baseline.

[0099] These three criteria are formed by different departments. For example, the business impact level of important business activities is assessed by the internal control and compliance department in conjunction with the business departments, with a three-year cycle.

[0100] The business modeling assets are maintained by the Digital Promotion Office of the Product Innovation Department. Project teams submit any model adjustment requests to this system. The demand management assets are organized and sorted out by the Business Demand Management Division of the Financial Technology Department, which focuses on enterprise-level projects and gradually sorts out user workflows and business functions.

[0101] If any asset changes, the latest business scope needs to be re-analyzed and confirmed, which consumes a lot of manpower and the probability of errors is high when manually checking. This application realizes automated checking, which improves the accuracy and efficiency of checking.

[0102] In practical applications, see Figure 3 Step S103: Perform statistical analysis on the business scope baseline, and update the test scope and cases, including:

[0103] S301. If it is displayed as not existing, the project team is no longer required to provide the corresponding test scope and cases.

[0104] In other words, if a business function / user workflow exists in the business scope that is entered into the database, but does not exist in the business modeling assets and requirements management assets, it will be displayed as "not found". In this case, it will be manually deleted after the administrator confirms and the business scope baseline will be updated. The project team will no longer be required to provide the corresponding test scope and cases.

[0105] S302. If it is displayed as a new addition, the project team is required to provide the corresponding test scope and cases, and to cover the test scope and cases accordingly.

[0106] In other words, if a business function / user workflow does not exist in the business scope of the database, but exists in any asset in the modeling or requirements, it will be displayed as "new". The business scope baseline needs to be updated, and the project team is required to provide the corresponding test scope and cases for coverage.

[0107] It should be noted that the mandatory business scope preservation method for this feature supports statistical analysis. The business scope serves as the basis for the test scope and case analysis, and the statistical analysis determines the coverage of the business scope by the test scope. The business scope baseline needs to be updated, and the project team is required to provide corresponding test scopes and cases to ensure coverage.

[0108] After the business scope baseline is generated, analysis is performed in the system containing the mandatory functional testing business scope preservation method to identify which business scopes will be covered by test scopes and which will not. Therefore, the number of business scopes and the number of test scopes covering those business scopes can be calculated.

[0109] For example, if a business scope is deleted, the project team is no longer required to provide corresponding test scopes and cases; if a business scope is added, the project team is required to provide corresponding test scopes and cases to cover it. The relevant data can only be updated after the system analyzes and determines that a business scope has been deleted. Afterwards, the corresponding project team is notified that the corresponding test scopes and cases can be deleted.

[0110] This embodiment supports statistical analysis to determine the coverage of the test scope with the business scope. This coverage of the functional test scope with the business scope ensures the completeness of the test scope and test cases.

[0111] Another embodiment of this application provides a functionally required business scope preservation system.

[0112] See Figure 4 The mandatory functional testing scope of the food preservation system includes:

[0113] The acquisition module 101 is used to acquire important business activities, business modeling assets, and demand management assets.

[0114] The update module 102 is used to update the business scope baseline based on important business activities, business modeling assets, and demand management assets within the business scope.

[0115] Case module 103 is used to perform statistical analysis on the business scope baseline and update the test scope and cases. The business scope baseline serves as the basis for sorting out the test scope and its cases, and statistical analysis is used to determine the coverage of the test scope on the business scope.

[0116] For details on the specific working process and principles of each of the above modules, please refer to the "Functional Required Test Business Scope Preservation Method" provided in the above embodiments. It will not be repeated here, but can be determined according to the actual situation, and all are within the protection scope of this application.

[0117] In this embodiment, the import module 101 acquires the current business scope baseline and imports the current business scope; the update module 102 updates the business scope baseline based on important business activities, business modeling assets, and requirement management assets within the business scope; the case module 103 performs statistical analysis on the business scope baseline and updates the test scope and cases; wherein, the business scope baseline serves as the basis for sorting out the test scope and its cases, and statistical analysis reveals the coverage of the test scope to the business scope; this simplifies the updating of the business scope baseline, improves the timeliness, accuracy, and coverage of the compared business scope, and provides the latest basis for the subsequent sorting and updating of the test scope and test cases.

[0118] In practical applications, when the update module 102 updates the business scope baseline based on important business activities, business modeling assets, and requirements management assets within the business scope, it is specifically used for:

[0119] Determine whether significant business activities have changed.

[0120] If not, then compare the differences between business modeling assets and demand management assets.

[0121] If a business function / user workflow exists in the business scope baseline but not in the business modeling asset or the requirements management asset, it will be displayed as non-existent, and the business function / user workflow will be deleted to form a new business scope baseline.

[0122] If a business function / user workflow exists in the business scope baseline and in the business modeling asset and / or the requirements management asset; or if a business function / user workflow does not exist in the business scope baseline and does not exist in either the business modeling asset or the requirements management asset, it will be displayed as unchanged and will remain as the current business scope baseline.

[0123] If a business function / user workflow does not exist in the business scope baseline, but exists in the business modeling assets and / or requirements management assets, it will be displayed as a new function / user workflow, forming a new business scope baseline.

[0124] In practical applications, update module 101 is used to delete business functions / user workflows and form a new business scope baseline, specifically for:

[0125] The administrator is prompted to manually delete the file.

[0126] And after confirming that the administrator has completed the manual deletion, update the business scope baseline.

[0127] In practical applications, the case module 103 is used to perform statistical analysis on the business scope baseline. When updating the test scope and cases, it is specifically used for:

[0128] If it is displayed as not existing, the project team will no longer be required to provide the corresponding test scope and cases.

[0129] If it is displayed as a new addition, the project team is required to provide the corresponding test scope and cases, and to cover the test scope and cases accordingly.

[0130] For details on the specific working process and principles of each of the above modules, please refer to the "Functional Required Test Business Scope Preservation Method" provided in the above embodiments. It will not be repeated here, but can be determined according to the actual situation, and all are within the protection scope of this application.

[0131] Another embodiment of this application provides a storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, it implements the function of the preservation method for the business scope as described in any of the above embodiments.

[0132] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0133] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0134] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0135] Another embodiment of the present invention provides an electronic device, such as... Figure 5 As shown, it includes:

[0136] One or more processors 201.

[0137] Storage device 202, on which one or more programs are stored.

[0138] When one or more programs are executed by one or more processors 201, the one or more processors 201 perform the function of any one of the above embodiments, which is a method for preserving the scope of business operations.

[0139] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts.

[0140] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

[0141] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0142] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0143] It should be noted that the functional testing scope preservation method and system, electronic device, and storage medium provided by this invention can be used in the fields of artificial intelligence, blockchain, distributed systems, cloud computing, big data, Internet of Things, mobile internet, network security, chips, virtual reality, augmented reality, holography, quantum computing, quantum communication, quantum measurement, digital twins, or finance. The above are merely examples and do not limit the application areas of the functional testing scope preservation method and system, electronic device, and storage medium provided by this invention.

[0144] The features described in the various embodiments of this specification can be substituted for or combined with each other. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0145] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0146] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for preserving a functional test service range, characterized by, The method comprises the following steps: acquiring important business activities, business modeling assets, and demand management assets; updating a business scope baseline according to the important business activities, the business modeling assets, and the demand management assets; statistically analyzing the business scope baseline to update a test scope and a case; wherein the business scope baseline serves as a basis for the test scope and the case, and the coverage of the test scope on the business scope is statistically analyzed; the updating of the business scope baseline according to the important business activities, the business modeling assets, and the demand management assets comprises the following steps: judging whether the important business activities have changed; if not, comparing the business modeling assets and the demand management assets for asset differences; if a business function / user workflow exists in the business scope baseline but does not exist in the business modeling assets and / or the demand management assets, the business function / user workflow is displayed as not existing and is deleted to form a new business scope baseline; if a business function / user workflow exists in the business scope baseline and exists in the business modeling assets and / or the demand management assets, or a business function / user workflow does not exist in the business scope baseline and does not exist in the business modeling assets and the demand management assets, the business function / user workflow is displayed as not changed and is kept as the current business scope baseline; if a business function / user workflow does not exist in the business scope baseline but exists in the business modeling assets and / or the demand management assets, the business function / user workflow is displayed as being newly added and is added to form a new business scope baseline.

2. The functional test service range preservation method according to claim 1, wherein, The statistical analysis of the business scope baseline to update the test scope and the case comprises the following steps: if the business function / user workflow is displayed as not existing, the project team is no longer required to provide the corresponding test scope and case; if the business function / user workflow is displayed as being newly added, the project team is required to provide the corresponding test scope and case, and coverage is performed according to the test scope and the case.

3. The functional test service range preservation method according to claim 1, wherein, The deletion of the business function / user workflow to form a new business scope baseline comprises the following steps: prompting an administrator to manually delete the business function / user workflow; and updating the business scope baseline after confirming that the administrator has completed the manual deletion.

4. The functional test service range preservation method according to claim 1, wherein, Before the updating of the business scope baseline according to the important business activities, the business modeling assets, and the demand management assets, the method further comprises the following step: determining an initial business scope baseline according to the important business activities, the business modeling assets, and the demand management assets.

5. A functional test service range preservation system, characterized by, The method comprises the following steps: an acquiring module, configured to acquire important business activities, business modeling assets, and demand management assets; an updating module, configured to update a business scope baseline according to the important business activities, the business modeling assets, and the demand management assets; a case module, configured to statistically analyze the business scope baseline to update a test scope and a case; wherein the business scope baseline serves as a basis for the test scope and the case, and the coverage of the test scope on the business scope is statistically analyzed; when the updating module is used to update the business scope baseline according to the important business activities, the business modeling assets, and the demand management assets, the updating module is specifically configured to: judge whether the important business activities have changed; If not, the business modeling asset and the requirement management asset are compared for asset difference; If the business function / user workflow exists in the business scope baseline and does not exist in the business modeling asset and the requirement management asset, it is displayed as not existing, and the business function / user workflow is deleted to form a new business scope baseline; If the business function / user workflow exists in the business scope baseline and exists in the business modeling asset and / or the requirement management asset, or the business function / user workflow does not exist in the business scope baseline and does not exist in the business modeling asset and the requirement management asset, it is displayed as unchanged, and the current business scope baseline is maintained; If the business function / user workflow does not exist in the business scope baseline and exists in the business modeling asset and / or the requirement management asset, it is displayed as added, and the business function / user workflow is added to form a new business scope baseline.

6. The functional test service range preservation system according to claim 5, wherein, The case module is used for statistical analysis of the business scope baseline, and updating of test scope and cases, and is specifically used for: If it is displayed as not existing, the project team is no longer required to provide corresponding test scope and cases; If it is displayed as added, the project team is required to provide corresponding test scope and cases, and coverage is performed according to the test scope and cases.

7. An electronic device, comprising: It comprises: One or more processors; A storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the function test business scope preservation method according to any one of claims 1-4.

8. A storage medium, characterized by A computer program is stored thereon, and when the computer program is executed by a processor, the function test business scope preservation method according to any one of claims 1-4 is implemented.

Images