Information system software maintenance guarantee resource configuration method based on task priority

Abstract

The invention discloses an information system software maintenance guarantee resource configuration method based on task priorities, and belongs to the technical field of software maintenance guarantee resource configuration research. According to the method, the talent team resources for information system software maintenance guarantee and the priority of all software maintenance tasks are firstly determined, then a human assignment model is adopted, the aim that the time of the software maintenance tasks reaches the minimum is taken as the target, and the talent team resources are scientifically and reasonably configured, so that the information system software maintenance cost is reduced, and the software maintenance efficiency is improved. And the information system software maintenance efficiency is improved.

Description

Technical Field

[0001] The present invention relates to a method for configuring information system software maintenance and guarantee resources based on task priorities, and belongs to the technical field of software maintenance and guarantee resource configuration research. Background Art

[0002] Software maintenance is the stage that takes up the largest proportion of time in the software life cycle. During the use of software after delivery, as work requirements and working environment (computer hardware and software, etc.) change, new demands for software maintenance will be put forward, and some software design defects and other problems will be discovered, all of which require maintenance work.

[0003] As information systems grow in size, their software structures become increasingly complex, and the degree of inter-system coupling increases. To meet operational requirements, information system software maintenance must be completed in a relatively short period of time. Furthermore, due to the relatively lagging top-level design of information construction, multiple systems, databases, application platforms, networks, and equipment from multiple vendors coexist within the information construction landscape, dramatically increasing the difficulty and workload of information system software maintenance.

[0004] When the maintenance and support resources for information system software are limited, only by adopting a scientific and practical maintenance and support resource allocation method and agile development method can we scientifically and rationally allocate talent team resources, improve the efficiency of information system software maintenance work, ensure that the information system quickly meets the use requirements, and give full play to the effectiveness of the information system. Summary of the Invention

[0005] The technical problem solved by the present invention is: to overcome the shortcomings of the existing technology, and propose an information system software maintenance and assurance resource configuration method based on task priority. Based on the talent team resources required for information system software maintenance and assurance and the software maintenance task priority, a human resource assignment model is adopted, with the goal of minimizing the time of software maintenance tasks, and the talent team resources are scientifically and reasonably configured to reduce the high maintenance cost of information system software and improve the maintenance efficiency of information system software.

[0006] The technical solution of the present invention is:

[0007] A method for allocating resources for information system software maintenance assurance based on task priorities, comprising:

[0008] Divide software maintenance tasks into four types: corrective maintenance, adaptive maintenance, improvement maintenance, and preventive maintenance, and determine the number of maintenance tasks under each type;

[0009] Determine the talent resources required for software maintenance assurance for each type of maintenance task based on the type and number of maintenance tasks under each type;

[0010] Determine the priority of all maintenance tasks based on the impact and urgency of software maintenance work;

[0011] Based on the priorities of all maintenance tasks, the determined talent team resources are configured to obtain the information system software maintenance guarantee resource configuration results, so as to minimize the time spent on maintenance work.

[0012] Furthermore, the method for determining the talent team resources required for each type of maintenance task to carry out software maintenance assurance is as follows:

[0013] 1) Based on the number of maintenance tasks for each maintenance type, determine the total maintenance workload for software maintenance personnel of each professional and technical level:

[0014] T ikm =N i ×T ikm ′

[0015] Where, T ikm The total number of maintenance tasks completed by a software maintainer with maintenance type i, specialty k and technical level m is N i Total working hours of T ikm ′ The standard working hours for a software maintenance person with professional k and technical level m to complete a software maintenance task under maintenance type i;

[0016] 2) Based on the total software maintenance workload, determine the number of software maintenance personnel of various professions and technical levels required for each maintenance type:

[0017]

[0018] Where M ikm is the total amount of software maintenance work T ikm The number of software maintenance personnel with a major of k and a technical level of m required; H is the personnel's day and night working hours; F is the number of days that a software maintenance personnel with a major of k and a technical level of m performs software maintenance work under maintenance type i specified in the software maintenance task; K1 is the software maintenance personnel utilization coefficient; K2 is the time utilization coefficient;

[0019] 3) Based on the number of software maintenance personnel of various professions and technical levels required for each maintenance type, determine the total number of software maintenance personnel required for the entire information system software maintenance process.

[0020] Furthermore, step 3) includes:

[0021] 3.1) Based on the obtained number of software maintenance personnel of various professions and technical levels required for each maintenance type, determine the number of software maintenance personnel required for each profession under the corresponding maintenance type:

[0022]

[0023] Where p is the total number of technical levels included in specialty k under maintenance type i;

[0024] 3.2) Based on the obtained number of software maintenance personnel required for each maintenance type, determine the number of software maintenance personnel required for the corresponding maintenance type:

[0025]

[0026] Where q is the total number of professions required for maintenance type i;

[0027] 3.3) Based on the obtained number of personnel for each maintenance type, determine the total number of software maintenance personnel required for the entire information system software maintenance process:

[0028]

[0029] Where r is the total number of maintenance types.

[0030] Furthermore, based on the impact and urgency of software maintenance work, the priorities of all maintenance tasks are determined as follows:

[0031] Determine the impact of maintenance tasks based on the number of users or businesses affected by the maintenance work, the impact of software failure modes, and the degree of task completion. The impact is divided into three levels: high, medium, and low, and values ​​are assigned to the three levels.

[0032] Based on the security criticality of information system software and the impact of the importance levels of different software functional modules in the same system on task completion and the severity of the consequences, the urgency of the acceptable delay in completing software maintenance service requests is determined, divided into four levels: urgent, high, medium, and low, and assigned values ​​to the four levels;

[0033] According to the two attributes of the software maintenance task, impact and urgency, define G = [g1, g2] for each software maintenance task, where g1 represents the impact value and g2 represents the urgency value;

[0034] Calculate the impact weight and urgency weight of each software maintenance task, and then calculate the priority η of the software maintenance task:

[0035]

[0036] Where λ j represents the weight of the j-th attribute of G, gj represents the value of the jth attribute of G, and there is

[0037] Obtain the priorities of all software maintenance tasks and sort them in descending order to obtain the priorities of all software maintenance tasks.

[0038] Furthermore, the analytic hierarchy process is used to calculate the impact weight and urgency weight of software maintenance tasks.

[0039] Furthermore, the determined talent team resources are allocated based on task priorities. The allocation method is as follows:

[0040] According to the priorities of all software maintenance tasks, a set of software maintenance tasks with priorities from high to low is obtained, TA = {TA1, TA2, ..., TA n};

[0041] According to the calculated talent team resources, the software maintenance task set corresponding to the maintenance personnel s is TA s , let TA s Elements in TA sc Indicates the maintenance task numbered c undertaken by maintenance personnel s, c t represents the number of all maintenance tasks undertaken by maintenance personnel s;

[0042] Talent team resources are allocated based on the following assumptions:

[0043] For maintenance personnel s, complete the maintenance task TA sc The time is TI sc ; Assume that maintenance personnel s can only perform one maintenance task at a time and can only start the next maintenance task after completing one maintenance task;

[0044] For each maintenance task TA d ,TA d ∈TA, assuming that each maintenance task can only be completed by one maintenance worker without interruption and within a limited time, the relationship between maintenance tasks only exists in sequential and parallel relationships, and for a maintenance task with a sequential constraint relationship, maintenance can only be started after the previous maintenance task is completed.

[0045] Furthermore, with the goal of completing all software maintenance tasks in the shortest time, a mathematical model of the human resource assignment problem is established to allocate the determined talent team resources:

[0046]

[0047] Where, T scIt represents the time taken by maintenance personnel s to complete maintenance task c. When maintenance personnel s does not perform maintenance task c, T sc The value of X is 0; sc Indicates whether maintenance personnel s is assigned to perform maintenance task c. If yes, the value is 1; if no, the value is 0.

[0048]

[0049] T sc =ST sc +TI sc *X sc

[0050] ∑ c ∑ s X sc =n

[0051]

[0052] T sc ≤TLA c

[0053] X sc ={0,1}

[0054]

[0055] Where, ST sc P is the start time of maintenance personnel s to carry out software maintenance task c; c represents the immediate predecessor task set of software maintenance task c, and represents P c The tasks in the TLA have a sequential relationship with the software maintenance task c; n is the number of all software maintenance tasks; c The latest time required to complete maintenance task c.

[0056] Furthermore, the start time ST when maintenance personnel s performs software maintenance task c is sc There are four situations:

[0057] Case 1: The immediate predecessor task set P of software maintenance task c c If it is empty, software maintenance task c is the first task performed by maintenance worker s, then the start time of executing software maintenance task c is the end time of maintenance worker s completing the previous maintenance task;

[0058] Case 2: The immediate predecessor task set P of software maintenance task c c If it is empty, the software maintenance task c is not the first task performed by the maintenance personnel s, then the start time of executing the software maintenance task c is the time when the maintenance personnel s executes the maintenance task set TA sc Software maintenance task c before software maintenance task c′ The maximum completion time;

[0059] The third case: the immediate predecessor task set P of software maintenance task c c is not empty, software maintenance task c is the first task performed by maintenance personnel s, then the start time of executing software maintenance task c is the time when maintenance personnel s completes the immediate predecessor task set P c The final completion time;

[0060] The fourth case: the immediate predecessor task set P of software maintenance task c c If it is not empty, the software maintenance task c is not the first task performed by the maintenance personnel s, then the start time of executing the software maintenance task c is the time when the maintenance personnel s executes the maintenance task set TA. sc Software maintenance task c before software maintenance task c ′ The maximum completion time of software maintenance task c and the predecessor task set P c The maximum value between the last completion time.

[0061] A computer-readable storage medium stores a computer program, wherein the computer program implements the steps of any of the above methods when executed by a processor.

[0062] An electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any of the above methods when executing the computer program.

[0063] The advantages of the present invention compared with the prior art are:

[0064] (1) The present invention determines the talent team resources required for information system software maintenance and assurance from a quantitative perspective through the software maintenance task volume and maintenance type, thereby resolving the uncertainty of information system software maintenance and assurance resources in the prior art.

[0065] (2) The present invention uses the hierarchical analysis method to determine the priority of the maintenance task based on the impact and urgency of the maintenance task, realizes the order of information system software maintenance work, and solves the randomness of information system software maintenance work.

[0066] (3) The present invention configures talent team resources according to task priorities through a human resource assignment model, thereby obtaining a software maintenance guarantee resource configuration method, which minimizes the time required to complete software maintenance tasks, improves the information system software maintenance efficiency, and saves the information system software maintenance cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0068] Figure 1 This is a flow chart of the information system software maintenance and guarantee resource allocation method based on task priority of the present invention;

[0069] Figure 2 This is a diagram showing the resource allocation results for information system software maintenance and assurance according to an embodiment of the present invention. DETAILED DESCRIPTION

[0070] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0071] The present invention proposes a method for allocating resources for information system software maintenance assurance based on task priority. Figure 1 As shown, the following steps are included:

[0072] S1: Determine the number of software maintenance tasks under the software maintenance type based on the content and nature of software maintenance.

[0073] Software maintenance types include corrective maintenance, adaptive maintenance, improvement maintenance, and preventive maintenance. Based on the software maintenance type, the number of software maintenance tasks under each type is determined.

[0074] S2: Determine the talent resources required for information system software maintenance based on the number and nature of software maintenance tasks. The specific methods are as follows:

[0075] S2.1: Based on the maintenance work recorded in the use and maintenance work analysis, determine the number of maintenance tasks for a maintenance type i as N i Total maintenance workload (total working hours) of software maintenance personnel with a certain profession k and a certain technical level m:

[0076] T ikm =N i ×T ikm ′ (1)

[0077] Where, T ikm The number of maintenance tasks completed by a software maintenance person with a certain professional k and a certain technical level m under a certain maintenance type i is Ni Total working hours; N i is the total number of software maintenance tasks included in a maintenance type i; T ikm ′ The standard working hours for a software maintenance personnel with a certain profession k and a certain technical level m to complete a software maintenance task under a certain maintenance type i.

[0078] S2.2: According to the total workload of software maintenance work (i.e. total working hours) T ikm , determine the number of software maintenance personnel with a certain profession k and a certain technical level m required for a certain maintenance type i:

[0079]

[0080] Where M ikm T is the total amount of software maintenance work (i.e. total working hours) under a maintenance type i ikm The required number of software maintenance personnel with a certain profession k and a certain technical level m; H is the personnel's day and night working hours, generally 12 to 16 hours; F is the number of days that software maintenance personnel with a certain profession k and a certain technical level m perform software maintenance work under a certain maintenance type i specified in the software maintenance task; K1 is the software maintenance personnel utilization coefficient, usually calculated at 70% to 90%; K2 is the time utilization coefficient, usually calculated at 80%.

[0081] S2.3: Total software maintenance workload (i.e. total man-hours) T for a maintenance type i ikm The number of software maintenance personnel M required with a certain profession k and a certain technical level m ikm , determine the total software maintenance workload (i.e. total working hours) T under a maintenance type i ikm The number of software maintenance personnel required for a certain profession k:

[0082]

[0083] Where p is the total number of technical levels of software maintenance personnel in a certain profession k under a certain maintenance type i.

[0084] S2.4: Total software maintenance workload (i.e. total man-hours) T for a maintenance type i ikm The number of software maintenance personnel required for a certain specialty k is used to determine the number of software maintenance personnel required for a certain maintenance type i:

[0085]

[0086] Where q is the total number of software maintenance personnel majors included in a maintenance type i.

[0087] S2.5: According to the number of personnel for each maintenance type M i, determine the total number of software maintenance personnel required during the entire information system software maintenance process:

[0088]

[0089] Where r is the total number of maintenance types. Software maintenance types include corrective maintenance, adaptive maintenance, improvement maintenance, and preventive maintenance.

[0090] S3: Prioritize all maintenance tasks for information system software based on the impact and urgency of software maintenance work

[0091] Sort n information system software maintenance tasks by priority, and the result is TA={TA1,TA2,…,TA n The priority of software maintenance tasks is determined by priority, which is achieved in the following way:

[0092] S3.1: The impact of maintenance tasks is determined based on the number of users or businesses affected by the maintenance work, the impact of software failure modes, and the degree of task completion. The impact is divided into three levels: high, medium, and low, with values ​​of 0.8, 0.5, and 0.2 respectively.

[0093] S3.2: The acceptable urgency of delaying the completion of software maintenance service requests shall be determined based on the safety criticality of the information system software, the importance of different software functional modules in the same system, the degree of impact on task completion, and the severity of the consequences. The delays are divided into four levels: urgent, high, medium, and low, with values ​​of 0.8, 0.6, 0.4, and 0.2, respectively.

[0094] S3.3: Define the impact and urgency attributes of the software maintenance task as G = [g1, g2], where g1 represents the impact and g2 represents the urgency. The values ​​of g1 and g2 are determined by S3.1 and S3.2.

[0095] S3.4: Use the AHP method to calculate the weights of impact and urgency, and thus calculate the priority η of the software maintenance task:

[0096]

[0097] Where λ j represents the weight of the j-th attribute of G, g j represents the value of the jth attribute of G, and there is

[0098] S4: Using the human resource assignment model, a software maintenance assurance resource allocation method based on task priority is adopted to allocate talent team resources, and an information system software maintenance assurance resource allocation method is obtained to minimize the time of software maintenance tasks.

[0099] S4.1: For the maintenance tasks TA arranged in order of priority, the talent team resource set M determined by S1 s ={1,2,…,s a}, where s is the maintenance personnel number. Let each maintenance personnel s(s∈M s ) There is a set of tasks arranged in order of maintenance task priority Among them, TA sc Indicates that the maintenance personnel s is responsible for the number c(c∈TA s ) maintenance tasks, c t represents the number of all maintenance tasks undertaken by maintenance personnel s;

[0100] S4.2: For each maintenance personnel s(s∈M s ), complete the maintenance task TA sc (TA sc ∈TA s ) is TI sc Assume that each maintenance worker s can only perform one maintenance task at a time and can only start the next maintenance task after completing one maintenance task;

[0101] S4.3: For each maintenance task TA d (TA d ∈TA), assuming that each maintenance task can only be completed by one maintenance worker without interruption and within a limited time, the relationship between maintenance tasks only exists in sequential and parallel relationships, and for a maintenance task with a sequential constraint, maintenance can only be started after the previous maintenance task is completed;

[0102] S4.4: Under the above assumptions, with the goal of completing all tasks in the shortest possible time, a mathematical model for the human resource assignment problem is established to allocate the determined talent team resources:

[0103] min:T=max s,c {T sc *X sc} (7)

[0104]

[0105] T sc =ST sc +TI sc *X sc (9)

[0106] ∑ c ∑ s X sc =n (10)

[0107]

[0108] T sc ≤TLA c (13)

[0109] X sc ={0,1} (14)

[0110]

[0111] Formula (7) minimizes the time required to complete all maintenance tasks. sc It represents the time taken by maintenance personnel s to complete maintenance task c. When maintenance personnel s does not perform maintenance task c, T sc The value of X is 0; sc Indicates whether maintenance personnel s is assigned to perform maintenance task c. If it is executed, the value is 1, and if not, the value is 0. sc The value of is expressed by formula (14).

[0112] Formulas (8) to (15) are the constraints of Formula (7).

[0113] In formula (8), ST sc P is the start time of maintenance task c by maintenance personnel s; c represents the immediate predecessor task set of maintenance task c, and P c The tasks in have a sequential relationship with maintenance task c. The start time of software maintenance personnel s performing maintenance task c is divided into the following four situations:

[0114] Case 1: Maintenance task c's immediate predecessor task set P c If it is empty, and maintenance task c is the first task performed by maintenance worker s, then the start time of maintenance task c is the end time of the previous maintenance task completed by maintenance worker s;

[0115] Case 2: Maintenance task c's immediate predecessor task set P c If it is empty, the maintenance task c is not the first task performed by the maintenance personnel s, then the start time of the maintenance task c is the time when the maintenance personnel s performs the maintenance task set TA. sc Maintenance task c before maintenance task c ′ The maximum completion time;

[0116] The third case: the immediate predecessor task set P of maintenance task c c If it is not empty, and maintenance task c is the first task performed by maintenance personnel s, then the start time of maintenance task c is the time when maintenance personnel s completes the immediate predecessor task set P. c The final completion time;

[0117] The fourth case: the immediate predecessor task set P of maintenance task c c If it is not empty, maintenance task c is not the first task performed by maintenance personnel s, then the start time of maintenance task c is the time when maintenance personnel s performs maintenance task set TA. sc Maintenance task c before maintenance task c ′ The maximum completion time of maintenance task c and the predecessor task set P c The maximum value between the last completion time.

[0118] Formula (9) is a method for calculating the end time of executing maintenance task c, which is the sum of the start time of maintenance task c and the actual maintenance time. sc It is the time required for maintenance personnel s who has the ability to perform maintenance task c to complete maintenance task c.

[0119] Formula (10) indicates that the sum of all assigned maintenance tasks is the total number of software maintenance tasks n.

[0120] Formula (11) represents the relationship between maintenance tasks and maintenance personnel in the constraint condition S4.3. Each maintenance task can only be completed by one maintenance personnel without interruption and within a limited time.

[0121] Formula (12) indicates that the total number of all maintenance tasks undertaken by maintenance personnel s in the constraint condition S4.1 is c t .

[0122] Formula (13) limits the maintenance time, and it is not possible to complete the maintenance task in an infinite time. c The latest time required to complete maintenance task c.

[0123] Formula (15) represents the total number of maintenance personnel and maintenance tasks in the S4.1 constraint.

[0124] The present invention is described in detail below by way of examples:

[0125] The information system software maintenance and guarantee resource allocation method based on task priority of the present invention, taking a certain command information system software as an example, specifically comprises the following steps:

[0126] S1: Determine the number of software maintenance tasks under each software maintenance type

[0127] According to the content and nature of software maintenance, the number of maintenance tasks for corrective maintenance of a command information system software is 5, and the number of maintenance tasks for completeness maintenance is 2.

[0128] S2: Determine the talent resources required for software maintenance assurance

[0129] S1.1: Identify workforce needs

[0130] The technical level of the talent team is categorized from 1 to 5, with higher numbers representing superior skills. Specialties are divided into maintenance and testing. To ensure rapid system commissioning, three corrective maintenance tasks require maintenance and testing professionals with a technical level of 5, two tasks require maintenance and testing professionals with a technical level of 4, and complete maintenance requires maintenance and testing professionals with a technical level of 4. Highly skilled professionals are responsible for rapidly locating, resolving, and testing faults.

[0131] The standard working hours for maintenance personnel with professional and technical level 5 to complete software maintenance tasks are 1.5 hours, the standard working hours for maintenance personnel with professional and technical level 4 to complete software maintenance tasks are 2 hours, the standard working hours for maintenance personnel with professional and technical level 5 to complete software maintenance tasks are 2 hours, and the standard working hours for maintenance personnel with professional and technical level 4 to complete software maintenance tasks are 3 hours.

[0132] The process of realizing talent team requirements is as follows:

[0133] (1) Determine the total maintenance workload (total man-hours) for each specialty and technical level of corrective maintenance and completeness maintenance:

[0134] Corrective maintenance:

[0135] The total maintenance workload (total working hours) of maintenance personnel with maintenance professional and technical level 5 is: T 115 =4.5h.

[0136] The total maintenance workload (total working hours) of maintenance personnel at maintenance professional and technical level 4 is: T 114 =4h.

[0137] The total maintenance workload (total working hours) of maintenance personnel with a test professional and technical level of 5 is: T 125 =6h.

[0138] The total maintenance workload (total working hours) of maintenance personnel at level 4 of the test professional technical level is: T 124 =6h.

[0139] Completeness maintenance:

[0140] The total maintenance workload (total working hours) of maintenance personnel at maintenance professional and technical level 4 is: T 214 =4h.

[0141] The total maintenance workload (total working hours) of maintenance personnel at level 4 of the test professional technical level is: T 224 =6h.

[0142] (2) Determine the number of maintenance personnel of each profession and technical level for corrective maintenance and completeness maintenance:

[0143] The day and night working hours are 12 hours; under the corrective maintenance specified in the software maintenance tasks, the number of working days for maintenance professional and technical level 5 software maintenance is 1 day, the number of working days for maintenance professional and technical level 4 software maintenance is 1 day, the number of working days for testing professional and technical level 5 software maintenance is 1 day, and the number of working days for testing professional and technical level 4 software maintenance is 1 day; the personnel utilization coefficient and time utilization coefficient of each profession and technical level are calculated as 80%.

[0144] Corrective maintenance:

[0145] The number of maintenance personnel with professional technical level 5 is: M 115 =1 person.

[0146] The number of maintenance personnel with maintenance professional and technical level 4 is: M 114 =1 person.

[0147] The number of maintenance personnel with test professional technical level 5 is: M 125 =1 person.

[0148] The number of maintenance personnel with test professional technical level 4 is: M 124 =1 person.

[0149] Completeness maintenance:

[0150] The number of maintenance personnel with maintenance professional and technical level 4 is: M 214 =1 person.

[0151] The number of maintenance personnel with test professional technical level 4 is: M 224 =1 person.

[0152] Maintenance personnel of each profession and technical level are numbered. Maintenance personnel of level 5 of maintenance profession and technical level are numbered as s M51 , maintenance professional and technical level 4 maintenance personnel number is s M41 、s M42 , the maintenance personnel of the test professional technical level 5 are numbered as s T51 , the number of the two maintenance personnel with the test professional technical level 4 is s T41 、s T42 .

[0153] (3) Determine the number of software maintenance personnel for each specialty: corrective maintenance and completeness maintenance:

[0154] Corrective maintenance: The number of software maintenance personnel required for maintenance is: M 11 =2 people, the number of software maintenance personnel required for testing is: M 12 =2 people.

[0155] Completeness maintenance: The number of software maintenance personnel required for maintenance is: M 21 =1 person, the number of software maintenance personnel required for testing is: M 22 =1 person.

[0156] (4) Determine the number of software maintenance personnel for corrective maintenance and completeness maintenance:

[0157] Corrective maintenance: The number of software maintenance personnel required is: M1 = 4 people.

[0158] Completeness maintenance: The number of software maintenance personnel required is: M2 = 2 people.

[0159] (5) Determine the total number of software maintenance personnel required during the maintenance of a command information system software: M = 6 people.

[0160] S3: Determine the priority of each maintenance task of information system software

[0161] Depend on Figure 2 Maintain the relationship between tasks and the impact and urgency of each task. Use the hierarchical analysis method to calculate the weights of each attribute of software maintenance task 1, task 2, ..., task 7, and then calculate the priority of each task.

[0162] Table 1 Impact and urgency values ​​of various tasks

[0163]

[0164] The weights of the attributes of software maintenance tasks 1, 2, ..., and 7 are calculated using the analytic hierarchy process:

[0165] The attribute weights for task 1 are (0.75, 0.25); the attribute weights for task 2 are (0.875, 0.125);

[0166] The attribute weights for task 3 are (0.75, 0.25); the attribute weights for task 4 are (0.833, 0.167);

[0167] The attribute weights for task 5 are (0.2, 0.8); the attribute weights for task 6 are (0.75, 0.25);

[0168] The attribute weights of task 7 are (0.25, 0.75).

[0169] According to S3, the priorities of software maintenance tasks 1, 2, 3, 4, 5, 6, and 7 are calculated to be 0.6, 0.8, 0.6, 0.6, 0.36, 0.45, and 0.5. Sorting them by priority, the arrangement results are Task 2, Task 1, Task 3, Task 4, Task 6, Task 7, and Task 5.

[0170] According to S4, according to the priority of software maintenance tasks, with the goal of minimizing software maintenance task time while meeting a certain service level, assign maintenance personnel to software maintenance tasks 2, 1, 3, 4, 6, 7, and 5, and determine the order in which each maintenance personnel performs tasks. Configuration as follows Figure 2 As shown, specifically:

[0171] (1) Task 2, Task 1, and Task 3 start maintenance at the same time, and maintenance personnel s M51 、s T51 Perform Task 2, by maintenance personnel s M41 、s T41 Perform Task 1, by maintenance personnel s M42 、s T42 Execute Task 3;

[0172] (2) Then, the maintenance personnel who completed task 2, s M51 、s T51 Execute Task 4;

[0173] (3) Then, the maintenance personnel who completed task 1, s M41 、s T41 Start executing Task 6;

[0174] (4) Next, the maintenance personnel who completed Task 4 M51 、s T51 Start executing Task 7;

[0175] (5) Finally, the maintenance personnel who completed Task 3 M42 、s T42 Start executing Task 5.

[0176] The minimum time required to complete all maintenance tasks is 15.5 man-hours. Without the human resource allocation model, randomly assigning maintenance tasks would require 16.5 man-hours to complete all maintenance tasks. Therefore, using the human resource allocation model to allocate talent resources can shorten the maintenance time of a command information system software, improve software maintenance efficiency, enable the command information system software to be put into use as soon as possible, and minimize the impact on task completion.

[0177] The above-described embodiments are only preferred specific implementations of the present invention. Common changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for allocating resources for information system software maintenance assurance based on task priority, characterized in that: include: Divide software maintenance tasks into four types: corrective maintenance, adaptive maintenance, improvement maintenance, and preventive maintenance, and determine the number of maintenance tasks under each type; Determine the talent resources required for software maintenance assurance for each type of maintenance task based on the type and number of maintenance tasks under each type; Determine the priority of all maintenance tasks based on the impact and urgency of software maintenance work; Based on the priorities of all maintenance tasks, the determined talent team resources are configured to obtain the information system software maintenance guarantee resource configuration results, so as to minimize the time spent on maintenance work.

2. The method for allocating information system software maintenance resources based on task priority according to claim 1, characterized in that: The method for determining the talent team resources required for each type of maintenance task to perform software maintenance assurance is: 1) Based on the number of maintenance tasks for each maintenance type, determine the total maintenance workload for software maintenance personnel of each professional and technical level: T ikm =N i ×T ikm ′ Where, T ikm The total number of maintenance tasks completed by a software maintainer with maintenance type i, specialty k and technical level m is N i Total working hours of T ikm ′ The standard working hours for a software maintenance person with professional k and technical level m to complete a software maintenance task under maintenance type i; 2) Based on the total software maintenance workload, determine the number of software maintenance personnel of various professions and technical levels required for each maintenance type: Where M ikm is the total amount of software maintenance work T ikm The number of software maintenance personnel with a major of k and a technical level of m required; H is the personnel's day and night working hours; F is the number of days that a software maintenance personnel with a major of k and a technical level of m performs software maintenance work under maintenance type i specified in the software maintenance task; K1 is the software maintenance personnel utilization coefficient; K2 is the time utilization coefficient; 3) Based on the number of software maintenance personnel of various professions and technical levels required for each maintenance type, determine the total number of software maintenance personnel required for the entire information system software maintenance process.

3. The method for allocating information system software maintenance resources based on task priority according to claim 2, characterized in that: Step 3) includes: 3.1) Based on the obtained number of software maintenance personnel of various professions and technical levels required for each maintenance type, determine the number of software maintenance personnel required for each profession under the corresponding maintenance type: Where p is the total number of technical levels included in specialty k under maintenance type i; 3.2) Based on the obtained number of software maintenance personnel required for each maintenance type, determine the number of software maintenance personnel required for the corresponding maintenance type: Where q is the total number of professions required for maintenance type i; 3.3) Based on the obtained number of personnel for each maintenance type, determine the total number of software maintenance personnel required for the entire information system software maintenance process: Where r is the total number of maintenance types.

4. The method for allocating information system software maintenance resources based on task priority according to claim 1, characterized in that: Determine the priority of all maintenance tasks based on the impact and urgency of software maintenance work, specifically: Determine the impact of maintenance tasks based on the number of users or businesses affected by the maintenance work, the impact of software failure modes, and the degree of task completion. The impact is divided into three levels: high, medium, and low, and values ​​are assigned to the three levels. Based on the security criticality of information system software and the impact of the importance levels of different software functional modules in the same system on task completion and the severity of the consequences, the urgency of the acceptable delay in completing software maintenance service requests is determined, divided into four levels: urgent, high, medium, and low, and assigned values ​​to the four levels; According to the two attributes of the software maintenance task, impact and urgency, define G = [g1, g2] for each software maintenance task, where g1 represents the impact value and g2 represents the urgency value; Calculate the impact weight and urgency weight of each software maintenance task, and then calculate the priority η of the software maintenance task: Where λ j represents the weight of the j-th attribute of G, g j represents the value of the jth attribute of G, and there is Obtain the priorities of all software maintenance tasks and sort them in descending order to obtain the priorities of all software maintenance tasks.

5. The method for allocating information system software maintenance resources based on task priority according to claim 4, characterized in that: The analytic hierarchy process is used to calculate the impact weight and urgency weight of software maintenance tasks.

6. The method for allocating information system software maintenance resources based on task priority according to claim 1, characterized in that: Allocation of identified talent resources based on task priorities is done as follows: According to the priorities of all software maintenance tasks, a set of software maintenance tasks with priorities from high to low is obtained, TA = {TA1, TA2, ..., TA n }; According to the calculated talent team resources, the software maintenance task set corresponding to the maintenance personnel s is TA s , let TA s Elements in TA sc Indicates the maintenance task numbered c undertaken by maintenance personnel s, c t represents the number of all maintenance tasks undertaken by maintenance personnel s; Talent team resources are allocated based on the following assumptions: For maintenance personnel s, complete the maintenance task TA sc The time is TI sc ; Assume that maintenance personnel s can only perform one maintenance task at a time and can only start the next maintenance task after completing one maintenance task; For each maintenance task TA d ,TA d ∈TA, assuming that each maintenance task can only be completed by one maintenance worker without interruption and within a limited time, the relationship between maintenance tasks only exists in sequential and parallel relationships, and for a maintenance task with a sequential constraint relationship, maintenance can only be started after the previous maintenance task is completed.

7. The method for allocating information system software maintenance resources based on task priority according to claim 6, characterized in that: With the goal of completing all software maintenance tasks in the shortest time, a mathematical model for the human resource assignment problem is established to allocate the determined talent team resources: Where, T sc It represents the time taken by maintenance personnel s to complete maintenance task c. When maintenance personnel s does not perform maintenance task c, T sc The value of X is 0; sc Indicates whether maintenance personnel s is assigned to perform maintenance task c. If yes, the value is 1; if no, the value is 0. T sc =ST sc +TI sc *X sc ∑ c ∑ s X sc =n T sc ≤TLA c X sc ＝{0,1} Where, ST sc P is the start time of maintenance personnel s to carry out software maintenance task c; c represents the immediate predecessor task set of software maintenance task c, and represents P c The tasks in the TLA have a sequential relationship with the software maintenance task c; n is the number of all software maintenance tasks; c The latest time required to complete maintenance task c.

8. The method for allocating information system software maintenance resources based on task priority according to claim 7, characterized in that: The start time ST when maintenance personnel s performs software maintenance task c sc There are four situations: Case 1: The immediate predecessor task set P of software maintenance task c c If it is empty, software maintenance task c is the first task performed by maintenance worker s, then the start time of executing software maintenance task c is the end time of maintenance worker s completing the previous maintenance task; Case 2: The immediate predecessor task set P of software maintenance task c c If it is empty, the software maintenance task c is not the first task performed by the maintenance personnel s, then the start time of executing the software maintenance task c is the time when the maintenance personnel s executes the maintenance task set TA sc Software maintenance task c before software maintenance task c ′ The maximum completion time; The third case: the immediate predecessor task set P of software maintenance task c c is not empty, software maintenance task c is the first task performed by maintenance personnel s, then the start time of executing software maintenance task c is the time when maintenance personnel s completes the immediate predecessor task set P c The final completion time; The fourth case: the immediate predecessor task set P of software maintenance task c c If it is not empty, the software maintenance task c is not the first task performed by the maintenance personnel s, then the start time of executing the software maintenance task c is the time when the maintenance personnel s executes the maintenance task set TA. sc Software maintenance task c before software maintenance task c ′ The maximum completion time of software maintenance task c and the predecessor task set P c The maximum value between the last completion time.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

Images