CN112069503A - Task management method, device and storage medium - Google Patents
Task management method, device and storage medium Download PDFInfo
- Publication number
- CN112069503A CN112069503A CN202010778788.4A CN202010778788A CN112069503A CN 112069503 A CN112069503 A CN 112069503A CN 202010778788 A CN202010778788 A CN 202010778788A CN 112069503 A CN112069503 A CN 112069503A
- Authority
- CN
- China
- Prior art keywords
- repair
- vulnerability
- bug
- priority
- duration
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title abstract description 26
- 230000008439 repair process Effects 0.000 claims abstract description 318
- 230000003044 adaptive effect Effects 0.000 claims abstract description 12
- 238000012360 testing method Methods 0.000 claims description 59
- 238000000034 method Methods 0.000 claims description 27
- 238000004590 computer program Methods 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 4
- 238000004891 communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 11
- 230000000875 corresponding effect Effects 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013102 re-test Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/577—Assessing vulnerabilities and evaluating computer system security
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a task management method, a task management device and a storage medium. In the embodiment of the application, the repair priority is set for the program bug, and each repair priority is configured with adaptive repair duration. Wherein the repair duration is inversely related to the repair priority. Thus, for the loophole to be repaired, the repair priority of the loophole can be obtained, and the repair duration matched with the repair priority is obtained according to the repair priority of the loophole; and then, displaying the bug and the repair time length of the bug in a repair task list according to the repair priority of the bug. The user can know the repair urgency of the vulnerability according to the repair duration of the vulnerability. Therefore, the time for repairing the bug is displayed so that the developers can know the repair urgency of the bug, the developers can be reminded of repairing the bug in time, and the bug repair efficiency is improved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a task management method, a device, and a storage medium.
Background
With the continuous development of communication technology, the applications of the intelligent terminal are more and more, and more Application programs (APPs) are developed for the intelligent terminal. Before the application program is released, the application program needs to be tested, repaired and the like so as to improve the reliability of the application program.
In the prior art, a tester tests an application to detect a program Bug (Bug), and feeds the detected Bug back to an application developer for repair. However, developers cannot know the repair urgency of each bug, so that bug repair is not timely, and repair efficiency is affected.
Disclosure of Invention
Aspects of the present application provide a task management method, device, and storage medium for displaying a repair urgency level of a program bug, and reminding a developer of repairing the bug in time, thereby improving bug repair efficiency.
An embodiment of the present application provides a task management method, including: acquiring the repair priority of the first vulnerability; acquiring a repair duration matched with the repair priority of the first bug according to the repair priority of the first bug; wherein the repair duration is inversely related to the repair priority; and displaying the first bug and the repair time length in a repair task list of a first user according to the repair priority of the first bug, so that the first user can know the repair urgency of the first bug according to the repair time length.
An embodiment of the present application further provides an electronic device, including: a memory, a processor, and a screen; wherein the memory is used for storing a computer program;
the processor is coupled to the memory for executing the computer program for performing the steps of the above-mentioned task management method.
Embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the task management method.
In the embodiment of the application, the repair priority is set for the program bug, and each repair priority is configured with adaptive repair duration. Wherein the repair duration is inversely related to the repair priority. Thus, for the loophole to be repaired, the repair priority of the loophole can be obtained, and the repair duration matched with the repair priority is obtained according to the repair priority of the loophole; and then, displaying the bug and the repair time length of the bug in a repair task list according to the repair priority of the bug. The user can know the repair urgency of the vulnerability according to the repair duration of the vulnerability. Therefore, the time for repairing the bug is displayed so that the developers can know the repair urgency of the bug, the developers can be reminded of repairing the bug in time, and the bug repair efficiency is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1a is a schematic flowchart of a task management method according to an embodiment of the present application;
fig. 1b is a schematic diagram of a repair task list provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the prior art, a tester tests an application to detect a program Bug (Bug), and feeds the detected Bug back to an application developer for repair. However, developers cannot know the repair urgency of each bug, so that bug repair is not timely, and repair efficiency is affected.
In some embodiments of the present application, repair priorities are set for the program bugs, and each repair priority is configured with an adaptive repair duration. Wherein the repair duration is inversely related to the repair priority. Thus, for the loophole to be repaired, the repair priority of the loophole can be obtained, and the repair duration matched with the repair priority is obtained according to the repair priority of the loophole; and then, displaying the bug and the repair time length of the bug in a repair task list according to the repair priority of the bug. The user can know the repair urgency of the vulnerability according to the repair duration of the vulnerability. Therefore, the time for repairing the bug is displayed so that the developers can know the repair urgency of the bug, the developers can be reminded of repairing the bug in time, and the bug repair efficiency is improved.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
It should be noted that: like reference numerals refer to like objects in the following figures and embodiments, and thus, once an object is defined in one figure or embodiment, further discussion thereof is not required in subsequent figures and embodiments.
Fig. 1a is a schematic flowchart of a task management method according to an embodiment of the present application. As shown in fig. 1a, the method comprises:
101. and acquiring the repair priority of the first vulnerability.
102. Acquiring the repair duration matched with the repair priority of the first bug according to the repair priority of the first bug; wherein the repair duration is inversely related to the repair priority.
103. And displaying the first bug and the repairing time length in a repairing task list of the first user according to the repairing priority of the first bug, so that the first user can know the repairing urgency of the first bug according to the repairing time length.
In practical applications, in the process from development to release of software, in order to improve the stability and performance of the software, a tester may test the software before the software is released. The software described in the embodiment of the present application may be an application program (APP), client software, or a web page.
The software is tested by a tester, the software program bug can be detected, and the detected bug is fed back to the software developer to be repaired. Optionally, the tester may upload the detected vulnerabilities to a task management system. The task management system may be installed in a computer device. The computer device may be a terminal device such as a notebook computer, a desktop computer, a tablet computer, or a smart phone, or may be a server device such as a server. In this way, developers can view the vulnerability to be repaired in the task management system. However, developers cannot know the repair urgency of each bug, so that bug repair is not timely, and repair efficiency is affected.
In order to solve the above technical problem, in this embodiment, repair priorities may be set for various vulnerabilities in advance. The repair priority of the vulnerability can be set according to the characteristics of the service associated with the vulnerability. Optionally, the repair priority of the vulnerability may be determined according to multiple dimensions, such as the level of the vulnerability-associated program in the software system, the influence of the vulnerability on the number of users, and the duration of the influence on the use of the users. Optionally, the higher the level of the program associated with the vulnerability in the software system is, the greater the vulnerability affects the number of users, and the longer the duration of the vulnerability affects the use of the users, the higher the repair priority of the vulnerability. Correspondingly, the higher the repair priority of the vulnerability is, the more the vulnerability needs to be modified in time, that is, the higher the repair urgency of the vulnerability is.
Further, in this embodiment, in order to enable the developer to repair the bug in time, different repair durations may also be set for bugs of different repair priorities. Wherein the repair duration of the vulnerability is inversely related to the repair priority thereof. That is, the higher the repair priority of the vulnerability is, the shorter the repair duration is, which indicates that the vulnerability needs to be repaired in time. The repair duration corresponding to the repair priority can be determined according to the historical duration of the vulnerability of which the developer modifies the repair priority. Preferably, the repair duration corresponding to the repair priority is equal to the average of the historical durations of the vulnerabilities of which the developers modify the repair priority.
Further, the corresponding relation between the repair priority and the repair duration of the bug can be preset in the task management system. Based on the correspondence between the repair priority and the repair duration of the bug, in this embodiment, the tester may upload the tested bug to the task management system. Accordingly, for a computer device installed with a task management system, in step 101, a repair priority of a vulnerability may be obtained. Optionally, the repair priority of the vulnerability may be set by a tester. Optionally, the tester may set the repair priority of the bug according to a pre-achieved priority setting standard and according to the situation of the current detected bug. Accordingly, for the computer device, in response to the setting operation of the repair priority for the vulnerability, the set repair priority may be acquired as the repair priority for the vulnerability. Optionally, the repair priority of the vulnerability may be identified with a number. For example, the repair priority is highest, with the priority number 1; the second repair priority, the corresponding priority number 2, and so on. In the following embodiments, for convenience of description, the vulnerability currently uploaded by the tester is defined as a first vulnerability.
Further, in step 102, a repair duration adapted to the repair priority of the first bug may be obtained according to the repair priority of the first bug. Optionally, the repair priority of the first vulnerability may be matched in the correspondence between the repair priority and the repair duration of the vulnerability, so as to obtain the repair duration adapted to the repair priority of the first vulnerability.
Next, in step 103, the first bug and the repair duration of the first bug may be displayed in the repair task list of the first user according to the repair priority of the first bug. Because the repair duration is negatively correlated with the repair priority, the higher the repair priority of the vulnerability is, the higher the repair urgency is. Therefore, the shorter the repair time of the vulnerability is, the higher the repair urgency of the vulnerability is, and the more timely the vulnerability needs to be repaired. Based on this, the first user can know the repair urgency of the vulnerability according to the repair duration of the vulnerability, and then determine the sequence of vulnerability repair according to the repair urgency of the vulnerability and repair the vulnerability in time, so that the vulnerability repair efficiency is improved.
On the other hand, the repair time of the bug can reflect the repair emergency degree of the bug to a certain extent, and the method is also beneficial to determining the sequence of the bugs by a user according to the repair time of the bug, reducing the probability that the user repairs the bug with lower emergency degree firstly, and setting aside the bug with higher repair emergency degree, and being beneficial to improving the stability and quality of software. This is because some bugs with higher urgency of repair may cause software system crash if not repaired in time.
It should be noted that, in this embodiment, the first user mainly refers to a developer of software, to be precise, the first user is a developer that repairs a bug of the software.
In this embodiment, a specific implementation manner that the first bug and the repair duration thereof are displayed in the repair task list of the first user is not limited. Optionally, the higher the priority of the first vulnerability, the more forward its display order in the fix list. Accordingly, the repair priority of the existing bug in the repair task list can be obtained. In the embodiment of the present application, for convenience of description and distinction, an existing vulnerability in the repair task list is defined as a second vulnerability. Wherein the number of the second vulnerabilities is 1 or more. Plural means 2 or more.
Further, the display sequence of the first vulnerability in the repair task list can be determined according to the priority of the first vulnerability and the priority of the second vulnerability; determining a display sequence of the first vulnerability in a repair task list; and adding the first bugs into the repair task list according to the display sequence of the first bugs in the repair task list. Optionally, as shown in fig. 1b, if the repair priority of the first bug is greater than the repair priority of the second bug, the first bug and the repair duration thereof are displayed in front of the second bug. Optionally, if the repair priority of the first bug is smaller than the repair priority of the second bug, the first bug and the repair time thereof are displayed behind the second bug. And if a bug A with the repair priority higher than that of the first bug exists in the second bug and a bug B with the repair priority lower than that of the first bug also exists, displaying the first bug and the repair time duration thereof between the bug A and the bug B.
Further, if the number of the vulnerabilities at the same repair priority is multiple (2 or more than 2), determining the display sequence of the vulnerabilities and the respective repair duration in the repair task list according to the repair task creation time of the vulnerabilities at the same repair priority. The earlier the repair task creating time of the bug with the same repair priority is, the earlier the display sequence of the bug and the repair time of the bug in the repair task list is.
In this embodiment, the bug fix task may also be timed. Optionally, the bug fixing task may be timed from creation of the bug fixing task, and the starting time of the bug fixing task is displayed in the fixing task list. For example, for the first bug, when the first bug and the repair time length thereof are added to the repair list, the repair task of the first bug is timed, and the started time length of the repair task is displayed in the vicinity of the first bug and the repair time length thereof. As shown in fig. 1b, the first bug, the repair time length of the first bug, and the started time length of the repair task of the first bug may be displayed in the same row. Optionally, the bug repair task countdown may be further set, the bug repair time duration is counted down, and the bug repair time duration countdown is displayed in the repair task list, so as to remind the first user to repair the bug as soon as possible.
In the embodiment of the application, in order to enable developers to repair bugs in time, different repair urgency degree prompt information can be set for bugs with different repair priorities. The repair urgency prompt message may prompt the effect of the vulnerability on system performance or the number of users. For example, as shown in fig. 1b, the fix urgency hint information suggests the impact of the vulnerability on the number of users. Further, the corresponding relationship between the priority of the vulnerability and the repair urgency indication information may be preset in the computer device. For the computer equipment, determining repair urgency degree prompt information adaptive to the repair priority of the first bug according to the repair priority of the first bug; and displaying the repair urgency prompt information in a first bug and repair time length associated area in a repair task list. Optionally, the associated region of the first bug and the repair duration may be a region located in the same row as the display region of the first bug and the repair duration.
For the repair task list, header information, i.e., table attribute information, may be set. Correspondingly, the information of the repair duration, the repair urgency degree prompt information, the repair start duration and the repair countdown of the bug can be added to the corresponding list according to the header information.
In the embodiment of the application, the display sequence of the first vulnerability and the second vulnerability in the repair task list can be adjusted according to the repair conditions of the first vulnerability and the second vulnerability. Optionally, the task establishment time and the repair time length of the first vulnerability and the second vulnerability can be taken; judging whether a bug which is not repaired for a long term exists in the first bug and the second bug according to the task establishing time and the repairing time of the first bug and the second bug; if so, adjusting the display sequence of the vulnerabilities which are not repaired at the overdue in the repair task list according to the repair priority and the overdue duration of the vulnerabilities which are not repaired at the overdue, and further adjusting the display sequence of the first vulnerability and the second vulnerability in the repair task list.
In the embodiment of the application, the task management system can manage the repair task and the test task. In this embodiment, after the developer finishes repairing the bug, the developer may upload the repaired bug to the task management system, and the task management system redistributes the repaired bug to the tester for testing to test whether the repair is successful. For the repair of the vulnerability, the repair cycle of the vulnerability includes: the repair duration of the bug and the retest duration after the bug repair is completed.
In order to enable the testers to test the repaired bugs in time, different test durations can be set for the bugs with different repair priorities. Wherein the testing duration of the vulnerability is inversely related to the repair priority thereof. That is, the higher the repair priority of a bug is, the shorter the test duration is, which indicates that the bug needs to be tested in time. The testing time length corresponding to the repair priority can be determined according to the historical time length of the bug of the repair priority tested by the tester, the software release time and the time required for repairing again by the developer if the repair is unsuccessful.
Further, the corresponding relation between the repair priority of the bug and the test duration can be preset in the task management system. Based on the correspondence between the repair priority and the test duration of the bug, in this embodiment, the tester may upload the tested bug to the task management system. Correspondingly, for the computer equipment provided with the task management system, the repairing completion operation aiming at the first bug can be responded, and the test duration adaptive to the complex priority is obtained according to the repairing priority of the first bug; and displaying the first bug and the test duration in a test task list of the second user according to the repair priority of the first bug. For a specific implementation manner of displaying the first bug and the test duration in the test task list, reference may be made to the above-mentioned related content of displaying the first bug and the repair duration in the repair task list, which is not described herein again. In this embodiment, the second user mainly refers to a tester of the software, and more specifically, the second user is a tester that tests the vulnerability of the software.
Because the test duration is inversely related to the repair priority, the higher the repair priority of the vulnerability is, the higher the repair urgency is. Therefore, the shorter the test duration of the bug is, the higher the repair urgency of the bug is, and the more timely the testing is required. Based on the method, the second user can know the repair urgency of the bug according to the test duration of the bug, and then determines the sequence of bug tests according to the repair urgency of the bug, tests the bug in time, and further contributes to improving the bug test efficiency.
Of course, the repair urgency level prompt information adapted to the repair priority level of the first bug is displayed in the test task list. Optionally, the repair urgency indication information is displayed in a first bug and test duration associated area in the test task list. Optionally, the associated region of the first bug and the test duration may be a region located in the same row as the display region of the first bug and the test duration.
Alternatively, for the test task list, header information, i.e., table attribute information, may be set. Correspondingly, the information such as the testing duration and the repair urgency degree prompt information of the bug can be added to the corresponding list according to the header information. Of course, the starting time of the testing task of the bug can be timed, and the starting time of the testing task of the bug is displayed in the testing task list; or, the test duration of the bug may be counted down, and the countdown of the test duration of the bug may be displayed in the test task list, and so on. For the display form of the starting time of the bug test task and the countdown of the bug test time in the test task list, reference may be made to the relevant content of the display form of the starting time of the bug fixing task and the countdown of the bug fixing time in the test task list, which is not described herein again.
It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subject of steps 101 and 102 may be device a; for another example, the execution subject of step 101 may be device a, and the execution subject of step 102 may be device B; and so on.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 101, 102, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.
Accordingly, embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the task management method.
Fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device can be a computer, a smart phone or a wearable device and other terminal devices, and can also be a server and other server side devices. As shown in fig. 2, the electronic apparatus includes: a memory 20a, a processor 20b and a screen 20 c; the memory 20a is used for storing computer programs.
The processor 20b is coupled to the memory 20a for executing a computer program for: acquiring the repair priority of the first vulnerability; acquiring the repair duration matched with the repair priority of the first bug according to the repair priority of the first bug; wherein the repair duration is inversely related to the repair priority; according to the repair priority of the first bug, the first bug and the repair duration are displayed in the repair task list of the first user displayed on the screen 30c, so that the first user can know the repair urgency of the first bug according to the repair duration.
In some embodiments, when obtaining the priority of the first vulnerability, the processor 20b is specifically configured to: in response to a setting operation of the repair priority for the first bug, the set repair priority is acquired as the repair priority for the first bug.
In other embodiments, processor 20b is further configured to: and acquiring the repair priority of the second bug existing in the repair task list. Correspondingly, the processor 20b displays the vulnerability to be repaired and the repair duration in the repair task list, and is specifically configured to: determining the display sequence of the first vulnerability in a repair task list according to the repair priority of the first vulnerability and the second vulnerability; and adding the first vulnerability and the repairing time thereof into the repairing task list according to the display sequence of the first vulnerability in the repairing task list.
In still other embodiments, the processor 20b is further configured to: determining repair urgency degree prompt information adaptive to the repair priority of the first vulnerability according to the repair priority of the first vulnerability; and displaying the repair urgency degree prompt information in the first bug and the associated area of the repair duration in the repair task list.
In some other embodiments, the processor 20b is further configured to: and adjusting the display sequence of the first vulnerability and the second vulnerability in the repair task list according to the repair conditions of the first vulnerability and the second vulnerability.
Further, the processor 20b is further configured to: acquiring task establishing time and repair time of the first vulnerability and the second vulnerability; judging whether a bug which is not repaired for a long term exists in the first bug and the second bug according to the task establishing time and the repairing time of the first bug and the second bug; if so, adjusting the display sequence of the vulnerabilities which are not repaired at the overdue in the repair task list according to the repair priority and the overdue duration of the vulnerabilities which are not repaired at the overdue, so as to adjust the display sequence of the first vulnerability and the second vulnerability in the repair task list.
Optionally, the processor 20b is further configured to: in response to the repair completion operation for the first bug, obtaining a test duration adaptive to the repair priority according to the repair priority of the first bug; wherein the test duration is inversely related to the repair priority; and displaying the first bug and the test duration in the test task list of the second user displayed on the screen 20c according to the repair priority of the first bug, so that the second user can know the test urgency of the first bug according to the test duration.
Optionally, the processor 20b is further configured to: and displaying repair urgency degree prompt information adaptive to the repair priority of the first bug in the associated area of the first bug and the test duration in the test task list.
In some optional embodiments, as shown in fig. 2, the electronic device may further include: communication component 20d, power component 20e, and audio component 20 f. Only some of the components are schematically shown in fig. 2, and it is not meant that the electronic device must include all of the components shown in fig. 2, nor that the electronic device only includes the components shown in fig. 2.
In embodiments of the present application, the memory is used to store computer programs and may be configured to store other various data to support operations on the device on which it is located. Wherein the processor may execute a computer program stored in the memory to implement the corresponding control logic. The memory may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
In the embodiments of the present application, the processor may be any hardware processing device that can execute the above described method logic. Alternatively, the processor may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or a Micro Controller Unit (MCU); programmable devices such as Field-Programmable Gate arrays (FPGAs), Programmable Array Logic devices (PALs), General Array Logic devices (GAL), Complex Programmable Logic Devices (CPLDs), etc. may also be used; or Advanced Reduced Instruction Set (RISC) processors (ARM), or System On Chips (SOC), etc., but is not limited thereto.
In embodiments of the present application, the communication component is configured to facilitate wired or wireless communication between the device in which it is located and other devices. The device in which the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G, 5G or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may also be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, or other technologies.
In the embodiment of the present application, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
In embodiments of the present application, a power supply component is configured to provide power to various components of the device in which it is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.
In embodiments of the present application, the audio component may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals. For example, for devices with language interaction functionality, voice interaction with a user may be enabled through an audio component, and so forth.
The electronic device provided by this embodiment sets the repair priority for the program bug, and each repair priority is configured with an adaptive repair duration. Wherein the repair duration is inversely related to the repair priority. Thus, for the loophole to be repaired, the repair priority of the loophole can be obtained, and the repair duration matched with the repair priority is obtained according to the repair priority of the loophole; and then, displaying the bug and the repair time length of the bug in a repair task list according to the repair priority of the bug. The user can know the repair urgency of the vulnerability according to the repair duration of the vulnerability. Therefore, the time for repairing the bug is displayed so that the developers can know the repair urgency of the bug, the developers can be reminded of repairing the bug in time, and the bug repair efficiency is improved.
It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for task management, comprising:
acquiring the repair priority of the first vulnerability;
acquiring a repair duration matched with the repair priority of the first bug according to the repair priority of the first bug; wherein the repair duration is inversely related to the repair priority;
and displaying the first vulnerability and the repairing time in a repairing task list of a first user according to the repairing priority of the first vulnerability so that the first user can know the repairing urgency of the first vulnerability according to the repairing time.
2. The method of claim 1, wherein obtaining the priority of the first vulnerability comprises:
and in response to the setting operation of the repair priority aiming at the first bug, acquiring the set repair priority as the repair priority of the first bug.
3. The method of claim 1, further comprising:
acquiring the repair priority of a second bug existing in the repair task list;
displaying the vulnerability to be repaired and the repair duration in a repair task list according to the repair priority of the first vulnerability, including:
determining the display sequence of the first vulnerability in the repair task list according to the repair priority of the first vulnerability and the second vulnerability;
and adding the first bugs and the repairing time thereof into the repairing task list according to the display sequence of the first bugs in the repairing task list.
4. The method of claim 1, further comprising:
determining repair urgency degree prompt information adaptive to the repair priority of the first vulnerability according to the repair priority of the first vulnerability;
and displaying the repair urgency degree prompt information in the first bug and the associated area of the repair duration in the repair task list.
5. The method according to any one of claims 1-4, further comprising:
and adjusting the display sequence of the first vulnerability and the second vulnerability in the repair task list according to the repair conditions of the first vulnerability and the second vulnerability.
6. The method of claim 5, further comprising:
acquiring task establishing time and repair time of the first vulnerability and the second vulnerability;
judging whether an overdue unrepaired vulnerability exists in the first vulnerability and the second vulnerability according to the task establishing time and the repairing time of the first vulnerability and the second vulnerability respectively;
if so, adjusting the display sequence of the vulnerability which is not repaired at the overdue period in the repair task list according to the repair priority and the overdue time length of the vulnerability which is not repaired at the overdue period so as to adjust the display sequence of the first vulnerability and the second vulnerability in the repair task list.
7. The method according to any one of claims 1-4, further comprising:
responding to the repairing completion operation aiming at the first bug, and acquiring the testing duration adaptive to the repairing priority according to the repairing priority of the first bug; wherein the test duration is inversely related to the repair priority;
and displaying the first vulnerability and the test time length in a test task list of a second user according to the repair priority of the first vulnerability so that the second user can know the test urgency degree of the first vulnerability according to the test time length.
8. The method of claim 7, further comprising:
and displaying repair urgency degree prompt information adaptive to the repair priority of the first bug in the test task list in the first bug and the associated area of the test duration.
9. An electronic device, comprising: a memory, a processor, and a screen; wherein the memory is used for storing a computer program;
the processor is coupled to the memory for executing the computer program for performing the steps of the method of any of claims 1-8.
10. A computer-readable storage medium having stored thereon computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010778788.4A CN112069503B (en) | 2020-08-05 | 2020-08-05 | Task management method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010778788.4A CN112069503B (en) | 2020-08-05 | 2020-08-05 | Task management method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112069503A true CN112069503A (en) | 2020-12-11 |
| CN112069503B CN112069503B (en) | 2024-09-20 |
Family
ID=73657804
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010778788.4A Active CN112069503B (en) | 2020-08-05 | 2020-08-05 | Task management method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112069503B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626825A (en) * | 2021-07-21 | 2021-11-09 | 南京星云数字技术有限公司 | Security vulnerability management and control method, device, equipment and computer readable medium |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006277153A (en) * | 2005-03-28 | 2006-10-12 | Nec Engineering Ltd | Bug management system |
| US20070266332A1 (en) * | 2006-05-11 | 2007-11-15 | General Dynamics Advanced Information Systems, Inc. | System, method and software for displaying visual cues |
| US20120174230A1 (en) * | 2011-01-04 | 2012-07-05 | Bank Of America Corporation | System and Method for Management of Vulnerability Assessment |
| JP2013065228A (en) * | 2011-09-20 | 2013-04-11 | Hitachi Solutions Ltd | Bug measure priority display system |
| CN103761156A (en) * | 2013-12-13 | 2014-04-30 | 北京同有飞骥科技股份有限公司 | Online repair method aimed at file system |
| CN105635121A (en) * | 2015-12-23 | 2016-06-01 | 赛尔网络有限公司 | Vulnerability severity level distribution statistical method based on manufacturers, device and system |
| CN106611126A (en) * | 2016-12-22 | 2017-05-03 | 西北大学 | Loophole severity assessment and repair method |
| CN107480533A (en) * | 2017-08-08 | 2017-12-15 | 深圳市腾讯计算机系统有限公司 | A kind of method, apparatus and device of leak reparation |
| CN108475365A (en) * | 2015-12-30 | 2018-08-31 | 微软技术许可有限责任公司 | By management role classification and divide priority |
| US20190102286A1 (en) * | 2017-10-03 | 2019-04-04 | International Business Machines Corporation | Visualization of vulnerabilities detected by static application testing |
| CN109656445A (en) * | 2018-12-14 | 2019-04-19 | Oppo广东移动通信有限公司 | Content processing method, device, terminal and storage medium |
| CN110069929A (en) * | 2019-04-18 | 2019-07-30 | 北京神州绿盟信息安全科技股份有限公司 | The construction method and device of loophole Analysis of The Disposal method and its analysis model |
| CN110178151A (en) * | 2017-01-06 | 2019-08-27 | 微软技术许可有限责任公司 | Task main view |
| CN111147491A (en) * | 2019-12-26 | 2020-05-12 | 深信服科技股份有限公司 | Vulnerability repairing method, device, equipment and storage medium |
| US20200162497A1 (en) * | 2018-11-19 | 2020-05-21 | Bmc Software, Inc. | Prioritized remediation of information security vulnerabilities based on service model aware multi-dimensional security risk scoring |
-
2020
- 2020-08-05 CN CN202010778788.4A patent/CN112069503B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006277153A (en) * | 2005-03-28 | 2006-10-12 | Nec Engineering Ltd | Bug management system |
| US20070266332A1 (en) * | 2006-05-11 | 2007-11-15 | General Dynamics Advanced Information Systems, Inc. | System, method and software for displaying visual cues |
| US20120174230A1 (en) * | 2011-01-04 | 2012-07-05 | Bank Of America Corporation | System and Method for Management of Vulnerability Assessment |
| JP2013065228A (en) * | 2011-09-20 | 2013-04-11 | Hitachi Solutions Ltd | Bug measure priority display system |
| CN103761156A (en) * | 2013-12-13 | 2014-04-30 | 北京同有飞骥科技股份有限公司 | Online repair method aimed at file system |
| CN105635121A (en) * | 2015-12-23 | 2016-06-01 | 赛尔网络有限公司 | Vulnerability severity level distribution statistical method based on manufacturers, device and system |
| CN108475365A (en) * | 2015-12-30 | 2018-08-31 | 微软技术许可有限责任公司 | By management role classification and divide priority |
| CN106611126A (en) * | 2016-12-22 | 2017-05-03 | 西北大学 | Loophole severity assessment and repair method |
| CN110178151A (en) * | 2017-01-06 | 2019-08-27 | 微软技术许可有限责任公司 | Task main view |
| CN107480533A (en) * | 2017-08-08 | 2017-12-15 | 深圳市腾讯计算机系统有限公司 | A kind of method, apparatus and device of leak reparation |
| US20190102286A1 (en) * | 2017-10-03 | 2019-04-04 | International Business Machines Corporation | Visualization of vulnerabilities detected by static application testing |
| US20200162497A1 (en) * | 2018-11-19 | 2020-05-21 | Bmc Software, Inc. | Prioritized remediation of information security vulnerabilities based on service model aware multi-dimensional security risk scoring |
| CN109656445A (en) * | 2018-12-14 | 2019-04-19 | Oppo广东移动通信有限公司 | Content processing method, device, terminal and storage medium |
| CN110069929A (en) * | 2019-04-18 | 2019-07-30 | 北京神州绿盟信息安全科技股份有限公司 | The construction method and device of loophole Analysis of The Disposal method and its analysis model |
| CN111147491A (en) * | 2019-12-26 | 2020-05-12 | 深信服科技股份有限公司 | Vulnerability repairing method, device, equipment and storage medium |
Non-Patent Citations (6)
| Title |
|---|
| JARY: "企业安全建设之漏洞管理与运营", pages 2, Retrieved from the Internet <URL:https://www.freebuf.com/articles/security-management/221508.html> * |
| 吕林涛;安存召;李翠;: "面向软件质量的Bug等级评价算法", 计算机工程与设计, no. 23, pages 113 - 116 * |
| 张军: "金融机构漏洞管理实践探索", 网络空间安全, vol. 11, no. 2, 25 February 2020 (2020-02-25), pages 3 - 4 * |
| 江晓莲;郑海山;: "面向安全漏洞管理的高校备案系统设计与实现", 网络安全技术与应用, no. 04, pages 153 - 155 * |
| 祝咏升;陈春雷;: "铁路网络安全威胁及漏洞管理平台研究", 铁路计算机应用, no. 08, 25 August 2020 (2020-08-25), pages 69 - 73 * |
| 胡浩;叶润国;张红旗;常德显;刘玉岭;杨英杰;: "面向漏洞生命周期的安全风险度量方法", 软件学报, no. 05, pages 41 - 57 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626825A (en) * | 2021-07-21 | 2021-11-09 | 南京星云数字技术有限公司 | Security vulnerability management and control method, device, equipment and computer readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112069503B (en) | 2024-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018223717A1 (en) | Webpage front-end testing method, device, system, apparatus and readable storage medium | |
| CN109684188B (en) | Test method and device | |
| US9038054B1 (en) | System and method for automated product version rollback | |
| CN111625443B (en) | Pressure testing method, device, equipment and storage medium | |
| CN105468504B (en) | Program testing method and device | |
| CN112346965A (en) | Test case distribution method, device and storage medium | |
| CN114415973A (en) | Slow disk detection method and device, electronic equipment and storage medium | |
| CN112069503B (en) | Task management method, device and storage medium | |
| CN112699044B (en) | Pressure testing method, equipment and storage medium | |
| CN108073610B (en) | Method and device for realizing webpage loading | |
| CN112346761B (en) | Front-end resource online method, device, system and storage medium | |
| CN113157162B (en) | Method, apparatus, medium and program product for revoking session messages | |
| CN114723866A (en) | Stuck detection method and device | |
| CN111506233B (en) | Method and equipment for providing book information in reading application | |
| CN108108175B (en) | Method and device for gray scale publishing | |
| CN110837467B (en) | Software testing method, device and system | |
| CN112799946B (en) | Buried point and data acquisition method, equipment and storage medium | |
| JP2013531949A (en) | Method and apparatus for enabling keystroke acceleration | |
| CN115757165A (en) | Automatic testing method, device, equipment and storage medium | |
| CN110769017A (en) | Data request processing method and device, storage medium and processor | |
| CN112069057A (en) | Code testing method, device, apparatus and storage medium | |
| CN109960659B (en) | Method and device for detecting application program | |
| CN112286571A (en) | Vulnerability repairing method and device and storage medium | |
| CN112365305B (en) | Ordering method, equipment, system and storage medium | |
| CN112346970B (en) | Method, device and storage medium for testing installation-free application code |
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 |