JP2008152475A - Program delivery system and program delivery method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage the result of a test to be performed to a program prior to delivery. <P>SOLUTION: A resource management device 30 manages an IP address specifying each test server 20 which performs the test prior to delivery in association of a resource ID in a delivery management table 354, a delivery resource management table 355 and a configuration management table 356. The device 30 reads a configuration management ID of the test server 20 corresponding to a resource that is an object of delivery from the delivery management table 354, and reads a configuration management ID of the test server 20 corresponding to a premise environment corresponding to the read delivery management ID from the configuration management table 356. The device 30 acquires a test result of delivery information which has the read configuration management ID as a delivery destination from the delivery management table 354, and determines whether to deliver the resource or not according to the test result. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a program distribution system and a program distribution method.

When a program is developed by a developer, the developed program is distributed to a production environment where a production operation is performed. Although program distribution is a simple task, human error is likely to occur. Various techniques for managing program distribution have been proposed (see, for example, Patent Document 1).
JP 2002-91765 A

  By the way, the developed program is tested before distribution. As a program test, a unit test for a program module, a combination test for a combination of a plurality of modules, and a system test for the entire program are known.

  However, at the time of program distribution, it is manually confirmed whether or not the program has been tested.

  The present invention has been made in view of such a background, and an object of the present invention is to provide a program distribution system and a program distribution method capable of managing the results of tests that a program should receive before distribution.

  The invention according to claim 1 of the present invention for solving the above-mentioned problems is a system for distributing the program to an execution device that executes the program, wherein the program is associated with a program ID indicating the program. A test environment storage unit for storing a test device ID for specifying a test device for performing the test, a test device ID indicating the test device, the program ID indicating the program tested in the test device, and a result of the test A test result storage unit for storing the result information indicating the program, a distribution program storage unit for storing the program ID indicating the program to be distributed, and the program ID read from the distribution program storage unit The test apparatus ID corresponding to the program ID is set to the test Read from the environment storage unit, the test apparatus ID and the test ID obtained by reading the result information corresponding to the program ID from the test result storage unit, the program according to the obtained result information A delivery permission / rejection determination unit that determines whether or not to distribute to an execution device.

  According to the program distribution system of the present invention, whether or not to distribute the program can be determined based on whether or not the test for the program to be distributed is successful. Therefore, it is possible to distribute only a program that has been successfully tested, and it is possible to prevent a mistake that causes a program that has not been tested to be distributed.

  Moreover, invention of Claim 2 among this invention is a program delivery system of Claim 1, Comprising: The said test environment memory | storage part contains the said program ID, the said execution apparatus which performs the said program, or the said In association with the device ID indicating the test device that performs the test of the program, the test device ID that specifies the test device that performs the test to be performed before the execution of the program or before the test of the program is stored. The distribution program storage unit stores the device ID indicating the execution device or the test device as a distribution destination of the program in association with the program ID, and the test result acquisition unit stores the program ID and The device ID is read from the distribution program storage unit, and the read program ID and device ID are Reading the test device ID for from the test environment storage unit, the distribution permission determination unit, and determining whether or not to transmit the program to the execution unit or the test device the device ID indicates.

  In this case, it is possible to set a test to be received before distribution depending on whether the distribution destination of the program is a program execution apparatus or a test apparatus that performs a program test.

  Moreover, invention of Claim 3 among the present invention is the program delivery system of Claim 2, Comprising: The 1st input column for inputting the said program ID, and the said execution apparatus or the said test apparatus A second input field for inputting the device ID indicating the test device ID indicating the test device that performs the test to be performed before the execution of the program in the execution device or the test in the test device Are displayed in a tree structure format with the second input field as a parent and the third input field as a child, and the program ID, device ID, and test A user interface that receives an input of a device ID is provided.

  According to a fourth aspect of the present invention, there is provided the program delivery system according to the first aspect, wherein the test apparatus ID and the program ID are associated with the test apparatus before the test. A premise test environment storage unit that stores a premise test device ID indicating another test device that performs the premise test that is the test to be performed, and the test result acquisition unit includes the first result information, Reading the premise test ID corresponding to the test device ID from the premise test environment storage unit, obtaining the second result information corresponding to the read premise test ID and the program ID from the test result determination unit, and The distribution availability determination unit determines whether to distribute the program to the execution device according to the first and second result information. And the.

  In this case, it is possible to cope with a case where a plurality of tests are performed on a program, for example, a combination test is performed before a system test.

  The invention according to claim 5 of the present invention is the program delivery system according to claim 1, wherein the file is another file having a dependency relationship with the file in association with the file name indicating the file. A dependency file storage unit that stores a dependency file name indicating a dependency file, wherein the program ID is a file name indicating a file in which the program is stored, and the distribution program storage unit indicates the file to be distributed A list of file names is stored, and for each of the file names included in the list, the dependent file name corresponding to the file name is acquired from the dependent file storage unit, and the acquired dependent file name is the Depending on whether it is included in the list, the dependent file of the file is also subject to distribution A dependency file determination unit that determines whether the distribution file is distributed to the execution device according to whether the dependency file is also a distribution target for all the files to be distributed; Decide whether or not to do.

  In this case, for example, it is possible to confirm whether files necessary for program execution, such as setting files and shared libraries, are distributed together with the program.

  Other problems and solutions to be disclosed by the present application will be made clear by the embodiments of the invention and the drawings.

  According to the present invention, it is possible to manage the results of tests that a program should undergo before distribution.

  Hereinafter, a resource management system according to an embodiment of the present invention will be described. In the resource management system of this embodiment, various resources related to program development are managed.

  In the present embodiment, the resource includes a source code of a development target program (hereinafter referred to as a development program), parameters and data used when executing the development program, a script used when compiling the development program, and a subroutine of the development program. Data that is managed as a file, such as a shared library.

  In addition, it is assumed that the development program is released through three stages of tests: a unit test, an integration test, and a system test. The unit test is a test performed on each part (hereinafter referred to as a module) of the development program, and the integration test is a test performed by combining a plurality of modules that have undergone the unit test. The integration test mainly verifies whether each module can be processed in cooperation with other modules. The system test is a test performed on the entire development program by combining all modules that have undergone unit tests and integration tests.

== System configuration ==
FIG. 1 is a diagram showing the overall configuration of the resource management system of this embodiment. As shown in the figure, the resource management system of the present embodiment includes a production server 10, a test server 20, a resource management device 30, an administrator terminal 41, a developer terminal 42, and a tester terminal 43. . The production server 10, the test server 20, the resource management device 30, the administrator terminal 41, the developer terminal 42, and the tester terminal 43 are connected to be communicable with each other via the communication network 50. The communication network 50 is, for example, a LAN (Local Area Network) or the Internet constructed by Ethernet (registered trademark) or a public telephone network. In this embodiment, it is assumed that communication by TCP / IP is performed in the communication network 50.

  The developer terminal 42 is a computer operated by the program developer. The developer terminal 42 is, for example, a personal computer or a workstation. The developer operates the developer terminal 42 to create a module. The module created by the developer is unit tested at the developer terminal 42. The module subjected to the unit test is transmitted to the resource management apparatus 30 and managed by the resource management apparatus 30.

  The production server 10 (corresponding to the execution device of the present invention) is a computer that provides an information processing service related to production work. The production server 10 is, for example, a personal computer or a workstation. The development program is distributed to the production server 10 after undergoing the various tests described above. In the present embodiment, the information processing service is provided by executing a program distributed by a plurality of production servers 10. A combination of one or more production servers 10 that provide one production service is called a production environment.

  The test server 20 (corresponding to the test apparatus of the present invention) is a computer that performs a program integration test and a system test, and a tester terminal 43 is a user (hereinafter referred to as a tester) that performs a program integration test and a system test. Is a computer that operates. The test server 20 and the tester terminal 43 are, for example, a personal computer or a workstation. The tester operates the tester terminal 43 to access the test server 20 to perform a combination test and a system test.

  A combination of one or more test servers 20 that performs the same integration test or system test is called a test environment. In the resource management system of this embodiment, as shown in FIG. 1, two test environments, an ST environment and a CT environment, are provided, a combined test is performed in the CT environment, and a system test is performed in the ST environment.

  The administrator terminal 41 is a computer operated by an administrator of the resource management system of this embodiment. The administrator terminal 41 is, for example, a personal computer or a workstation. The administrator operates the administrator terminal 41 to access a resource management device 30 (to be described later) and perform various settings.

  The resource management device 30 is a computer that manages modules created by a developer and distributes the modules to the production server 10 and the test server 20 in accordance with settings.

== Resource management device 30 ==
FIG. 2 is a diagram illustrating a hardware configuration of the resource management device 30. As shown in the figure, the resource management device 30 includes a CPU 301, a memory 302, a storage device 303, a communication port 304, and an input / output device 305. The storage device 303 stores various programs and data, for example, a hard disk drive, a CD-ROM drive, a flash memory, or the like. The CPU 301 implements various functions by activating programs stored in the storage device 303. The communication port 304 is an interface for connecting to the communication network 50. The communication port 304 is, for example, an adapter for accessing Ethernet (registered trademark) or a modem for connecting to a public telephone line network. The input / output device 305 is, for example, a keyboard, a mouse, or a display that performs data input / output.

  FIG. 3 is a diagram illustrating a software configuration of the resource management device 30. As shown in the figure, the resource management device 30 includes a resource registration unit 311, a resource information registration unit 312, a configuration information registration unit 313, a test information registration unit 314, an approval information registration unit 315, a resource distribution unit 316, and a resource storage unit. 351, a resource management table 352, a prerequisite resource management table 353, a distribution management table 354, a distribution resource management table 355, and a configuration management table 356. Note that the CPU 301 of the resource management apparatus 30 stores the functional units of the resource registration unit 311, the resource information registration unit 312, the configuration information registration unit 313, the test information registration unit 314, the approval information registration unit 315, and the resource distribution unit 316. This is realized by reading the program stored in the device 303 into the memory 302 and executing it. Further, the resource storage unit 351, the resource management table 352, the prerequisite resource management table 353, the distribution management table 354, the distribution resource management table 355, and the configuration management table 356 are provided by the memory 302 and the storage device 303 of the resource management device 30. Realized as a storage area.

  The configuration management table 356 stores information indicating the configuration of the production environment and the test environment (hereinafter referred to as configuration information). The configuration information has a tree structure. FIG. 4 shows a configuration example of configuration information stored in the configuration management table 356. As shown in the figure, the configuration information of this embodiment includes a configuration management ID, a parent ID, a name, an attribute type, an OS, an IP address, a server name, a distribution method, a user name, a password, and a prerequisite environment. .

  The configuration management ID is identification information of configuration information. The parent ID is information indicating the configuration information that is the parent of the configuration information. The attribute type indicates the type of configuration information.

  The attribute type is any one of “root”, “environment”, “on / batch”, and “server”. When the attribute information is information indicating the entire tree structure, the attribute type is “root”. The configuration management table 356 has only one configuration information whose attribute type is “root”. When the attribute information is information about the production environment or the test environment, the attribute type is “environment”. When the attribute information is information about the production server 10 or the test server 20, the attribute type is “server”. When the attribute information indicates the operation type of the production server 10 or the test server 20, the attribute type is “on / batch”. When the attribute type is “on / batch”, the name is “online” or “batch”.

  When the attribute type is “server”, the OS, IP address, server name, distribution method, user name, and password are set. The OS is information indicating the type of operating system operating on the production server 10 or the test server 20. The IP address is the IP address of the production server 10 or the test server 20, and the server name is the name of the production server 10 or the test server 20. The distribution method indicates a protocol for distributing resources to the production server 10 and the test server 20. In the present embodiment, the distribution method is “cifs” or “ftp”. The user name and password are a user name and password that are used for authentication when resources are distributed to the production server 10 or the test server 20 by “cifs” or “ftp”.

  The prerequisite environment is information indicating a test environment to which the resource should be distributed before the resource is distributed to the production server 10 or the test server 20 that constitutes the environment when the attribute type is “environment”. . In the present embodiment, the configuration management ID of the configuration information corresponding to the test environment is used as the prerequisite environment. For example, for the ST environment for performing the system test, the resources should be distributed first to the CT environment for performing the integration test. Therefore, the configuration information of the CT environment is included in the prerequisite environment of the configuration information for the ST environment. A management ID is set. In addition, since a system test should be performed before the actual operation, the configuration management ID of the configuration information for the ST environment is set as the prerequisite environment for the configuration information for the production environment.

  The configuration information registration unit 313 receives configuration information from the administrator terminal 41 and registers the received configuration information in the configuration management table 356. Details of configuration information registration processing by the configuration information registration unit 313 will be described later.

  The resource storage unit 351 stores various resources such as modules, setting files, and shared libraries. The resource storage unit 351 is realized, for example, as a file system directory provided by an operating system operating on the resource management apparatus 30.

  The resource registration unit 311 receives resources such as modules and setting files from the developer terminal 42 and stores them in the resource storage unit 351.

  The resource management table 352 stores information about resources (hereinafter referred to as resource information). A configuration example of the resource information registered in the resource management table 352 is shown in FIG. As shown in the figure, the resource information includes a resource ID, a parent ID, a name, a path, an attribute type, and an execution server ID. The resource ID is identification information of resource information. The resource information has a tree structure, and the parent ID is the resource ID of the parent resource information. The name is a file name indicating the resource, and the path is a full path indicating the resource. The attribute type indicates the type of resource. In the present embodiment, the attribute type is any one of “root”, “folder”, and “file”. The execution server ID is information indicating the production server 10 or the test server 20 to which the resource is distributed. In the present embodiment, the execution server ID is a configuration management ID of configuration information about the production server 10 or the test server 20.

  The prerequisite resource management table 353, when distributing a certain resource to the production server 10 or the test server 20, manages information (hereinafter referred to as prerequisite resource information) that manages a resource to be distributed simultaneously with the resource (hereinafter referred to as prerequisite resource). .) Is memorized. A configuration example of the prerequisite resource information stored in the prerequisite resource management table 353 is shown in FIG. As shown in the figure, the prerequisite resource information includes a resource ID, a prerequisite resource ID, and a prerequisite. The resource ID is identification information of the resource information, and the prerequisite resource ID is identification information of the resource information about the prerequisite resource. A precondition is a description of a premise resource.

  The distribution management table 354 stores information related to resource distribution (hereinafter referred to as distribution information). As will be described later, the resource management device 30 distributes resources based on distribution information whose distribution date is the current date. A configuration example of distribution information stored in the distribution management table 354 is shown in FIG. As shown in the figure, the distribution information includes a distribution ID, an applicant ID, an application date, a distribution date, a distribution destination, a tester ID, a test result, a test completion date, an approver ID, an approval date, and a distribution result. .

  The distribution ID is identification information of distribution information. The applicant ID is identification information (hereinafter referred to as a user ID) of the user who registered the distribution information. The application date is the date when the distribution information is registered.

  The distribution date is a scheduled date for distributing the resource. The distribution destination is information for specifying the production server 10 or the test server 20 to which the resource is distributed. In the present embodiment, the distribution destination is a configuration management ID indicating configuration information about the production server 10 or the test server 20.

  The tester ID is a user ID indicating a tester who has performed a test on the resource to be distributed, and the test result is the result of the above test. In the present embodiment, it is assumed that the test result is either “OK” or “NG”. The test completion date is the date when the tester performed the test.

  The approver ID is a user ID of an administrator who has made approval for resource distribution. The approval date is the date on which the administrator has made the above approval.

  The distribution result is information indicating a result of resource distribution. In the present embodiment, it is assumed that the distribution result is either “OK” or “NG”.

  The distribution resource management table 355 (corresponding to the distribution program storage unit of the present invention) stores information related to resources to be distributed (hereinafter referred to as distribution resource information). FIG. 8 shows a configuration example of distribution resource information stored in the distribution resource management table 355. As shown in the figure, the distribution resource information includes a distribution ID, a resource ID, and a prerequisite resource ID. The distribution ID is identification information of the above distribution information. The resource ID is information for specifying a resource to be distributed. In the present embodiment, the resource ID included in the distribution resource information indicates the resource information registered in the resource management table 352. The prerequisite resource ID is a prerequisite resource ID corresponding to the resource ID in the above-described prerequisite resource management table 353.

The distribution management table 354, the distribution resource management table 355, and the resource management table 352 set the production server 10 or the test server 20 as a distribution destination for a certain resource, and set a value in the prerequisite environment of the configuration information. In the case where it is determined, the test server 20 to be tested prior to the distribution of the resource is specified (corresponding to the test environment storage unit of the present invention).
The resource information registration unit 312 registers information about resources. The resource information registration unit 312 receives the resource information, the prerequisite resource information, and the delivery resource information from the administrator terminal 41, and the received resource information, the prerequisite resource information, and the delivery resource information, the resource management table 352, the prerequisite resource management. Register in the table 353 and the distribution resource management table 355.

  The test information registration unit 314 registers test results. The test information registration unit 314 accepts the input of the test result and the distribution ID from the tester, and corresponds the user ID indicating the tester, the input test result, and the current date to the input distribution ID. Set to the tester ID, the test result, and the test completion date of the distribution information.

  The approval information registration unit 315 registers that approval related to distribution has been performed. The approval information registration unit 315 receives the input of the distribution ID of the distribution information to be approved from the administrator, and sets the user ID indicating the administrator and the current date of the distribution information corresponding to the input distribution ID. Set for each approver ID and approval date.

  The resource distribution unit 316 (corresponding to the test result acquisition unit and the distribution availability determination unit of the present invention) depends on the distribution information registered in the distribution management table 354 and the distribution resource information corresponding to the distribution information. The resource is distributed to the production server 10 or the test server 20. The resource distribution unit 316 uses the user name and password of the configuration information to indicate the IP address of the configuration information indicated by the distribution information distribution destination according to a protocol such as FTP or CIFS indicated in the configuration information distribution method. Deliver resources. Note that a general file copy process can be employed for the distribution process by the resource distribution unit 316. Information necessary for copying this file is included in the configuration information.

== Processing ==
Hereinafter, processing of the resource management device 30 will be described. In this embodiment, the administrator, the sub-administrator, the developer, and the tester operate the administrator terminal 41, the developer terminal 42, and the tester terminal 43 to log in to the resource management apparatus 30 and perform various information. It is assumed that each screen displayed by the resource management device 30 is displayed on the administrator terminal 41, the developer terminal 42, and the tester terminal 43.

  FIG. 9 is a diagram illustrating an example of a screen 70 that displays a menu of processing performed by the resource management device 30. As shown in the figure, a screen 70 includes a menu display field 701 for a manager, a menu display field 702 for a developer leader (hereinafter also referred to as a sub-administrator), and a menu display for a developer. A column 703 and a tester menu display column 704 are provided. Whether or not each display field is displayed is determined by the user who has logged into the resource management apparatus 30. For example, when the administrator is logged in, all of the display columns 701 to 704 are displayed on the screen 70, and when the sub administrator is logged in, the display columns 702 to 704 are displayed on the screen 70. The When a general developer is logged in, the display fields 703 and 704 are displayed on the screen 70. When the tester is logged in, only the display field 704 is displayed on the screen 70. When a process is selected from the screen 70, the process selected in the resource management apparatus 30 is performed.

  FIG. 10 is a diagram showing the flow of processing by the resource management device 30 when performing general development work. In the present embodiment, it is assumed that the user of the resource management system selects a process from the screen 70 so as to follow the procedure shown in FIG.

  The resource management device 30 receives configuration information input from the administrator and performs configuration information registration processing (S501). The resource management device 30 receives input of resource information whose attribute is “root” from the administrator (S502). Input of resource information whose attribute is “folder” is received from the sub-administrator (S503), and input of resource information whose attribute is “file” is received from the administrator, sub-administrator, or general developer ( S504), resource information is registered. The resource management device 30 accepts input of distribution information from the administrator, performs distribution information registration processing (S505), and performs approval processing related to resource distribution (S506). The resource management device 30 distributes resources to the production server 10 and the test server 20 based on the approved distribution information (S507). In addition, when there is an input of a test result from the tester, the resource management device 30 performs a test result registration process (S508). Details of each process will be described below.

== Configuration information registration process ==
FIG. 11 is a diagram showing the flow of configuration information registration processing.
First, the resource management device 30 receives input of configuration information until receiving an end instruction from the administrator (S521), and registers the received configuration information in the configuration management table 356 (S522). When the resource management device 30 receives update data for updating the configuration information, the resource management device 30 updates the configuration information registered in the configuration management table 356 with the received update data.

  A screen 72, which is an example of an interface for receiving input of configuration information, is shown in FIG. The screen 72 includes a display field 721 for displaying a tree structure of configuration information, and a display field 722 for details of configuration information. In the display field 721, each piece of configuration information registered in the configuration management table 356 is displayed in a tree shape. The administrator selects the parent configuration information by clicking with the mouse.

  In the example of FIG. 12, “batch (012)” (corresponding to the configuration information whose configuration management ID is 012 in the example of the configuration management table 356 shown in FIG. 4) is selected. The screen 72 includes a display column 722 for each item of configuration information, and each item of the configuration information selected in the display column 721 is displayed in the display column 722. When the add menu 723 is selected on the screen 72, a dialog 74 for inputting configuration information shown in FIG. 13 is displayed.

  As shown in FIG. 13, the dialog 74 includes an input field 741 for each item of configuration information. The administrator inputs each item of configuration information to be newly created in each input field 741 and presses the save button 742. When the save button 742 is pressed, the resource management apparatus 30 inputs the configuration management ID of the configuration information selected in the display column 721 of FIG. 12 as the parent ID into each input column 741 of the dialog 74 of FIG. Configuration information in which the value and the parent ID are set is generated, and the generated configuration information is registered in the configuration management table 356.

  When the configuration information is registered in the configuration management table 356 as described above, the resource management apparatus 30 determines whether or not configuration information having the attribute type “root” is registered in the configuration management table 356 ( S522). When the configuration information whose attribute type is “root” is not registered (S523: NO), the resource management device 30 performs the processes of (S521) to (S522) until receiving an end instruction from the administrator again.

  When the configuration information whose attribute type is “root” is registered (S523: YES), the resource management apparatus 30 performs the following processing for each configuration information registered in the configuration management table 356.

  When the attribute type is “server” (S524: YES), the resource management device 30 re-registers the configuration information from (S521) if the IP address, the user name, or the password is not set in the configuration information. Perform input processing. In this case, the configuration information registered in the configuration management table 356 may be output, and the configuration information output by the administrator may be corrected.

  When the IP address, the user name, and the password are set in the configuration information (S525), the resource management device 30 follows the protocol indicated by the configuration information distribution method, and the production server 10 or the test server indicated by the configuration information IP address 20 is tried whether it can be accessed using a user name and a password (S526). If the access cannot be made (S526: NO), the configuration information input process from (S521) is performed again. In this case, the resource management device 30 displays a message indicating that the production server 10 or the test server 20 indicated by the IP address could not be accessed.

  The resource management device 30 repeats the above processing to set the configuration of the production environment and the test environment, and confirms the user name and password accessible to the production server 10 and the test server 20 and the distribution method.

== Resource information registration process ==
FIG. 14 is a diagram illustrating a flow of registration processing of configuration information whose attribute type is “route”. Configuration information whose attribute type is “root” can be registered only by an administrator. The resource management device 30 repeats the following processing until an end instruction is received from the user.

  The resource management device 30 receives input of each item of resource information from the user (S541), determines whether or not the logged-in user is an administrator (S542), and is an administrator (S542: YES), It is determined whether or not the attribute type of the received resource information is “route” (S543). When the attribute type is “route” (S543: YES), the resource management apparatus 30 determines whether or not the resource information with the attribute type “root” is registered in the resource management table 352 (S544). If resource information whose attribute type is “root” is registered (S544: YES), a message indicating that the resource information of “root” has already been registered is displayed, and the process proceeds to (S541), and again Accepts input of resource information.

The resource management device 30 determines whether a name and path are set in the input resource information (S545). If the name and path are set (S545: YES), the resource information is stored in the resource management table. It registers in 352 (S546).
As described above, the configuration information whose attribute type is “root” is registered.

  Configuration information whose attribute type is “folder” or “file” is also registered in the same manner. FIG. 15 is a diagram illustrating a flow of registration processing of configuration information whose attribute type is “folder”. Configuration information whose attribute type is “folder” can be registered only by an administrator and a sub-administrator. The resource management device 30 repeats the following processing until an end instruction is received from the user.

The resource management device 30 receives input of resource information from the user (S561), and determines whether the logged-in user is an administrator or a sub-administrator (S562). If the user is an administrator or a sub-administrator (S562: YES), the resource management apparatus 30 determines whether the attribute type of the input resource information is not “root” (S563). When the attribute type is not “root” (S563: NO) and the name and path of the resource information are set (S564: YES), the resource information is registered in the resource management table 352 (S565). If the attribute type is “root” (S563: YES), or if no name or path is set in the resource information (S564: NO), the process proceeds to (S561) to accept the input of the resource information again. To.
As described above, the configuration information whose attribute type is “folder” is registered.

  FIG. 16 is a diagram illustrating a flow of registration processing of configuration information whose attribute type is “file”. Resource information whose attribute type is “file” can be registered by all users. The resource management device 30 performs the following processing until an end instruction is received from the user.

The resource management device 30 receives input of resource information from the user (S581), and determines whether or not the attribute type of the received resource information is “file” (S582). When the attribute type is “file” (S582: YES) and the name and path of the resource information are set (S583: YES), the resource management apparatus 30 registers the resource information in the resource management table 352 (S584). ).
As described above, resource information whose attribute type is “file” is registered.

  FIG. 17 is a diagram illustrating an example of a screen 76 that is an interface for receiving input of resource information. As shown in the figure, the screen 76 includes a display column 761 for displaying resource information in a tree structure and a display column 762 for displaying each item of resource information. In the display column 761, each resource information registered in the resource management table 352 is displayed in a tree shape. When resource information is selected in the display column 761, each item of the selected resource information is displayed in the display column 762. In the example of FIG. 17, “B (008)” is selected, and each item of resource information whose resource ID is “008” is displayed in the display column 762. When the add menu 763 is selected on the screen 76, a dialog 78 for inputting resource information shown in FIG. 18 is displayed. As shown in FIG. 18, the dialog 78 includes an input field 781 for each item of resource information. The administrator, sub-administrator, or developer inputs each item of resource information in the input field 781 of the dialog 78 and presses the save button 782. When the save button 782 is pressed, the resource management device 30 uses the resource ID of the resource information selected in the display field 761 of FIG. 17 as the parent ID and the value input in the input field 781 of the dialog 78 of FIG. Then, resource information in which the parent ID is set is generated, and the generated resource information is registered in the resource management table 352. As described above, the resource information is registered in the resource management table 352.

== Distribution information registration process ==
FIG. 19 is a diagram illustrating a flow of registration processing of distribution information.
The resource management device 30 receives an input of a distribution date (S601), receives an input of the production server 10 or the test server 20 that is a resource distribution destination (S602), and a resource ID (hereinafter, distribution) indicating a resource to be distributed An input of a list of target resource IDs) is accepted (S603).

  When the resource management device 30 is instructed by the user to automatically add the prerequisite resource (S604: YES), the resource management device 30 performs the following processing for each of the distribution target resource IDs included in the list.

  The resource management device 30 acquires a prerequisite resource ID corresponding to the distribution target resource ID from the prerequisite resource management table 353 (S605). When the resource management apparatus 30 can acquire the prerequisite resource ID (S606: YES), if the acquired assumption resource ID is not included in the list (S607: NO), the resource management device 30 is included in the list. It is added (S608).

  The resource management apparatus 30 can automatically set other resources related to the resource to be distributed as distribution targets by performing the above processing for each distribution target resource ID.

  Next, the resource management device 30 performs the following processing for each of the distribution target resource IDs included in the list.

The resource management apparatus 30 acquires a prerequisite resource ID corresponding to the distribution target resource ID from the prerequisite resource management table 353 (S609). If the resource management device 30 can acquire the premise resource ID (S610: YES), if the premise resource ID is not included in the list of distribution resource IDs (S611: NO), the resource management apparatus 30 returns to (S603) and distributes again. Accept input of target resource.
Through the above processing, for each resource to be distributed, related prerequisite resources can also be set as distribution targets.

The resource management device 30 newly assigns a distribution ID (S612), and sets the distribution ID assigned, the user ID indicating the logged-in user, the current date, the input distribution date, and the distribution destination. Information is generated, and the generated distribution information is registered in the distribution management table 354 (S613). Further, the resource management device 30 registers the distribution ID, the distribution target resource ID, and the corresponding prerequisite resource ID in the distribution resource management table 355 for each of the distribution target resource IDs (S614).
As described above, the distribution information and the distribution resource information are registered in the distribution management table 354 and the distribution resource management table 355.

  FIG. 20 is a diagram illustrating an example of a user interface used for distribution information registration processing. As shown in FIG. 20, the screen 80 includes a display field 801 that displays a list of distribution information, and the display field 801 displays a list of distribution information registered by the currently logged-in user. Specifically, the resource management device 30 reads distribution information whose applicant ID matches the user ID of the currently logged-in user from the distribution management table 354 and outputs the read distribution information as a list in the display field 801. When a new application button 802 is pressed on the screen 80, the resource management device 30 displays a distribution information input screen 82.

  The input screen 82 shown in FIG. 20 includes a distribution date input field 821, an input field 822 for the production server 10 or test server 20 that is a distribution destination, and an input field 823 for a resource to be distributed.

  The input field 822 is a pull-down list, and a list of the production server 10 and the test server 20 can be selected.

  In the input field 823, each resource information registered in the resource management table 352 is displayed in a tree shape, and a check box is displayed for each resource information. The user can select a resource to be distributed by checking a check box. Further, when a certain resource is selected in the input field 823, a resource that is a descendant of the resource is also selected. For example, in the example of FIG. 20, when a check box 824 is selected, its check boxes 825 and 826 are also checked.

  If the execution server ID of the resource information is set, the resource may not be selected if the distribution destination selected in the input field 822 and the execution server ID do not match. In the example of FIG. 20, the check box 827 cannot be selected.

  When the distribution date is input in the input field 821, the distribution destination is selected in the input field 822, the resource to be distributed is selected in the input field 823, and the application button 828 is pressed, the resource management apparatus 30 The distribution information is registered by the process of FIG.

== Approval processing ==
FIG. 21 is a diagram showing the flow of the approval process. The resource management device 30 displays a list of distribution information registered in the distribution management table 354 (S681), and performs the following processing until an end instruction is received. The resource management device 30 receives the designation of the distribution ID of the distribution information to be approved (S682), and the user of the user who is logged in at the approver ID and approval date of the distribution information corresponding to the specified distribution ID The ID and the current date are set and the distribution management table 354 is updated (S683). As described above, the distribution information is approved.

  FIG. 22 is a diagram illustrating an example of a user interface used for the approval process. As shown in the figure, on the screen 84, a list of distribution information registered in the distribution management table 354 is displayed, and a check box 841 for approving distribution is displayed in each distribution information. The administrator can specify the distribution ID to be approved by checking the check box 841 corresponding to the distribution information to be approved. When the approval button 842 is pressed, the resource management device 30 performs an approval process on the checked distribution information.

== Distribution processing ==
FIG. 23 is a diagram illustrating a flow of resource distribution processing.
The resource management device 30 reads the distribution information in which values are set for the approver ID and the approval date and “OK” is not set in the distribution result from the distribution management table 354 (S641). The following processing is performed for each piece of information.

  If the distribution date of the distribution information is the current date (S642: YES), the resource management device 30 acquires configuration information whose configuration management ID matches the distribution information distribution destination from the configuration management table 356 (S643). . The resource management device 30 acquires the configuration information that is an ancestor of the acquired configuration information and has the attribute type “environment” (hereinafter referred to as environment information) (S644). If the configuration management ID is assigned to the prerequisite environment of the acquired environment information (S645: YES), the resource management device 30 performs a test result confirmation process shown in FIG. 24 (S646).

  The resource management device 30 sets the test flag to “false” (S661), and from the configuration management table 356, the configuration management ID that matches the prerequisite environment of the above environment information (hereinafter referred to as prerequisite environment information). Obtain (S662). The resource management apparatus 30 acquires the configuration information that is a descendant of the acquired prerequisite environment information and has the attribute type “server” (hereinafter referred to as prerequisite configuration information) (S663), and acquires the acquired prerequisite configuration information. The following processing is performed for each of the above. The resource management device 30 acquires from the distribution management table 354 the distribution destination that matches the configuration management ID of the prerequisite configuration information (hereinafter referred to as the prerequisite distribution information) (S664), and the test result of the acquired assumption distribution information. Is “OK” (S665: YES), the test flag is set to “true” (S666). By repeating the above processing, it is possible to confirm whether or not the test has already been successful in the test server 20 configuring the test environment corresponding to the prerequisite environment.

  When the test flag becomes “true” by the above-described test result confirmation process (S647: YES), or when the prerequisite environment of the environment information is empty (S645: NO), the resource management apparatus 30 Then, the configuration information corresponding to the distribution destination of the distribution information is acquired from the configuration management table 356 (S648), and the resource ID corresponding to the distribution ID of the distribution information is acquired from the distribution resource management table 355 (S649). The resource management device 30 acquires a path corresponding to the acquired resource ID from the resource management table 352 (S650). The resource management device 30 uses the username and password of the configuration information for the production server 10 or the test server 20 indicated by the IP address of the configuration information, and is specified by the path according to the protocol indicated by the configuration information distribution method. The resource stored in the resource storage unit 351 is distributed (S651). The resource management apparatus 30 updates the distribution management table 354 so that the distribution result is the distribution information distribution result (S652).

  As described above, when there is a precondition test for the approved distribution information, the resource is distributed only when the result of the test is “OK”. Therefore, for example, when it is necessary to perform integration testing prior to system testing, integration testing has not succeeded by setting the testing environment for integration testing as a prerequisite environment for testing the system testing. It is possible to prevent resources from being delivered to the test environment for system testing. As a result, the test can be performed step by step reliably.

== Test result registration process ==
FIG. 25 is a diagram showing a flow of processing for registering a test result from a tester.
The resource management device 30 displays a list of distribution information registered in the distribution management table 354 (S681), and receives an input of a distribution ID and a test result (S682). The resource management device 30 adds the user ID of the logged-in user, the input test result, and the current date to the tester ID, test result, and test completion date of the distribution information corresponding to the received distribution ID. The distribution management table 354 is set and updated (S683).

  FIG. 26 is a diagram illustrating an example of a user interface used for test result registration processing. As shown in the figure, distribution information is displayed in a list on a screen 86, and a test result input field 861 is attached to each distribution information. The input field 861 is a pull-down list for selecting “OK” or “NG”, and the tester selects “OK” or “NG” from the pull-down list and inputs the test result in the input field 861. When the update button 862 is pressed, the resource management apparatus 30 registers the test result for each piece of distribution information for which the test result has been input, by the process of FIG. 25 described above.

  Although the present embodiment has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

It is a figure which shows the whole structure of the resource management system of this embodiment. 2 is a diagram illustrating a hardware configuration of a resource management device 30. FIG. 3 is a diagram showing a software configuration of a resource management device 30. FIG. 5 is a diagram illustrating a configuration example of configuration information stored in a configuration management table 356. FIG. It is a figure which shows the structural example of the resource information registered into the resource management table 352. It is a figure which shows the structural example of the prerequisite resource information memorize | stored in the prerequisite resource management table 353. It is a figure which shows the structural example of the delivery information memorize | stored in the delivery management table 354. It is a figure which shows the structural example of the delivery resource information memorize | stored in the delivery resource management table. 6 is a diagram illustrating an example of a screen 70 that displays a menu of processing performed by the resource management device 30. FIG. FIG. 4 is a diagram showing a flow of processing by a resource management device 30. It is a figure which shows the flow of the registration process of structure information. It is a figure which shows the screen 72 which is an example of the interface for receiving the input of structure information. It is a figure which shows the dialog 74 for inputting structure information. It is a figure which shows the flow of a registration process of the structure information whose attribute classification is "root". It is a figure which shows the flow of a registration process of the structure information whose attribute classification is "folder". It is a figure which shows the flow of a registration process of the structure information whose attribute classification is "file." It is a figure which shows an example of the screen 76 which is an interface for receiving the input of resource information. It is a figure which shows the dialog 78 for inputting resource information. It is a figure which shows the flow of a registration process of delivery information. It is a figure which shows an example of the user interface used for the registration process of delivery information. It is a figure which shows the flow of an approval process. It is a figure which shows an example of the user interface used for an approval process. It is a figure which shows the flow of the delivery process of a resource. It is a figure which shows the flow of the confirmation process of a test result. It is a figure which shows the flow of a process which registers the test result from a tester. It is a figure which shows an example of the user interface used for the registration process of a test result.

Explanation of symbols

10 production server 20 test server 30 resource management device 301 CPU
302 Memory 303 Storage Device 304 Communication Port 305 Input / Output Device 311 Resource Registration Unit 312 Resource Information Registration Unit 313 Configuration Information Registration Unit 314 Test Information Registration Unit 315 Approval Information Registration Unit 316 Resource Distribution Unit 351 Resource Storage Unit 352 Resource Management Table 353 Premise Resource management table 354 Distribution management table 355 Distribution resource management table 356 Configuration management table 41 Administrator terminal 42 Developer terminal 43 Tester terminal 70 Screen 701 Display field 702 Display field 703 Display field 704 Display field 72 Screen 721 Display field 722 Display field 723 Additional menu 74 Dialog 741 Input field 742 Save button 76 Screen 761 Display field 762 Display field 763 Additional menu 78 Dialog 781 Input field 782 Save button 80 screen 01 display field 802 new application button 82 input screen 821 input field 822 input field 823 input field 824 check box 825 check box 826 check box 827 check box 828 application button 84 screen 841 check box 842 approval button 86 screen 861 input field 862 update button

Claims (6)

A system for distributing the program to an execution device that executes the program,
A test environment storage unit that stores a test device ID that identifies a test device for testing the program in association with a program ID indicating the program;
A test result storage unit for storing a test device ID indicating the test device, the program ID indicating the program tested in the test device, and result information indicating the result of the test;
A distribution program storage unit that stores the program ID indicating the program to be distributed;
The program ID is read from the distribution program storage unit, the test device ID corresponding to the read program ID is read from the test environment storage unit, and the read test device ID and the result information corresponding to the program ID are read. A test result acquisition unit acquired from the test result storage unit;
In accordance with the acquired result information, a delivery permission determination unit that determines whether to distribute the program to the execution device;
A program distribution system comprising: The program distribution system according to claim 1,
The test environment storage unit associates the program ID with the device ID indicating the execution device that executes the program or the test device that performs the test of the program, and before the execution of the program or the program Storing the test device ID that identifies the test device performing a test to be performed before the test;
The distribution program storage unit stores the device ID indicating the execution device or the test device as a distribution destination of the program in association with the program ID,
The test result acquisition unit reads the program ID and the device ID from the distribution program storage unit, reads the test device ID corresponding to the read program ID and device ID from the test environment storage unit,
The delivery permission determination unit determines whether to distribute the program to the execution device or the test device indicated by the device ID;
A program distribution system characterized by the above. The program distribution system according to claim 2,
A first input field for inputting the program ID, a second input field for inputting the device ID indicating the execution device or the test device, and execution or test of the program in the execution device. A third input field for inputting the test apparatus ID indicating the test apparatus performing the test to be performed before the test in the apparatus, and the third input field with the second input field as a parent. A user interface that accepts input of the program ID, the device ID, and the test device ID.
A program distribution system characterized by the above. The program distribution system according to claim 1,
Prerequisite test environment storage for storing a premise test device ID indicating another test device that performs a premise test, which is the test to be performed before the test in the test device, in association with the test device ID and the program ID Part
The test result acquisition unit reads the prerequisite test ID corresponding to the test device ID from the prerequisite test environment storage unit in addition to the first result information, and corresponds to the read prerequisite test ID and the program ID Obtaining second result information from the test result determination unit;
The delivery enable / disable determining unit determines whether to distribute the program to the execution device in accordance with the first and second result information;
A program distribution system characterized by the above. The program distribution system according to claim 1,
A dependency file storage unit that stores a dependency file name indicating a dependency file that is a dependency file that is associated with a file name indicating the file,
The program ID is a file name indicating a file in which the program is stored,
The distribution program storage unit stores a list of the file names indicating files to be distributed,
For each of the file names included in the list, the dependency file name corresponding to the file name is acquired from the dependency file storage unit, and whether the acquired dependency file name is included in the list, A dependency file determination unit that determines whether the dependency file of the file is also a distribution target;
The delivery permission determination unit further determines whether to distribute the file to the execution device according to whether the dependent file is also a distribution target for all the files to be distributed;
A program distribution system characterized by the above. A method of distributing the program to an execution device that executes the program,
Computer
In association with a program ID indicating the program, a test device ID for specifying a test device for testing the program is stored in a memory;
Storing the test device ID indicating the test device, the program ID indicating the program tested in the test device, and the result information indicating the result of the test in the memory in association with each other;
Storing the program ID indicating the program to be distributed in the memory;
The program ID is read from the memory, the test apparatus ID corresponding to the read program ID is read from the memory, and the read test apparatus ID and the result information corresponding to the input program ID are the test result. Obtained from the storage,
Determining whether to distribute the program to the execution device according to the obtained result information;
A program delivery method characterized by the above.

Images