CN117290257B - Software lifecycle standardization management method and system based on plug-in call - Google Patents
Software lifecycle standardization management method and system based on plug-in call Download PDFInfo
- Publication number
- CN117290257B CN117290257B CN202311590006.4A CN202311590006A CN117290257B CN 117290257 B CN117290257 B CN 117290257B CN 202311590006 A CN202311590006 A CN 202311590006A CN 117290257 B CN117290257 B CN 117290257B
- Authority
- CN
- China
- Prior art keywords
- plug
- call
- abnormal
- calling
- invalid
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 53
- 238000012360 testing method Methods 0.000 claims abstract description 62
- 238000004458 analytical method Methods 0.000 claims abstract description 38
- 238000012544 monitoring process Methods 0.000 claims abstract description 24
- 238000000034 method Methods 0.000 claims abstract description 17
- 238000005457 optimization Methods 0.000 claims abstract description 15
- 238000004364 calculation method Methods 0.000 claims abstract description 11
- 230000002159 abnormal effect Effects 0.000 claims description 158
- 230000006870 function Effects 0.000 claims description 30
- 230000009257 reactivity Effects 0.000 claims description 18
- 230000005856 abnormality Effects 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 17
- 238000010606 normalization Methods 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/24—Classification techniques
- G06F18/243—Classification techniques relating to the number of classes
- G06F18/2433—Single-class perspective, e.g. one-against-all classification; Novelty detection; Outlier detection
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a software life cycle standardized management method and system based on plug-in call, and belongs to the technical field of software management; the calling process of the plug-in is monitored and counted in terms of time, and the calling state of the plug-in can be intuitively obtained through monitoring the obtained calling time; the calling performance of the plug-in call is further classified under the condition that the result of the plug-in call is effective, and the single calling performance state of the plug-in can be obtained; the single call analysis result of the earlier-stage plug-in is subjected to simultaneous calculation to analyze and classify the overall call performance of the plug-in, so that data support in overall monitoring can be provided for the subsequent replacement and management of the plug-in call; the method and the device are used for solving the technical problems that in the existing scheme, monitoring analysis of different aspects cannot be implemented on the local state and the overall state of the plug-in call of the testing and verifying link in the software life cycle, and dynamic management and control cannot be carried out on the follow-up call and optimization upgrading of the plug-in.
Description
Technical Field
The invention relates to the technical field of software management, in particular to a software lifecycle standardized management method and system based on plug-in call.
Background
The standardized management of the software life cycle refers to the process of carrying out standardized and effective management on each stage in the software development process, and covers the whole process from the initial concept and planning stage to the termination and maintenance stage of the software project; the goal of this management process is to ensure that the software project is completed on time, with high quality, and meets user needs and expectations. A plug-in refers to a separate software component that may be integrated with the main software system to implement a particular function or enhance an existing function.
When the conventional software life cycle standardization management scheme is used for implementing the test and verification links of software, most of the test parameters and test results of the plug-in call are counted, single results and overall results of the plug-in test are judged and adjusted according to experience of testers, monitoring analysis in different aspects cannot be automatically implemented on the local state and the overall state of the plug-in call of the test and verification links in the software life cycle, and subsequent call and optimization upgrading of the plug-in cannot be dynamically managed and controlled.
Disclosure of Invention
The invention aims to provide a software life cycle standardization management method and system based on plug-in call, which are used for solving the technical problems that in the existing scheme, different aspects of monitoring analysis can not be implemented on the local state and the whole state of the plug-in call of a test and verification link in the software life cycle, and the follow-up call and optimization upgrading of the plug-in can not be dynamically managed and controlled.
The aim of the invention can be achieved by the following technical scheme:
a software life cycle standardization management method based on plug-in call comprises the following steps:
the validity monitoring analysis of the plug-in call is implemented on the testing and verifying link before the software release to obtain plug-in call testing information;
uploading the abnormal scheduling data in the plug-in call test information to a plug-in abnormal sharing database to carry out sharing update of the abnormal scheduling data, and dynamically managing and controlling subsequent call and optimization upgrading of the plug-in.
Preferably, the step of obtaining the test information by the plug-in includes:
all plug-ins contained before the software test are acquired, numbered and marked according to a preset sequence, version numbers, suppliers and calling functions corresponding to the plug-ins are sequentially acquired according to the numbered sequence, plug-in basic monitoring data are obtained through combination, and monitoring analysis is carried out on each plug-in call implemented in the test and verification link before the software release;
marking the time point of the application call of the plug-in as first time, marking the time point of the completion call of the plug-in as second time, and acquiring the call duration corresponding to the call of the plug-in according to the second time and the first time; and confirming the result of the plug-in call.
Preferably, if the result of the plug-in call is invalid, generating an invalid call tag, and acquiring an exception reason corresponding to the invalid result according to the invalid call tag and marking the exception reason as a first exception reason, wherein the first exception reason comprises but is not limited to a compatibility problem and a security risk problem;
if the result of the plug-in call is effective, generating an effective call label, and classifying the call performance of the plug-in call according to the effective call label.
Preferably, a corresponding calling time length threshold value is obtained according to a calling function of the plug-in, and the calling time length corresponding to the calling of the plug-in is compared with the calling time length threshold value for analysis;
if the calling time length is smaller than the calling time length threshold value, generating a calling excellent label;
if the calling time length is not less than the calling time length threshold value and is not more than D of the calling time length threshold value, D is a real number which is more than one hundred, generating a calling qualified label;
if the calling time length is greater than D of the calling time length threshold value, D is a real number greater than one hundred, generating a calling disqualification label;
the local plugin scheduling analysis data is composed of an invalid call tag, a valid call tag, a good call tag, a qualified call tag or a disqualified call tag.
Preferably, when validity analysis is sequentially implemented on the call of all the plugins, all local plugin scheduling analysis data generated by calling different plugins in the test and verification link are acquired according to the serial number sequence and traversed;
counting the total number of first result tags and the total number of second result tags, which appear in invalid call tags and valid call tags, and counting the total number of first state tags, the total number of second state tags and the total number of third state tags, which appear in calling excellent tags, calling qualified tags and calling unqualified tags; sequentially acquiring the corresponding reactivity of different plug-in call tests through calculation; and analyzing the calling test state of the plug-in according to the reactivity.
Preferably, comparing the reactivity corresponding to the plug-in call test with a preset reaction threshold value for analysis, if the reactivity is smaller than the reaction threshold value, generating a reaction effective label and marking the corresponding plug-in as an effective plug-in;
if the reactivity is not less than the reaction threshold, generating a reaction invalid tag, marking the corresponding plugin as an invalid plugin, associating the invalid plugin with a second exception cause, and forming exception scheduling data by all the invalid call tags, the first exception cause, the reaction invalid tag and the second exception cause;
all valid plug-ins and invalid plug-ins and abnormal scheduling data form plug-in call test information.
Preferably, uploading the abnormal scheduling data in the plug-in call test information to a plug-in abnormal sharing database to perform sharing update of the abnormal scheduling data, including:
acquiring and traversing abnormal scheduling data in the plug-in call test information, and if invalid call labels exist in the abnormal scheduling data, acquiring call functions and version numbers of the corresponding plug-ins according to the invalid call labels and setting the call functions and version numbers as a first update identifier and a second update identifier respectively;
obtaining an abnormal large class in the plug-in abnormal shared database according to the first updating identification, obtaining an abnormal small class corresponding to plug-in abnormality in the abnormal large class according to the second updating identification, and storing a first abnormality reason, a second abnormality reason, a provider and a tested software version corresponding to the plug-in the abnormal small class;
if the abnormal subclass does not exist, a corresponding abnormal subclass is newly created according to the first updating identification;
if the abnormal scheduling data has the reactive invalid tag, acquiring an alarm prompt for generating the reactive abnormality of the provider corresponding to the invalid plug-in according to the reactive invalid tag, and generating an alarm prompt for replacing the same call function plug-in for the tester.
Preferably, when a tester determines the replaced same calling function plugin, acquiring the calling function and version number of the same calling function plugin which is determined to be replaced and respectively setting the calling function and version number as a first target identifier and a second target identifier, acquiring a corresponding abnormal major class in a plugin abnormal shared database according to the first target identifier, marking the abnormal major class as a selected major class, and performing traversal matching on all abnormal minor classes in the selected major class of the second target identifier;
if the traversal matching is successful, a matching success label is generated, and the first abnormal reason and the second abnormal reason associated with the second target mark are pushed according to the matching success label and the tester is warned to prompt whether to continue using the plug-in unit;
if the traversal matching is successful, generating a matching identification tag, and prompting a tester to continue using the plug-in according to the matching identification tag.
Preferably, when the subsequent calling and optimizing upgrading of the plug-in are dynamically managed, suppliers and versions corresponding to different plug-ins in the plug-in abnormal shared database and all first abnormal reasons are obtained, and the different first abnormal reasons are numbered and marked;
acquiring and marking the weights of the abnormal reasons corresponding to all the first reasons, counting the total number of the first abnormal reasons corresponding to the weights of the same abnormal reasons, and marking;
extracting all abnormal reason weights corresponding to the plug-in and the numerical value of the total number of the first abnormal reasons corresponding to the same Chang Yuanyin weight, and obtaining an abnormal influence coefficient corresponding to the plug-in through calculation;
and arranging all corresponding plugins in a descending order according to the numerical value of the abnormal influence coefficient, marking the plugins corresponding to the abnormal influence coefficient larger than the abnormal influence threshold as selected plugins, and generating an alarm prompt for optimizing and upgrading for suppliers corresponding to the selected plugins.
In order to solve the above problems, the present invention further provides a software lifecycle standardization management system based on plug-in call, including:
the software test call analysis module is used for carrying out validity monitoring analysis of plug-in call on the test and verification links before software release to obtain plug-in call test information;
the abnormal calling plug-in management module is used for uploading abnormal scheduling data in the plug-in calling test information to the plug-in abnormal sharing database to carry out sharing update of the abnormal scheduling data, and carrying out dynamic management and control on subsequent calling and optimization upgrading of the plug-in.
In order to solve the above problems, the present invention also provides a storage medium including at least one processor; and a memory communicatively coupled to the at least one processor;
the memory stores a computer program executable by the at least one processor, so that the at least one processor can execute a software lifecycle standardization management method based on plug-in call.
Compared with the prior art, the invention has the beneficial effects that:
according to the invention, the single call analysis result of the earlier plug-in is subjected to simultaneous calculation to analyze and classify the overall call performance of the plug-in, so that the overall call performance condition of different plug-ins can be intuitively and comprehensively obtained, the data support in the aspect of overall monitoring can be provided for the subsequent replacement and management of the plug-in call, and the data utilization and expansion in the aspect of the call monitoring analysis of the plug-in are realized;
according to the method, the abnormal data called by different plug-ins tested by different main bodies are shared and updated through the plug-in abnormal shared database, so that effective abnormal data reference analysis can be provided for other main bodies when the same plug-ins are subsequently tested and called, and meanwhile, matching and reference of historical abnormal data can be implemented before the plug-ins subsequently replaced by the main bodies are called, so that the testing and verification of the replaced abnormal plug-ins are reduced, and the variety of the utilization of the historical abnormal data of the plug-ins is improved;
according to the method and the device, all abnormal data corresponding to different plugins in the plugin abnormal shared database are subjected to simultaneous calculation to obtain the corresponding abnormal influence coefficient, the abnormal influence of the plugins is analyzed and classified according to the abnormal influence coefficient, and suppliers of different plugins can timely and efficiently obtain the abnormal influence condition of the corresponding plugins according to the classification result, so that subsequent calling and optimization upgrading of different plugins can be dynamically managed and prompted, and the overall effect of post-optimization upgrading maintenance of different plugins is improved.
Drawings
The invention is further described below with reference to the accompanying drawings.
FIG. 1 is a block flow diagram of a software lifecycle normalization management method based on plug-in invocation in accordance with the present invention.
FIG. 2 is a block flow diagram of validating results of a plug-in call in a software lifecycle normalization management method based on the plug-in call in accordance with the present invention.
FIG. 3 is a block flow diagram of dynamic management and control of subsequent calls and optimization upgrades of plug-ins in a software lifecycle normalization management method based on plug-in calls.
FIG. 4 is a block diagram of a software lifecycle normalization management system based on plug-in invocation in accordance with the present invention.
Fig. 5 is a schematic structural diagram of a computer device implementing a software lifecycle normalization management method based on plug-in calls.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which are obtained by persons skilled in the art without any inventive effort, are within the scope of the present invention based on the embodiments of the present invention.
Example 1:
as shown in fig. 1, the present invention is a software lifecycle standardization management method based on plug-in call, including:
the validity monitoring analysis of the plug-in call is implemented on the testing and verifying link before the software release to obtain plug-in call testing information; comprising the following steps:
all plug-ins contained before the software test are acquired and numbered and marked according to a preset sequence, wherein the preset sequence can be the sequence of test verification, the version numbers, suppliers and calling functions corresponding to the plug-ins are sequentially acquired according to the numbering sequence, basic plug-in monitoring data are obtained through combination, and monitoring analysis is carried out on each plug-in call implemented in the test and verification links before the software release;
specifically, a time point of the application call of the plug-in is marked as a first time, a time point of the completion call of the plug-in is marked as a second time, and a call duration corresponding to the call of the plug-in is obtained according to the second time and the first time; the units corresponding to the first time and the second time are seconds, and the unit of the calling time length is seconds;
the monitoring statistics is implemented from the time aspect through the calling process of the plug-in, the calling state of the plug-in can be intuitively obtained through monitoring the obtained calling time, reliable data support can be provided for the performance analysis of the subsequent plug-in calling, and the diversity of monitoring data utilization is improved;
as shown in fig. 2, validating the result of the plugin call, wherein the validation is performed by a tester, if the result of the plugin call is invalid, an invalid call tag is generated, and according to the invalid call tag, an abnormal reason corresponding to the invalid result is obtained and marked as a first abnormal reason, wherein the first abnormal reason includes but is not limited to a compatibility problem and a security risk problem;
if the result of the plug-in call is effective, generating an effective call label, classifying the call performance of the plug-in call according to the effective call label, and acquiring a corresponding call duration threshold according to the call function of the plug-in;
the effective means that normal operation of a corresponding calling function, such as normal display of webpage jump, can be realized through plug-in calling;
comparing and analyzing the calling time length corresponding to the calling of the plug-in with a calling time length threshold, wherein the calling time length threshold is determined according to the historical test big data of the corresponding plug-in, and the calling time length threshold can be the average calling time length of the historical test big data;
if the calling time length is smaller than the calling time length threshold value, generating a calling excellent label;
if the calling time length is not less than the calling time length threshold value and is not more than D of the calling time length threshold value, D is a real number which is more than one hundred, generating a calling qualified label;
if the calling time length is greater than D of the calling time length threshold value, D is a real number greater than one hundred, generating a calling disqualification label;
the local plug-in scheduling analysis data is composed of an invalid call tag, an effective call tag, a good call tag, a qualified call tag or an unqualified call tag;
in the embodiment of the invention, the calling performance of the plug-in call is further classified under the condition that the result of the plug-in call is effective, so that the single calling performance state of the plug-in can be obtained, and reliable local data support can be provided for the analysis of the overall calling performance state of the subsequent plug-in;
when validity analysis is sequentially carried out on the call of all plugins, all local plugin scheduling analysis data generated by calling of different plugins in a test and verification link are obtained according to a numbering sequence and traversed, the total number YJ of first result tags and the total number EJ of second result tags, which appear in invalid call tags and valid call tags, the total number YZ of first state tags, the total number EZ of second state tags and the total number SZ of third state tags, which appear in the process of calling excellent tags, calling qualified tags and calling unqualified tags, are counted;
by the formulaSequentially calculating and acquiring the reactivity Fy corresponding to the calling test of different plug-ins; wherein u1,u2 and u3 are proportionality coefficients, u1 is more than 0 and less than 1, u2 is more than 0 and less than 1, and u3 is more than 0 and less than 1; u1+u2+u3=1, and the scaling factor in the formula can be set by those skilled in the art according to the actual situation or obtained by simulation of a large number of sample data;
it should be noted that, the reactivity is a numerical value used for analyzing and evaluating the overall calling performance of the plug-in the test and verification process; the smaller the reactivity is, the more excellent the calling performance of the corresponding plug-in is;
analyzing the calling test state of the plug-in according to the reactivity, and comparing the reactivity corresponding to the plug-in calling test with a preset reaction threshold value for analysis;
if the reactivity is smaller than the reaction threshold, generating a reaction effective label and marking the corresponding plug-in as an effective plug-in;
if the reactivity is not less than the reaction threshold, generating a reaction invalid tag, marking the corresponding plugin as an invalid plugin, and associating the invalid plugin with a second abnormal reason, wherein the second abnormal reason can be understood that the calling of the plugin can normally run but does not meet the requirement of plugin test, such as that the plugin calling is too slow in reaction;
all invalid call tags and first exception reasons and the invalid call tags and second exception reasons are reflected to form exception scheduling data;
all the effective plug-ins, the invalid plug-ins and the abnormal scheduling data form plug-in calling test information;
in the embodiment of the invention, the single call analysis result of the earlier plugin is subjected to simultaneous calculation to analyze and classify the overall call performance of the plugin, so that the overall call performance condition of different plugins can be intuitively and comprehensively obtained, the data support in the aspect of overall monitoring can be provided for the subsequent replacement and management of the plugin call, and the data utilization and expansion in the aspect of plugin call monitoring analysis are realized.
Uploading abnormal scheduling data in the plug-in call test information to a plug-in abnormal sharing database to carry out sharing update of the abnormal scheduling data, and dynamically managing and controlling subsequent call and optimization upgrading of the plug-in; comprising the following steps:
acquiring and traversing abnormal scheduling data in the plug-in call test information, and if invalid call labels exist in the abnormal scheduling data, acquiring call functions and version numbers of the corresponding plug-ins according to the invalid call labels and setting the call functions and the version numbers as a first update identifier and a second update identifier respectively, wherein the first update identifier and the second update identifier play a role in category identification;
obtaining an abnormal large class in the plug-in abnormal shared database according to the first updating identification, obtaining an abnormal small class corresponding to plug-in abnormality in the abnormal large class according to the second updating identification, and storing a first abnormality reason, a second abnormality reason, a provider and a tested software version corresponding to the plug-in the abnormal small class;
if the abnormal subclass does not exist, a corresponding abnormal subclass is newly created according to the first updating identification;
different from the abnormal data called by different plug-ins tested by different main bodies in the prior art, the abnormal data called by the plug-ins implemented by different main bodies are mutually isolated to form a data island, so that the defect of test resource waste is caused by repeated occurrence of the abnormal data called by the plug-ins implemented by different main bodies; in the embodiment of the invention, the abnormal data called by different plug-ins tested by different main bodies are shared and updated by the plug-in abnormal shared database, so that effective abnormal data reference analysis can be provided for other main bodies when the same plug-ins are subsequently tested and called, and meanwhile, the matching and reference of historical abnormal data can be implemented for the plug-ins which are subsequently replaced by the main bodies before the plug-ins are called, the testing and verification of the replaced abnormal plug-ins are reduced, and the diversity of the utilization of the historical abnormal data of the plug-ins is improved.
If the abnormal scheduling data has the reactive invalid tag, acquiring an alarm prompt for generating a reactive abnormality of a provider corresponding to the invalid plug-in according to the reactive invalid tag, and generating an alarm prompt for replacing the same call function plug-in for a tester;
in addition, when a tester determines the replaced same calling function plugin, acquiring the calling function and version number of the same calling function plugin which is determined to be replaced, setting the calling function and version number as a first target identifier and a second target identifier respectively, acquiring a corresponding abnormal major class in a plugin abnormal sharing database according to the first target identifier, marking the abnormal major class as a selected major class, and performing traversal matching on all abnormal minor classes in the selected major class by the second target identifier;
if the traversal matching is successful, a matching success label is generated, and the first abnormal reason and the second abnormal reason associated with the second target mark are pushed according to the matching success label and the tester is warned to prompt whether to continue using the plug-in unit;
if the traversal matching is successful, generating a matching identification tag, and prompting a tester to continue using the plug-in according to the matching identification tag;
as shown in fig. 3, when performing dynamic management and control on subsequent call and optimization upgrade of the plug-in, acquiring suppliers and versions corresponding to different plug-ins in the plug-in abnormal shared database and all first abnormal reasons, numbering the different first abnormal reasons, and marking the different first abnormal reasons as i, i=1, 2,3, … …, n; n is a positive integer;
setting different first abnormality reasons corresponding to different abnormality reason weights, acquiring all abnormality reason weights corresponding to the first reasons and marking as YQi, counting the total number of the first abnormality reasons corresponding to the same abnormality reason weights and marking as YZi;
the abnormal cause weight is used for carrying out digital and differential representation on a plurality of first abnormal causes of the text, reliable data support can be provided for the optimization updating alarm of the subsequent plug-in from the aspect of the abnormal cause, and the specific value of the abnormal cause weight can be determined by a person skilled in the art according to experience and historical test big data corresponding to the plug-in;
extracting all abnormal reason weights corresponding to the plug-in and the numerical value of the total number of the first abnormal reasons corresponding to the same Chang Yuanyin weight and passing through a formulaCalculating and obtaining an abnormal influence coefficient Yy corresponding to the plug-in;
the abnormal influence coefficient is a numerical value for performing simultaneous calculation on all abnormal data corresponding to the plug-in to perform overall evaluation on the abnormal influence in the aspect of testing; the larger the abnormal influence coefficient is, the larger the abnormal influence of the corresponding plug-in is, and the more the corresponding suppliers are required to process in time;
and arranging all corresponding plugins in a descending order according to the numerical value of the abnormal influence coefficient, marking the plugins corresponding to the abnormal influence coefficient larger than an abnormal influence threshold as selected plugins, determining the abnormal influence threshold according to the sample test big data of all plugins, and generating an alarm prompt for optimizing upgrading for suppliers corresponding to the selected plugins.
In the embodiment of the invention, the corresponding abnormal influence coefficients are obtained by carrying out simultaneous calculation on all the abnormal data corresponding to different plugins in the plugin abnormal shared database, the abnormal influence of the plugin is analyzed and classified according to the abnormal influence coefficients, and the abnormal influence condition of the corresponding plugin can be timely and efficiently obtained by suppliers of different plugins according to the classification result, so that subsequent calling and optimizing upgrading of different plugins can be timely and dynamically managed and prompted, and the overall effect of post-optimizing upgrading maintenance of different plugins is improved.
In addition, the formulas related in the above are all formulas for removing dimensions and taking numerical calculation, and are one formula which is obtained by acquiring a large amount of data and performing software simulation through simulation software and is closest to the actual situation.
Example 2:
as shown in fig. 4, a software lifecycle normalization management system based on plug-in call includes:
the software test call analysis module is used for carrying out validity monitoring analysis of plug-in call on the test and verification links before software release to obtain plug-in call test information;
the abnormal calling plug-in management module is used for uploading abnormal scheduling data in the plug-in calling test information to the plug-in abnormal sharing database to carry out sharing update of the abnormal scheduling data, and carrying out dynamic management and control on subsequent calling and optimization upgrading of the plug-in.
Example 3:
fig. 5 is a schematic structural diagram of a computer device for implementing a software lifecycle normalization management method based on plug-in call according to an embodiment of the present invention.
The computer device may include a processor, memory, and a bus, and may also include a computer program stored in the memory and executable on the processor, such as a program for a software lifecycle normalization management method based on plug-in calls.
The memory includes at least one type of readable storage medium, including flash memory, a removable hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, etc. The memory may in some embodiments be an internal storage unit of a computer device, such as a removable hard disk of the computer device. The memory may also be an external storage device of the computer device in other embodiments, such as a plug-in mobile hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. that are provided on the computer device. Further, the memory may also include both internal storage units and external storage devices of the computer device. The memory may be used not only for storing application software installed in a computer device and various types of data, for example, code of a program of a software lifecycle normalization management method based on a plug-in call, but also for temporarily storing data that has been output or is to be output.
The processor may in some embodiments be comprised of integrated circuits, for example, a single packaged integrated circuit, or may be comprised of multiple integrated circuits packaged in the same location or in different locations, including one or more central processing units (Central Processing unit, CPU), microprocessors, digital processing chips, graphics processors, combinations of various control chips, and the like. The processor is a Control Unit (Control Unit) of the computer device, connects various components of the entire computer device using various interfaces and lines, and executes various locations of the computer device and processes data by running or executing programs or modules stored in a memory (e.g., a program based on a software lifecycle normalization management method called by a plug-in, etc.), and calling data stored in the memory.
The bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. The bus is arranged to enable a connection communication between said memory and at least one processor or the like.
Fig. 5 shows only a computer device having components, and it will be understood by those skilled in the art that the structure shown in fig. 5 is not limiting of the computer device and may include fewer or more components than shown, or may combine certain components, or a different arrangement of components.
For example, although not shown, the computer device may further include a power source (such as a battery) for powering the various components, preferably the power source may be logically connected to the at least one processor by a power management device such that charge management, discharge management, and power consumption management are achieved by the power management device. The power supply may also include one or more of any of a direct current or alternating current power supply, recharging device, power failure detection circuit, power converter or inverter, power status indicator, etc. The computer device may also include various sensors, bluetooth modules, wi-Fi modules, etc., which are not described in detail herein.
Further, the computer device may also include a network interface, which may optionally include a wired interface and/or a wireless interface (e.g., WI-FI interface, bluetooth interface, etc.), typically used to establish a communication connection between the computer device and other computer devices.
The computer device may optionally further comprise a user interface, which may be a Display, an input unit such as a Keyboard (Keyboard), or a standard wired interface, a wireless interface. Alternatively, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch, or the like. The display may also be referred to as a display screen or display unit, as appropriate, for displaying information processed in the computer device and for displaying a visual user interface.
It should be understood that the above-described embodiments are for illustrative purposes only and are not limited to this configuration in the scope of the patent application.
A program of a software lifecycle normalization management method based on plug-in calls stored in a memory in a computer device is a combination of instructions.
Specifically, the specific implementation method of the above instruction by the processor may refer to descriptions of related steps in the corresponding embodiments of fig. 1 to fig. 4, which are not repeated herein.
Further, the modules/units integrated with the computer device may be stored in a computer readable storage medium if implemented in the form of software location units and sold or used as stand-alone products. The computer readable storage medium may be volatile or nonvolatile. For example, the computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM).
The invention also provides a computer readable storage medium storing a computer program which, when executed by a processor of a computer device, causes a computer to perform the method of the invention.
In the several embodiments provided in the present invention, it should be understood that the disclosed method may be implemented in other manners. For example, the above-described embodiments of the invention are merely illustrative, e.g., the division of modules is merely a logical location division, and other manners of division may be implemented in practice.
The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each location module in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software location modules.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof.
Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made to the technical solution of the present invention without departing from the spirit and scope of the technical solution of the present invention.
Claims (10)
1. A software life cycle standardization management method based on plug-in call is characterized by comprising the following steps:
the validity monitoring analysis of the plug-in call is implemented on the testing and verifying link before the software release to obtain plug-in call testing information;
uploading abnormal scheduling data in the plug-in call test information to a plug-in abnormal sharing database to carry out sharing update of the abnormal scheduling data, and dynamically managing and controlling subsequent call and optimization upgrading of the plug-in; the abnormal scheduling data consists of all invalid call tags and a first abnormal reason and reflects invalid tags and a second abnormal reason;
if the result of the plug-in call is invalid, generating an invalid call label, acquiring an abnormal reason corresponding to the invalid result according to the invalid call label, and marking the abnormal reason as a first abnormal reason;
if the reactivity is not less than the reaction threshold, generating a reaction invalid tag, marking the corresponding plugin as an invalid plugin, and associating the invalid plugin with a second abnormal reason; the reactivity is a numerical value used for analyzing and evaluating the overall calling performance of the plug-in the test verification process.
2. The software lifecycle normalization management method based on plug-in call according to claim 1, wherein the step of obtaining the test information by the plug-in call comprises:
all plug-ins contained before the software test are acquired, numbered and marked according to a preset sequence, version numbers, suppliers and calling functions corresponding to the plug-ins are sequentially acquired according to the numbered sequence, plug-in basic monitoring data are obtained through combination, and monitoring analysis is carried out on each plug-in call implemented in the test and verification link before the software release;
marking the time point of the application call of the plug-in as first time, marking the time point of the completion call of the plug-in as second time, and acquiring the call duration corresponding to the call of the plug-in according to the second time and the first time; and confirming the result of the plug-in call.
3. A software lifecycle normalization management method based on plug-in invocation as claimed in claim 2, wherein the first exception cause comprises, but is not limited to, compatibility issues and security risk issues;
if the result of the plug-in call is effective, generating an effective call label, and classifying the call performance of the plug-in call according to the effective call label.
4. The software lifecycle standardization management method based on plug-in call according to claim 3, characterized in that the corresponding call duration threshold is obtained according to the call function of the plug-in, and the corresponding call duration of the plug-in call is compared with the call duration threshold for analysis;
if the calling time length is smaller than the calling time length threshold value, generating a calling excellent label;
if the calling time length is not less than the calling time length threshold value and is not more than D of the calling time length threshold value, D is a real number which is more than one hundred, generating a calling qualified label;
if the calling time length is greater than D of the calling time length threshold value, D is a real number greater than one hundred, generating a calling disqualification label;
the local plugin scheduling analysis data is composed of an invalid call tag, a valid call tag, a good call tag, a qualified call tag or a disqualified call tag.
5. The standardized management method of software lifecycle based on plug-in call according to claim 4, wherein when validity analysis is performed on calls of all plug-ins in turn, all local plug-in scheduling analysis data generated by call of different plug-ins in test and verification links are obtained according to the sequence of numbers and traversed;
counting the total number of first result tags and the total number of second result tags, which appear in invalid call tags and valid call tags, and counting the total number of first state tags, the total number of second state tags and the total number of third state tags, which appear in calling excellent tags, calling qualified tags and calling unqualified tags; sequentially acquiring the corresponding reactivity of different plug-in call tests through calculation; and analyzing the calling test state of the plug-in according to the reactivity.
6. The standardized management method for software lifecycle based on plug-in call according to claim 5, wherein the reactivity corresponding to the plug-in call test is compared with a preset reaction threshold value for analysis, and if the reactivity is smaller than the reaction threshold value, a reaction effective label is generated and the corresponding plug-in is marked as an effective plug-in;
all valid plug-ins and invalid plug-ins and abnormal scheduling data form plug-in call test information.
7. The software lifecycle standardization management method based on plug-in call according to claim 1, wherein uploading the abnormal scheduling data in the plug-in call test information to a plug-in abnormal sharing database to perform sharing update of the abnormal scheduling data comprises:
acquiring and traversing abnormal scheduling data in the plug-in call test information, and if invalid call labels exist in the abnormal scheduling data, acquiring call functions and version numbers of the corresponding plug-ins according to the invalid call labels and setting the call functions and version numbers as a first update identifier and a second update identifier respectively;
obtaining an abnormal large class in the plug-in abnormal shared database according to the first updating identification, obtaining an abnormal small class corresponding to plug-in abnormality in the abnormal large class according to the second updating identification, and storing a first abnormality reason, a second abnormality reason, a provider and a tested software version corresponding to the plug-in the abnormal small class;
if the abnormal subclass does not exist, a corresponding abnormal subclass is newly created according to the first updating identification;
if the abnormal scheduling data has the reactive invalid tag, acquiring an alarm prompt for generating the reactive abnormality of the provider corresponding to the invalid plug-in according to the reactive invalid tag, and generating an alarm prompt for replacing the same call function plug-in for the tester.
8. The standardized management method of software lifecycle based on plug-in call according to claim 7, wherein when a tester determines the same call function plug-in to be replaced, the tester obtains the call function and version number of the same call function plug-in to be replaced and respectively sets the call function and version number as a first target identifier and a second target identifier, obtains the corresponding abnormal major class in the plug-in abnormal shared database according to the first target identifier and marks the abnormal major class as a selected major class, and performs traversal matching on all the abnormal minor classes in the selected major class of the second target identifier;
if the traversal matching is successful, a matching success label is generated, and the first abnormal reason and the second abnormal reason associated with the second target mark are pushed according to the matching success label and the tester is warned to prompt whether to continue using the plug-in unit;
if the traversal matching is successful, generating a matching identification tag, and prompting a tester to continue using the plug-in according to the matching identification tag.
9. The software lifecycle standardization management method based on plug-in call, when carrying out dynamic management and control on subsequent call and optimization upgrading of the plug-in, obtaining suppliers and versions corresponding to different plug-ins in the plug-in exception sharing database and all first exception reasons, numbering and marking the different first exception reasons;
acquiring and marking the weights of the abnormal reasons corresponding to all the first reasons, counting the total number of the first abnormal reasons corresponding to the weights of the same abnormal reasons, and marking;
extracting all abnormal reason weights corresponding to the plug-in and the numerical value of the total number of the first abnormal reasons corresponding to the same Chang Yuanyin weight, and obtaining an abnormal influence coefficient corresponding to the plug-in through calculation;
and arranging all corresponding plugins in a descending order according to the numerical value of the abnormal influence coefficient, marking the plugins corresponding to the abnormal influence coefficient larger than the abnormal influence threshold as selected plugins, and generating an alarm prompt for optimizing and upgrading for suppliers corresponding to the selected plugins.
10. A software lifecycle normalization management system based on plug-in call, applied to the software lifecycle normalization management method based on plug-in call as claimed in any one of claims 1 to 9, comprising:
the software test call analysis module is used for carrying out validity monitoring analysis of plug-in call on the test and verification links before software release to obtain plug-in call test information;
the abnormal calling plug-in management module is used for uploading abnormal scheduling data in the plug-in calling test information to the plug-in abnormal sharing database to carry out sharing update of the abnormal scheduling data, and carrying out dynamic management and control on subsequent calling and optimization upgrading of the plug-in.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311590006.4A CN117290257B (en) | 2023-11-27 | 2023-11-27 | Software lifecycle standardization management method and system based on plug-in call |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311590006.4A CN117290257B (en) | 2023-11-27 | 2023-11-27 | Software lifecycle standardization management method and system based on plug-in call |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117290257A CN117290257A (en) | 2023-12-26 |
| CN117290257B true CN117290257B (en) | 2024-02-02 |
Family
ID=89248433
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311590006.4A Active CN117290257B (en) | 2023-11-27 | 2023-11-27 | Software lifecycle standardization management method and system based on plug-in call |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117290257B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113516337A (en) * | 2021-03-25 | 2021-10-19 | 中国雄安集团数字城市科技有限公司 | Method and device for monitoring data security operation |
| CN114297512A (en) * | 2022-01-27 | 2022-04-08 | 中国农业银行股份有限公司 | Data recommendation method and device, electronic equipment and storage medium |
| CN116737677A (en) * | 2023-07-04 | 2023-09-12 | 康键信息技术（深圳）有限公司 | Resource processing method, device, computer equipment and readable storage medium |
| WO2023202299A1 (en) * | 2022-04-20 | 2023-10-26 | 北京字跳网络技术有限公司 | Sdk upgrade method and apparatus, and computer device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9794292B2 (en) * | 2015-10-26 | 2017-10-17 | Amazon Technologies, Inc. | Providing fine-grained access remote command execution for virtual machine instances in a distributed computing environment |
| US10417629B2 (en) * | 2016-09-02 | 2019-09-17 | Microsoft Technology Licensing, Llc | Account identifier digitization abstraction |
| WO2020141957A1 (en) * | 2019-01-04 | 2020-07-09 | Samsung Electronics Co., Ltd. | A method and apparatus for organizing and detecting swarms in a network |
-
2023
- 2023-11-27 CN CN202311590006.4A patent/CN117290257B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113516337A (en) * | 2021-03-25 | 2021-10-19 | 中国雄安集团数字城市科技有限公司 | Method and device for monitoring data security operation |
| CN114297512A (en) * | 2022-01-27 | 2022-04-08 | 中国农业银行股份有限公司 | Data recommendation method and device, electronic equipment and storage medium |
| WO2023202299A1 (en) * | 2022-04-20 | 2023-10-26 | 北京字跳网络技术有限公司 | Sdk upgrade method and apparatus, and computer device |
| CN116737677A (en) * | 2023-07-04 | 2023-09-12 | 康键信息技术（深圳）有限公司 | Resource processing method, device, computer equipment and readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| A Survey on How Test Flakiness Affects Developers and What Support They Need To Address It;Martin Gruber等;《2022 IEEE Conference on Software Testing, Verification and Validation (ICST)》;全文 * |
| 基于平台加插件的软件系统设计在自动测试系统中的实现;刘颐芳等;《电脑编程技巧与维护》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117290257A (en) | 2023-12-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20140157239A1 (en) | System and method for peer-based code quality analysis reporting | |
| US10169002B2 (en) | Automated and heuristically managed solution to quantify CPU and path length cost of instructions added, changed or removed by a service team | |
| CN107679683B (en) | Software development progress early warning method and device | |
| CN111694844B (en) | Enterprise operation data analysis method and device based on configuration algorithm and electronic equipment | |
| CN114519524A (en) | Enterprise risk early warning method and device based on knowledge graph and storage medium | |
| CN116089250B (en) | Man-machine interaction optimization management system and management method | |
| CN112463530A (en) | Anomaly detection method and device for micro-service system, electronic equipment and storage medium | |
| CN112541688B (en) | Service data verification method and device, electronic equipment and computer storage medium | |
| CN112631903A (en) | Task testing method and device, electronic equipment and storage medium | |
| CN117290257B (en) | Software lifecycle standardization management method and system based on plug-in call | |
| CN117193975A (en) | Task scheduling method, device, equipment and storage medium | |
| CN112950344A (en) | Data evaluation method and device, electronic equipment and storage medium | |
| CN117114409A (en) | Data processing method, device and storage medium for enterprise data | |
| CN111651500A (en) | User identity recognition method, electronic device and storage medium | |
| CN113313211B (en) | Text classification method, device, electronic equipment and storage medium | |
| CN114896164A (en) | Interface optimization method and device, electronic equipment and storage medium | |
| CN115033489A (en) | Code resource detection method and device, electronic equipment and storage medium | |
| CN114968816A (en) | Data simulation-based strategy testing method, device, equipment and storage medium | |
| CN111045849A (en) | Method, device, server and storage medium for identifying reason of checking abnormality | |
| CN111400191A (en) | Webpage security testing method and device and computer readable storage medium | |
| CN112579046B (en) | User story analysis method and device, electronic equipment and storage medium | |
| CN111414398B (en) | Data analysis model determining method, device and storage medium | |
| CN115062495B (en) | Method and device for analyzing insulating property of material, electronic equipment and storage medium | |
| CN114237689A (en) | System version monitoring method and device, electronic equipment and readable storage medium | |
| CN117932613A (en) | Method and device for analyzing vulnerability influence range by code traceability and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |