Support apparatus, support method, and support program

Abstract

To support proper determination of priority of development items in view of a system.SOLUTION: A support apparatus according to the present invention has: a storage device for storing development item information including development items for a target system accessed by a plurality of users in a predetermined entrepreneur and their priority; and a processing apparatus for executing an acquisition process of acquiring information on an active user as a user currently accessing the target system, a priority updating process of updating priority of each of development items included in the development item information on the basis of an access mode of the active user, and an output process for outputting the updated priority.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an assistance device, an assistance method, and an assistance program. [Background technology]

[0002] In projects that design and develop digital solutions to solve organizational challenges, such as those of companies, development priorities are managed and determined before proceeding. However, when developing applications, development teams tend to focus on the functional requirements of the digital solution first, and if the person in charge does not have the know-how to develop infrastructure or non-functional requirements, it is difficult to balance the development of functional and non-functional requirements. Furthermore, because customer needs and issues to be addressed change constantly, it is difficult to appropriately determine what to prioritize with limited resources.

[0003] Patent document 1 discloses an update program application decision support device that provides decision support information based on the importance of the update program as well as system environment information and user application status when deciding whether to apply a software update program to a computer. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2023-136145 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-mentioned technology has a problem in that it is difficult to appropriately determine the priorities of system development items, including functional and non-functional requirements, in digital solutions.

[0006] The present invention has been made in consideration of the above circumstances, and its purpose is to provide an assistance device, assistance method, and assistance program that can assist in appropriately determining the priority of development items for a system. [Means for solving the problem]

[0007] One aspect of the present invention for solving the above problem is a support device that includes a storage device that stores development item information including each development item and its priority for a target system accessed by multiple users at a specified business operator, and a processing device that executes an acquisition process that acquires information about active users who are currently accessing the target system, a priority update process that updates the priority of each development item included in the development item information based on the access patterns of the active users, and an output process that outputs the updated priorities. [Effects of the Invention]

[0008] According to the present invention, it is possible to assist in appropriately determining the priorities of development items for a system. Configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of the configuration of a development management support system. [Figure 2] FIG. 10 is a diagram illustrating an example of an end-user information table. [Figure 3] FIG. 10 is a diagram illustrating an example of a backlog preset table. [Figure 4] FIG. 2 is a process flow diagram illustrating an outline of the process performed by the development management support device. [Figure 5] FIG. 10 illustrates an example of a development item management table. [Figure 6] FIG. 10 illustrates an example of a failure backlog table. [Figure 7] FIG. 10 is a process flow diagram illustrating details of a priority update process. [Figure 8] FIG. 10 is a diagram illustrating an example of an updated development item management table. [Figure 9] FIG. 10 is a diagram showing a first example of a priority presentation screen. [Figure 10] FIG. 10 is a diagram showing a second example of a priority presentation screen. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings. In the following explanation, various types of information may be described using expressions such as "table," "list," and "queue," but the various types of information may also be expressed using data structures other than these. To indicate that the information is not dependent on the data structure, "XX table," "XX list," etc. may be referred to as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable. When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted. Furthermore, in the following description, processing performed by executing a program may be described, but the program is executed by a processor (e.g., a CPU or a GPU) to perform the specified processing while appropriately using storage resources (e.g., a memory) and / or interface devices (e.g., a communication port), and therefore the subject of the processing may be the processor. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be any computing unit, and may include a dedicated circuit (e.g., an FPGA or an ASIC) that performs a specific processing. A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0011] <Development management support system> FIG. 1 is a diagram showing an example of the configuration of a development management support system 1. The development management support system 1 is an information processing system that supports management in projects that are responsible for the design and development of systems (for example, applications). In this embodiment, an information processing system related to a digital solution to be introduced to a specified business entity (organization) such as a company or an association will be used as the system to be developed (hereinafter, sometimes referred to as the "target system"). The target system has already been introduced and is running at the business entity, and multiple end users eU access and use the digital solutions related to the target system (applications, programs, databases, OS (Operating System), etc.).

[0012] 1, the development management support system 1 includes a development management support device 10 (support device) and a user terminal 20. The development management support device 10 and the user terminal 20 are communicably connected to each other via a wired or wireless communication network N such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line.

[0013] The user terminal 20 is an information processing device used by a person in charge of managing development items of the target system (for example, a product owner), and is, for example, a personal computer, a tablet terminal, or a smartphone.

[0014] The development management support device 10 is an information processing device that supports the management of development related to a target system. The development management support device 10 includes, as an example, a processing device 11 such as a CPU (Central Processing Unit), a storage device 12 such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), a memory 13 such as a RAM (Random Access Memory) or a ROM (Read Only Memory), an input device 14 such as a keyboard, a mouse, or a touch panel, an output device 15 such as a display or a printer, and a communication device 16 configured with a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like. The processing device 11, the storage device 12, the memory 13, the input device 14, the output device 15, and the communication device 16 are interconnected via a bus.

[0015] The storage device 12 stores a system log information table 300, an end user information table 400, a backlog preset table 500, a fault backlog table 600 (response information) described later, and a development item management table 700 (development item information) described later.

[0016] The system log information table 300 is a database that stores various logs related to the target system. For example, the system log information table 300 stores multiple log files that are periodically transmitted from the target system. The log files also record operation information (e.g., the type of failure, the date and time of occurrence, etc.) related to the occurrence of events (including failures, etc.) in the target system.

[0017] (End user information table) FIG. 2 is a diagram showing an example of an end user information table. The end user information table 400 is a database that accumulates the usage history of all end users eU who use the digital solution of the target system. The end user information table 400 has the following data items: end user ID 401, in which the end user's identification information is set; used solution 402, in which the digital solution used by the end user is set; status 403, in which the usage status of the used solution (e.g., logged out, active, etc.) is set; and timestamp 404, in which the timestamp of status 403 is set. The usage status "active" indicates that the digital solution of the target system is being used (e.g., logged in) during a specified period (e.g., one hour, one day, one month, etc.). The end user information table 400 is automatically updated whenever the usage status of each end user eU who uses the target system changes.

[0018] (Backlog preset table) FIG. 3 is a diagram showing an example of a backlog preset table. The backlog preset table 500 is a database that stores general-purpose backlogs that can be added in advance from the backlog (development items) of the system development of the target system. The backlog preset table 500 has the following data items: development ID 501, in which identification information of the development item is set; development item 502, in which the content of the development item is set; and development cost 503, in which the cost required to develop the development item is set. The development items include development items of functional requirements and development items of non-functional requirements. Functional requirements are functional requirements required by customers (businesses) when building the target system. On the other hand, non-functional requirements are non-functional requirements such as availability, performance, scalability, operability, maintainability, migration, security, system environment, ecology, etc.

[0019] The development management support device 10 realizes the following functional units by having the CPU 11 read out a program stored in the storage device 12 into the RAM of the memory 13 and execute it: a fault monitoring unit 101, an end user management unit 102, a threshold management unit 103, a development value calculation unit 104, a backlog addition unit 105, a priority update unit 106, an information search unit 107, an information update unit 108, an input operation unit 109, and a display unit 110.

[0020] The fault monitoring unit 101 refers to the system log information table 300, monitors the health or performance of the target system based on changes in the system log, and executes fault detection processing to detect faults that occur in the target system. Faults that can occur in the target system include, for example, abnormalities related to non-functional requirements, such as system downtime.

[0021] The end user management unit 102 executes an acquisition process by referencing the end user information table 400 to acquire information on end users eU whose usage status in the target system is "active" (hereinafter, sometimes referred to as "active end users"). Active end users are users who are currently accessing the target system. Based on the acquired information, the end user management unit 102 then monitors the access behavior of active end users in the target system (for example, increase / decrease, access frequency, access time, etc.).

[0022] The threshold management unit 103 monitors whether the occurrence of a failure (frequency of occurrence, scale of occurrence, number of occurrences, etc.) exceeds a predetermined threshold.

[0023] When the occurrence of a failure exceeds a threshold, the development value calculation unit 104 obtains the development cost required for the backlog (development item) to correct the occurrence from the backlog preset table 500, and calculates the development value of the backlog (development item) to correct the failure based on the obtained development cost and the net profit (profit and loss) generated by the access behavior of active end users due to the occurrence of the failure (in this embodiment, an increase or decrease in the number of active end users). Note that in this embodiment, the profit and loss due to an increase or decrease in the number of active end users is the amount of loss incurred or increased profit per unit time.

[0024] The backlog addition unit 105 refers to the fault backlog table 600 to identify a development item to correct the fault that has occurred, and if the identified development item is not included in the development item management table 700, executes an addition process to add the identified development item to the development item management table 700.

[0025] The priority update unit 106 executes a priority update process for updating the priority of each development item in the development item management table 700 based on the development value of the development item that will correct the problem that has occurred.

[0026] The information search unit 107 searches for various types of information from the storage device 12 or an external device via a network.

[0027] The information update unit 108 updates various pieces of information stored in the storage device 12 .

[0028] The input operation unit 109 receives input from the user via the input device 14 .

[0029] The display unit 110 displays various information on the output device 15. For example, the display unit 110 executes an output process for outputting the updated priority of each development item.

[0030] The programs that realize the functions of the fault monitoring unit 101, end user management unit 102, threshold management unit 103, development value calculation unit 104, backlog addition unit 105, priority update unit 106, information search unit 107, information update unit 108, input operation unit 109, and display unit 110 may be pre-recorded on an external storage medium, or may be introduced when needed via a predetermined communication network. Furthermore, the programs may be recorded on, for example, a portable or fixed recording medium and distributed. Next, the processing performed by the development management support device 10 will be described.

[0031] <Processing Overview> 4 is a processing flow diagram illustrating an outline of processing performed by the development management support device 10. The processing shown in this diagram is executed, for example, when a predetermined input is made to the development management support device 10 by a person in charge (for example, a product owner), or at a predetermined timing (for example, a predetermined time or a predetermined time interval).

[0032] First, the development management support device 10 determines a target system to be developed (S101). For example, the development management support device 10 receives a selection input of the target system from a person in charge (for example, a product owner).

[0033] Next, the development management support device 10 acquires the development items of the determined target system. For example, the development management support device 10 accepts, from the person in charge, a selection input of development items to be applied to the target system (for example, development items related to functions to be added to or modified in the target system) from the development items registered in the backlog preset table 500. Then, the development management support device 10 sets the acquired development items in the development item management table 700 (S102).

[0034] (Development item management table) 5 is a diagram showing an example of a development item management table. The development item management table 700 is a database for managing development items of a target system. The development item management table 700 has the following data items: priority 701, which sets the priority of the development item; development item ID 702, which sets the identification information of the development item; development content 703, which sets the development content of the development item; development value 704, which sets the development value of the development item; and development cost 705, which sets the cost required to develop the development item. The priority 701 and development value 704 may be set and registered by the person in charge in the processing of S102. The development item management table 700 is updated as needed depending on the development status.

[0035] Next, the development management support device 10 receives from the person in charge the registration (setting input) of faults that may occur in the target system and thresholds related to the faults (for example, the frequency of fault occurrence, the number of times the fault occurs, or the scale of the fault, etc.) (S103).

[0036] Next, the development management support device 10 accepts from the person in charge a registration (setting input) of a backlog (development item) to be added to the development item management table 700 when the number of detected failures exceeds a threshold (S104). The development management support device 10 sets the information registered in S103 and S104 in the failure backlog table 600.

[0037] (Fault backlog table) 6 is a diagram showing an example of a fault backlog table. The fault backlog table 600 is a database that manages faults that may occur in the target system and a backlog (such as functions or items that require development or improvement) for correcting (resolving) the faults. The fault backlog table 600 has the following data items: fault 601, which sets the content of the fault; threshold 602, which sets the threshold for adding the backlog to the development item management table 700; backlog 603, which sets the backlog; and development cost 604, which sets the cost required to develop the backlog. The backlog set in the fault backlog table 600 is, for example, a development item for general-purpose non-functional requirements.

[0038] Next, the development management support device 10 executes a priority update process to update the development item management table 700 in response to a failure that has occurred in the target system (S105), and then ends the process. Note that the development management support device 10 may periodically repeat the priority update process while the target system is in operation.

[0039] <Priority update process> 7 is a process flow diagram illustrating the details of the priority update process, which is the details of the priority update process in S105 described above.

[0040] First, the fault monitor unit 101 monitors the data of the target system by referring to the system log information table 300 (S201).

[0041] Next, the fault monitoring unit 101 determines whether or not a fault has occurred in the target system based on the monitored data (S202). If no fault has occurred (S202: No), the fault monitoring unit 101 ends this priority update process.

[0042] On the other hand, when a failure occurs (S202: Yes), the threshold management unit 103 determines whether the occurrence of the failure is equal to or greater than the threshold set in the failure backlog table 600 (S203). For example, in the example shown in Fig. 6, when the failure is "server down", the failure monitoring unit 101 determines that the threshold is exceeded when the server down occurs at least once per hour. If the occurrence of failures is less than the threshold (S203: No), this priority update process is terminated.

[0043] On the other hand, if the occurrence of a problem is equal to or greater than the threshold (S203: Yes), the backlog adding unit 105 searches the problem backlog table 600 for a backlog (development item) that corrects the problem (S204).

[0044] Next, the backlog adding unit 105 determines whether the searched backlog has already been registered in a development item in the development item management table 700 (S205). If the extracted backlog has been registered in the development item management table 700 (S205: Yes), the backlog adding unit 105 proceeds to the processing of S210.

[0045] On the other hand, if the extracted backlog is not registered in the development item management table 700 (S205: No), the backlog adding unit 105 refers to the backlog preset table 500 and adds the searched backlog to the development item management table 700 (S206).

[0046] In parallel with the processing of S204 to S206, the end user management unit 102 refers to the end user information table 400 and extracts active end users who accessed the target system before and after the occurrence of the failure (S207).

[0047] Next, the end user management unit 102 calculates the increase or decrease in the number of active end users before and after the occurrence of the failure (the increase or decrease in the number of active end users due to the failure) (S208). For example, the end user management unit 102 calculates the number of end users eU that became inactive due to the occurrence of the failure.

[0048] Next, the end user management unit 102 multiplies (multiplies) the increase or decrease in the number of active end users by the user unit price, which is the profit per user, and the period until the current scheduled completion date of the backlog for correcting the problem, to calculate the profit (profit or loss) to be obtained by using up the backlog for correcting the problem (e.g., system modification, etc.) (S209). For example, in the event of a "server down" problem, the end user management unit 102 calculates the profit or loss to be obtained by using up the backlog for "server strengthening" by multiplying the number of end users eU that became inactive due to the problem (number of reduced users), the user unit price, and the period (number of reduced users x user unit price x period). Note that, if the scheduled completion date of the development is undecided, the end user management unit 102 may assume that the scheduled completion date of the development is the case where the backlog for correcting the problem is set to the lowest priority (i.e., where the backlog is used up after all development items registered in the development item management table 700 are completed).

[0049] Next, the development value calculation unit 104 calculates the development value of the backlog for correcting the problem by dividing the calculated profit and loss by the development cost of the backlog for correcting the problem (S210).

[0050] Next, the priority update unit 106 updates the priority of each development item registered in the development item management table 700 based on the calculated development value (S211). Specifically, the priority update unit 106 sets the priority of a development item with a high development value higher than the priority of a development item with a low development value.

[0051] (Development item management table) Fig. 8 is a diagram showing an example of the development item management table after updating. In the example shown, a record of the development content "Server Enhancement" in the first row has been added with a priority of "1" to the data example shown in Fig. 5. This is because the development value of the development content "Server Enhancement" is greater than the other development items "Linkage with System X" and "Addition of information registration function".

[0052] Next, the display unit 110 displays a priority presentation screen presenting the updated priorities of each development item on the user terminal 20 (S212), after which the priority update process ends.

[0053] (Priority presentation screen) 9 is a diagram showing a first example of a priority presentation screen. The priority presentation screen 800 shown in this figure has an area for displaying a list of data for each item in the development item management table 700 in tabular form. That is, the display unit 110 displays a list of the priority 801, development ID 802, development content 803, development value 804, development cost 805, etc. of each development item registered in the development item management table 700 on the priority presentation screen 800.

[0054] (Priority presentation screen) 10 is a diagram showing a second example of a priority presentation screen. The priority presentation screen 900 shown in this figure includes a first area 910 that displays development items that are in planning (Planning) and the person in charge thereof, a second area 920 that displays development items that are in progress (In Progress) and the person in charge thereof, and a third area 930 that displays development items that have been completed (Done) and the person in charge thereof. The priority presentation screen 900 presents the priority of each development item in the form of a board arranged in the Kanban method to make it easy for the person in charge to manage. When the priority presentation screen 900 is displayed, the development item management table 700 has data items for the progress status of the development item (Planning, Progress, Development Completed, etc.) and the person in charge.

[0055] The display unit 110 may display development items with higher priority in preference to development items with lower priority on the priority presentation screens 800 and 900. "Displaying with priority" includes displaying development items in order from highest priority to lowest priority, or highlighting development items with higher priority. "Displaying with emphasis" includes changing the display color, changing the font size, changing the background color, or adding a mark, etc.

[0056] Furthermore, in the above-described flow, the processes of S203 to S206 and the processes of S207 to S209 are executed in parallel, but this is not limited to this. The processes of S207 to S209 may be executed after S203 to S206, or the processes of S207 to S209 may be executed before the processes of S203 to S206.

[0057] As described above, the development management support device 10 of this embodiment stores development item information (development item management table 700) including each development item and its priority for a target system accessed by multiple users (end users eU) at a specified business operator, and executes an acquisition process to acquire information about active users who are currently accessing the target system, a priority update process to update the priority of each development item included in the development item information based on the access pattern of the active users, and an output process to output the updated priorities.

[0058] In other words, the development management support device 10 of this embodiment automatically updates the priority of each development item based on the access patterns of active users of the target system (e.g., an increase or decrease in the number of active users), thereby assisting system developers in appropriately determining the priority of development items for the system.

[0059] In addition, the development management support device 10 of this embodiment stores development item information including each development item of functional requirements and non-functional requirements for a target system accessed by multiple users at a specified business operator and its priority, executes a fault detection process to detect a fault that has occurred in the target system, and in a priority update process, updates the priority of the development item of the non-functional requirements that corrects the fault that has occurred based on the increase or decrease in the number of active users due to the fault.

[0060] This allows the priority of development items for non-functional requirements to correct the problem to be appropriately determined according to the increase or decrease in the number of active users due to the problem. Therefore, even if the person in charge (e.g., product owner) does not have know-how related to the development of infrastructure or non-functional requirements, support can be provided to appropriately advance the development of functional and non-functional requirements.

[0061] Furthermore, in the priority update process, the development management support device 10 of this embodiment updates the priority of the development item for correcting the problem that has occurred, based on the profit or loss of the business operator due to an increase or decrease in the number of active users caused by the problem that has occurred.

[0062] This allows the priority of each development item to be appropriately determined, taking into consideration the profit or loss of the business operator due to the occurrence of a failure.

[0063] Furthermore, in the priority update process, the development management support device 10 of this embodiment updates the priority of the development item that corrects the occurred fault based on the profit or loss of the business operator due to an increase or decrease in the number of active users caused by the occurred fault, and the development cost related to the development item that corrects the occurred fault.

[0064] This allows the priorities of development items for correcting obstacles to be appropriately determined based on their development value.

[0065] Furthermore, in the priority update process, the development management support device 10 of this embodiment calculates profit and loss based on the profit and loss per unit number of users, the period until the scheduled completion of development of the development item that corrects the problem that has occurred, and the increase or decrease in the number of active users, and updates the priority of the development item that corrects the problem that has occurred based on the calculated profit and loss and development cost.

[0066] This allows the priority of development items for correcting the problems to be calculated taking into account deadlines and costs, that is, cost performance.

[0067] Furthermore, in the priority update process, the development management support device 10 of this embodiment assigns a higher priority to development items with a high development value, which is the value obtained by dividing profit and loss by development cost, than to development items with a low development value.

[0068] This allows development items with high development value to be given a higher priority, allowing the system developer to more appropriately determine the priority of each development item.

[0069] Furthermore, the development management support device 10 of this embodiment stores correspondence information (fault backlog table 600) that associates faults with development items that correct the faults, and if the development item that corrects the fault that has occurred is not included in the development item information (development item management table 700), it refers to the correspondence information and executes an addition process that adds the development item that corrects the fault that has occurred to the development item information.

[0070] As a result, if a development item (backlog) for correcting an occurred problem is not included in the development item management table 700, the backlog can be automatically added to the development item management table 700 and added to the development targets.

[0071] Furthermore, in the output process, the development management support device 10 of this embodiment displays development items with higher priority in preference to development items with lower priority.

[0072] This allows the person in charge (for example, the product owner) to easily identify high-priority development items.

[0073] The present invention is not limited to the above-described embodiments, and can be implemented using any components within the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the characteristics of the invention are not impaired. Furthermore, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of ​​the present invention are also included within the scope of the present invention.

[0074] For example, part of the hardware provided in each device of this embodiment may be provided in another device.

[0075] Furthermore, each program of the development management support device 10 or the user terminal 20 may be provided in another device, a certain program may consist of multiple programs, or multiple programs may be integrated into one program. Furthermore, the development management support device 10 may be realized in a cloud environment, an on-premise environment, an edge environment, or the like.

[0076] Furthermore, in the above-described embodiment, quantitative evaluation using an increase or decrease in the number of active end users has been described, but the analysis of information related to end users eU is not limited to this, and may also be data such as system responsiveness, or specific messages obtained from end users eU. For example, comments obtained from end users eU may be processed using natural language processing or a large-scale language model and reflected in the estimation of KPIs.

[0077] Furthermore, in the above-described embodiment, an increase or decrease in the number of active end users has been described as an example of the access mode of active end users, but the access mode is not limited to this and may be access frequency, access time, etc. When the access mode is access frequency or access time, the development management support device 10 may calculate profit or loss due to the occurrence of a failure based on an increase or decrease in access frequency or access time.

[0078] Furthermore, in the above-described embodiment, the granularity of the development target is measured in units of "development items" that make up "digital solutions," but depending on the scale and characteristics of the system, it may also be measured in units of "functions" or "program modules" that can be reused as software components.

[0079] Furthermore, the process of determining whether to implement the prioritized development items in the development management support system 1, or the implementation itself, may be performed by a human being or automatically by a machine (computer). [Explanation of symbols]

[0080] 1. Development management support system 10 Development management support device 20 User terminal 101 Fault Monitoring Department 102 End User Management Department 103 Threshold Management Unit 104 Development Value Calculation Department 105 Backlog Addition Section 106 Priority update section 107 Information Search Department 108 Information update department 109 Input operation section 110 Display section 300 System Log Information Table 400 End User Information Table 500 Backlog Preset Table 600 Defect Backlog Table 700 Development Item Management Table

Claims

1. a storage device that stores development item information including each development item and its priority for a target system accessed by a plurality of users of a predetermined business; an acquisition process for acquiring information on active users who are currently accessing the target system; a priority update process for updating the priority of each development item included in the development item information based on the access patterns of the active users; an output process for outputting the updated priority; A support device comprising a processing unit that executes the above.

2. the storage device stores development item information including each development item of functional requirements and non-functional requirements for a target system accessed by a plurality of users of a predetermined business operator and its priority; The processing device includes: Execute a fault detection process to detect a fault that has occurred in the target system; In the priority update process, the priority of the development item of the non-functional requirement for correcting the problem that has occurred is updated based on an increase or decrease in the number of active users due to the problem. The support device according to claim 1 .

3. The processing device includes: In the priority update process, the priority of the development item for correcting the problem that has occurred is updated based on the profit or loss of the business operator due to an increase or decrease in the number of active users caused by the problem that has occurred. The support device according to claim 2 .

4. The processing device includes: In the priority update process, the priority of the development item for correcting the occurred failure is updated based on the profit or loss of the business operator due to an increase or decrease in the number of active users caused by the occurred failure and the development cost related to the development item for correcting the occurred failure. The support device according to claim 3 .

5. The processing device includes: In the priority update process, the profit and loss is calculated based on the profit and loss per unit number of users, the period until the scheduled completion of development of the development item for correcting the problem that has occurred, and an increase or decrease in the number of active users, and the priority of the development item for correcting the problem that has occurred is updated based on the calculated profit and loss and the development cost. The support device according to claim 4.

6. The processing device includes: In the priority update process, a development item having a large development value, which is a value obtained by dividing the profit and loss by the development cost, is given a higher priority than a development item having a small development value.

6. The support device according to claim 4 or 5.

7. the storage device stores correspondence information that associates a fault with a development item for correcting the fault; The processing device includes: if the development item for correcting the problem that has occurred is not included in the development item information, executing an addition process for adding the development item for correcting the problem that has occurred to the development item information by referring to the correspondence information; The support device according to claim 2 .

8. The processing device includes: In the output process, development items with higher priority are displayed in preference to development items with lower priority. The support device according to claim 1 .

9. an information processing device that stores development item information including each development item and its priority for a target system accessed by a plurality of users of a predetermined business; an acquisition process for acquiring information on active users who are currently accessing the target system; a priority update process for updating the priority of each development item included in the development item information based on the access patterns of the active users; an output process for outputting the updated priority; How to help carry out this.

10. an information processing device that stores development item information including each development item and its priority for a target system accessed by a plurality of users of a predetermined business; an acquisition process for acquiring information on active users who are currently accessing the target system; a priority update process for updating the priority of each development item included in the development item information based on the access patterns of the active users; an output process for outputting the updated priority; A support program to help implement this.

Images