JP2015111429A - Alteration management support apparatus, alteration management support method, and alteration management support program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To display a related hierarchical task structure in a software development project to a user, using a shortcut.SOLUTION: An alteration management support apparatus 1 that hierarchizes software altering work according to the reason for alteration and tasks prescribing the contents of work to be done by each assigned person and supports management of the altering work according to the tasks comprises configuration output means 20 that outputs the configuration of the hierarchical structure of tasks and tasks constituting the hierarchical structure, shortcut designating means 30 that designates prescribed tasks constituting the hierarchical structure, and task display control means 90 that causes designated tasks and tasks belonging to lower positions among all the tasks to be displayed. When there are multiple shortcuts, the task display control means 90 causes a shortcut so set as to be displayed to the user of a prescribed alteration management support apparatus 1 to be displayed.

Description

  The present invention relates to a change management support apparatus, a change management support method, and a change management support program.

  In a software development project in a company, when software is changed in accordance with a change request such as failure handling or new function installation, the change work is managed in units of tasks or tickets, and these are subdivided and assigned to workers ( Hereinafter referred to as a task).

  In addition to the work content, the task defines the reason for change related to the work content and the work content handled by the person in charge. In addition, information such as work progress status, manager, person in charge, scheduled start date, scheduled end date, changed source code, and the like is added. In order to manage the entire project, change management software capable of centrally managing tasks is generally used.

  Depending on the size of the software, the task is divided into a plurality of subtasks and has a parent-child relationship. Here, in the conventional change management software, in order to display a certain end task, it is necessary to expand all the task trees including the target task or output and display all the task lists. For this reason, when the hierarchy is complicated or the number of tasks is large, there is a problem that visibility is deteriorated.

  On the other hand, Patent Document 1 relates to a document or task representing a project from a document distributed and managed on the task tree by automatically obtaining a document stored at a higher level of the hierarchical task tree. A project management system that can discover and present information is disclosed.

  Patent Document 2 discloses a project management system that can graphically show the progress of work from input progress management data and the like, and can grasp the current progress of each person from the work flow.

  However, in Patent Document 1, it is not possible to accurately grasp a task in the vicinity of the assigned range related to itself.

  In Patent Document 2, the progress of work is output as a work flow in a flat manner, and visibility is deteriorated in a huge project having a hierarchical structure.

  The present invention has been made in view of the above problems, and a change management support device for displaying a task related to a user using a shortcut when displaying a hierarchical task structure in a software development project, a change An object is to provide a management support method and a change management support program.

  In order to solve the above-described problems and achieve the object, the change management support apparatus according to the present invention stratifies software change work by tasks that define the reason for change and the work contents of the person in charge. A change management support apparatus for supporting the management of the change work by a task, a configuration output means for outputting a configuration of a hierarchical structure of tasks, a task constituting the hierarchical structure, and a hierarchy output by the configuration output means Shortcut designating means for designating a predetermined task constituting the hierarchical structure of the structure, and task display control means for displaying the task designated by the shortcut designating means and tasks belonging to the lower level of the task When there are a plurality of shortcuts, the task display control means Characterized in that for displaying the shortcut that is configured to display.

  Also, the change management support method according to the present invention stratifies software change work by tasks that define the reason for change and the work contents of the person in charge, and supports the management of the change work by the hierarchized tasks. A change management support method, comprising: a hierarchical structure of tasks; a configuration output step for outputting a task that constitutes the hierarchical structure; and a configuration of the hierarchical structure output in the configuration output step. A shortcut designating step for designating a predetermined task to be performed, and a task display control step for displaying a task designated by the shortcut designating step and a task belonging to the lower level of the task. The display control step displays to the user who uses the predetermined change management support method. Characterized in that for displaying the shortcut that is so that set.

  According to the present invention, a change management support device, a change management support method, and a change management support program for displaying a task related to a user using a shortcut when displaying a hierarchical task structure in a software development project Can provide.

It is a figure showing the example of a screen display of the change management assistance apparatus which concerns on one Embodiment of this invention. It is a block diagram of a function structure of the change management assistance apparatus which concerns on one Embodiment of this invention. It is a figure showing the example of the task table which concerns on one Embodiment of this invention. It is a flowchart showing the process of registration of the shortcut which concerns on one Embodiment of this invention. It is a figure showing the example of operation of the shortcut registration on the screen of the change management assistance apparatus which concerns on one Embodiment of this invention. It is a figure showing the example of the shortcut management table which concerns on one Embodiment of this invention. It is a figure showing the example of the task table which concerns on one Embodiment of this invention. It is a flowchart showing the process of the display of the shortcut which concerns on one Embodiment of this invention. It is a figure showing the example of a screen display of the change management assistance apparatus which concerns on one Embodiment of this invention. It is a figure showing the example of the task management table which concerns on one Embodiment of this invention. It is a figure showing the example of the user selection dialog which displays the task of the change management assistance apparatus which concerns on one Embodiment of this invention. It is a flowchart showing the process of the display of the task which concerns on one Embodiment of this invention. It is a figure showing the example of a screen display of the change management assistance apparatus which concerns on one Embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 shows a screen display example of a change management support apparatus according to an embodiment of the present invention. In the screen display example, three display areas (hereinafter referred to as “panes”) are configured under a menu area included in a general window application starting from “file”.

  The “project list” is displayed in the left pane of the screen, and the hierarchical structure of the tasks that make up the project is displayed. There are multiple projects, and a hierarchical structure of tasks is formed for each project. When one task belonging to a project displayed in the left pane of the screen is selected, a “task list” belonging to that task is displayed in the upper right pane of the screen. When one task displayed in the upper right pane of the screen is selected, the details of that task are displayed in the lower right pane of the screen.

  FIG. 1 shows an example of a “next-generation framework-compatible project” according to this embodiment. The “next-generation framework support project” includes “controller development”, “engine development”, and “display development” tasks. Furthermore, there is a “COPY function development” task under the “controller development” task, and “module 1 development”, “module 2 development”, and “module 3 development” thereunder.

  For example, in order for a user engaged in “module 1 development” to display information on subtasks belonging to the “module 1 development” task, a tree of “next-generation framework compatible projects” is sequentially expanded in the left pane of the screen. Next, when “module 1 development” is displayed and the task name is selected, a subtask list of the “module 1 development” task is displayed in the upper right pane of the screen. Then, by selecting individual tasks, task information can be displayed.

  FIG. 2 shows a block diagram of a functional configuration of the change management support apparatus according to the embodiment of the present invention. The change management support apparatus 1 includes a configuration storage unit 10, a configuration output unit 20, a shortcut designation unit 30, a display user designation unit 40, a user identification unit 50, a shortcut management table 60, a task management table 70, a shortcut display control unit 80, and a task. Display control means 90 is provided. Further, the configuration display means 100 is provided outside the change management support apparatus 1.

  The configuration storage means 10 stores the task hierarchical structure configuration and details of the task in the task table 11. Details of the task table 11 will be described later.

  The configuration output unit 20 refers to the task table 11 and outputs the configuration of the task hierarchy and the contents of the task to the shortcut display control unit 80 or the task display control unit 90.

  The shortcut designating unit 30 updates the shortcut management table 60 in response to an instruction to register and delete a shortcut from the user who uses the change management support apparatus 1. The shortcut is designated by the user in order to facilitate access to information on a specific task among the tasks stored in the task table 11. Since the designated shortcut is displayed independently directly under the project, the user can directly access the target task. The shortcut management table 60 also holds information as to which user to display each shortcut.

  The display user specifying means 40 is used to specify to which user the tasks stored in the task table 11 are displayed. The designated content is recorded in the task management table 70.

  The user identification unit 50 identifies a user who is using the change management support apparatus 1. By identifying a user, shortcuts and tasks associated with that user can be identified.

  The shortcut management table 60 is a table provided to associate and store a user of the change management support apparatus related to a task designated as a shortcut. The shortcut management table 60 will be described in detail later.

  The task management table 70 is a table provided to associate and store a user of the change management support apparatus related to each task. The task management table 70 will be described in detail later.

  The shortcut display control means 80 refers to the shortcut management table 60 and outputs the task specified by the shortcut and the configuration of the subtask. Further, the shortcut management table 60 is referenced to output a shortcut that can be displayed by the identified user.

  The task display control unit 90 outputs the entire configuration of the task hierarchy output from the configuration output unit 20 to the configuration display unit 100. Further, the contents of those tasks are output to the configuration display means 100. At this time, referring to the task management table 70, a task that can be displayed by the identified user is output.

  The configuration display means 100 displays the structure of the hierarchical structure of tasks and the contents of the tasks output by the shortcut display control means 80 and the task display control means 90 using the shortcut display means 101 and the task display means 102. The shortcut display unit 101 displays not only the overall structure of the task hierarchy but also the hierarchy formed below the task specified by the shortcut. The task display unit 102 displays a list of tasks belonging to the task specified by the shortcut and details thereof.

  As described above, the user of the change management support apparatus 1 can quickly access information on a predetermined task among tasks constituting a complex hierarchical structure using a shortcut. Further, even when the number of shortcuts increases, visibility can be enhanced by displaying shortcuts related to the user. Further, the task specified by the shortcut can be made highly visible by displaying a task related to the task.

  The change management support device 1 may be a general computer having a CPU, a main storage device, an auxiliary storage device, and a network interface, and the type of hardware to be realized does not matter. The components shown in FIG. 2 may be provided on partially different computers. In that case, they are connected by a network. In FIG. 2, the configuration display unit 100 is provided outside the change management support apparatus 1, but may be provided inside.

(Details of task table)
Next, the task table 11 will be described.

  FIG. 4 shows an example of the data structure stored in the task table 11 according to the present embodiment. The task table 11 includes “task ID”, “task name”, “parent task ID”, “manager”, “person in charge”, “status”, “scheduled start date”, “scheduled completion date”, “reason for change”. And “modified source code”.

  “Task ID” is an ID assigned to uniquely identify a task.

  “Parent task ID” indicates the ID of the parent task of the task. For example, since the “controller development” task is the highest task, no value is stored in the “parent task ID”. Further, since the “module 1 development” task is a lower-level task of “COPY function development”, “1” which is the “task ID” of “COPY function development” is designated as the “parent task ID”. .

  The “task name” is a name given to the task.

  “Manager” and “person in charge” represent the manager and person in charge of the task. The administrator is a person who mainly refines the task and determines a person in charge who should perform the work. The person in charge receives an instruction from the administrator and executes the work. On the other hand, the person in charge changes the “state” based on the progress status of the task, and updates the information of “changed source code” as necessary.

  The administrator and the person in charge have editing authority for the task, but the administrator has a wider editing authority than the person in charge, such as being able to change “scheduled start date” and “scheduled completion date” described later. Since the scope of authority of the manager and the person in charge differs for each software, the present invention does not limit the authority that each has.

  “Status” represents the progress of work related to the task. “Scheduled start date” and “scheduled completion date” represent the scheduled start date and the scheduled completion date of work related to the task. The “reason for change” represents the reason why the work related to the task has occurred. The “changed source code” represents the location of the source code changed in the change work related to the task.

  Note that the data stored in the task table 11 is merely an example. Actually, it can have other items as data accompanying the task. In addition, the storage format and order of data regarding each item vary depending on the change management software, and the format is not limited in the example of the present embodiment. In the present invention, only representative items are briefly described for the sake of simplicity, and the scope of the invention is not limited only to the data displayed in the figure.

(Shortcut registration and deletion process flow)
Next, shortcut registration and deletion processing will be described with reference to FIGS. 4 and 5. A shortcut is created by a user to facilitate access to a specific task. For example, if a shortcut to the “Module 1 Development” task is created in the “Next Generation Framework Support Project” shown in FIG. 1, the “Next Generation Framework Support Project” is directly under the “Next Generation Framework Support Project” as shown in FIG. The “module 1 development” task is displayed. FIG. 5 shows only the “project list” portion of the left pane of FIG. 1 extracted and displayed. Hereinafter, the registration process will be described in detail.

  FIG. 4A shows a flow of processing for registering a shortcut by the shortcut designation unit 30 shown in FIG.

  In step S100, the shortcut designating unit 30 identifies the task designated for the shortcut registration by the user. In order to identify the task specified by the user, for example, a menu as shown in FIG. 5A is displayed. Specifically, the task name is acquired by causing the user to select “Register in shortcut” displayed when the task name is right-clicked. The example of FIG. 5A shows an operation of registering the task of “Module 1 development” as a shortcut.

  In step S110, the task information specified in step S100 is written into the shortcut management table 60. The shortcut management table 60 holds information including a task name designated as a shortcut. Details of the shortcut management table 60 will be described later.

  Next, in step S120, when a display user is selected, it progresses to step S130, and when a display user is not selected, a process is complete | finished. A display user represents a user related to a registered shortcut. That is, a user designated as a display user for a certain shortcut can display the shortcut on the change management support apparatus 1. If no display user is selected here, the shortcut is displayed only to the user who created the shortcut.

  Next, in step S <b> 130, the display user specifying unit 40 registers information about the selected display user in the shortcut management table 60. The display user selection method can be identified by, for example, displaying the dialog shown in FIG. 8 and selecting the display user by the user. In the example of FIG. 7, “A”, “B”, “C”, and “D” are selected as the users who display the shortcut of “Module 1 development”. Examples of users displayed as candidates that can be selected as candidates include users registered in the change management support apparatus 1. By default, this setting is selected as a user that can only be displayed by the user. This setting is made so that only a user who needs a shortcut is displayed.

  This is the end of the shortcut registration process. In the example of the present embodiment, as shown in FIG. 5B, the “module 1 development” task is registered as a shortcut and displayed immediately below the “next-generation framework-compatible project”. The user can quickly display a task list belonging to the “module 1 development” task by selecting the “module 1 development” task displayed as a shortcut. On the other hand, the shortcut immediately after creation can be displayed only by yourself in the default setting, and an explicit setting is required to display it to other users. As a result, unnecessary information for unrelated users does not increase on the screen, and visibility can be prevented from deteriorating.

  Note that the user selection processing in step S130 does not necessarily have to be performed in this processing flow for registering a shortcut. Once a shortcut is created by this processing flow, it may be manually set by the user. In this case, “display user selection” can be performed using the submenu or the like for the created shortcut from the screen of FIG. 5B in which the shortcut is registered. Thereafter, the dialog shown in FIG. 7 is displayed so that a display user can be selected.

  Further, in the dialog illustrated in FIG. 7 illustrated for selecting “display user”, the users “A” to “E” are selected in a check box format. However, if the number of users to be selected increases, you can select from the drop-down list, select the group to which the user belongs first and then narrow down the target, or select after searching and narrowing down it can. In the embodiment of the present invention, the user interface for user selection is not specified.

  FIG. 4B is a flow of processing for deleting a shortcut by the shortcut designation unit 30 shown in FIG. FIG. 5B is a diagram illustrating an example of input received from the user when deleting a shortcut.

  In step S200, the shortcut specifying unit 30 identifies a shortcut that the user intends to delete. The shortcut to be deleted by the user is identified by the operation shown in FIG. Specifically, the user is caused to select “Delete Shortcut” which is displayed when a shortcut to be deleted is right-clicked. In this example, the shortcut “module 1 development” is deleted.

  Next, in step S210, the corresponding item is deleted from the shortcut management table 60 in order to delete the shortcut specified in step S200. As a result, the item “module 1 development” is deleted from the shortcut management table, and the shortcut is not displayed.

  In the present embodiment, if a shortcut is deleted, it affects all users who have been able to display the shortcut until then. Therefore, in practice, it is necessary to allow the change management support apparatus 1 to delete the shortcut only to those who have a specific authority, or to make it impossible to delete if there is a user other than himself / herself that can be displayed. .

(Details of shortcut management table)
An example of the shortcut management table 60 is shown in FIG. The shortcut management table 60 includes items of “shortcut ID”, “task name”, and “display user”. The “shortcut ID” is an ID assigned to uniquely specify a shortcut. As the “task name”, the name of the task specified in step S100 of FIG. The “display user” stores the display user selected in step S130. A user designated as a “display user” can display the shortcut.

(Shortcut display process flow)
In the present embodiment, a shortcut to a task can be created by the processing shown in FIGS. On the other hand, in order to prevent the number of shortcuts itself from increasing and the visibility from deteriorating, a shortcut relevant to the user is selected and displayed. The processing flow will be described with reference to FIG.

  In step S300, the shortcut display control unit 80 reads the shortcut information from the shortcut management table 60. On the other hand, the user identification means 50 identifies a user who is trying to display a shortcut.

  Next, in step S <b> 310, the shortcut display control unit 80 determines whether or not the contents of the shortcut can be displayed with reference to the item “display user” in the shortcut management table 60. If the user identified in step S300 is included in the “display user” item of the shortcut management table 60, it is determined that the user can display the user.

  Next, in step S320, the shortcut display control unit 80 notifies the shortcut display unit 101 of the shortcut determined to be displayable in step S310. The shortcut display unit 101 displays the tasks side by side immediately below the project name.

  Next, in step S330, when all the shortcut information in the shortcut management table 60 has been read, the process ends. If there is an unprocessed shortcut, the process returns to step S300.

  A display example of the shortcut is shown in FIG. In FIG. 13, a “COPY function development” task and an “engine development” task are displayed as independent shortcuts. Other items displayed in FIG. 13 will be described later.

  In the present embodiment, when a plurality of shortcuts having a parent-child relationship are registered, the shortcut structure may be displayed while maintaining the hierarchical structure. The method will be described below.

  The shortcut display control means 80 refers to the task table 11 using the task name as a key for the task related to the shortcut determined to be displayable in step S310, and the relationship with the task already processed as a displayable task. To figure out. Then, when processing as a task that can be newly displayed, it may be controlled to display while maintaining the parent-child relationship with them.

  This will be described using a specific example. In the present embodiment, it is assumed that it is determined that the “controller development” task can be displayed by the first process of step S320. Here, the “controller development” task has a “COPY function development” task in the lower level, and a “module 1 development” task in the lower level of the “COPY function development” task.

  Next, assume that “module 1 development” can be displayed in the second step S320. At this time, the “module 1 development” task is displayed below the “controller development” task displayed for the first time. The “Module 1 Development” task is not a task that directly belongs to the “Controller Development” task, but has a vertical relationship across the “COPY Function Development” task, so it can be displayed as shown above. .

  Assume that it is determined that the “COPY function development” task can be displayed by the third processing in step S320. At this time, “controller development”, “COPY function development”, and “module 1 development” are displayed in a tree shape.

  Alternatively, it is assumed that the “engine development” task can be displayed by the third process of step S320. At this time, “engine development” has no vertical relationship with either “controller development” or “module 1 development” that can be displayed, and is thus displayed as a new independent shortcut.

  As described above, among tasks determined to be displayable, when there are lower tasks as viewed from the upper tasks, they may be displayed in a tree shape while maintaining their upper and lower relations.

  In this embodiment, the shortcut display control unit 80 reads the shortcut management table 60 one by one, and notifies the shortcut display unit 101 of tasks related to the shortcuts that can be displayed. However, in actual processing, the shortcut display control unit 80 reads the shortcut management table 60 at a time, internally determines whether or not each shortcut can be displayed, and collectively sends the result to the shortcut display unit 101. May be taken.

  In this embodiment, the user identified in step S300 is collated with the “display user” in the shortcut management table 60 to determine whether or not the shortcut can be displayed. However, the determination may be made based on attributes set in the task itself indicated by the shortcut. The attribute set in the task itself includes, for example, an access right set in the task. The access right includes, for example, an editing authority and a viewing authority given to the manager or person in charge of the task. That is, if the user has an access right for the task indicated by the shortcut, it may be determined that the shortcut can be displayed.

(Shortcut display example)
Next, a screen display example of a shortcut in the change management support apparatus according to the present embodiment will be described with reference to FIG. The screen configuration is the same as in FIG.

  In FIG. 9, “module 1” that can be displayed to the users “A”, “B”, “C”, and “D” through the flow of FIG. 4A and the operations of FIG. 5A and FIG. A shortcut to the "Development" task has been created. Here, it is assumed that the user “A” operates the change management support apparatus 1 and displays a screen.

  The “controller development”, “COPY function development”, and “display development” in the left pane of the screen display the overall configuration of the task hierarchy output by the task output unit 102 through the task display control unit 80. , Get and display. On the other hand, “Module 1 Development” in the left pane of the screen is a shortcut display, which is displayed by the shortcut display means 101 based on the information controlled and output by the shortcut display control means 80.

  Here, in FIG. 6 which is an example of the shortcut management table 60 in the present embodiment, shortcuts other than “module 1 development” are also registered. However, in FIG. 9, no shortcut other than “Module 1 development” is displayed. This is because the user “A” is not included in the “display user” item of those shortcuts.

  Thus, the visibility of a screen is improved by limiting the user who displays a shortcut.

(Selection of task display user and display example)
So far, only the user related to the task related to the shortcut using the “display user” stored in the shortcut management table 60 has been described. In the present embodiment, the task specified by the shortcut and the tasks belonging to the task can be processed so as to be displayed only to related users. The process will be described below.

  An example of the task management table 70 in this embodiment is shown in FIG.

  The task management table 70 has items of “task ID” and “display user”. As the “task ID”, the same value as the “task ID” shown in the task table 11 shown in FIG. 3 is used. That is, the task table 11 and the task management table 70 are associated with each other by “task ID”. The “display user” is used to select a user who can display the task, similarly to the “display user” item in the shortcut management table 60.

  In the present embodiment, the display user specifying means 40 makes an inquiry to the user using a dialog as shown in FIG. 11 in order to specify “display user”. For example, by right-clicking the mouse on a specific task displayed in the “task list” in FIG. 9, a submenu “Register a user to display the task” is displayed, and the user is allowed to select. As a result, a task to be set for “display user” can be specified.

  The display user specifying means 40 writes information in the task management table 70 of FIG. 10 for the user selected by the user and the task ID of the identified task.

  As described above, the display user specifying means 40 manages the users related to the tasks by using the task management table 70, so that when the user displays the tasks, only the tasks related to the user can be displayed.

  In the dialog illustrated in FIG. 11 illustrated for selecting “display user”, users “A” to “E” can be selected in a check box format. When the number of users to be selected increases, you can select from the drop-down list, select the group to which the user belongs, select after selecting the target, or search and select after selecting . In the embodiment of the present invention, the user interface for user selection is not specified.

  Unlike the case of shortcuts, selecting a display user for each task takes time. Therefore, by default, the setting of the shortcut display user may be inherited and changed individually later.

(Task display processing flow)
A processing flow for selecting and displaying a task for each user will be described with reference to FIG.

  In step S400, the task display control unit 90 reads the task output from the configuration output unit 20. Next, the task display control unit 90 reads the task management table 70. On the other hand, the user identification means 50 identifies the user who is going to display a task.

  Next, in step S410, the task display control unit 90 determines whether the task can be displayed with reference to the item “display user” in the task management table 70. If the user identified in step S400 is included in the “display user” item of the task management table 70, it is determined that the task can be displayed.

  Next, in step S420, the task display control unit 90 selects the task determined to be displayable in step S410, and notifies the task display unit 102 of it. The task display means 102 displays the task.

  Next, in step S430, when all the task information has been read, the process ends. If there is an unprocessed task, the process returns to step S400.

  In this embodiment, the task display control unit 90 reads the task management table 70 one by one and notifies the task display unit 102 of tasks that can be displayed. However, in actual processing, there is a method in which the task display control means 90 reads the task management table 70 at a time, internally judges whether each task can be displayed, and sends the results to the task display means 102 together. May be taken.

  The processing flow for displaying the task has been described above. By combining this processing and the processing flow for displaying the shortcut described above, information related to the user can be displayed for the task specified as the shortcut and the task lower than the task.

  In this embodiment, the user identified in step S400 is collated with the “display user” in the task management table 70 to determine whether the task can be displayed. However, the determination may be made based on the attributes included in the task table 11. Examples of the attribute include “manager” and “person in charge”. That is, if the user is “manager” or “person in charge”, it may be determined that the task can be displayed. Further, if there is an access right for the “parent task” to which the task belongs, it may be determined that the task can be displayed.

  In the present embodiment, the user who can select “display user” is not particularly defined. However, only those who have a specific authority in the change management support apparatus 1 may be able to perform it.

  In the present embodiment, the task table 11 and the task management table 70 exist separately, and the task information and the item “display user” are associated with each other using the “task ID” as a key. However, these may be managed by being merged into one table, or may be divided and stored in three or more tables. The configuration of these tables also depends on the structure of the database that stores the tables, but is not limited in the embodiment of the present invention.

(Example of task display)
FIG. 13 shows an example of a screen display of the change management support apparatus in the present embodiment. Here, along with the example of the present embodiment, an example when the user “D” displays the screen is shown.

  Unlike the example of FIG. 9, “COPY function development”, “module 1 development”, “module 3 development”, and “engine development” are displayed as shortcuts in the left pane of the screen. Then, the “module 1 development” task is selected, and a task list is displayed in the right pane of the screen. Here, as a result of the display control by the task display control means 90 based on the task management table 70, a list of tasks that can be displayed is displayed. In the example of FIG. 14, only “change work B” is displayed as a task belonging to the “module 1 development” task. This is because the task that can be displayed by the user “D” is only the task ID “2”, that is, “change work B” in the example of FIG.

  As described above, the task related to the user who displays the task is displayed in the task list, so that necessary information can be quickly accessed. Moreover, when the number of tasks increases, visibility can be kept high.

  As described above, according to the present invention, it is possible to select and display tasks and shortcuts related to the user who accesses the change management support apparatus 1 including the person in charge, the administrator, and the third party. As a result, the user can quickly access information on a predetermined task among tasks constituting a complicated hierarchical structure using a shortcut. Even when the number of shortcuts increases, visibility can be enhanced by displaying shortcuts related to the user. Further, regarding the subtask of the task designated as a shortcut, similarly, by displaying a thing related to the user, the visibility can be enhanced.

DESCRIPTION OF SYMBOLS 1 Change management support apparatus 10 Configuration memory | storage means 11 Task table 20 Configuration output means 30 Shortcut designation means 40 Display user designation means 50 User identification means 60 Shortcut management table 70 Task management table 80 Shortcut display control means 90 Task display control means 100 Configuration display Means 101 Shortcut display means 102 Task display means

JP 2010-33424 A JP 2006-227955 A

Claims (7)

A change management support device that stratifies software change work by a task that defines a reason for change and the work contents of a person in charge, and supports management of the change work by the layered task,
A structure output means for outputting a structure of a hierarchical structure of tasks and tasks constituting the hierarchical structure;
Of the hierarchical structure output by the configuration output means, shortcut specifying means for specifying a predetermined task constituting the hierarchical structure;
Task display control means for displaying a task specified by the shortcut specifying means and a task belonging to a lower level of the task;
When there are a plurality of shortcuts, the task display control means displays the shortcuts set to be displayed to a predetermined user of the change management support apparatus. A shortcut management table for storing the change management support device user associated with the shortcut in association with the shortcut;
The change management support apparatus according to claim 1, wherein the task display control unit controls display contents so as to display a task related to the user by referring to the shortcut management table. The change management support apparatus according to claim 2, wherein the task display control unit displays a shortcut to a manager or a person in charge of the task designated by the shortcut designation unit. A change management support method that stratifies software change work by a task that defines the reason for change and the work content of the person in charge, and supports management of the change work by the layered task,
A configuration output step for outputting a configuration of a hierarchical structure of tasks and tasks constituting the hierarchical structure;
Of the hierarchical structure output in the configuration output step, a shortcut designation step for designating a predetermined task constituting the hierarchical structure;
A task display control step for displaying a task specified by the shortcut specifying step and a task belonging to a lower level of the task,
When there are a plurality of shortcuts, the task display control step displays the shortcut set to be displayed to a user who uses the predetermined change management support method. The task display control step refers to a task management table for storing and associating a user who uses the change management support method related to each task, and displays the contents related to displaying the task related to the user. The change management support method according to claim 4, wherein the change management support method is controlled. 6. The change management support method according to claim 5, wherein the task display control step displays a shortcut to a manager or a person in charge of the task designated in the shortcut designation step. A change management support program for causing a computer to execute the change management support method according to any one of claims 4 to 6.

Images