JP2007115155A - Program structure management device and program structure management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program structure management device for facilitating the generation of program structural drawing clarifying common parts and the reusing of the common parts in a program structure by analyzing a common structure in a program. <P>SOLUTION: The program structure management device 100 is provided with a program structure analyzing means 101, a program structural drawing generating means 102, a template file list generating means 103 and a template program generating means 104. The program structure analyzing means 101 analyzes a program file, extracts information about a processing sequence and stores the information. The program structural drawing generating means 102, the template file lit generating means 103 and the template program generating means 104 extract common parts of the processing sequence about a plurality of programs on the basis of program structure information and generate a program structural drawing, a template file list and a template program, respectively. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention, during program development, analyzes the structure of an installed program, visualizes the structure of the program, and shows a common part that can be reused, thereby supporting program quality assurance and program structure reuse. Concerning the configuration to do.

In recent system development, the development cycle is becoming shorter and shorter. In particular, when a business system or business service system is disclosed, it is a strong requirement as a customer need to shorten the development cycle and shorten the time required for development and maintenance so that it can be used. In addition, shortening the period required for maintenance and function change for once-developed and completed business systems and business service systems is also becoming necessary in B2C systems and the like in which the fashion changes rapidly.
It is said that programs must be shared and reused in order to shorten the development period and maintenance / function change period. In recent years, “Java” (“Java” is a registered trademark of Sun Microsystems, Inc.), “Visual C #”, “.NET Visual Basic” as a programming language that enables commonization and reuse of programs. Object-oriented languages such as “.NET” such as “.NET” have been frequently used in development.
However, since there are few developers who understand these object orientations at present, there are still many projects and developers who develop using a procedural method using an object oriented language. In other words, the current situation is that the project cannot be shared and reused, and the development period and maintenance / function change period cannot be shortened.
Moreover, it is important to shorten the program function change period while shortening the function change period. However, unless the program developer understands the program structure and sufficiently understands the program function, the program function change period cannot be shortened.
Also, in current software development, program developers often create programs with their own experience and intuition, and in a project consisting of multiple program developers, the software structure of even one application has become different. It often happens. It is not easy for the person who developed the program in the initial development to change the function of such an application. Other program developers who did not participate in the program development in the initial initial development should change the program function. It's not easy, and I can't expect a shorter period.
On the contrary, the program function change period becomes long, and problems that are not in time for the development delivery date arise.
The problem that can occur here is that the period required for development is given only for a short period, and as a result, there is no time for determining the program structure.
However, if the program is developed without determining the program structure, the number of defective programs increases, which may cause quality deterioration.

In order to solve these problems, it is necessary to increase the number of portions where the program structure is shared by one program as much as possible, and to create a program having the same function in a plurality of portions.
Therefore, application frameworks have recently attracted attention, but it takes time and man-hours to understand application frameworks.
By reusing the program structure once experienced by the developing program developer, the man-hours understood by the application framework can be reduced.
These application frameworks must also be customizable for individual development. In other words, if there are 100 developments, there should be 100 different application frameworks.

As a development support device that makes it easy to understand the structure of the developed program with regard to the problems described above, a program developed in an object-oriented language is analyzed, and the class diagram is based on the analysis result. The structure provided with the means to generate | occur | produce design documents, such as these is well-known (for example, refer patent document 1).
JP 2000-112742 A

  However, since the configuration described in Patent Document 1 creates a design document for the purpose of understanding the program structure itself, it is not suitable for sharing the program structure or reusing the common part. It was.

  The present invention is for solving the above-mentioned problems, and by analyzing the common structure in the program, it is easy to generate a program structure diagram clearly showing the common part and to reuse the common part in the program structure. An object of the present invention is to provide a program structure management apparatus.

In order to solve the above-mentioned problem, the present invention is a program structure management device for analyzing and managing the program structure of a plurality of program files constituting software, the program structure in each program file being analyzed, Means for extracting information on the order of each process included in the program and storing it in the program structure information in the software.
In addition, a program structure diagram that acquires the program structure information, extracts a common part of the processing order included in the program structure information for a plurality of program files constituting the software, and shows the common part as a common structure. It further has a means for generating.
Further, the program structure information is acquired, a common part of the processing order included in the program structure information is extracted for a plurality of program files constituting the software, and a plurality of program files having the common part are to be templated A means for displaying as a file is provided.
Further, according to an arbitrary selection of the program file displayed as the template file among the plurality of program files constituting the software, the selected program file and program structure information corresponding to the program file And a means for generating a template file composed of the common portions in the program file and generating a template program by combining the generated template files.
The program structure management program of the present invention is a program structure management program for causing a computer to execute processing for analyzing and managing the program structure of a plurality of program files constituting software, wherein the program structure in each program file is And a process for extracting information relating to the order of each process included in the program file and storing it in the program structure information in the software.
In addition, a program structure diagram that acquires the program structure information, extracts a common part of the processing order included in the program structure information for a plurality of program files constituting the software, and shows the common part as a common structure. It is characterized by further causing a computer to execute a process to be generated.
Further, the program structure information is acquired, a common part of the processing order included in the program structure information is extracted for a plurality of program files constituting the software, and a plurality of program files having the common part are to be templated The computer is further caused to execute processing for displaying as a file.
Further, according to an arbitrary selection of the program file displayed as the template file among the plurality of program files constituting the software, the selected program file and program structure information corresponding to the program file Based on the above, a template file composed of the common parts in the program file is generated, and the computer is further caused to generate a template program by combining the generated template files.

With the above configuration, in the present invention, the program structure is analyzed, and information related to the order of processing in each program file is included in the program structure information, so that a plurality of programs can be obtained by referring to the program structure information. The common part in the file can be easily confirmed.
In addition, based on the program structure information, a program structure diagram showing the common parts of the processing order is generated and displayed so that software managers and developers can easily understand the common parts of the program structure. It becomes possible to make it. Therefore, it is possible to select an optimal program structure in software.
Further, by displaying a program file having a part in common processing order as a template file based on the program structure information, it is possible to easily select a program file to be reused.
Further, by generating a template file based on the program structure information corresponding to the selected template file, it is possible to easily reuse a program file having a common part.

Hereinafter, a program structure management apparatus according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a schematic configuration of a program structure management apparatus according to an embodiment of the present invention.
The program structure management apparatus 100 according to the present embodiment includes a program structure analysis unit 101, a program structure diagram generation unit 102, a templated file list generation unit 103, a template program generation unit 104, a file repository 105, and a program Each information storage means of the structure information storage unit 106 is provided.
The configuration of each processing unit and the processing performed by each processing unit will be described below.

First, the configuration and processing of the program structure analysis unit 101 and the program structure diagram generation unit 102 will be described in relation to the program structure analysis and the program structure diagram generation and display processing.
FIG. 2 is a block diagram showing a schematic configuration of the program structure analyzing means 101.
The program structure analysis unit 101 includes a file type determination processing unit 201 and a program structure analysis unit 202. The file type determination processing unit 201 performs determination processing of the processing target file 200 and storage processing in the file repository 105. The program structure analysis unit 202 performs a program structure analysis process for the program file and a storage process in the program structure information storage unit 106.

FIG. 3 is a flowchart showing processing performed by the program structure analysis unit 101.
When the program developer or project manager accepts input of a program file that has been completed or is being developed, or a document file such as a design document (step 301), the program structure analysis unit 101 inputs the file type determination processing unit 201. The file type is determined for the file (step 302), and the input file is stored in the file repository 105 (step 303). The file type determination process in this case is performed by determining the extension of the program file. Alternatively, the program file may be compiled and the determination may be made based on whether the compilation passes. In the file repository 105, all input files are allocated and stored for each project and each application.
In step 303, when the file type is a program file, the program structure analysis unit 202 analyzes the program structure and stores the analysis result in the program structure information storage unit 106. In the present embodiment, processing relating to the order of each process included in a plurality of program files (method call for one event transaction and repetition for each line of the program) is extracted and stored in the program structure information.

FIG. 4 is a block diagram showing a schematic configuration of the program structure diagram generation means 102.
The program structure diagram generation unit 102 includes a program detail display unit 401, a program structure diagram generation unit 402, and a program structure diagram display unit 403.
The program information display unit 401 acquires the program structure information stored in the program structure information storage unit 106 and displays the list.
The program structure diagram generation unit 402 generates a program structure diagram based on the program structure information stored in the program structure information storage unit 106.
The program structure diagram display unit 403 is generated by the program structure diagram generation unit 402 and displays the program structure diagram.

FIG. 5 is a flowchart showing processing performed by the program structure diagram generation unit 102.
When the program structure diagram generation unit 102 receives a program structure diagram display request from a project manager or the like (step 501), the program information display unit 401 creates a project (software) whose structure information is stored in the program structure information storage unit 106. ) (Step 502), and based on the acquired identification information, a list of projects is displayed on an operation terminal such as a project manager (step 503).
When an arbitrary selection is accepted from the listed projects (step 504), the program structure diagram generation unit 402 acquires program structure information corresponding to the selected project from the program structure information storage unit 106 (step 504). 505), a program structure diagram is generated (step 506) and transferred to the program structure diagram display unit 403. In the generation of the program structure diagram, the program structure information is referred to, a common part of a processing order common to a plurality of program files is extracted, and a program structure diagram showing the common part as a common structure is generated.
The program structure diagram display unit 403 displays the acquired program structure diagram on an operation terminal such as a project manager (step 507).
By the above processing, for example, a project manager who is developing a program can refer to the structure of a program implemented by a large number of program developers participating in the project at once in the program structure diagram. Therefore, it becomes easy to detect a structural difference and issue a correction instruction, which ultimately leads to reduction in man-hours and improvement in program quality. In addition, when reusing a program or reusing a structure, it is possible to easily select a program structure suitable for customization, such as referring to the program structure in advance and minimizing modifications. become.

Next, processing performed by the templated file list generation unit 103 and the template program generation unit 104 will be described in relation to the reuse of the program structure.
First, a templated file list generation process performed by the templated file list generating unit 103 will be described as a premise for generating a template program.
FIG. 6 is a block diagram showing a schematic configuration of the templated file list generation unit 103.
The templated file list generation unit 103 includes a templated file determination unit 601 and a templated file list output unit 602.
The templated file determination unit 601 determines whether the file is a templated target file based on the program structure information stored in the program structure information storage unit 106. Here, the template target file refers to a program file having a common part of processing order common to a plurality of program files based on the program structure information.
The templated file list output unit 602 generates a templated file list according to the determination result of the templated file determination unit 601 and displays the list.

FIG. 7 is a flowchart showing processing performed by the templated file list generation unit 103.
When the program structure diagram generation unit 102 receives a program structure diagram display request from a project manager or the like (step 701), the program information display unit 401 creates a project (software) whose structure information is stored in the program structure information storage unit 106. ) (Step 702), and based on the acquired identification information, a list of projects is displayed on an operation terminal such as a project manager (step 703).
When an arbitrary selection is accepted from the displayed projects and a request to output a templated file list is received (step 704), the templated file determination unit 601 stores program structure information corresponding to the selected project as a program. Obtained from the structure information storage unit 106 (step 705), the program structure information of the selected project is referred to, and a template file to be determined is determined (step 706). Here, the template file is a file in which a plurality of program files include a common part (common structure) in the processing order.
The templated file list output unit 602 displays a list of templates to be templated on an operation terminal such as a project manager based on the determination result of the templated file determination unit 601 (step 707).

Next, the processing performed by the template program generation unit 104 for the templated files displayed as a list will be described.
FIG. 8 is a block diagram showing a schematic configuration of the template program generating means 104.
The template program generation unit 104 includes a template program name input unit 801, a template program generation unit 802, and a template program output unit 803.
The template program name input unit 801 accepts designation of files constituting a template program and input of file names among the files to be templated displayed in a list. The template program generation unit 802 acquires information on the file structure of the designated file from the program structure information storage unit 106, and generates a templated file.
The template program output unit 803 outputs the generated templating file and a copy of the file stored in the file repository.

FIG. 9 is a flowchart showing processing performed by the template program generation unit 104.
The template program name input unit 801 of the template program generation unit 104 accepts the selection of an arbitrary file from the list-displayed files to be templated and the input of the file name (step 901), and passes them to the template program generation unit 802.
The template program generation unit 802 acquires program structure information corresponding to the selected program file from the program structure information storage unit 106 (step 902), generates a template file based on the program structure information (step 903), Passed to the template program output unit 803. Here, the template file refers to a program file composed of a common part (common structure) of processing order included in a plurality of program files.
The template program output unit 803 obtains a copy of the executable file corresponding to the template file from the file repository 105 (step 904), and displays it on the operation terminal such as a project manager together with the template file (step 904). 905). The template program is composed of a plurality of template files generated based on a plurality of arbitrarily selected templates.
With the above processing, the existing completed program structure can be easily referred to in a diagram format, and a template program can be created by reusing the program structure closest to the program to be developed or the program structure experienced in the past. It becomes possible to make it. In other words, by configuring a template program using a combination of files to be templated that make up an existing project, the program structure can be shared, improving the maintainability, expandability, and quality of the program, Man-hours can be reduced.

Each of the above processes will be described using specific examples.
FIG. 10 is a screen transition diagram of the employee information search system as a Web application to be processed by the program structure management apparatus according to the present embodiment. In this example, Microsoft ASP. 2 shows a Web application program using the NET technology.
The employee information search system as a Web application shown in this example is composed of a search input screen 1010, a search result screen 1020, and a detailed display screen 1030 in all three screens.
In the Web application program 1000, the name of the employee who wants to search is input in the text box 1011 of the search input screen 1010, and the search result screen 1020 is transitioned to when the search button 1012 is clicked. If the search button 1012 is clicked while the text box 1011 is blank, an error message is displayed.
On the search result screen 1020, when the employee name hyperlink 1021 is clicked, a transition is made to the detail display screen 1030.

FIG. 11 shows an outline of the project configuration of the employee information retrieval system shown in FIG. 10 and the files constituting the project. The project here refers to the development environment called "Visual Studio .NET" that is frequently used when developing ".NET applications". It is a management file.
As shown in FIG. 11, in this example, there is a project file 1101 called whois, a folder 1102 called Db, and five C # files 1103 for database access are included below the folder 1102. Further, in the same hierarchy, there is a folder 1104 called Scenario, and three C # files 1105 for implementing an operation scenario of each form screen are included below that.
In addition, AssemblyInfo.cs file 1106 containing meta information to be embedded in the application at compile time, Global.asax file 1107 for implementing processing to be performed at the start / end of the application and at the start / end of the session, and the configuration information of the application Web.config file 1108, search input screen Web form file Search.aspx1109, search result screen Result.aspx1110, detailed display screen 1111, compilation, which is an application framework that controls screen transitions and session control when executing applications A defined execution file 1112 and a definition file 1113 in which screen transitions and session control used by the application framework are defined.

FIG. 12 is a diagram showing a control arrangement on the search input screen 1010.
Controls arranged on the search input screen 1010 shown in this example include, for example, an employee name text box 1201 for inputting an employee name or a pseudonym of the employee name to be searched, and an essential input for the employee name text box 1201 There are an employee text box check 1202 to be checked, a search button 1203 to be clicked when performing a search, and a reset button 1204 to reset the entered employee name.

FIG. 13 is a diagram showing an example of the ASPX file constituting the search input screen 1010 shown in FIG.
In the ASPX file 1300, controls 1301 to 1304 are implemented corresponding to the controls 1201 to 1204 on the search input screen 1010.

FIG. 14 is a diagram showing a control arrangement on the search result screen 1020.
The controls arranged on the search result screen 1020 shown in this example include, for example, a search result data grid 1401 for displaying search result information, an employee name hyperlink 1402 for displaying employee detailed information, and a search There is a button 1403 to an input screen for making a transition to the search input screen for performing again.

FIG. 15 is a diagram showing an example of the ASPX file constituting the search result screen 1020 shown in FIG.
In the ASPX file 1500, controls 1501 to 1503 are mounted in correspondence with the controls 1401 to 1403 on the search result screen 1020.

FIG. 16 is a diagram showing a control arrangement on the detail display screen 1030.
The controls arranged on the detailed display screen 1030 shown in this example include, for example, an employee number label 1601, a name label 1602, a kana label 1603, a department label 1604, a department label 1605, and a section label 1606. , Label 1607, telephone number label 1608, email label 1609, and search input screen button 1610 for transitioning to the search input screen.

FIG. 17 is a diagram showing an example of the ASPX file constituting the detail display screen 1030 shown in FIG.
In the ASPX file 1700, controls 1701 to 1710 are mounted in correspondence with the controls 1601 to 1610 on the detail display screen 1030. In the ASPX file 1700 shown in FIG. 17, only the mounting parts of the controls 1701 to 1710 are shown, and the other parts are omitted.

18 to 20 are diagrams showing examples of code-behind classes for dynamically displaying character strings, images, and the like on the Web forms of the search input screen 10101, the search result screen 1020, and the detailed display screen 1030, respectively. . The code-behind class is a class file for creating a business result by calling and processing a business class, a database access class, etc., and dynamically displaying a character string, an image, etc. on a Web form.
As shown in FIG. 18, the code-behind class 1800 of the search input screen 1010 includes a component definition unit 1801 that defines component import, a namespace definition unit 1802, a Search class definition unit 1803, and a member variable definition unit 1804. , A Page_Load method definition unit 1805, an OnInit method definition unit 1806, an InitializeComponent method definition unit 1807, and event hands 1808 and 1809.
The component definition unit 1801 imports an 11-step namespace and includes components provided in the “.NET Framework” and components defined in a namespace different from code-behind in the employee information search system. It is defined to be imported and used. This file contains one code that inherits the EmployeeInfo.Framework.BasePage class that hides various processes by inheriting the standard code-behind class (System.Web.UI.Page class) provided by ".NET Framework" A behind-class is defined.
Three member variables are defined in the member variable definition unit 1804 of the Search class definition unit 1803. These three variables indicate Web server controls that are defined in the Web form that the Search class, which is a code-behind class, is responsible for displaying dynamic character strings and images. Specifically, txtSerchKey corresponds to a text box Web server control defined on Search.aspx, rdValSearchKey corresponds to a validator Web server control, and btnSearch corresponds to a button Web server control.
The Page_Load method definition unit 1805 defines a method that is processed first when a request is made on the search input screen 1010.
The OnInit method definition unit 1806 compiles a Web form with a method that is executed only once when the system is requested for the first time after the employee information retrieval system is placed on the Web server. Methods are defined that are responsible for forming server controls.
The InitializeComponent method definition unit 1807 defines a method for executing an event handler to assign a process to a certain method on the code-behind class when an event occurs in the Web server control arranged in the Web form. The
An event handler 1808 indicates assignment of processing to the btnToSearch_Click method when a click event occurs in the search button.
An event handler 1809 indicates an event handler when a search button (corresponding to a member variable btnSearch in the code behind class) arranged on the search input screen is clicked.

  Similarly, the code-behind class 1900 of the search result screen 1020 shown in FIG. 19 and the code-behind class 2000 of the detail display screen 1030 shown in FIG. , 2002, Search class definition unit 1903, 2003, member variable definition unit 1904, 2004, Page_Load method definition unit 1905, 2005, OnInit method definition unit 1906, 2006, InitializeComponent method definition unit 1907, 2007, event Hands 1908, 1909, 2008.

21 to 23 are classes (hereinafter referred to as “scenario classes”) that define the order in which business processes are called in response to events occurring on the search input screen 1010, search result screen 1020, and detail display screen 1030, respectively. .) Is a diagram illustrating an example.
As shown in FIG. 21, the scenario class 2100 of the search input screen 1010 includes a component definition unit 2101 that defines component import, a namespace definition unit 2102, a scenario class definition unit 2103, a Play method definition unit 2104, And a business process definition unit 2105.
The component definition part 2101 imports a 6-step name space, and is provided in the “.NET Framework” component or a component defined in a name space different from this scenario class in the employee information search system. Is defined to be imported and used. In this file, a scenario parent class prepared exclusively for the employee information retrieval system is prepared, and the ResultScenario class as one scenario class that inherits the EmployeeInfo.Framework.BaseScenario class that inherits it and hides various processes. Is defined.
The scenario class definition unit 2103 includes a Play method definition unit 2104 that defines a Play method having one string-type argument called EventID, and a business process definition unit 2105 that defines a business process.

  Similarly, the scenario class 2200 on the search result screen 1020 shown in FIG. 22 and the scenario class 2300 on the detail display screen 1030 shown in FIG. A scenario class definition unit 2203, 2303, a Play method definition unit 2204, 2304, and a business process definition unit 2205, 2305. The scenario classes 2200 and 2300 also have definition units 2206 and 2306 that return business process results.

The program structure management apparatus 100 according to the present embodiment stores the file structure 105 in the file repository 105 by the program structure analysis processing means 101 in response to the input of the project (program file, etc.) of the employee information search system configured as described above. A program file and a file other than the program file are stored, a copy of the program file is generated and analyzed, and the analysis result is stored in the program structure information storage unit 106. An area for each application system is prepared in the file repository 105.
FIG. 24 is a diagram illustrating an example of the relationship between the tables constituting the program structure information storage unit 106.
In the present embodiment, the program structure information storage unit 106 includes a software table 2401, a project table 2402, a reference component table 2403, a file table 2404, an import table 2405, a class table 2406, an in-class member call order table 2407, an in-class The table includes a member table 2408, an in-method call order table 2409, and a member argument table 2410. In this embodiment, information indicating the processing order included in each program file is stored in each of the in-class member call order table 2407, the in-method call order table 2409, and the member argument table 2410.
The software table 2401 is associated with the project table 2402.
The project table 2402 is associated with the reference component table 2403 and the file table 2404.
The file table 2404 is associated with the import table 2405 and the class table 2406.
The class table 2406 is associated with the in-class member call order table 2407 and the in-class member table 2408.
The in-class member table 2408 is associated with the in-method call order table 2409 and the member argument table 2410.

FIG. 25 is a diagram illustrating an example of the data structure of the software table 2401.
The software table 2401 has data items of software ID and software name, for example.
In the table shown in each figure, “PK” in the attribute indicates a primary key, and “FK” indicates a foreign key.

FIG. 26 is a diagram illustrating an example of the data structure of the project table 2402.
The project table 2402 includes, for example, data items of software ID, project ID, project name, and project type. The software table 2401 is associated with a software ID.

FIG. 27 is a diagram illustrating an example of the data structure of the reference component table 2403.
The reference component table 2403 includes, for example, data items of software ID, project ID, reference component ID, and reference component name. The project table 2402 is associated with a software ID and a project ID.

FIG. 28 is a diagram illustrating an example of the data structure of the file table 2404.
The file table 2404 has data items of software ID, file ID, file name, and library ID, for example. The project table 2402 is associated with a software ID.

FIG. 29 is a diagram illustrating an example of the data structure of the import table 2405.
The import table 2405 includes, for example, data items of software ID, file ID, import ID, import name, and reference component ID. The file table 2404 is associated with a software ID and a file ID.

FIG. 30 is a diagram illustrating an example of the data structure of the class table 2406.
The class table 2406 has data items of software ID, file ID, class ID, class name, and base class ID, for example. The base class ID is for identifying the base class for each class. The file table 2404 is associated with a software ID and a file ID.

FIG. 31 is a diagram showing an example of the data structure of the in-class member call order table 2407.
The in-class member call order table 2407 has, for example, data items of software ID, file ID, class ID, method ID, and call order. The calling order indicates the calling order (line number) of the programs in the class. The class table 2406 is associated with a software ID, a file ID, and a class ID.

FIG. 32 is a diagram showing an example of the data structure of the in-class member table 2408.
The in-class member table 2408 includes, for example, data items of software ID, file ID, class ID, class member ID, and class member type. The class table 2406 is associated with a software ID, a file ID, and a class ID.

FIG. 33 is a diagram illustrating an example of the data structure of the in-method call order table 2409.
The in-method call order table 2409 includes, for example, data items of software ID, file ID, class ID, class member ID, processing details, and member call order. Here, the processing details indicate the programs in the method, and the member calling order indicates the calling order (line number) of the programs in the method. The in-method member call processing order table 2409 is associated with the in-class member table 2408 by software ID, file ID, class ID, and class member ID.

FIG. 34 is a diagram showing an example of the data structure of the member argument table 2410. As shown in FIG.
The member argument table 2410 has, for example, data items of software ID, file ID, class ID, class member ID, argument name, argument type, and argument call order. The argument call order indicates the call order (line number) of each argument. The in-class member table 2408 is associated with the software ID, file ID, and class ID.

In accordance with the data structure of each of the above tables 2401 to 2410, the input program file is analyzed and stored in the program structure information storage unit 106, and the program arbitrarily selected by the project developer or the like is stored in each table 2401. Based on the program structure information stored in ˜2410, a program structure diagram is generated and displayed. In the generation of the program structure diagram, the processing order of the processing that occurs at each event is traced, and as a result of tracing, the name of the method to be called and the common part of the processing performed in the method are extracted. A program structure diagram generated based on the extracted common part is displayed.
35 and 36 are diagrams showing an example of the program structure diagram generated by the program structure diagram generating means. In this example, a UML class diagram is generated as a program structure diagram. In the generation of the program structure diagram in this case, the base class ID of the class table 2406 is referred to to check the parent-child relationship of each class, and then the member variable in the class is referred to by referring to the in-class member table 2408 for each class. The class diagram shown in each figure is generated by extracting the methods. Also, event handler methods are extracted from the in-class member table 2408, class steps processed from each event handler method are called line by line from the in-method call order table 2409, and common lines in the call order are extracted and shared. Part.
A program structure diagram 3500 shown in FIG. 35 shows class diagrams corresponding to the code-behind classes 1800, 1900, and 2000 shown in FIGS. 18 to 20 for the search input screen 1010, the search result screen 1020, and the detailed display screen 1030, respectively.
A program structure diagram 3600 shown in FIG. 36 shows class diagrams corresponding to the scenario classes 2100, 2200, and 2300 shown in FIGS. 21 to 23 for the search input screen 1010, the search result screen 1020, and the detailed display screen 1030, respectively. .
In each program structure diagram, the common part is highlighted by color-coded display or the like. It is also possible to generate a program structure diagram that displays only the common part.

When a project manager, a program developer, or the like referring to the above program structure diagram desires to reuse the program structure, the program structure management apparatus 100 is requested to generate a template program.
In response to the template program generation request, the program structure management apparatus 100 acquires the program structure information stored in the program structure information storage unit 106, and determines whether each file is a file to be templated (a file having a common structure). . For example, in the employee information search system, examples of the file to be templated include files such as a code-behind file and a scenario class file. On the other hand, if the C # file under the Db folder for acquiring employee information from the database does not have a common structure, it should be a file that should not be templated. After the above determination, a templated file list in which the templated file and other files are clearly displayed is displayed.
The program management apparatus 100 allows a project manager or program developer who wants to reuse the program structure to select a required file from among the files to be templated, and inputs a file name for each file. Generate a template program.

Hereinafter, an example of a template file constituting a part of a template program generated using the program structure of the employee information search system will be described with reference to FIGS.
FIG. 37 is a diagram showing an example of a project configuration output as a template for a calculation system using the program structure of the employee information search system.
This example shows a calculation system consisting of a calculation formula input screen and a calculation result output screen. The code-behind files are CalcInput.aspx and CalcOutput.aspx, and the scenario class files are CalcInputScenario.cs and CalcOutputScenario.cs. Yes. In this case, methods and variables that are not common to the part to be made into a template file are specified, and the common implementation is performed for the file in which the file name is input.
FIG. 38 is a diagram showing an example of a code-behind template file on the calculation formula input screen, and FIG. 39 is a diagram showing an example of a scenario class template file on the calculation formula input screen.
The templated file shown in each figure uses the common structure part of the code behind and scenario class files for the search input screen of the employee information search system.

  As described above, in the program structure management device according to the present embodiment, the program structure closest to the program to be developed or the program experienced in the past can be easily referred to the existing completed program structure in a diagram format. It is possible to create a template program by reusing the structure, and by making the program structure common, it becomes possible to improve the maintainability, expandability and quality of the program and reduce the man-hours.

Note that the present invention is not only applicable to object-oriented languages, but can be applied to program files in other languages as long as the common part of the processing order in each program file can be extracted by analyzing the program file. Is possible.
Further, the program structure diagram is not limited to a class diagram, and may be constituted by a flow diagram, for example. Also in this case, a flow diagram is generated by the same processing as that for generating a class diagram, and common processing is highlighted.

It is a block diagram which shows schematic structure of the program structure management apparatus which concerns on one embodiment of this invention. It is a block diagram which shows schematic structure of the program structure analysis means which comprises the program structure management apparatus which concerns on one embodiment of this invention. It is a flowchart which shows the process which a program structure analysis means performs. It is a block diagram which shows schematic structure of the program structure figure production | generation means which comprises the program structure management apparatus which concerns on one embodiment of this invention. It is a flowchart which shows the process which a program structure diagram production | generation means performs. It is a block diagram which shows schematic structure of the templated file list production | generation means which comprises the program structure management apparatus which concerns on one embodiment of this invention. It is a flowchart which shows the process which a templated file list production | generation means performs. It is a block diagram which shows schematic structure of the template program production | generation means which comprises the program structure management apparatus which concerns on one embodiment of this invention. It is a flowchart which shows the process which a template program production | generation means performs. It is a figure which shows an example of the screen which comprises the application used as the process target of this invention. It is a figure which shows the outline | summary of the project structure of the application shown in FIG. 10, and the file which comprises a project. It is a figure which shows the control arrangement | positioning on the search input screen shown in FIG. It is a figure which shows an example of the ASPX file which comprises the search input screen shown in FIG. It is a figure which shows the control arrangement | positioning on the search result screen shown in FIG. It is a figure which shows an example of the ASPX file which comprises the search result screen shown in FIG. It is a figure which shows the control arrangement | positioning on the detailed information screen shown in FIG. It is a figure which shows an example of the ASPX file which comprises the detailed information screen shown in FIG. It is a figure which shows an example of the code behind class of the search input screen shown in FIG. It is a figure which shows an example of the code behind class of the search result screen shown in FIG. It is a figure which shows an example of the code behind class of the detailed information screen shown in FIG. It is a figure which shows an example of the scenariod class of the search input screen shown in FIG. It is a figure which shows an example of the scenario class of the search result screen shown in FIG. It is a figure which shows an example of the scenario class of the detailed information screen shown in FIG. It is a figure which shows the outline | summary of the table structure of a program structure information storage part. It is a figure which shows an example of the data structure of the software table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the project table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the reference component table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the file table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the import table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the class table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the member call order table in a class which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the in-class member table which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the member call order table in a method which comprises a program structure information storage part. It is a figure which shows an example of the data structure of the member argument table which comprises a program structure information storage part. It is a figure which shows an example of the program structure figure produced | generated based on the analysis result of the code behind class shown in FIGS. It is a figure which shows an example of the program structure figure produced | generated based on the analysis result of the scenario class shown in FIGS. It is a figure which shows an example of the project structure which carried out the template output about the calculation system using the program structure of the employee information search system. It is a figure which shows an example of the code-behind template-ized file of a calculation formula input screen. It is a figure which shows an example of the template file of the scenario class of a calculation formula input screen.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 Program structure management apparatus, 101 Program structure analysis means, 102 Program structure diagram generation means, 103 Template file list generation means, 104 Template program generation means, 105 File repository, 106 Program structure information storage part, 201 File type determination processing part 202 Program structure analysis unit 401 Program detail display unit 402 Program structure diagram generation unit 403 Program structure diagram display unit 601 Templated file determination unit 602 Templated file list output unit 801 Template program name input unit 802 Template program generation unit, 803 template program output unit,

Claims (8)

A program structure management device for analyzing and managing the program structure of a plurality of program files constituting software,
A program structure comprising: means for analyzing a program structure in each program file, extracting information related to an order of each process included in the program file, and storing it in the program structure information in the software Management device.   Obtaining the program structure information, extracting a common part of the processing order included in the program structure information for a plurality of program files constituting the software, and generating a program structure diagram showing the common part as a common structure The program structure management apparatus according to claim 1, further comprising means.   The program structure information is acquired, a common part of the processing order included in the program structure information is extracted for a plurality of program files constituting the software, and a plurality of program files having the common part are used as a template target file. The program structure management apparatus according to claim 1, further comprising a display unit.   Based on the selected program file and the program structure information corresponding to the program file, according to an arbitrary selection of the program file displayed as the template file among the plurality of program files constituting the software, 4. The program management apparatus according to claim 3, further comprising means for generating a template file composed of the common part in the program file and generating a template program by a combination of the generated template files. A program structure management program for causing a computer to execute processing for analyzing and managing a program structure of a plurality of program files constituting software,
Processing for analyzing the program structure in each of the program files;
A program structure management program for causing a computer to execute processing for extracting information relating to the order of each process included in the program file and storing it in the program structure information in the software.   Obtaining the program structure information, extracting a common part of the processing order included in the program structure information for a plurality of program files constituting the software, and generating a program structure diagram showing the common part as a common structure 6. The program structure management program according to claim 5, further causing the computer to execute processing.   The program structure information is acquired, a common part of the processing order included in the program structure information is extracted for a plurality of program files constituting the software, and a plurality of program files having the common part are used as a template target file. 7. The program structure management program according to claim 5, further causing the computer to execute a display process. Based on the selected program file and the program structure information corresponding to the program file, according to an arbitrary selection of the program file displayed as the template file among the plurality of program files constituting the software, 8. The program structure management according to claim 7, further comprising: generating a template file composed of the common parts in the program file, and causing the computer to further execute a process of generating a template program by combining the generated template files. program.

Images