JP2020115317A - Management device, method, and program - Google Patents

Abstract

To provide a management device capable of improving convenience of users in software product development, a method, and a program.SOLUTION: A management device according to an embodiment comprises first acquiring means, identifying means, second acquiring means, and display processing means. The first acquiring means acquires commitment information for managing source code versions. The identifying means identifies a task defined for source code editing on the basis of the acquired commitment information. The second acquiring means acquires task information indicating the identified task. The display processing means displays task information acquired in association with the source codes.SELECTED DRAWING: Figure 1

Description

Embodiments of the present invention relate to a management device, a method, and a program.

Generally, source code management tools and task management tools are known as tools that can be used in the development of software products.

The source code management tool is a tool for managing the version of source code written in a programming language. On the other hand, the task management tool is a tool for managing the progress status of tasks defined for source code editing work.

A software product developer (user) can efficiently develop a software product by using the above-mentioned source code management tool and task management tool.

However, since the source code management tool and the task management tool are used independently, the correspondence relationship between the source code managed by the source code management tool and the task managed by the task management tool is unknown, The convenience of the user in developing a software product may be low.

JP, 2010-128650, A

Therefore, the problem to be solved by the present invention is to provide a management apparatus, method, and program capable of improving the convenience of the user in the development of software products.

The management device according to the embodiment includes a first acquisition unit, a specification unit, a second acquisition unit, and a display processing unit. The first acquisition unit acquires commit information for managing the version of the source code. The specifying means specifies a task defined for the editing work of the source code based on the acquired commit information. The second acquisition unit acquires task information indicating the specified task. The display processing means displays the acquired task information in association with the source code.

FIG. 3 is a block diagram showing an example of a functional configuration of a management device according to the first embodiment. The figure which shows an example of the system configuration of a management apparatus. The flowchart for explaining the outline of the source code management tool. The figure which shows an example of the data structure of commit information. The figure which shows an example of the data structure of hierarchical structure information. The flowchart for demonstrating the outline of a task management tool. The figure which shows an example of the data structure of task information. The flowchart which shows an example of the processing procedure of a management apparatus. The figure which shows an example of a correspondence table. The figure which shows an example of the layout of a display screen. The figure which shows the example of a display of a 1st area|region. The figure which shows the example of a display of the status of a task. The figure which shows the example of a display of commit information. The figure which shows the example of a display of task information. The figure which shows the example of a display of a 2nd area|region. The flowchart which shows an example of the processing procedure of the management apparatus at the time of searching a file. The figure which shows the example of a display of a search result. The block diagram which shows an example of the functional structure of the management apparatus which concerns on 2nd Embodiment. The flowchart which shows an example of the processing procedure of a management apparatus. The figure for demonstrating the display example of a 1st area|region. The block diagram which shows an example of a functional structure of the management apparatus which concerns on 3rd Embodiment. The flowchart which shows an example of the processing procedure of a management apparatus. The figure for demonstrating the display example of a 1st area|region.

Hereinafter, each embodiment will be described with reference to the drawings.
(First embodiment)
First, the first embodiment will be described. The management device according to the present embodiment is a device that manages information related to source code (source code related information), and is used for linking a source code management tool and a task management tool used for developing a software product. To be

Here, the source code management tool is a tool (application program) for managing the version of the source code described in a programming language such as Java (registered trademark) and C language in software product development. The source code version is updated (changed) by, for example, addition of functions, correction, improvement, and derivative development of the source code. As the source code management tool, for example, open source software such as Git and Subversion can be used.

The task management tool is a tool (application program) for tracking and managing the progress status of a task defined for source code editing work in software product development. The tasks managed by the task management tool include various work cases such as software product defects, function additions, and improvements. For example, GitHub and Redmine can be used as the task management tool.

The management device (management tool) according to the present embodiment has a function of managing the correspondence relationship between the source code managed by the source code management tool and the task managed by the task management tool.

In the source code management tool, for example, commit information for managing the source code version is held. On the other hand, the task management tool holds task information indicating a task. The details of the commit information and the task information will be described later.

FIG. 1 is a block diagram showing an example of the functional configuration of the management apparatus according to this embodiment. As illustrated in FIG. 1, the management device 10 includes a correspondence table creation unit 11, a task information acquisition unit 12, a storage unit (DB) 13, a first display processing unit 14, a search unit 15, and a second display processing unit 16. ..

The correspondence table creation unit 11 acquires the commit information for managing the version of the source code held in the above-mentioned source code management tool. The correspondence table creation unit 11 identifies, based on the acquired commit information, the task defined for the editing operation of the source code whose version is managed by the commit information. As a result, the correspondence table creation unit 11 creates a correspondence table (correspondence information) indicating the correspondence relationship between the source code managed by the source code management tool and the tasks managed by the task management tool.

In the following description, it is noted that the source codes and tasks whose correspondence relationships are shown in the correspondence table created by the correspondence table creating unit 11 correspond to each other.

The task information acquisition unit 12 acquires task information indicating a task corresponding to the source code managed by the source code management tool, based on the correspondence table created by the correspondence table creation unit 11.

The correspondence table created by the correspondence table creation unit 11 and the task information acquired by the task information acquisition unit 12 are stored in the storage unit 13.

Based on the correspondence table stored in the storage unit 13, the first display processing unit 14 displays the task information stored in the storage unit 13 in association with the source code corresponding to the task indicated by the task information.

The search unit 15 is a source code managed by a source code management tool (a file in which the source code is stored) based on a search condition (for example, a keyword) specified by a user who uses the management device 10. Execute the process to search for.

The second display processing unit 16 displays the search result (for example, the file name of the file in which the source code is stored) by the search unit 15.

FIG. 2 shows an example of a system configuration of the management device 10 shown in FIG. Here, the management device 10 will be described as a personal computer (PC), for example, but the management device 10 may be another electronic device.

As illustrated in FIG. 2, the management device 10 includes a CPU 101, a non-volatile memory 102, a main memory 103, a BIOS-ROM 104, a system controller 105, an input device 106, a display device 107, an embedded controller (EC) 108, and the like.

The CPU 101 is a processor that controls the operation of each component in the management device 10. The CPU 101 executes various programs loaded from the nonvolatile memory 102, which is a storage device, into the main memory 103. This program is a program for managing the correspondence between the source code managed by the operating system (OS) and the source code management tool and the tasks managed by the task management tool (hereinafter referred to as management program). ) Etc. are included.

In this embodiment, the management program may be realized as a plug-in incorporated in an application program (tool) for providing an integrated development environment, for example.

The CPU 101 also executes a basic input/output system (BIOS) stored in the BIOS-ROM 104. The BIOS is a program for controlling hardware.

The system controller 105 is a device that connects the local bus of the CPU 101 and various components.

The input device 106 includes, for example, a keyboard and a mouse. The display device 107 includes, for example, a display such as a liquid crystal display device. The EC 108 is a one-chip microcomputer that includes an embedded controller for power management.

Although only the CPU 101, the non-volatile memory 102, the main memory 103, the BIOS-ROM 104, the system controller 105, the input device 106, the display device 107, and the EC 108 are shown in FIG. 2, the management device 10 may be, for example, an HDD (Hard Disk Drive). Other storage devices such as a Disk Drive) and an SSD (Solid State Drive) may be provided, or a communication device configured to execute communication with an external device may be provided.

In the present embodiment, some or all of the respective units 11, 12 and 14 to 16 shown in FIG. 1 execute the above management program on the CPU 101 (that is, the computer of the management device 10) shown in FIG. 2, for example. That is, it is realized by software. Note that the management program can be stored in a computer-readable storage medium in advance and distributed. Further, the management program may be downloaded to the management device 10 via a network, for example.

Here, although it has been described that some or all of the units 11, 12 and 14 to 16 are realized by software, some or all of the units 11, 12 and 14 to 16 are realized by hardware, for example. Alternatively, it may be realized as a combined configuration of software and hardware.

The storage unit 13 shown in FIG. 1 is realized by, for example, the non-volatile memory 102 shown in FIG. 2 or another storage device.

The source code management tool and the task management tool linked by the management device 10 according to the present embodiment will be briefly described below.

First, an outline of the source code management tool will be described with reference to the flowchart in FIG. The source code management tool is realized, for example, as an application program, and the user executes the source code management tool (application program) on the management device 10 or another electronic device different from the management device 10 to execute the source code management tool. Code management tools can be used. 3 shows an example of a processing procedure of the management apparatus 10 or another electronic device that executes the source code management tool, it is assumed in FIG. 3 that the source code management tool executes the processing.

It is assumed that the source code management tool holds a file that stores a source code (hereinafter referred to as a target source code) edited by a user who uses the source code management tool.

When the user uses the source code management tool as described above, the source code management tool displays the target source code (step S1). Note that the process of step S1 is executed, for example, by a user who uses the source code management tool specifying a file in which the target source code is stored.

In this case, the target source code displayed in step S1 is edited according to the user's operation (step S2). The editing of the target source code in step S2 includes, for example, changing, modifying, adding and deleting the code (line) described in the target source code.

Here, the source code management tool has a function of managing the version of the source code (software product) as described above. In this case, the source code management tool manages the source code edited by the user in units called commits. For example, when a new version of the source code (that is, the edited source code) is registered, The changed part (difference) from the source code registered immediately before the source code (source code immediately before) is recorded.

It should be noted that the registration of a new version of the source code in order to record the changed portion from the immediately preceding source code is referred to as “commit”.

When the new version of the target source code is committed after the processing of step S2 described above is committed, the source code management tool generates commit information for managing the version of the target source code (step S3).

The commit information (that is, the version of the target source code) generated in step S3 is held in the source code management tool together with the file in which the new version of the target source code is stored.

FIG. 4 shows an example of the data structure of the commit information described above. As shown in FIG. 4, the commit information includes a commit ID, a file name, a changed line, and a commit comment.

The commit ID is identification information for identifying the commit (that is, the version), which is assigned to the commit when the source code is committed.

Filename is the filename of the file that contains the committed source code.

The changed line indicates the position (for example, line number) of the line changed from the immediately preceding source code in the committed source code. Note that the changed line may include information on the changed content (addition, correction, deletion, etc.).

The commit comment is a text (for example, a comment about editing the source code) created (input) by the user when the source code is committed.

In the example shown in FIG. 4, commit information 201 and 202 are shown. The commit information 201 includes a commit ID “1”, a file name “file 1”, a change line “change line 1”, and a commit comment “aaa”. According to this commit information 201, the source code in which the line indicated by “changed line 1” has been changed from the immediately preceding source code (the source code stored in the file whose file name is “file 1”) is committed. , The commit ID “1” is assigned to the commit. Further, the commit information 201 indicates that the commit comment created by the user when the source code stored in the file with the file name “file 1” is committed is “aaa”. There is.

Further, the commit information 202 includes a commit ID “2”, a file name “file 1”, a change line “change line 2”, and a commit comment “bbb”. According to this commit information 202, the source code (the source code stored in the file whose file name is “file 1”) in which the line indicated by “changed line 2” has been changed from the immediately preceding source code is committed. , The commit ID “2” is assigned to the commit. Further, the commit information 202 indicates that the commit comment created by the user when the source code stored in the file with the file name “file 1” is committed is “bbb”. There is.

Although not shown in FIG. 4, the commit comment in the present embodiment identifies a task defined for the committed source code editing work (that is, a task corresponding to the source code). It is assumed that the task identification information (hereinafter, referred to as a task ID) for performing the task is included.

That is, for example, the commit comment included in the commit information 201 and 202 includes a task ID for identifying the task corresponding to the source code stored in the file whose file name is "file 1". Since the commit information 201 and 202 include the same file name "file 1", the commit comments included in the commit information 201 and 202 include the same task ID, for example.

Note that, for example, depending on the timing of committing the source code, even commit information including the same file name may include task IDs in which the commit comment included in the commit information is different.

Although only the commit information 201 and 202 are described for convenience in FIG. 4, the commit information is generated each time the source code is committed, and is retained in the source code management tool.

By using the source code management tool that holds the commit information as described above, the user can check (review) the source code of an arbitrary version, for example.

Note that the data structure of the commit information described in FIG. 4 is an example, and the commit information includes other information such as the user name of the user who edited the source code and the date and time when the source code was edited. Good.

Further, the commit information shown in FIG. 4 includes one file name in association with one commit (commit ID), but one commit may include a plurality of file names. In other words, a commit may contain changes for multiple files.

Here, in the source code management tool, it is possible to manage each version of a plurality of source codes, but a plurality of files (source code files) that store each of the plurality of source codes are, for example, a hierarchy. It is assumed that they are managed so as to be arranged in a plurality of folders having a structure.

In this case, the source code management tool holds information indicating the hierarchical structure of a plurality of folders in which each file is arranged (hereinafter referred to as hierarchical structure information).

FIG. 5 shows an example of the data structure of the hierarchical structure information. As shown in FIG. 5, the hierarchical structure information includes an upper layer (information indicating) and a lower layer (information indicating).

The upper layer indicates a folder located higher in the hierarchical structure than the associated lower layer (folder or file). The upper layer includes, for example, a folder name.

The lower layer indicates a folder or file located in the lower level of the hierarchical structure with respect to (the folder of) the corresponding upper layer. The lower layer includes, for example, a folder name or a file name.

In the example shown in FIG. 5, the folder with the folder name “Folder A” is located at the upper level of the hierarchical structure, and the folder with the folder name “Folder 1” is located below the folder. It is shown. In addition, the folder with the folder name “folder 1” is located at the upper level of the hierarchical structure, and the files with the file names “file 1” and “file 2” are located below the folder. It is shown. In other words, in the example shown in FIG. 5, two files whose file names are "file 1" and "file 2" are subordinate to the folder whose folder name is "folder A". It is shown that they are managed so as to be placed in a folder that is "1".

According to such hierarchical structure information, for example, a plurality of source code files can be arranged in a plurality of folders having a hierarchical structure and displayed as a list.

Next, an outline of the task management tool will be described with reference to the flowchart of FIG. The task management tool is realized, for example, as an application program, and the user executes the task management tool (application program) on, for example, the management device 10 or another electronic device different from the management device 10 to execute the task management tool. Can be used. FIG. 6 shows an example of a processing procedure of the management apparatus 10 or another electronic device that executes the task management tool. In FIG. 6, the task management tool will be described as executing the processing.

Here, a user who uses the task management tool can register (create) a task defined for a source code editing operation.

In this case, the task management tool assigns a task ID for identifying the task (hereinafter referred to as a target task) registered by the user (step S11). The task ID may be automatically assigned to the target task, or may be designated by the user, for example.

Next, the task management tool inputs the title of the target task designated (created) by the user in response to the user's operation (step S12).

Further, the task management tool inputs the description of the target task designated (created) by the user according to the user's operation (step S13).

When the process of step S13 is executed, the task management tool displays the task ID assigned to the target task in step S11, the title of the target task input in step S12, and the target task input in step S13. Task information (task information indicating the target task) including the description of (1) is generated (step S14).

The task information (target task) generated in step S14 is managed by the task management tool.

In the example illustrated in FIG. 6, the processing in steps S11 to S14 is described as being sequentially executed, but the order of the processing in steps S11 to S13 may be appropriately changed, for example. Further, the process of step S11 may be executed, for example, when the process of step S14 is executed.

FIG. 7 shows an example of the data structure of the task information described above. As shown in FIG. 7, the task information includes a task ID, title, description, status and history.

The task ID is identification information (identification information for identifying the task created by the user) assigned to the task in step S11 shown in FIG.

The title is the title of the task identified by the associated task ID.

The description is a description (text) of the task identified by the associated task ID.

The status indicates the status (progress status) of the task identified by the associated task ID. Note that, when the task information is generated in step S14 described above, the status included in the task information is “open (start)”. On the other hand, when the task indicated by the task information (that is, the source code editing work) is completed, the status included in the task information is changed to “closed (ended)”. The status included in the task information is changed from “open” to “closed”, for example, in response to a user operation. It is also possible to change the status of a task that was once changed to "closed" to "open" again. In the present embodiment, the task information includes “open” and “closed” as task statuses, but the task information may include other statuses.

Here, a series of source code defined as a task may be edited by, for example, a plurality of users, and in this case, the task management tool may comment on the task exchanged between the plurality of users. (Text) can be recorded as a history. That is, the history included in the task information corresponds to (history of) the user's comment regarding the task identified by the associated task ID.

In the example shown in FIG. 7, task information 211 and 212 are shown. The task information 211 includes a task ID “1”, a title “title 1”, a description “ccc”, a status “closed”, and a history “ddd”. According to the task information 211, the title of the task identified by the task ID “1” is “title 1”, the description of the task is “ccc”, and the comment (history of) the task is “ddd”. Is shown. Further, the task information 211 indicates that the status of the task identified by the task ID “1” is “closed”.

In addition, the task information 212 includes a task ID “2”, a title “title 2”, a description “eee”, a status “open”, and a history “fff”. According to the task information 212, the title of the task identified by the task ID “2” is “title 2”, the description of the task is “eee”, and the comment (history) of the task is “fff”. Is shown. Further, the task information 212 indicates that the status of the task identified by the task ID “2” is “open”.

In FIG. 7, only the task information 211 and 212 has been described for the sake of convenience, but the task information is generated for each task registered by the user and held in the task management tool.

By using the task management tool that holds the task information as described above, the user can check the progress status of the task, for example.

The data structure of the task information described with reference to FIG. 7 is an example, and the task information may include other information such as the type of task.

Next, an example of the processing procedure of the management apparatus 10 according to the present embodiment will be described with reference to the flowchart of FIG.

First, a user who uses the management device 10 activates the above-described management program (management tool) on the management device 10.

When the management program is started on the management device 10, the correspondence table creation unit 11 acquires the commit information stored in the above-mentioned source code management tool (step S21).

Next, the correspondence table creation unit 11 specifies the task corresponding to each of the source codes managed by the source code management tool, based on the commit information acquired in step S21. As a result, the correspondence table creating unit 11 associates the source code managed by the source code management tool with the task defined for editing the source code (that is, the task corresponding to the source code). A correspondence table showing the relationship is created (step S22).

Here, the commit information acquired in step S21 includes the commit ID, the file name, the changed line, and the commit comment as described in FIG. 4, but the correspondence table creating unit 11 includes the commit comment. The extracted task ID is extracted (acquired), and the file name associated with the commit comment is associated with the extracted task ID.

In step S22, such a process is executed for each commit information, so that, for example, the file name (that is, the source code file) and the task ID (that is, the task corresponding to the source code) as shown in FIG. ) Is associated with each other and a correspondence table is created.

In the example shown in FIG. 9, for example, the file name "file 1" and the task ID "1" are included in the correspondence table in association with each other. According to this, it is shown that the task defined for the editing work of the source code stored in the file whose file name is "file 1" is the task identified by the task ID "1". ing.

Similarly, in the example shown in FIG. 9, for example, the file name “file 2” and the task ID “2” are included in the correspondence table in association with each other. According to this, it is shown that the task defined for the editing work of the source code stored in the file whose file name is "file 2" is the task identified by the task ID "2". ing.

Returning to FIG. 8 again, the task information acquisition unit 12 retrieves task information indicating the task identified by the task ID included in the correspondence table created in step S22 from the task information held in the task management tool. It is acquired (step S23). Specifically, in step S23, the task information including the task ID included in the correspondence table created in step S22 is acquired.

The correspondence table created in step S22 and the task information acquired in step S23 are stored in the storage unit 13.

Next, the first display processing unit 14 acquires the hierarchical structure information held in the source code management tool, and based on the hierarchical structure information, the hierarchical structure of a plurality of folders in which a plurality of files are arranged ( Hereinafter, a file hierarchy will be displayed on the display device 107 (step S24). In this file hierarchy, the file names of files in which a plurality of source codes are stored are displayed in a list in a format arranged in a plurality of folders having a hierarchical structure.

Further, the first display processing unit 14 displays the task information stored in the storage unit 13 based on the correspondence table stored in the storage unit 13 (step S25).

In step S25, the first display processing unit 14 acquires the task information included in the correspondence table from the storage unit 13 in association with the file name on the file hierarchy displayed in step S24, and the task information concerned. Is displayed in association with the file name.

Although the task information includes the task ID, the title, the description, the situation, and the history as described in FIG. 7, the task information in step S25 includes, for example, the task ID and the title. Further, the process of step S25 is executed for each file name included in the correspondence table.

Hereinafter, a screen (hereinafter, referred to as a display screen) displayed on the management device 10 (display device 107) by executing the processing illustrated in FIG. 8 described above will be specifically described.

Here, FIG. 10 shows an example of the layout of the display screen. As shown in FIG. 10, a first area 301, a second area 302, a third area 303, and a fourth area 304 are arranged on the display screen 300.

In the example illustrated in FIG. 10, the first area 301 is arranged on the left side when viewed from the user who uses the management device 10. The second area 302 is arranged on the right side of the user who uses the management apparatus 10. That is, the first region 301 and the second region 302 are arranged at positions facing each other with the third region 303 and the fourth region 304 interposed therebetween.

The third region 303 is located between the first region 301 and the second region 302 and is located above the fourth region 304. The fourth region 304 is located between the first region 301 and the second region 302, and is located below the third region 303.

The first area 301 is an area for displaying, for example, the above-mentioned file hierarchy (that is, displaying file names of files arranged in each of a plurality of folders having a hierarchical structure). In the first area 301, the task information is displayed in association with the file name on the file hierarchy. A specific display example in the first area 301 will be described later.

The second area 302 is, for example, an area for displaying a list of tasks managed by the task management tool (files storing task information indicating the tasks). In the second area 302, for example, a list of task IDs and titles included in the task information is displayed.

Here, the user can specify the file name on the file hierarchy displayed in the first area 301 by operating the management device 10. The third area 303 is an area for displaying the source code (the latest version of the source code) stored in the file having the file name specified by the user in the first area 301. The source code displayed in the third area 303 is obtained from the source code management tool or the like based on the file name (path of the file in which the source code is stored) specified by the user in the first area 301, for example. It should be done.

Further, the user can specify the tasks (task ID and title) listed in the second area 302 by operating the management device 10. The fourth area 304 is an area for displaying task information indicating a task designated by the user in the second area 302. The task information displayed in the fourth area 304 is acquired from the storage unit 13, for example.

The layout shown in FIG. 10 is an example, and for example, the first region 301 and the second region 302 may be arranged adjacent to each other, or the third region 303 and the fourth region 304 may be arranged apart from each other. It may have been done. Further, the positions of the first area 301 to the fourth area 304 may be appropriately changed. Further, on the display screen 300, areas other than the first area 301 to the fourth area 304 shown in FIG. 10 may be further arranged.

Although not shown in FIG. 10, the display screen 300 may be provided with a toolbar or the like for using various functions relating to the development of the software product, for example.

Next, with reference to FIG. 11, a display example of the above-described first area 301 shown in FIG. 10 will be described.

Note that in FIG. 11, for convenience, only a part of the first region 301 is shown. In FIG. 11, “Folder A”, “Folder 1”, and “Folder 2” represent folder names, and “File 1”, “File 2”, and “File 3” represent file names, respectively. There is. The same applies to the following figures.

In the following description, for convenience, the folders whose folder names are “Folder A”, “Folder 1” and “Folder 2” are simply referred to as Folder A, Folder 1 and Folder 2, respectively. Similarly, files having file names "file 1", "file 2" and "file 3" are simply referred to as file 1, file 2 and file 3, respectively.

As shown in FIG. 11, the hierarchical structure of the folder A, the folder 1 and the folder 2 is displayed in the first area 301, and the file 1, the file 2 and the file 3 arranged in the folder 1 are further displayed. It is displayed.

Note that the folders 1 and 2 shown in FIG. 11 are folders arranged under the folder A. Further, in FIG. 11, files and the like arranged in the folder 2 are omitted.

Here, in the first area 301, task information indicating a task corresponding to the source code stored in the file 1 is displayed in association with the file 1. As the task information indicating the task corresponding to the file 1, the task ID and title included in the task information are displayed. Specifically, in FIG. 11, although the task information “the job is executed on the day following the #12 data collection day” (hereinafter referred to as the first task information) is displayed in association with the file 1. In this case, “#12” is the task ID, and “the job is executed on the day following the data collection day” is the task title.

Similarly, in the first area 301, task information “change #10 theme for each user” (hereinafter referred to as second task information) is displayed in association with the file 2. In this case, “#10” is the task ID, and “change theme for each user” is the task title.

Further, in the first area 301, task information “Determine the size of #1 bubble in consultation with Mr. XX” (hereinafter referred to as third task information) is displayed in association with the file 3. In this case, "#1" is the task ID and "the size of the bubble is determined in consultation with Mr. XX" is the task title.

In such a first area 301, the contents of the task corresponding to each source code (file) can be confirmed on the file hierarchy.

Further, in the example shown in FIG. 11, the first task information “the job is executed on the day following the data collection day #12” and the second task information “#10 the theme is changed for each user in association with the folder 1”. And the third task information "determine the size of #1 bubble in consultation with Mr. XX".

That is, to a folder in which a plurality of files are arranged, task information indicating a task corresponding to the source code stored in each of the files is displayed in association with each other.

Depending on the size of the area for displaying the task information in the first area 301, the task information may not be displayed in association with the folder.

Further, the display form of the task information (first to third task information) in the first area 301 shown in FIG. 11 is an example, and as the task information, for example, only the task title may be displayed.

Although the task ID and the title of the task are displayed as the task information in FIG. 11, the task status may be further displayed. Specifically, when displaying the task information in which the task status is “closed”, for example, a task ID with a strikethrough may be displayed. The example shown in FIG. 12 indicates that the status of the task corresponding to the source code stored in the file 3 (that is, the task indicated by the third task information) is “closed”.

Note that FIG. 12 shows an example in which a strikethrough is added to the task ID, but the user can understand whether the status of the task indicated by the task information is “open” or “closed”. For example, the status of the task may be displayed in different modes.

Further, in the present embodiment, the description has been made assuming that a plurality of files are arranged and displayed in a folder having a hierarchical structure, but the folder name (that is, file hierarchy) is omitted from the display in the first area 301. The file names may simply be displayed in a list format.

Here, when the file (file name) is designated by the user in the first area 301 as described above, the source code stored in the file is displayed in the third area 303. Specifically, when the file 1 displayed in the first area 301 shown in FIG. 11 is designated, the source code stored in the file 1 is displayed in the third area 303.

The source code (the file in which the source code is stored) displayed in the third area 303 may be acquired from the source code management tool or may be stored in the storage unit 13 in advance.

Although the source code is displayed in the third area 303 here, for example, the commit information of the source code stored in the file designated by the user may be displayed in the third area 303. In this case, for example, in the format as shown in FIG. 13, the changed portion in the source code stored in the file designated by the user (that is, the changed line included in the commit information) is displayed. According to this, the user can grasp the history of the editing work (changed part) up to the source code (the latest version of the source code) stored in the file designated by the user.

Further, the user can also specify the task information displayed in association with the file name in the first area 301. The task information designated by the user in this way is displayed in the fourth area 304 as described above. FIG. 14 shows a display example of task information in the fourth area 304. Note that FIG. 14 illustrates an example of the fourth area 304 when the task information indicating the task identified by the task ID “#1” is displayed. As shown in FIG. 14, the fourth area 304 displays the task ID “#1”, the title included in the task information including the task ID “#1”, the description, the situation, the history, and the like.

Although the tasks managed by the task management tool are displayed in a list in the second area 302, the task IDs and task titles included in the task information indicating the tasks are listed in the second area 302. Shall be displayed. In this case, in the second area 302, the tasks may be simply displayed as a list, but as shown in FIG. 15, the file name of the file storing the source code corresponding to the task (or the path of the file) is They may be displayed in association with each other. The file name of the file that stores the source code corresponding to the task can be acquired (specified) based on the correspondence table stored in the storage unit 13, for example.

In the example shown in FIG. 15, the file name “file 3” is displayed in the second area 302 in association with the task identified by the task ID “#1”, for example. According to this, it is possible to easily understand that the file in which the source code corresponding to the task identified by the task ID “#1” is stored is “file 3”.

Similarly, in the second area 302, for example, the file in which the source code corresponding to the task identified by the task ID “#10” is stored is “file 2” and is identified by the task ID “#12”. It is possible to easily understand that the file in which the source code corresponding to the task is stored is “File 1”.

Although not shown in FIG. 15, for example, a plurality of file names may be displayed in association with a task identified by one task ID.

In addition, the task information specified by the user in the second area 302 may be displayed in the fourth area 304 described above.

Further, for example, when the source code stored in the file designated by the user in the first area 301 is displayed in the third area 303, the task information indicating the task corresponding to the source code is displayed in the fourth area 304. It may be displayed. That is, in the third area 303 and the fourth area 304, the source code and the task information indicating the task corresponding to the source code may be displayed in association with each other.

As described above, in the display screen 300 (the first area 301, the second area 302, the third area 303, and the fourth area 304), the source code managed by the source code management tool and the task management tool are managed. It is possible to display the associated tasks in various ways.

Here, in the management device 10 according to the present embodiment, it is possible to search for a file that stores the source code managed by the source code management tool.

Hereinafter, an example of a processing procedure of the management device 10 when searching for a file will be described with reference to the flowchart of FIG.

When searching for files, the user can specify search conditions using the input device 106 (eg, keyboard, etc.). The search unit 15 acquires the search condition designated by the user (step S31). The search condition acquired in step S31 includes, for example, a search word (keyword).

Next, the search unit 15 searches for a file (file path) that matches the search condition acquired in step S31 from the files that store the source code managed by the source code management tool (step S32). ..

Here, for example, a comment (annotation) can be directly described in the source code. Assuming that the search condition acquired in step S32 is a search word, a file storing a source code in which a comment including the search word is described is acquired as a search result. Although the comment in the source code is used as the search target here, the search target may be the entire source code.

Furthermore, the search unit 15 searches the task information stored in the storage unit 13 (task information held in the task management tool) for task information that matches the search condition acquired in step S31 ( Step S33).

Assuming that the search condition acquired in step S32 is a search word as described above, task information in which the search word is included in the text such as the title, description, or history is searched for in step S33.

In this case, the file storing the source code corresponding to the task indicated by the task information searched in step S33 is acquired as the search result. The file storing the source code corresponding to the task is a file having a file name associated with the task ID for identifying the task in the correspondence table stored in the storage unit 13 described above.

When the processing of step S33 is executed, the second display processing unit 16 displays a list of (the file names of) the files acquired as the search result on the display device 107 (step S34).

Here, FIG. 17 shows a display example of search results when the processing shown in FIG. 16 is executed. Here, the search result when the search word "bubble size" is specified by the user as the search condition is shown. The file name of the file acquired as the search result will be described as being displayed in the first area 301, for example.

In the example shown in FIG. 17, the file 3 (file name “file 3”) is displayed in the first area 301 as a search result. The file 3 is arranged in the folder 1 arranged below the folder A.

Further, in the first area 301, the third task information “Determine the #1 bubble size in consultation with Mr. XX” is displayed in association with the file 3.

That is, in FIG. 17, since the third task information (task title) displayed in association with the file 3 includes the search word “bubble size”, the file 3 is acquired as the search result. An example is shown.

Further, in the first area 301, the part corresponding to the search word included in “Determine the size of bubble #1 after consultation with Mr. XX” displayed as the third task information (that is, “size of bubble”). )) may be highlighted, for example, as shown in FIG.

Although the file name of the file acquired as the search result is displayed in the first area 301 here, the file name (that is, the search result) is displayed in an area other than the first area 301. May be.

As described above, in the present embodiment, the commit information for managing the version of the source code is acquired, and the task defined for the source code editing work is specified based on the acquired commit information. , Acquiring task information indicating the specified task.

In the present embodiment, the task information obtained as described above is displayed in association with the source code. Correspondence can be easily grasped. According to this, it is possible to efficiently use the source code management tool and the task management tool, and it is possible to improve the convenience of the user in the development of the software product.

Further, in the present embodiment, a file in which each of a plurality of source codes arranged in each of a plurality of folders having a hierarchical structure is stored is displayed as a list, and the source code stored in the file is displayed. The task information indicating the task is displayed in association with the file. With such a configuration, even if the source code management tool manages versions of a plurality of source codes, it is possible to easily grasp the task corresponding to each of the plurality of source codes. It will be possible.

Further, in the present embodiment, task information corresponding to the search condition designated by the user is searched, and a file storing the source code corresponding to the task indicated by the searched task information is displayed as the search result. Specifically, the task information in the present embodiment includes text (for example, title, description, history, etc.) regarding the task indicated by the task information, and the search word (keyword) specified by the user as a search condition is converted into text. The included task information is retrieved.

In the present embodiment, with such a configuration, it is possible to search the source code (file storing the same) using the task information, and to search using only the contents described in the source code. By comparison, various searches can be realized.

Although a comment may be written in the source code, it is also possible to search the source code in which the comment is written, which includes the search word specified as the search condition.

In the present embodiment, the commit comment (commit comment included in the commit information) created by the user when the source code is committed includes a task ID for identifying the task corresponding to the source code. Be described (described). In the present embodiment, such a configuration makes it possible to appropriately specify the correspondence between the source code and the task.

Here, the description has been made assuming that the commit comment includes the task ID, but if the task corresponding to the source code can be specified, the commit comment includes other information (for example, a title). It may be configured to be.

In the present embodiment, the task ID and the task title are displayed as the task information, but the status of the task included in the task information may be displayed. With such a configuration, the user can easily grasp the progress status of the task corresponding to the source code based on whether the status of the task corresponding to each source code is “open” or “closed”. It becomes possible to do.

Further, in the second area 302, a list of tasks managed by the task management tool is displayed. As described above, the source code (file name of the file storing the) corresponding to the task is associated with the task. It may be displayed. According to such a configuration, when a task in which a bug is embedded is clear among the tasks displayed in the second area 302, the source code corresponding to the task (that is, the file to be modified Candidates) can be easily grasped.

In this embodiment, the correspondence table creation unit 11, the task information acquisition unit 12, the storage unit 13, the first display processing unit 14, the search unit 15, and the second display processing unit 16 are included in the management device 10. However, each of these units 11 to 16 may be distributed and arranged in a plurality of devices. That is, the management device 10 according to the present embodiment may be realized by a plurality of devices. Further, the management device 10 may be configured such that at least a part of each of these units 11 to 16 is arranged in an external device.

(Second embodiment)
Next, a second embodiment will be described. In the present embodiment, the same parts as those in the drawings used in the description of the first embodiment described above are designated by the same reference numerals. Further, in the following description, the part different from the above-described first embodiment will be mainly described.

FIG. 18 is a block diagram showing an example of the functional configuration of the management apparatus according to this embodiment. As illustrated in FIG. 18, the management device 10 includes a progress degree calculation unit 17 in addition to the units 11 to 16 illustrated in FIG. 1 described above.

For example, for each folder in which a plurality of files are arranged, the progress degree calculation unit 17 calculates the ratio of tasks that are open (working) in the folder (hereinafter referred to as progress degree).

The degree of progress calculated for each folder by the degree-of-progress calculation unit 17 is displayed by the first display processing unit 14 in association with (the folder name of) the folder.

Next, an example of the processing procedure of the management apparatus 10 according to the present embodiment will be described with reference to the flowchart in FIG.

First, the processes of steps S41 to S43 corresponding to the processes of steps S21 to S23 shown in FIG. 8 described above are executed.

Next, the progress calculation unit 17 calculates the progress in each folder in which a plurality of files are arranged (step S44).

Here, the process of step S44 will be specifically described with the folder for calculating the progress degree as the target folder.

First, the progress degree calculation unit 17 identifies a plurality of files arranged in the target folder based on the hierarchical structure information held in the source code management tool.

Next, the progress degree calculation unit 17 acquires task information indicating a task corresponding to the source code stored in each of the identified plurality of files, based on the correspondence table stored in the storage unit 13. ..

The degree-of-progress calculation unit 17 calculates, as the degree of progress, the proportion of tasks whose task status is “open” among the tasks indicated by the acquired task information. The degree of progress may be the percentage of tasks whose task status is “closed”.

In step S44, the above-described processing is executed for all the folders to calculate the progress degree for each folder.

When the process of step S44 is executed, the processes of steps S45 and S46 corresponding to the processes of steps S24 and S25 shown in FIG. 8 described above are executed.

Further, the first display processing unit 14 displays the degree of progress calculated for each folder in step S44 in association with the folder name of the folder displayed in step S24 (step S47).

Next, with reference to FIG. 20, a display example of the first area 301 after the above-described processing shown in FIG. 19 is executed will be described.

As shown in FIG. 20, the hierarchical structure of the folder A, the folder 1 and the folder 2 is displayed in the first area 301, and the files 1, 2 and 3 arranged in the folder 1 are further displayed. ing.

Further, in the first area 301, the first task information “the job is executed on the day following the #12 data collection day” is displayed in association with the file 1. Similarly, in the first area 301, the second task information “change #10 theme for each user” in association with the file 2 is displayed. Further, in the first area 301, the third task information “determine the size of #1 bubble in consultation with Mr. XX” in association with the file 3 is displayed.

Further, in the first area 301, the above-mentioned first to third task information items associated with the folder 1 are displayed.

Here, it is assumed that the status of the task included in the first and second task information is “open” and the status of the task included in the third task information is “closed”. In this case, 2/3 is calculated as the degree of progress in the folder 1.

The degree of progress in the folder 1 calculated in this way is displayed in the first area 301 in association with the folder 1. Specifically, as shown in FIG. 20, the degree of progress in the folder 1 is, for example, in an area corresponding to the degree of progress (ratio) in a rectangular frame 401 surrounding the folder name “folder 1”. It is displayed by adding color. In the example shown in FIG. 20, since the degree of progress in the folder 1 is 2/3, the color is given to the 2/3 area in the frame 401.

In the first area 301, for example, the status of tasks included in the task information indicating the tasks corresponding to the source code stored in each file may be displayed in the same manner. Specifically, as shown in FIG. 20, when the status of the task included in the above-described first and second task information is “open”, a rectangular frame 402 surrounding the file name “file 1”. And the color is given to all of the areas within the rectangular frame 403 surrounding the file name “file 2”. On the other hand, when the task status included in the third task information is “closed”, no color is given to the area within the rectangular frame 404 surrounding the file name “file 3”.

As described above, in the present embodiment, the task information indicating the task corresponding to the source code stored in each of the plurality of files is displayed in association with the folder in which the plurality of files are arranged, and the display is performed. The ratio (that is, the degree of progress) of tasks whose status is “open” (first status) among the tasks indicated by the executed task information is displayed. In the present embodiment, with such a configuration, for example, the task status corresponding to the source code stored in each of the plurality of files arranged in the folder is arranged in the folder without individually checking the status of the task. It is possible to easily grasp the progress status of the entire task corresponding to the source code stored in a plurality of files.

Further, in the present embodiment, for example, by displaying the status of the task corresponding to the source code stored in each file in the same manner (format), the status of the task can be individually confirmed. Is.

Note that this embodiment may be applied to the above-described first embodiment. Specifically, the degree of progress in the present embodiment may be displayed together with the search result described in the first embodiment, for example.

(Third Embodiment)
Next, a third embodiment will be described. In the present embodiment, the same parts as those in the drawings used in the description of the first embodiment described above are designated by the same reference numerals. Further, in the following description, a part different from the first and second embodiments described above will be mainly described.

FIG. 21 is a block diagram showing an example of the functional configuration of the management apparatus according to this embodiment. As illustrated in FIG. 21, the management device 10 includes an object creating unit 18 in addition to the units 11 to 16 illustrated in FIG. 1 described above.

As described in the first embodiment, the task information indicating the task corresponding to the source code (task information stored in the storage unit 13) includes texts such as a title, a description, and a history.

The object creating unit 18 creates an object (hereinafter referred to as a word cloud) that represents a word that appears in the text included in the task information as described above.

The word cloud created by the object creating unit 18 is displayed in association with the task information in which the word cloud is created and the source code (file storing the task) corresponding to the task indicated by the task information.

Next, an example of the processing procedure of the management device 10 according to the present embodiment will be described with reference to the flowchart in FIG.

First, the processes of steps S51 to S53 corresponding to the processes of steps S21 to S23 shown in FIG. 8 described above are executed.

Next, the object creating unit 18 creates a word cloud based on the task information acquired in step S53 and stored in the storage unit 13 (step S54).

Here, the process of step S54 will be specifically described. The object creating unit 18 acquires one of the task information stored in the storage unit 13 (hereinafter referred to as target task information).

The object creating unit 18 performs analysis processing such as morphological analysis on the text (title, description, and history) included in the acquired target task information, and extracts the words included in the text.

The object creating unit 18 creates a word cloud representing the extracted words. A specific example of the word cloud created by the object creating unit 18 will be described later.

In step S54, the above-described process is executed for all the task information stored in the storage unit 13 (that is, the task information indicating the task corresponding to the source code), so that the word for each task information is stored. A cloud is created.

When the process of step S54 is executed, the processes of steps S55 and S56 corresponding to the processes of steps S24 and S25 shown in FIG. 8 described above are executed.

Further, the first display processing unit 14 sets the word cloud created for each task information in step S54 to the file name of the file storing the source code corresponding to the task indicated by the task information displayed in step S24. They are displayed in association with each other (step S57).

According to the processing shown in FIG. 22, the outline of the source code stored in each file can be displayed in the word cloud of the task (task information indicating the) corresponding to the source code.

Next, with reference to FIG. 23, a display example of the first area 301 after the above-described processing of FIG. 22 is executed will be described.

As shown in FIG. 23, a hierarchical structure of a folder A, a folder 1 and a folder 2 is displayed in the first area 301, and a file 1, a file 2 and a file 3 arranged in the folder 1 are further displayed. ing.

Further, in the first area 301, the first task information “the job is executed on the day following the #12 data collection day” is displayed in association with the file 1. Similarly, in the first area 301, the second task information “change #10 theme for each user” in association with the file 2 is displayed. Further, in the first area 301, the third task information “determine the size of #1 bubble in consultation with Mr. XX” in association with the file 3 is displayed.

Here, in the present embodiment, the text included in the first task information in association with the file 1 and the first task information (for example, the title “the job is executed on the next day of the data collection date”) The word cloud 501 created from is further displayed.

Note that the word cloud 501 represents the appearance frequency (priority) of each word included in the text included in the first task information. Specifically, the word cloud 501 includes words written in a size determined according to the appearance frequency in the text included in the first task information.

Further, in association with the file 2 and the second task information, the word cloud 502 created from the text included in the second task information (for example, the title “change the theme for each user”) is further displayed.

The word cloud 502 represents the appearance frequency of each word that constitutes the text included in the second task information. Specifically, the word cloud 502 includes words written in a size determined according to the frequency of appearance in the text included in the second task information.

Similarly, a word cloud created in association with the file 3 and the third task information, and created from the text included in the third task information (for example, the title "Determine the bubble size in consultation with Mr. XX") 503 is further displayed.

The word cloud 503 represents the frequency of appearance of each word that constitutes the text included in the third task information. Specifically, the word cloud 503 includes words expressed in a size determined according to the frequency of appearance in the text included in the third task information.

According to the above-mentioned word clouds 501 to 503, the user can see the words that appear in the text included in each of the first to third task information (that is, the content of the task indicated by each of the first to third task information). ) Can be grasped.

Here, although not described in FIG. 22 described above, the word cloud in the present embodiment may be created in a folder in which a plurality of files are arranged. In this case, the word cloud may be created from the text included in the task information indicating the task corresponding to the source code stored in each of the plurality of files arranged in the folder.

The word cloud 504 shown in FIG. 23 is the first to third task information displayed in association with the folder 1 (that is, the sources stored in each of the files 1 to 3 arranged in the folder 1). It is a word cloud created from the text included in the first to third task information indicating the task corresponding to the code.

The display mode of the word cloud shown in FIG. 23 is an example, and if the user can grasp the word (and the appearance frequency of the word) that appears in the text included in the task information, the word cloud is, for example, Words that appear frequently may be displayed in other modes such as being displayed in a specific color.

Further, it is assumed that the words included in the word cloud are, for example, a predetermined number of words that appear frequently in the text included in the task information and that have a high appearance frequency.

Further, as shown in FIG. 23, when the word cloud displayed in the first area 301 is designated by the user, the word cloud may be enlarged and displayed.

Note that, in FIG. 23, a word cloud created mainly from the titles included in the task information is shown for convenience, but the word cloud is, as described above, the description and history included in the task information. It may include a word that appears in.

As described above, in the present embodiment, a word cloud (object) that represents a word that appears in text included in task information is created, and the created word cloud is a source code corresponding to the task indicated by the task information. Is displayed in association with.

In addition, in this embodiment, the word loud represents the appearance frequency of the word in the text included in the task information. Specifically, the word cloud includes words expressed in a size determined according to the frequency of appearance in the text included in the task information.

In the present embodiment, by displaying the word cloud in association with the source code as described above, it is possible to intuitively grasp the outline of the source code without opening the file storing the source code. Become.

Note that this embodiment may be applied to the above-described first and embodiment. Specifically, the word cloud in the present embodiment is displayed, for example, in association with the file acquired as the search result when the search result described in the first embodiment is displayed in the first area 301. Alternatively, the task (task information indicating the task) may be displayed in association with the task when the list is displayed in the second area 302. Further, the word cloud may be displayed together when displaying the degree of progress in the second embodiment described above.

According to at least one embodiment described above, it is possible to provide a management device, method, and program capable of improving the convenience of the user in developing a software product.

Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the invention described in the claims and equivalents thereof as well as included in the scope and the gist of the invention.

10... Management device, 11... Correspondence table creation unit, 12... Task information acquisition unit, 13... Storage unit, 14... First display processing unit, 15... Search unit, 16... Second display processing unit, 17... Progress degree calculation Parts, 18... Object creation unit, 101... CPU, 102... Nonvolatile memory, 103... Main memory, 104... BIOS-ROM, 105... System controller, 106... Input device, 107... Display device, 108... EC.

Claims (12)

First acquisition means for acquiring commit information for managing the version of the source code,
Specifying means for specifying a task defined for the editing work of the source code based on the obtained commit information,
Second acquisition means for acquiring task information indicating the specified task,
A display processing unit that displays the acquired task information in association with the source code. The first acquisition unit acquires a plurality of commit information for managing each version of a plurality of source codes,
The specifying unit specifies a task corresponding to each of the plurality of source codes based on the plurality of acquired commit information,
The display processing means displays a list of files in which each of the plurality of source codes arranged in each of a plurality of folders having a hierarchical structure is stored, and a task corresponding to the source code stored in the files. The management device according to claim 1, wherein the task information indicating the item is displayed in association with the file. Further comprising search means for searching task information corresponding to a search condition designated by a user who uses the management device,
The management device according to claim 2, wherein the display processing unit displays a file storing a source code corresponding to the task indicated by the searched task information, as a search result. The task information includes text related to the task indicated by the task information,
The search condition includes a keyword specified by the user,
The management apparatus according to claim 3, wherein the search unit searches for task information in which the keyword includes a keyword specified by the user. The management device according to claim 4, wherein the search result includes a file that stores a source code including a keyword specified by the user or a source code in which a comment including the keyword is described. The task information includes the status of the task indicated by the task information,
The display processing means displays task information indicating a task corresponding to a source code stored in each of the plurality of files in association with a folder in which the plurality of files are arranged, and the displayed task. The management device according to claim 2, wherein a ratio of tasks whose status is the first status is displayed among the tasks indicated by the information. Further comprising a creating means,
The task information includes text about the task,
The creating means creates an object representing a word that appears in the text included in the task information,
The management apparatus according to claim 1, wherein the display processing unit displays the created object in association with the source code. The management device according to claim 7, wherein the object represents an appearance frequency of the word in the text included in the task information. The management device according to claim 8, wherein the words included in the object are displayed in a size determined according to the frequency of appearance in the text included in the task information. The commit information includes task identification information for identifying a task corresponding to the source code,
The management device according to claim 1, wherein the specifying unit specifies a task corresponding to the source code based on task identification information included in the commit information. Steps to get the commit information to manage the source code version,
Identifying a task defined for the editing work of the source code based on the obtained commit information,
Obtaining task information indicating the identified task,
Displaying the obtained task information in association with the source code. On the computer,
Steps to get the commit information to manage the source code version,
Identifying a task defined for the editing work of the source code based on the obtained commit information,
Obtaining task information indicating the identified task,
A step of displaying the acquired task information in association with the source code.

Images