JP7322255B2 - Electronic computer, method and program - Google Patents

Description

The embodiments of the present invention relate to electronic computers, methods and programs.

In general, it is necessary to understand the contents of source code written in a programming language in order to operate and maintain software whose specifications are unknown, which is called legacy code.

However, it is difficult and extremely time consuming to understand the contents of a huge amount of source code (hereinafter referred to as code reading).

"Doxygen", [online], 14 Feb, 2011, [searched November 20, 2018], Internet <URL: http://www.doxygen.jp/>

Therefore, the problem to be solved by the present invention is to provide a computer, method, and program capable of supporting code reading.

A computer according to an embodiment includes display processing means and editing processing means. The display processing means displays a screen on which a first area displaying source code and a second area displaying a diagram representing at least part of the source code are arranged. The editing processing means edits the diagram displayed in the second area. A plurality of functions are described in the source code. When at least one function described in the source code displayed in the first area is designated by a user using a computer, the editing processing means converts the function symbol representing the function into the second area. Add to the diagram displayed in the area. The display processing means, when a first comment is created at a position specified by the user in the source code displayed in the first area, displays function symbols displayed in the second area. The first comment is added to the function symbol representing the function described at the position specified by the user in the source code, and the function symbol displayed in the second area is displayed by the user. When the second comment is created for the designated function symbol, the second comment is added to the position where the function represented by the function symbol is described in the source code displayed in the first area. displayed.

1 is a block diagram showing an example of the functional configuration of a code reading assistance device according to an embodiment; FIG. The figure which shows an example of the system configuration|structure of a code reading assistance apparatus. 4 is a diagram showing an example of the data structure of function information included in code analysis information; FIG. A diagram showing an example of the data structure of code block information included in code analysis information. The figure which shows an example of the data structure of code addition information. The figure which shows an example of the data structure of diagram information. The figure which shows an example of the data structure of diagram additional information. 4 is a flowchart showing an example of a processing procedure of diagram display processing; FIG. 4 is a diagram showing an example of a display screen when the code reading support program is started; FIG. 4 is a diagram showing an example of a display screen when source code is displayed in the code display area; FIG. 4 is a diagram for specifically explaining function symbols; FIG. 4 is a diagram for specifically explaining diagram display processing; FIG. 4 is a diagram for specifically explaining diagram display processing; FIG. 4 is a diagram for specifically explaining diagram display processing; FIG. 4 is a diagram for explaining a case where function symbols representing the functions are added after a plurality of functions are specified; The figure which shows an example of the display screen in which the area|region for displaying a diagram as a whole is further arranged. 6 is a flowchart showing an example of a processing procedure of comment addition processing; The figure which shows an example of a comment creation screen. FIG. 5 is a diagram for specifically explaining comment addition processing; 5 is a flowchart showing an example of a processing procedure of highlighting change processing; FIG. 5 is a diagram for specifically explaining highlighting change processing;

Embodiments will be described below with reference to the drawings.
The computer according to the present embodiment is used to support understanding (code reading) of source code written in a programming language such as Java (registered trademark) or C language. Hereinafter, the computer according to this embodiment will be referred to as a code reading support device for convenience.

FIG. 1 is a block diagram showing an example of the functional configuration of the code reading support device according to this embodiment. As shown in FIG. 1, the chord reading support device 10 includes a chord storage section 11, a diagram storage section 12, a chord display processing section 13, a diagram display processing section 14, an operation reception section 15 and an editing processing section 16.

The code storage unit 11 stores, for example, source codes whose contents should be understood by the user using the code reading support device 10 . The code storage unit 11 also stores code analysis information indicating analysis results for the source code stored in the code storage unit 11 . Note that the code storage unit 11 may store a plurality of source codes and code analysis information indicating analysis results for each of the plurality of source codes.

Here, the source code includes a plurality of functions, each of which consists of at least one code block. In the present embodiment, a code block is, for example, a group (block) of code written over a plurality of lines. equivalent to part.

In this case, the code analysis information stored in the code storage unit 11 indicates functions included in the source code stored in the code storage unit 11, code blocks that constitute the functions, and the like.

To obtain the code analysis information, it is necessary to analyze the source code, and the analysis of the source code is executed in an integrated development environment, for example. Also, Eclipse JDT, Understand, Clang, etc. can be used as code analysis tools for providing this integrated development environment.

Further, the code storage section 11 stores information added to the source code stored in the code storage section 11 when the source code is displayed (hereinafter referred to as code additional information).

The diagram storage unit 12 stores diagram information used to display a diagram representing at least part of the source code stored in the code storage unit 11 . The diagram storage unit 12 also stores information added to the diagram when the diagram is displayed using the diagram information (hereinafter referred to as additional diagram information).

Here, in the chord reading assistance device 10 according to the present embodiment, a screen including at least a chord display area (first display area) and a diagram display area (second display area) is displayed.

The code display processing unit 13 executes processing for displaying the source code stored in the code storage unit 11 in the code display area. Note that the code display processing unit 13 adds code additional information stored in the code storage unit 11 to the source code when displaying the source code in the code display area.

The diagram display processing unit 14 uses the diagram information stored in the diagram storage unit 12 to execute processing for displaying a diagram representing part of the source code displayed in the code display area in the diagram display area. The diagram display processing unit 14 adds the diagram additional information stored in the diagram storage unit 12 to the diagram when displaying the diagram in the diagram display area. The diagram display processing unit 14 uses the chord analysis information stored in the chord storage unit 11 when displaying the diagram.

The operation reception unit 15 receives a user's operation on the source code displayed in the code display area and the diagram displayed in the diagram display area.

The edit processing unit 16 edits the diagram displayed in the diagram display area, for example, based on the user's operation received by the operation receiving unit 15 . Further, the edit processing unit 16 changes (changes) the chord additional information stored in the chord storage unit 11 and the diagram additional information stored in the diagram storage unit 12 based on the user's operation received by the operation reception unit 15. To edit.

The code reading support device 10 according to the present embodiment has a function as a source code viewer (or editor) and a diagram editor function that represents at least part of the source code.

FIG. 2 shows an example of the system configuration of the code reading support device 10 shown in FIG. Although the code reading support device 10 is assumed to be, for example, a personal computer (PC), the code reading support device 10 may be another computer.

As shown in FIG. 2, the code reading support device 10 includes a CPU 101, a nonvolatile 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. .

A CPU 101 is a processor that controls the operation of each component in the code reading support device 10 . The CPU 101 executes various programs loaded into the main memory 103 from the non-volatile memory 102, which is a storage device. This program includes an operating system (OS), a program for supporting code reading as described above (hereinafter referred to as a code reading support program), and the like.

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

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

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. EC 108 is a one-chip microcomputer containing an embedded controller for power management.

Although FIG. 2 shows only the CPU 101, the nonvolatile 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, the code reading support device 10 includes: For example, it may be provided with other storage devices such as HDD (Hard Disk Drive) and SSD (Solid State Drive), or may be provided with a communication device or the like configured to execute communication with an external device. good.

In this embodiment, the code storage unit 11 and the diagram storage unit 12 shown in FIG. 1 are implemented using, for example, the non-volatile memory 102 shown in FIG. 2 or other storage devices.

In the present embodiment, some or all of the units 13 to 16 shown in FIG. 1 cause the CPU 101 shown in FIG. 2 (that is, the computer of the code reading assistance device 10) to execute the code reading assistance program. , that is, implemented by software. Note that the code reading support program can be stored in advance in a computer-readable storage medium and distributed. Also, the code reading assistance program may be downloaded to the code reading assistance device 10 via a network, for example.

Here, some or all of the units 13 to 16 have been described as being realized by software, but some or all of the units 13 to 16 may be realized by hardware, for example, or software and hardware. It may also be implemented as a hardware combination configuration.

Various information stored in the code storage unit 11 and the diagram storage unit 12 shown in FIG. 1 will be described below.

First, the code analysis information stored in the code storage unit 11 will be described with reference to FIGS. 3 and 4. FIG. As described above, the source code stored in the code storage unit 11 includes a plurality of functions, each of which consists of at least one code block. and code block information indicating code blocks that constitute the function.

FIG. 3 shows an example of the data structure of function information included in the code analysis information described above. As shown in FIG. 3, the function information includes source code ID, function ID and location information.

A source code ID is identification information for identifying a source code stored in the code storage unit 11 .

A function ID is identification information for identifying a function included in the source code identified by the source code ID associated with the function ID.

The position information is the function ID associated with the position information in the source code stored in the code storage unit 11 (that is, the source code identified by the source code ID associated with the position information). indicates the location of the function identified by . Note that the position information included in the function information includes line numbers (start line and end line) where the function in the source code is described.

In the example shown in FIG. 3, function information 111a and 111b are shown. The function information 111a includes a source code ID "1", a function ID "1", and position information "x1-x2". According to this function information 111a, the source code identified by the source code ID "1" includes the function identified by the function ID "1", and the function is from the x1 line in the source code. It is shown that it is described in the x2 line.

On the other hand, the function information 111b includes source code ID "1", function ID "2", and position information "y1 to y2". According to this function information 111b, the source code identified by the source code ID "1" includes the function identified by the function ID "2", and the function is from line y1 in the source code. It is shown that it is described in the y2 line.

3, only the function information 111a and 111b are explained for convenience, but the code analysis information stored in the code storage unit 11 includes functions included in the source code stored in the code storage unit 11. contains function information for

FIG. 4 shows an example of the data structure of code block information included in code analysis information. As shown in FIG. 4, the code block information includes function IDs, code block IDs, and position information.

The function ID is a function ID included in the function information described above, and is identification information for identifying a function included in the source code stored in the code storage unit 11 .

A code block ID is identification information for identifying a code block forming a function identified by a function ID associated with the code block ID.

The position information indicates the position of the code block identified by the code block ID associated with the position information in the source code stored in the code storage unit 11 described above. Note that the position information included in the code block information includes line numbers where the code blocks in the source code are written.

In the example shown in FIG. 4, code block information 112a and 112b are shown. The code block information 112a includes function ID "1", code block ID "1", and position information "x11 to x12". According to the code block information 112a, the function identified by the function ID "1" is composed of the code block identified by the code block ID "1", and the code block is the x11th line in the source code. It is shown that it is described in the x12th line.

On the other hand, the code block information 112b includes function ID "1", code block ID "2", and position information "x13-x14". According to the code block information 112b, the function identified by the function ID "1" is composed of the code block identified by the code block ID "2", and the code block is the x13 line in the source code. It is shown that it is described in the x14th line.

4, only the code block information 112a and 112b are explained for convenience, but the code analysis information stored in the code storage unit 11 includes functions included in the source code stored in the code storage unit 11. contains code block information for each code block that constitutes the

As shown in FIG. 4, one function (that is, the function identified by the function ID "1") corresponds to a plurality of code blocks (that is, code blocks identified by each of the code block IDs "1" and "2"). block), but the function may have a nested structure such that, for example, another code block is written within one code block. Alternatively, the function itself may be treated as one code block.

FIG. 5 shows an example of the data structure of code additional information stored in the code storage unit 11. As shown in FIG. As shown in FIG. 5, the code additional information includes a source code ID, additional content, and position information.

A source code ID is identification information for identifying a source code stored in the code storage unit 11 .

The additional content indicates content added to the source code when the source code identified by the source code ID associated with the additional content is displayed in the code display area. Note that, in the present embodiment, comments, emphasis information, and the like, for example, are added to the source code displayed in the code display area.

The position information is the source code stored in the code storage unit 11 to which comments, emphasis information, etc. are added according to the additional content associated with the position information (that is, the source code associated with the position information). Indicates the location (portion) of the source code identified by the code ID. The position information included in the code additional information includes line numbers and the like, like the position information included in the function information and code block information described above.

In the example shown in FIG. 5, code additional information 113a and 113b are shown. The code additional information 113a includes a source code ID "1", additional content "emphasis", and position information "x1 to x2". According to this code addition information 113a, when the source code identified by the source code ID "1" is displayed in the code display area, the emphasis information is added to the x1 line to the x2 line in the source code. It is shown that

When the emphasis information is added to the source code, for example, a figure, symbol, mark, or the like indicating that the emphasis is placed on the corresponding portion of the source code (that is, by the position information included in the code addition information) indicated position), but the font (typeface, thickness, color, etc.) of the portion (text) may be changed. That is, in the present embodiment, "emphasis information is added to (the part of) the source code" means that the user can understand that the relevant source code part is emphasized. It refers to performing a predetermined process on the part of the source code. In the following description, adding highlighting information to the source code is expressed as highlighting the source code for convenience.

On the other hand, the code additional information 113b includes the source code ID "1", additional content "comment 1", and position information "x15". According to the code addition information 113b, when the source code identified by the source code ID "1" is displayed in the code display area, it is indicated that the comment 1 is added to the x15 line in the source code. It is

Although only the code additional information 113a and 113b has been described in FIG. 5 for the sake of convenience, the code storage unit 11 may store other additional information.

Also, in the example shown in FIG. 5, only comments and emphasis information are added as additional content, but the additional content is added to the source code when the source code is displayed (that is, the It may be other content as long as it changes the display of the source code.

Next, FIG. 6 shows an example of the data structure of diagram information stored in the diagram storage unit 12. As shown in FIG. As shown in FIG. 6, the diagram information includes diagram ID, caller function ID and callee function ID.

The diagram ID is identification information for identifying the diagram displayed in the above diagram display area.

The caller function ID is identification information for identifying a function (first function) included in the source code stored in the code storage unit 11 . A function identified by a caller function ID is defined to include a function identified by a callee function ID associated with the caller function ID.

A callee function ID is identification information for identifying a function (second function) included in the source code stored in the code storage unit 11 . The function identified by the callee function ID is a function described in the function identified by the callee function ID associated with the callee function ID.

That is, the function identified by the above caller function ID is the caller function, and the function identified by the callee function ID is the callee function. For this reason, the caller function ID and the callee function ID included in the diagram information are used to represent the calling relationship between a plurality of functions in the diagram displayed using the diagram information.

In the example shown in FIG. 6, diagram information 121a and 121b are shown. The diagram information 121a includes diagram ID "1", caller function ID "1", and callee function ID "2". According to this diagram information 121a, the diagram identified by the diagram ID "1" is a calling function in which the function identified by the callee function ID "2" is called in the function identified by the caller function ID "1". shown to represent the relationship.

On the other hand, the diagram information 121b includes diagram ID "1", caller function ID "2", and callee function ID "3". According to this diagram information 121b, the diagram identified by the diagram ID "1" is a call that the function identified by the callee function ID "3" is called in the function identified by the caller function ID "2". shown to represent the relationship.

Although only the diagram information 121a and 121b has been described in FIG. 6 for the sake of convenience, the diagram storage unit 12 may store other diagram information.

Note that as shown in FIG. 6, a diagram (for example, a diagram identified by diagram ID "1") may represent a plurality of calling relationships.

FIG. 7 shows an example of the data structure of diagram additional information stored in the diagram storage unit 12. As shown in FIG. As shown in FIG. 7, the diagram additional information includes diagram ID, additional content and position information.

The diagram ID is identification information for identifying the diagram displayed in the diagram display area.

The additional content indicates content added to the diagram when the diagram identified by the diagram ID associated with the additional content is displayed in the diagram display area. Note that, in the present embodiment, for example, comments and emphasis information are added to the diagrams displayed in the diagram display area.

The positional information indicates a position on the diagram identified by the diagram ID associated with the positional information, to which comments, emphasis information, or the like are added according to the additional content associated with the positional information. As the position information included in the diagram additional information, for example, the function ID and code block information ID described above are used.

In the example shown in FIG. 7, additional diagram information 122a and 122b are shown. The diagram additional information 122a includes diagram ID "1", additional content "emphasis", and position information "function ID "1"". According to this diagram additional information 122a, when the diagram identified by the diagram ID "1" is displayed in the diagram display area, the emphasis information is added to the position expressing the function identified by the function ID "1". It is shown that

In addition, when emphasis information is added to the diagram, for example, a color indicating that it is emphasized may be added to the corresponding part of the diagram (that is, the position indicated by the position information included in the diagram information). However, a symbol, mark, pattern, or the like indicating that the portion is emphasized may be added. That is, in the present embodiment, "emphasis information is added to (a part of) a diagram" means that the diagram is displayed so that the user can understand that the relevant diagram part is emphasized. It means to apply a predetermined process to the part of In the following description, adding emphasis information to a diagram is referred to as highlighting the diagram for convenience.

On the other hand, the diagram additional information 122b includes diagram ID "1", additional content "comment 2", and position information "code block ID "1". According to this diagram additional information 122b, when the diagram identified by the diagram ID "1" is displayed in the diagram display area, the comment 2 is placed at the position expressing the code block identified by the code block ID "1". is shown to be added.

It should be noted that a diagram can represent not only functions included in the source code but also code blocks that constitute the functions, and a specific example of the diagram will be described later.

Although various information used in the present embodiment is described in FIGS. 3 to 7 above, the information described in FIGS. 3 to 7 is an example, and part of the information may be omitted. , the information may include other information (items).

The data structures shown in FIGS. 3 to 5 are only examples, and the code analysis information (function information and information) and code additional information stored in the code storage unit 11 may be collectively managed as one piece of information. good. Similarly, the data structures shown in FIGS. 6 and 7 are examples, and the diagram information and diagram additional information stored in the diagram storage unit 12 may be collectively managed as one piece of information.

Next, the operation of the code reading assistance device 10 according to this embodiment will be described. Here, the processing for generating and displaying a diagram representing part of the source code (hereinafter referred to as diagram display processing) and the processing for adding comments to the source code (hereinafter referred to as comment addition processing). notation) and processing for changing the presence/absence of highlighting for the source code (hereinafter referred to as highlighting change processing and notation).

First, an example of the processing procedure of the diagram display processing will be described with reference to the flowchart of FIG.

A user using the code reading support device 10 activates the above code reading support program on the code reading support device 10 .

When the code reading support program is started on the code reading support device 10, the display device 107 (display) provided in the code reading support device 10 displays a screen as shown in FIG.

As shown in FIG. 9 , a screen (hereinafter referred to as a display screen) 200 displayed on the chord reading support device 10 includes a chord display area 201 and a diagram display area 202 .

In the example shown in FIG. 9, the chord display area 201 and the diagram display area 202 are arranged side by side, for example, vertically adjacent to each other. Note that the chord display area 201 and the diagram display area 202 may be arranged adjacent to each other in the horizontal direction, for example.

In addition, the display screen 200 further includes a file selection area 203 . The user can select a source code (file) to be displayed, for example, in the code display area 201 in the file selection area 203 .

The user can create a diagram representing part of the source code by performing various operations on the display screen 200 described above.

Further, when diagram information (file) for displaying a diagram created in the past, for example, is selected in the file selection area 203, the diagram can be displayed in the diagram display area 202.

Here, when creating a diagram representing part of the source code as described above, the user selects the source code (file) in the file selection area 203 .

In this case, the code display processing unit 13 displays the source code selected by the user (hereinafter referred to as the target source code) in the code display area 201 (step S1).

If the entire target source code cannot be displayed in the code display area 201 , the target source code is partially displayed in the code display area 201 . In this case, the user scrolls the display of the code display area 201 using the input device 106 (for example, mouse and keyboard) provided in the code reading support device 10 to display the desired portion of the target source code. shall be able to

When the process of step S1 is executed, the user displays one of a plurality of functions included in the target source code (hereinafter referred to as a first target function) in the code display area 201, and displays the first target function. Perform the operation to specify the target function (notation as function addition operation). The user can instruct to add the first target function to the diagram by performing this function addition operation. Note that the function addition operation includes an operation of moving the cursor to the position where (the definition of) the first target function is described in the code display area 201, but may be another operation.

The operation accepting unit 15 determines whether or not the function addition operation described above has been accepted (performed by the user) (step S2).

If it is determined that the function addition operation has been accepted (YES in step S2), the editing processing unit 16 creates a diagram (hereinafter referred to as a target diagram) to which the first target function (part of the target source code) has been added. ) is generated (step S3). In this case, the edit processing unit 16 generates diagram information including a diagram ID for identifying the target diagram and a function ID (caller function ID) for identifying the first target function. The diagram information generated in step S3 is stored in the diagram storage unit 12. FIG.

Next, the edit processing unit 16 generates additional diagram information to be added to the target diagram to be displayed using the diagram information generated in step S3 (step S4). In this case, the edit processing unit 16 generates diagram additional information including, for example, a diagram ID for identifying the target diagram, additional content "emphasis", and a function ID (position information) for identifying the first target function. The diagram additional information generated in step S4 is stored in the diagram storage unit 12. FIG.

When the process of step S4 is executed, the diagram display processing unit 14 generates a target diagram based on the diagram information and diagram additional information stored in the diagram storage unit 12 (step S5).

According to the above-described diagram information and diagram additional information, in step S5, a first object function is added and an object diagram in which the first object function is highlighted is generated. The target diagram generated in step S5 is displayed in the diagram display area 202 (step S6).

In addition, the editing processing unit 16 adds additional information (hereinafter referred to as code additional information ) is generated (step S7). In this case, the edit processing unit 16, for example, inputs the source code ID for identifying the target source code displayed in step S1, the additional content "emphasis", and the line number (position information) where the first target function is described. Generate code additional information containing The code additional information generated in step S7 is stored in the code storage section 11. FIG.

When the process of step S7 is executed, the code display processing unit 13 reflects the code additional information stored in the code storage unit 11 on the target source code displayed in the code display area 201 (step S8). According to the code additional information described above, the part where the first target function of the target source code displayed in the code display area 201 is described is highlighted by executing the process of step S8. According to this, in the target source code, functions added to the target diagram and functions not added to the target diagram can be displayed separately.

After the process of step S8 is executed, the process returns to step S2 and the process is repeated. Here, the code display area 201 displays the part where the first target function of the target source code is described. A function addition operation can be performed to specify another function described (hereinafter referred to as a second target function). The user instructs to add the second target function to the diagram by performing this function addition operation.

When it is determined in step S2 that such a function addition operation has been accepted, the part where the definition of the second target function is described is displayed in the code display area 201, and the processes after step S3 are executed. .

Since the second target function is written in the first target function, it corresponds to the callee function when the first target function is the caller function. In this case, in step S3, the diagram ID for identifying the target diagram, the function ID for identifying the first target function (caller function ID), and the function ID for identifying the second target function (callee Generate diagram information including function ID). According to this, the second object function can be added to the object diagram, and the calling relationship between the first object function and the second object function can be expressed in the object diagram.

The relationship between the first target function (caller function) and the second target function (callee function) is determined, for example, by the code analysis information stored in the code storage unit 11 (that is, each function is described). However, even if information defining the relationship (for example, call location information including connection lines and connection destinations in the target source code) is separately managed in the code reading support device 10 good.

Since the processing of steps S4 to S7 executed below is as described above, detailed description thereof will be omitted here.

According to the diagram display process described above, a function specified by the user (for which the function addition operation was performed) among the functions included in the target source code is added to the target diagram, and between the added functions can be automatically represented in the target diagram.

If it is determined in step S2 that the function addition operation has not been accepted (NO in step S2), the diagram display processing ends.

In FIG. 8, it is assumed that the processes are executed in the order of steps S3 to S7, but the order of the processes may be changed as appropriate. Specifically, for example, the processes of steps S3 to S5 may be executed after the processes of steps S7 and S8.

The diagram display processing described above will be specifically described below. FIG. 10 is an example of a screen (display screen) displayed on the code reading support device 10 when the process of step S1 shown in FIG. 8 is executed.

As shown in FIG. 10, when step S1 shown in FIG. 8 is executed, the target source code is displayed in the code display area 201 included in the display screen 200. FIG. In the example shown in FIG. 10, the code display area 201 displays a portion (5th to 13th lines) where the definition of the main function included in the target source code is described. In FIG. 10, the numerical value attached to the left side of each line of the target source code represents the line number.

The user can perform a function addition operation to specify, for example, the main function on the display screen 200 shown in FIG. In this case, the user instructs to add the main function to the diagram by, for example, placing the cursor on the part where the definition of the main function is written in the code display area 201 .

When the main function is designated as described above, the processes of steps S3 to S6 shown in FIG. 8 are executed. In step S3 in this case, diagram information including a diagram ID for identifying the target diagram to which the main function is added and a function ID (caller function ID) for identifying the main function is generated. At this point, the function corresponding to the callee function has not been specified, so the diagram information does not include the callee function ID.

In step S4, the diagram ID (diagram ID for identifying the target diagram) included in the diagram information generated in step S3, the additional content "emphasis", and the function ID for identifying the main function (position information ) is generated.

In step S5, a target diagram is generated based on the diagram information generated in step S3 and the diagram additional information generated in step S4. In step S5, a target diagram is generated that includes a symbol (hereinafter referred to as function symbol) representing the main function identified by the function ID (caller function ID) included in the diagram information.

Now, with reference to FIG. 11, the function symbols described above will be specifically described. Here, for the sake of convenience, a function different from the above-described main function will be used for explanation.

A function 301 (toy_call function) shown on the left side of FIG. 11 is composed of a code block 301a corresponding to a while statement, and code blocks 301b and 301c corresponding to if statements. The code block 301a further includes a code block 301d corresponding to an if statement.

A function symbol 302 representing such a function 301 is composed of a main symbol 301a representing the entire function 301 and sub-symbols 302b to 302e representing code blocks 301a to 301d constituting the function 301 respectively.

The positions where the sub-symbols 302b to 302e are arranged in the function symbol 302 (main symbol 302a) are determined based on the code analysis information (function information and code block information) stored in the code storage section 11. FIG. Specifically, for example, the sub-symbol 302b is arranged on the main symbol 302a corresponding to the position where the code block 301a represented by the sub-symbol 302b in the function 301 is written. The same is true for other sub-symbols 302c-302e.

That is, in the present embodiment, the code block (the position where the function ID is described) constituting the function identified by the function ID (caller function ID and callee function ID) included in the diagram information is included in the function ID. By specifying based on the code block information, it is possible to generate a function symbol composed of a main symbol representing the entire function and sub-symbols representing code blocks constituting the function.

The object diagram including the function symbols generated as described above is displayed in the diagram display area 202 in step S6.

When the processes of steps S3 to S6 are executed, the processes of steps S7 and S8 are executed. In step S7 in this case, code additional information including a source code ID for identifying the target source code, additional content "emphasis", and position information "5 (line) to 13 (line)" is generated. Further, in step S8, the code additional information generated in step S7 is reflected in the target source code displayed in the code display area 201. FIG.

Here, FIG. 12 shows an example of the display screen 200 after the processes of steps S3 to S8 have been executed.

Although the details are omitted, the function symbol 400 representing the main function shown in FIG. It is composed of a symbol 400b. Also, the function symbols 400 (main symbol 400a and sub-symbol 400b) displayed in the diagram display area 202 are highlighted (for example, displayed in color) based on the above diagram additional information. ).

Also, in the code display area 201, the part where the definition of the main function is described is highlighted. Specifically, for example, the part where the definition of the main function is described displayed in the code display area 201 shown in FIG. A highlighted highlighting line 500 is provided.

As described above, in this embodiment, by specifying a function included in the target source code in the code display area 201, the target diagram including the function symbol representing the function can be displayed in the diagram display area 202. The portion where the function is described displayed in the code display area 201 can be highlighted.

Next, the user can specify another function described in the main function displayed in the code display area 201 (that is, perform a function addition operation on the other function). In the code display area 201 shown in FIG. 12, for example, the toymodel_exec function included in the main function is specified.

When the toymodel_exec function is specified in the code display area 201 shown in FIG. 12, the part where the definition of the toymodel_exec function is described is displayed in the code display area 201 included in the display screen 200 as shown in FIG. (that is, the display in the code display area 201 transitions from the main function to the toymodel_exec function). Note that FIG. 13 shows only part of the toymodel_exec function.

Here, the processing of steps S3 to S6 shown in FIG. 8 is executed. In step S3 in this case, the diagram ID for identifying the target diagram to which the toymodel_exec function is added, the function ID (caller function ID) for identifying the main function, and the function for identifying the toymodel exec function Diagram information including an ID (called function ID) is generated.

Also, in step S4, additional diagram information is generated that includes the diagram ID, the additional content "emphasis", and the function ID (positional information) for identifying the toymodel_exec function included in the diagram information generated in step S3.

In step S5, a target diagram is generated based on the diagram information generated in step S3 and the diagram additional information generated in step S4.

In this case, in step S5, a function symbol (hereinafter referred to as main function symbol) representing the main function identified by the caller function ID included in the diagram information is generated. Also, in step S5, a function symbol representing the toymodel_exec function identified by the called function ID included in the diagram information (hereinafter referred to as toymodel exec function symbol) is generated. Since each function symbol is as described above, detailed description thereof is omitted here.

Furthermore, in step S5, a target diagram is generated that represents the calling relationship between the main function (caller function) and the toymodel_exec function (callee function).

As a result, a target diagram is generated that includes the main function symbol and the toymodel_exec function symbol and expresses the calling relationship between the main function and the toymodel_exec function.

The target diagram generated in step S5 is displayed in the diagram display area 202 in step S6.

As described above, when the processes of steps S3 to S6 shown in FIG. 8 are executed, the processes of steps S7 and S8 are executed. In this case, in step S7, code additional information including a source code ID for identifying the target source code, additional content "emphasis", and position information "22 (line) to 42 (line)" is generated. Although not shown in FIG. 13, the position information "22 to 42" indicates that the definition of the toymodel_exec function is described on the 22nd to 42nd lines in the source code. Also, in step S8, the code additional information generated in step S7 is reflected in the target source code displayed at 201 in the code display area.

Here, FIG. 14 shows an example of the display screen 200 after the processing of steps S3 to S8 is executed by the user specifying the toymodel_exec function as described above.

As shown in FIG. 14, in the diagram display area 202 included in the display screen 200, a target diagram including the main function symbol 400 and the toymodel_exec function symbol 600 is displayed. The main function symbol 400 is the same function symbol as the main function symbol 400 displayed in the diagram display area 202 shown in FIG. 12 described above.

On the other hand, the toymodel_exec function symbol 600 is composed of a main symbol 600a representing the entire toymodel_exec function and sub-symbols 600b to 600f representing code blocks constituting the toymodel_exec function.

In the target diagram displayed in the diagram display area 202 shown in FIG. 14, the main function symbol 400 (main symbol 400a and sub-symbol 400b) and toymodel_exec function symbol 600 (main symbol 600a and sub-symbols 600b to 600f) are Highlighted based on diagram additional information above.

Furthermore, the target diagram displayed in the diagram display area 202 includes a call line (an arrow from the main function symbol to the toymodel_exec function) 700 connecting the main function symbol and the toymodel_exec function symbol. As a result, in the target diagram, it is possible to express a calling relationship in which the main function is the caller function and the toymodel_exec function is the callee function.

Here, in the main function displayed in the code display area 201 shown in FIGS. 10 and 12, the toymodel_exec function is included in a portion other than the code block corresponding to the if statement that constitutes the main function. . In this case, a call line 700 representing the connection relationship between the main function and the toymodel_exec function is connected to the main symbol 400a (below the sub-symbol 400b) of the main function symbol 400 as shown in FIG.

That is, in this embodiment, the calling line (arrow) representing the calling relationship between the calling function and the called function is the position (main symbol or sub-symbol). For example, if the callee function is described in a code block that constitutes the caller function, the call line representing the calling relationship between the caller function and the callee function is connected to the sub symbol representing the code block. be done.

Here, the connection of the calling line on the side of the calling function has been described, but on the side of the called function, the calling line may be connected to the name of the called function, etc., as shown in FIG. 14, for example.

Also, the target diagram displayed in the diagram display area 202 may further include an indicator 800 . This indicator 800 represents the portion of the subject source code displayed in the code display area 201 in the subject diagram. In other words, when a function is displayed as part of the target source code in the code display area 201, the indicator 800 points to the function symbol representing that function.

Specifically, for example, when a function symbol 600 is provided with an indicator 800 as shown in FIG. It represents that it is displayed in the area 201 .

Although FIG. 14 shows an example in which the indicator 800 is a triangular mark, the indicator 800 may have another shape. Also, the indicator 800 may be represented by graphics, symbols, characters, colors, or the like, as long as the portion of the target source code displayed in the code display area 201 can be grasped.

Also, in the code display area 201, the portion where the definition of the toymodel_exec function is described is highlighted. Specifically, for example, in the code display area 201 shown in FIG. 14, the part where the definition of the toymodel_exec function is described has a colored highlighting line 900 to indicate that it is highlighted. Granted.

Here, the case where the main function and the toymodel_exec function are specified in order (that is, the main function and the toymodel_exec function are added to the diagram) has been explained, but another function (described within the toymodel_exec function) is described after the toymodel_exec function. function) is specified, the same processing as the processing of steps S3 to S8 described above is executed. By repeating such processing, a diagram containing function symbols (main symbols and sub-symbols) representing each of a plurality of functions designated by the user and representing calling relationships between the functions is generated. It can be displayed in the display area 202 .

In the processing shown in FIG. 8, the processing of steps S3 to S8 is executed each time a function is designated, but for example, the processing of steps S3 to S8 is executed after a plurality of functions are designated. It may be configured to be It should be noted that the timing at which the processes of steps S3 to S8 are executed may be instructed by the user.

Specifically, as shown in FIG. 15, after the diagram to which the main function is added is displayed in the diagram display area 202, the toymodel_exec function and the toymodel_exec function described in the main function are displayed in the code display area 201. It is assumed that the toy_call function described in the above and the get_flag function described in the toy_call function are sequentially specified. Note that each of the functions specified by the user and the order in which each of the functions was specified (that is, the functions of the intermediate path) are held (stored) in the code reading support device 10 . After specifying the get_flag function, for example, when the user instructs to display (generate) a diagram, the processing of steps S3 to S8 shown in FIG. 8 is executed. In this case, the diagram display area 202 displays a diagram including function symbols (toymodel_exec function symbol, toy_call function symbol, and get_flag function symbol) representing each of the toymodel_exec function, toy_call function, and get_flag function. Also, in this diagram, call lines (arrows) are displayed to represent the calling relationship with the toymodel_exec function as the caller function and the toy_call function as the callee function. Similarly, in this diagram, call lines (arrows) are displayed to represent the calling relationship with the toy_call function as the caller function and the get_flag function as the callee function.

In this embodiment, the user refers to the diagram displayed in the diagram display area 202 by designating the functions sequentially designated by the user, for example, a specific operation of the computer based on the target source code (program) ( behavior) can be read.

Although the diagram is displayed in the diagram display area 202 in this embodiment, the display screen 200 may have another area for displaying the diagram. Specifically, for example, as shown in FIG. 16, an area (third display area) 204 for displaying the diagram as a whole may be further arranged on the display screen 200 . In this case, in the diagram display area 202, a portion of the diagram specified in the area 204 for displaying the entire diagram may be enlarged and displayed. Note that the diagram display area 202 may display the entire diagram and the area 204 may display a portion of the diagram. Furthermore, the display or non-display of the area 204 may be configured to be selectable by the user.

Also, the diagram information and diagram additional information generated in the above diagram display process are stored in the diagram storage unit 12 . Therefore, by designating the diagram information and diagram additional information stored in the diagram storage unit 12 in the file selection area 203, the diagram created (displayed) by the user using the code reading device 10 can be shared with other users. It is also possible for the user to refer (browse) the

Furthermore, in the present embodiment, the function specified by the user is added to the diagram, but if the main function is specified by the user as shown in FIG. The toymodel_exec function, the toy_call function described in the toymodel_exec function, and the get_flag function described in the toy_call function are automatically added to the diagram. In such a configuration, the user may select a function to be approved for addition to the diagram from among the functions (that is, candidates) automatically added to the diagram.

Also, when a plurality of functions are described in one function, the one function (caller function) may be connected to a plurality of callee functions via a plurality of call lines.

In addition, in the diagram display process described above, each time a function specification operation is performed, a function symbol representing the function specified in the function specification operation is generated. Function symbols may be generated in advance and managed within the code reading support device 10 .

Next, an example of the processing procedure of comment addition processing will be described with reference to the flowchart of FIG. 17 . Note that the comment addition processing in the present embodiment refers to processing for editing (creating, deleting, etc.) additional information (code additional information and diagram additional information) including comments as additional content.

Here, by executing the diagram display process described above, the target source code is displayed in the code display area 201, and the target diagram to which the function (function symbol) specified by the user is added in the diagram display area 202. shall be displayed.

Here, in this embodiment, the user can add a comment to the target source code displayed in the code display area 201, for example. A comment for the target source code can be added for each line in which the code is written.

When adding a comment to the target source code as described above, the user displays the portion of the target source code to which the comment should be added in the code display area 201, and performs an operation to add the comment (hereinafter referred to as a comment addition operation). notation). By performing this comment adding operation, the user can add (add) a comment to the target source code. Note that the comment addition operation includes an operation of designating a line number to which a comment should be added, an operation of creating the comment, and the like.

The operation reception unit 15 determines whether or not the comment addition operation described above has been received (performed by the user) (step S11).

If it is determined that the comment addition operation has been accepted (YES in step S11), the edit processing unit 16 generates code addition information to be added to the target source code (step S12). In this case, the edit processing unit 16 uses the source code ID for identifying the target source code, the comment (additional content) created by the user in the above-described comment addition operation, and the line number specified by the user in the comment addition operation. Generate code additional information including (location information). The code additional information generated in step S<b>12 is stored in the code storage section 11 .

When the process of step S12 is executed, the code display processing unit 13 reflects the code additional information stored in the code storage unit 11 on the target source code displayed in the code display area 201 (step S13). According to the code addition information described above, a comment is displayed (added) to the portion (line) specified by the user of the target source code displayed in the code display area 201 by executing the process of step S13. be.

Also, the edit processing unit 16 generates diagram additional information to be added to the target diagram displayed in the diagram display area 202 (step S14). In this case, the edit processing unit 16 uses the diagram ID for identifying the target diagram, the comment (additional content) created by the user in the comment addition operation, and the code corresponding to the line number specified by the user in the comment addition operation. Diagram additional information including a code block ID (positional information) for identifying a block (a code block containing the code written at the line number) is generated. If there is no code block corresponding to the line number specified by the user, the diagram additional information may include a function ID for identifying the function corresponding to the line number. The diagram additional information generated in step S14 is stored in the diagram storage unit 12. FIG.

When the process of step S14 is executed, the diagram display processing unit 14 reflects the diagram additional information stored in the diagram storage unit 12 on the target diagram displayed in the diagram display area 202 (step S15). According to the diagram additional information described above, a comment is displayed (added) to the sub-symbol corresponding to the line number specified by the user by executing the process of step S15. As described above, when a function ID is included in the diagram additional information as position information, even if a comment is added to the function symbol (the main symbol that constitutes it) representing the function identified by the function ID, good.

According to the above-described comment adding process, for example, when a comment is added (added) to the target source code, the same comment can be displayed at the corresponding portion of the target diagram.

Note that if it is determined in step S11 that the comment addition operation has not been accepted (NO in step S11), the comment addition process ends.

The comment adding process described above will be specifically described below. Here, as shown in FIG. 12, the target source code (the part where the main function is described) is displayed in the code display area 201, and the target diagram (the function symbol 400 representing the main function) is displayed in the diagram display area 202. shall be displayed.

In this case, it is assumed that a comment is added to line 8 of the target source code, for example. In this case, the user uses the input device 106 (eg, mouse or keyboard) to place the cursor on line 8 of the target source code, for example, and right-click. Note that this operation corresponds to the operation of specifying the line number to which the comment should be added.

Here, as described above, when the cursor is placed on the eighth line of the target source code and a right-click operation is performed, the screen shown in FIG. Is displayed.

As shown in FIG. 18, the comment creating screen 1000 is provided with a comment creating area 1000a. A user can use the input device 106 to create a comment in the comment creation area 1000a.

The comment creation screen 1000 is further provided with an "OK" button 1000b and a "Cancel" button 1000c.

When a comment is created in the comment creation area 1000a and the user presses the "OK" button 1000b, the creation of the comment is completed.

On the other hand, when the user presses the "cancel" button 1000c, the creation of the comment is cancelled.

When comment creation on the comment creation screen 1000 is completed as described above, the processes of steps S12 to S15 shown in FIG. 17 are executed. In step S12 in this case, the source code ID for identifying the target source code, the comment (additional content) created by the user on the comment creating screen 1000, and the "8 Code additional information including "(row)" (position information) is generated.

In step S<b>13 , the comment additional information generated in step S<b>12 is reflected in the target source code displayed in the code display area 201 .

On the other hand, in step S14, the diagram ID for identifying the target diagram, the comment (additional content) created by the user on the comment creation screen 1000, and the code block corresponding to the line number specified by the user in the code display area 201 Diagram information including a code block ID (positional information) for identifying is generated.

In step S15, the diagram information generated in step S14 is reflected in the target diagram displayed in the diagram display area 202. FIG.

Here, FIG. 19 shows an example of the display screen 200 after the processes of steps S12 to S15 described above are executed.

As shown in FIG. 19, a comment created by the user is added to the fifth line of the target source code displayed in the code display area 201 .

A comment created by the user is added to the sub-symbol 400b included in the main function symbol 400 included in the target diagram displayed in the diagram display area 202. FIG.

When a comment is added to the position (line) specified by the user in the target source code in the code display area 201 in this way, the same comment is added to the corresponding part of the target diagram.

In the present embodiment, when a comment is added to the target source code, the comment is reflected in the target diagram. However, for example, the user can add a comment to the target diagram. be. In this case, comments added to the target diagram are reflected in the target source code.

A comment for a target diagram can be added to, for example, a main symbol or a sub-symbol that constitutes the target diagram. According to this, for example, when a comment is added to the main symbol that constitutes the target diagram, any line in which the function represented by the main symbol (function symbol) in the target source code is described It is sufficient if the comment is displayed (added) to, for example. On the other hand, for example, when a comment is added to a sub-symbol that constitutes the target diagram, the comment is displayed in any line where the code block represented by the sub-symbol in the target source code is described. (addition) is sufficient.

Moreover, although the case where a comment is added has been described in the present embodiment, it is also possible to delete the comment. When a comment is deleted, the additional information (code additional information and diagram additional information) including the comment as additional content is deleted, and the deletion of the additional information is reflected in the target source code and target diagram.

Next, an example of the processing procedure of the highlighting change processing will be described with reference to the flowchart of FIG. 20 . Note that the highlighting change process in this embodiment is a process of editing (creating, deleting, etc.) additional information (code additional information and diagram additional information) including emphasis as additional content.

Here, by executing the diagram display process described above, the target source code is displayed in the code display area 201, and the target diagram to which the function (function symbol) specified by the user is added in the diagram display area 202. shall be displayed.

Here, the user can change whether or not to highlight the target source code displayed in the code display area 201, for example. The presence or absence of highlighting can be changed for each code block constituting a function, for example.

As described in the diagram display processing and the like shown in FIG. Each function symbol representing that function is highlighted. Therefore, the case of canceling the highlighting of (the highlighted portion of) the target source code will be mainly described here.

When canceling the highlighting of the target source code as described above, the user displays the highlighted portion of the target source code in the code display area 201, and performs an operation to cancel the highlighting (hereinafter referred to as the canceling operation). notation). The user can cancel the highlighting of the target source code by performing this highlighting cancellation operation. Note that the operation for canceling highlighting includes an operation for designating (the line number in which is described) the code block whose highlighting is to be canceled.

The operation receiving unit 15 determines whether or not the above-described de-emphasizing operation has been received (ie, performed by the user) (step S21).

When it is determined that the emphasis canceling operation has been accepted (YES in step S21), the editing processing unit 16 deletes the code addition information added to the target source code (step S22). In this case, the edit processing unit 16 stores the source code ID for identifying the target source code, the additional content "emphasis", and the line number (position information) where the code block specified by the user in the deemphasis operation is described. The included code additional information is deleted from the code storage unit 11 .

When the process of step S22 is executed, the code display processing unit 13 reflects the deletion of the code additional information in step S22 on the target source code displayed in the code display area 201 (step S23). According to the deletion of the code additional information described above, by executing the process of step S23, the highlighted display of the portion of the code block specified by the user in the target source code displayed in the code display area 201 is canceled. be.

Also, the edit processing unit 16 deletes the diagram additional information added to the target diagram displayed in the diagram display area 202 (step S24). In this case, the edit processing unit 16 includes a diagram ID for identifying the target diagram, a code block ID (position information) for identifying the code block specified by the user in the additional content "emphasis" and the deemphasis operation. The diagram additional information is deleted from the diagram storage unit 12. The code block ID for identifying the code block specified by the user includes the line number where the code block specified by the user is described and the code analysis information ( code block information).

When the process of step S24 is executed, the diagram display processing unit 14 reflects the deletion of the diagram additional information in step S24 on the target diagram displayed in the diagram display area 202 (step S25). According to the above-described deletion of additional diagram information, the highlighting of the sub-symbol representing the code block specified by the user of the target diagram displayed in the diagram display area 202 is canceled by executing the process of step S25. be done.

According to the above-described highlighting change processing, for example, when the highlighting of the target source code (code block) is canceled (whether or not highlighting is changed), the corresponding portion of the target diagram (the sub-symbol representing the code block) Similarly, the highlighting of can be canceled (whether or not highlighting can be changed).

Note that if it is determined in step S21 that the highlighting cancellation operation has not been accepted (NO in step S21), the highlighting change process is terminated.

The highlighting change processing described above will be specifically described below. Here, as shown in FIG. 12, the target source code (the part where the main function is described) is displayed in the code display area 201, and the target diagram (the function symbol 400 representing the main function) is displayed in the diagram display area 202. shall be displayed.

In this case, it is assumed that the highlighting of the code block described in the 8th to 10th lines of the target source code is canceled. In this case, the user uses the input device 106 (eg, mouse or keyboard) to perform an operation to specify the eighth to tenth lines of the target source code.

In this case, the processes of steps S22 and S23 shown in FIG. 20 are executed. In step S22 in this case, the source code ID for identifying the target source code, the additional content "emphasis", and "8 (line) to 10 (line)" selected (designated) by the user (position information ) is deleted from the code storage unit 11 .

Specifically, before the process of step S22 is executed, the source code ID for identifying the target source code, the additional content "emphasis", and the position information "5 (line) to 13 (line)" is stored in the code storage unit 11. Therefore, when the code additional information described above is deleted from the code storage unit 11, the code storage unit 11 stores the source code ID for identifying the target source code, the additional content "emphasis", and the position information "5". Code additional information including (line) to 7 (line)", source code ID for identifying the target source code, additional content "emphasis" and position information "11 (line) to 13 (line) ” is stored.

In step S23, the deletion of the comment additional information in step S22 is reflected in the target source code displayed in the code display area 201. FIG.

On the other hand, in step S24, the diagram ID for identifying the target diagram, the additional content "emphasis", and the code block ID for identifying the code block described on the 8th to 10th lines selected by the user. The diagram information including (position information) is deleted from the diagram storage unit 12 .

In step S25, the deletion of the diagram additional information in step S24 is reflected in the target diagram displayed in the diagram display area 202. FIG.

Here, FIG. 21 shows an example of the display screen 200 after the processes of steps S22 to S25 described above are executed.

As shown in FIG. 21, in the 8th to 10th lines of the target source code displayed in the code display area 201, the highlighting line 500 indicating that it is highlighted is deleted (that is, unhighlighted).

Also, the sub-symbol 400b included in the main function symbol 400 included in the target diagram displayed in the diagram display area 202 is not colored to indicate that it is highlighted (that is, the highlighting is canceled). is being used).

As described above, in this embodiment, when the highlighting of the position specified (selected) by the user in the target source code is released, the highlighting of the corresponding portion of the target diagram is also released.

Here, for the sake of convenience, the case where the highlighting of the 8th to 10th lines of the target source code is canceled has been described, but in general, the highlighting of the part that does not work in the predetermined behavior is not performed by the user's operation. be released accordingly.

In the present embodiment, the case where the highlighting is canceled has been mainly described. may In this case, additional information (code additional information and diagram additional information) including highlighting as additional content may be generated, and the additional information should be reflected in the target source code and target diagram.

Further, in the present embodiment, when the presence/absence of highlighting for the target source code is changed, the change in the presence/absence of highlighting is reflected in the target diagram. A configuration may be adopted in which, when a change is made, the change in the presence or absence of the highlighting is reflected in the target source code.

As described above, in this embodiment, a code display area 201 (first display area) for displaying source code and a diagram display area 202 (second display area) for displaying a diagram representing at least part of the source code are arranged. The displayed screen is displayed, and the diagram displayed in the diagram display area 202 is edited (created). Note that, in the present embodiment, a function (a function symbol representing it) designated by the user among a plurality of functions included in the source code displayed in the code display area 201 can be added to the diagram.

In general tools for supporting code reading, it is difficult to reflect the user's intentions, for example, elements that the user (developer) does not want to be shown are displayed. With the configuration described above, it is possible to create and display a diagram intended by the user, so that it is possible to appropriately assist code reading.

In addition, in the present embodiment, the portion of the source code displayed in the code display area 201 where the function specified by the user is described is highlighted. According to such a configuration, the user can easily identify the function added to the diagram among the multiple functions included in the source code.

Further, in this embodiment, the function symbols described above include sub-symbols representing code blocks that make up the function specified by the user. Also, the position of a sub-symbol included in a function symbol is based on the position of the code block represented by the sub-symbol described within the function represented by the function symbol. According to such a configuration, the user can easily grasp the positional relationship and the like of the code blocks forming the function specified by the user in the diagram.

Furthermore, in this embodiment, for example, when a first function is specified, a first function symbol representing the first function is added to the diagram, and when a second function included in the first function is specified, A second function symbol representing the second function is added to the diagram. Also, when the second function is specified, the portion of the source code where the second function is described is displayed in the code display area 201 . In this embodiment, with such a configuration, functions described in each function (that is, callee functions) can be sequentially specified in the code display area 201 .

Also, in this embodiment, the diagram represents the calling relationship between the first function and the second function described above. Specifically, the calling relationship between the first function and the second function can be represented by a call line (arrow) connecting the first function symbol and the second function symbol. In this embodiment, such a configuration allows the user to easily grasp the calling relationship between a plurality of functions in the diagram.

Furthermore, in the present embodiment, the calling line representing the calling relationship between the first function and the second function is a sub-symbol representing the code block in which the second function is described among the code blocks constituting the first function. and the second function symbol. With such a configuration, it is possible to easily grasp the position (code block) where the second function is described in the first function in the diagram.

In this embodiment, only part of the source code is displayed in the code display area 201, but a diagram is added to the diagram when functions included in the source code are displayed in the code display area 201. contains an indicator pointing to the function symbol representing the function in question. With such an indicator, it is possible to easily grasp the relevant portion (function symbol, etc.) of the diagram corresponding to the content displayed in the code display area 201 .

Further, in this embodiment, the display screen 200 may further include an area 204 for displaying the diagram as a whole. In this case, the diagram display area 202 displays, for example, an enlarged portion of the diagram specified by the user. With such a configuration, it is possible to easily confirm the details of the diagram.

Furthermore, in this embodiment, when a comment is created for the source code displayed in the code display area 201 , the comment is also reflected in the diagram displayed in the diagram display area 202 . Similarly, when a comment is created for the diagram displayed in the diagram display area 202 , the comment is also reflected in the source code displayed in the code display area 201 . In this embodiment, with such a configuration, for example, even if a comment is added to either the source code or the diagram, it is possible to check the comment in both the source code and the diagram.

In addition, in this embodiment, when the presence or absence of highlighting for the source code displayed in the code display area 201 is changed, the change in the presence or absence of highlighting is also applied to the diagram displayed in the diagram display area 202. reflect. Similarly, when the presence/absence of highlighting for the diagram displayed in the diagram display area 202 is changed, the change in the presence/absence of highlighting is also reflected in the source code displayed in the code display area 201.例文帳に追加In this embodiment, with such a configuration, for example, even if the presence or absence of highlighting is changed in either the source code or the diagram, it is possible to confirm the change in both the source code and the diagram. becomes.

That is, in the present embodiment, the function as a source code viewer (editor) and the function as a diagram editor operate in cooperation with each other, thereby improving convenience for the user.

Note that the code reading device 10 according to the present embodiment described above can be used, for example, when operating and maintaining software whose specifications are unknown, which is called legacy code. Specifically, it is often difficult to understand (code reading) the contents of such software (source code), but the code reading device 10 according to the present embodiment can be used to reflect the user's intentions. By checking the specific operation (behavior) with reference to the diagram, it is possible to ease the difficulty of reading the code.

In the present embodiment, the chord reading support device 10 has been described as including the chord storage unit 11 and the diagram storage unit 12, but the code storage unit 11 (the chord analysis information and the chord additional information stored therein) And at least a part of (the diagram information and diagram additional information stored in) the diagram storage unit 12 may be managed by an external device different from the chord reading support device 10 . In such a configuration, the information stored in the code storage section 11 or the diagram storage section 12 may be received from an external device as needed.

While several embodiments of the invention have been described, these embodiments have been presented by way of example 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 modifications can be made without departing from the scope of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, as well as the scope of the invention described in the claims and equivalents thereof.

DESCRIPTION OF SYMBOLS 10... Chord reading assistance apparatus (electronic computer), 11... Code storage part, 12... Diagram storage part, 13... Chord display processing part, 14... Diagram display processing part, 15... Operation reception part, 16... Editing process part, 101 CPU 102 Non-volatile memory 103 Main memory 104 BIOS-ROM 105 System controller 106 Input device 107 Display device 108 EC.

Claims (10)

display processing means for displaying a screen on which a first area displaying a source code and a second area displaying a diagram representing at least part of the source code are arranged;
and editing processing means for editing the diagram displayed in the second area,
A plurality of functions are described in the source code,
When at least one function described in the source code displayed in the first area is designated by a user using a computer, the editing processing means converts the function symbol representing the function into the second area. Add to the diagram displayed in the area,
The display processing means is
When the first comment is created at the position specified by the user in the source code displayed in the first area, the corresponding function symbol in the source code displayed in the second area. adding and displaying the first comment to a function symbol representing a function written at a position specified by a user;
When a second comment is created for a function symbol specified by the user among the function symbols displayed in the second area, the function symbol in the source code displayed in the first area indicates the second comment. A computer that adds and displays the second comment at the position where the function is described. 2. The computer according to claim 1, wherein a portion of the source code displayed in the first area where the function specified by the user is described is highlighted. each of the plurality of functions is composed of at least one code block;
2. The electronic computer according to claim 1, wherein said function symbols include sub-symbols representing code blocks forming a function specified by said user. 4. The computer according to claim 3, wherein the position of a sub-symbol included in said function symbol is based on the position of a code block represented by said sub-symbol described in the function represented by said function symbol. a portion of the source code is displayed in the first area;
2. The computer according to claim 1, wherein said diagram includes an indicator pointing to a function symbol representing a function added to said diagram when said function described in said source code is displayed in said first area. . The screen further includes a third area for displaying the diagram as a whole,
2. The computer according to claim 1, wherein a part of said diagram is enlarged and displayed in said second area. wherein, when the presence/absence of highlighting for the source code displayed in the first area is changed, the editing processing means reflects the change in the presence/absence of highlighting in the diagram displayed in the second area. Item 1. The electronic computer according to item 1. wherein, when the presence or absence of highlighting for the diagram displayed in the second area is changed, the editing processing means reflects the change in the presence or absence of highlighting in the source code displayed in the first area. Item 1. The electronic computer according to item 1. A computer-implemented method comprising:
displaying a screen on which a first area displaying source code and a second area displaying a diagram representing at least part of the source code are arranged;
and editing the diagram displayed in the second area;
A plurality of functions are described in the source code,
In the editing step, when at least one function described in the source code displayed in the first area is designated by a user using a computer, the function symbol representing the function is changed to the second function. including steps to add to the diagram displayed in the area,
The displaying step includes:
When the first comment is created at the position specified by the user in the source code displayed in the first area, the corresponding function symbol in the source code displayed in the second area. adding and displaying the first comment to a function symbol representing a function written at a position specified by a user;
When a second comment is created for a function symbol specified by the user among the function symbols displayed in the second area, the function symbol in the source code displayed in the first area indicates the second comment. a step of adding and displaying the second comment at a position where the function is described. A program executed by a computer of an electronic calculator,
to the computer;
displaying a screen on which a first area displaying source code and a second area displaying a diagram representing at least part of the source code are arranged;
performing a step of editing the diagram displayed in the second area;
A plurality of functions are described in the source code,
In the editing step, when at least one function described in the source code displayed in the first area is designated by a user using a computer, the function symbol representing the function is changed to the second function. including steps to add to the diagram displayed in the area,
The displaying step includes:
When the first comment is created at the position specified by the user in the source code displayed in the first area, the corresponding function symbol in the source code displayed in the second area. adding and displaying the first comment to a function symbol representing a function written at a position specified by a user;
When a second comment is created for a function symbol specified by the user among the function symbols displayed in the second area, the function symbol in the source code displayed in the first area indicates the second comment. a step of adding the second comment to the position where the function is described and displaying it.

Images