JP2009104393A - Software trouble ticket management system and method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software trouble ticket management system for more efficiently performing development operation by reducing takeover loads between persons in charge which are caused when developing a software program. <P>SOLUTION: In the software trouble ticket management system, a trouble ticket management means 3410 records information about a fault caused in a software program under developing in a trouble ticket. A reproduction environment generation means 3420 generates a reproduction environment for reproducing the fault and the generated reproduction environment is stored in a reproduction environment information storage means 3200. Further, a correlation control means 3300 correlates the generated reproduction environment with the trouble ticket. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a software failure slip management system, method, and program, and more particularly, to a software failure slip management system, method, and program for automatically constructing a reproduction environment of a failure that has occurred in software.

  In general, a software program development process includes a process for evaluating, correcting, and improving the function by some method. A process for correcting or improving the software program is referred to as a test process. A tester in charge of the test in the test process tests whether the software program functions correctly according to the required specifications. If an error is found in the operation of the target software program in this test, this error in operation is called a failure. A failure record is a record of the failure of the software program.

  In general, the failure slip workflow is a task in which the creation of a failure slip in the test process is a task, and the operations from creation to handling and termination are arranged according to the work order. There are multiple persons in the trouble ticket workflow, such as a person in charge of testing and a person in charge of developing a software program that corrects a trouble that has occurred in the test, and the work is performed while taking over. The information recorded in the failure slip becomes the inherited content. Each operation that occurs from the start to the end of the trouble ticket workflow is defined as a state. FIG. 2 shows an example of a process for creating a trouble ticket in software program development.

  FIG. 5 is a diagram showing an example of a failure slip that records details of the failure status that has occurred, its handling, and confirmation of handling. In FIG. 5, reference numerals 501 to 503 describe basic information on a trouble slip such as a state on a workflow and a person in charge. Reference numerals 504 to 506 describe correspondences to the failure slips in each state on the workflow.

  On the other hand, in order to perform software program development work, it is necessary to prepare an environment suitable for the work. For example, in order to perform software program development work, it is necessary to prepare a personal computer (hereinafter simply referred to as “PC”), a program file, a setting file, a development tool (editor, debugger, etc.), and a compiler.

  Further, in order to deal with a failure, the hardware or software listed above must be in a state where the failure is reproduced. For example, the program file must have a version that reproduces the failure. A hardware or software necessary for executing and developing such a software program is configured to reproduce a failure, and is referred to herein as a reproduction environment.

  In general, the task of creating a reproduction environment is carried out by each person in charge with reference to the information on the failure slip. For example, assuming the above-described general trouble ticket workflow, the following occurs.

  First, the person in charge builds a reproduction environment for testing, and the person in charge of testing conducts tests on it. Second, the person in charge of the test places the found trouble in the trouble form and takes over to the person in charge of development. Third, the person in charge of development builds a reproduction environment for development based on the information entered (recorded) in the trouble slip, deals with the trouble, and records the contents of the trouble in the trouble slip. Fourth, when handing over to another developer, the succeeding developer builds a reproduction environment that reflects the actions taken by the previous developer based on the information recorded in the failure slip. Continue to take action.

  In this way, each person in charge must construct a reproduction environment in order to deal with one failure. In addition, it is expected that one person in charge will have multiple tasks, but a reproduction environment must be constructed for each failure. In other words, when developing a software program to be tested, a work for creating a reproduction environment occurs multiple times.

  Therefore, a technique for reducing the work load for creating a reproduction environment has been considered. For example, Patent Document 1 discloses a technology for copying a reproduction environment of a program development server and automatically constructing a similar reproduction environment in an integration test server. The program development server has a function of automatically converting an execution environment setting file for program development for an integration test server, thereby realizing a reproduction environment without human intervention.

In addition, the mainstream of development work was to build a reproduction environment on the PC of each developer in charge and execute it directly. On the other hand, with the spread of the Internet and the advancement of security technology, an attempt has been made to develop a program by remote operation by creating a reproduction environment on servers in remote locations including overseas. Patent Document 2 discloses a technique for providing a software development environment free of charge to a user on the Web, and providing a user with an application development method and an application development system for development in the development environment.
JP 2003-248582 A JP 2002-182910 A

  However, in the above-described conventional technique, when dealing with one failure, it is difficult to accurately take over the situation at the moment when the previous person actually caused the failure and the action taken. In other words, the information recorded on the failure slip alone cannot be communicated to the person in charge who has taken over, and it is also very burdensome for the entrant to record the situation in detail. Furthermore, it is very difficult to reproduce a failure with low reproducibility or a failure in which an event must continue to be generated for several days in order to reproduce it in another reproduction environment. Even if a reproduction environment having the same configuration is prepared, the reproduction is not always easy.

  Although the technique of the above-mentioned patent document 1 reduces the load for constructing the reproduction environment, there is a problem that it is difficult to take over the state in which the person in charge has taken some measures for the reproduction environment. In addition, the technology of Patent Document 2 enables access to the reproduction environment from the Web, but it is easy to determine a specific reproduction environment constructed for dealing with a specific failure from a plurality of reproduction environments. There is a problem that can not be done.

  The present invention has been made in view of the above problems, and a software failure slip management system capable of reducing the takeover load between persons in charge when developing a software program and performing development work more efficiently. The purpose is to provide. Furthermore, it aims at providing the software failure vote method and program.

  In order to achieve the above object, a software failure slip management system according to claim 1 is composed of a failure failure management server for developing a software program and a client terminal connected to the server via a network. In the software failure slip management system, the failure slip management server generates a failure slip management means for managing failure slips in which information relating to failures occurring in the software program is recorded, and a reproduction environment for reproducing the failure A reproduction environment information storage means for storing the generated at least one reproduction environment, and a related control means for associating the generated reproduction environment with the failure slip. And

  In order to achieve the above object, the failure slip management method according to claim 18 comprises a failure slip management server for developing a software program and a client terminal connected to the server via a network. In a failure slip management method of a software failure slip management system, a failure slip management process for managing a failure slip in which information relating to a failure occurring in the software program is recorded, and a reproduction environment for generating a reproduction environment for reproducing the failure A generation step, a reproduction environment information storage step for storing the generated at least one reproduction environment in a storage unit, and an associated control step for associating the generated reproduction environment with the failure slip. And

  ADVANTAGE OF THE INVENTION According to this invention, the inheritance load between the persons in charge who generate | occur | produce when developing a software program can be reduced, and development work can be performed more efficiently.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the present embodiment, it is assumed that the failure handling work of the Web application system is assumed.

(First embodiment)
As a first embodiment of the present invention, a description will be given of a method of generating a reproduction environment when creating a new trouble ticket and managing the generated reproduction environment in association with the trouble card. In addition, a method for uniquely identifying and accessing the reproduction environment from the failure slip will be described.

  FIG. 1 is a diagram showing a configuration example of a software failure vote management system according to the first embodiment of the present invention.

On the network 200, a client terminal 1000 and a failure slip management server 3000 are present. Both the client terminal 1000 and the trouble ticket management server 3000 include at least a control unit such as a CPU and a memory such as a RAM. Thereafter, the CPU controls each part of the hardware in accordance with the input signal or the program read into the RAM.
In the client terminal 1000, a WEB browser 1100 operates. The WEB browser 1100 is connected to the connection unit 3100 of the failure slip management server 3000 via the network 200 to transmit and receive data.

  The failure slip management server 3000 includes a connection unit 3100, a reproduction environment information storage unit 3200, a related control unit 3300, a failure slip control / management unit 3400, and an association information storage unit 3500. Hereinafter, these detailed configurations will be described in order.

  First, the connection unit 3100 distributes the request from the WEB browser 1100 to an appropriate location. The reproduction environment information storage unit 3200 stores a plurality of reproduction environments (reproduction environment information) 3210, an editor 3230, a compiler 3240, and a debugger 3250. The reproduction environment 3210 stores software, setting files, DBs, sources, log information, and the like necessary for each WEB application in order to execute or develop the WEB application. In this embodiment, the reproduction environment 3210 includes a DB connection setting file 3211, a class file 3212, a DB 3213, a source 3214, a WEB application server setting file 3215, a WEB application server 3216, and log information 3217.

  The reproduction environment 3210 is generated for each failure slip stored and managed in the failure slip DB 3440. In addition, in this embodiment, a test reproduction environment 3220 is prepared. Assume that a tester performs a test on a WEB application (hereinafter referred to as “test reproduction environment WEB application”) that operates in the test reproduction environment 3220. The elements constituting the test reproduction environment 3220 are the same as those of the reproduction environment 3210. The test reproduction environment 3220 is copied at a timing when a new failure slip is created, and a new reproduction environment 3210 is generated.

  The association control unit 3300 associates the failure form stored and managed in the failure form DB 3440 with the reproduction environment 3210 stored in the reproduction environment information storage unit 3200, and associates the association information with the association information storage unit 3500. Store. In order to access each element of the reproduction environment 3210 associated with a certain trouble ticket from the trouble ticket control / management unit 3400 side, it is necessary to inquire the related control means 3300 for information for accessing the appropriate reproduction environment 3210. is there.

  The reproduction environment control / management unit 3400 includes a failure form management unit 3410, a reproduction environment generation unit 3420, a failure form display unit 3430, and a failure form DB 3440. The trouble ticket management means 3410 plays the role of a controller of the trouble ticket management system, and comprises a workflow trouble ticket management system 3411, person-in-charge management means 3412, and trouble ticket number assigning means 3413.

  The workflow failure slip management system 3411 is a general failure slip management WEB application system having functions such as failure slip editing / saving / state transition. Further, the workflow failure slip management system 3411 has a role of creating a development screen 2000 shown in FIG. 20 for operating the reproduction environment 3210.

  The person-in-charge management unit 3412 performs exclusive control of operations on the reproduction environment 3210 associated with the failure slip. That is, only the user who is currently in charge of the failure slip is allowed to access the reproduction environment associated with the failure slip to prevent access conflict. The failure ticket number assigning unit 3413 assigns a unique number in the system to the failure ticket. In addition, a failure slip number is assigned to all operation events related to the failure slip, so that information for accessing the corresponding reproduction environment 3210 can be acquired.

  The reproduction environment generation unit 3420 generates a reproduction environment 3210 in response to a request from the workflow failure form management system 3411 when a failure form is newly created. The reproduction environment generating unit 3420 includes a reproduction environment copying unit 3421, a setting file rewriting unit 3422, and an application server starting unit 3423.

  The failure slip display means 3430 performs display of the failure slip 500 shown in FIG. 5, display of the development screen 2000 of FIG. 20, and event operation control for accessing the reproduction environment 3210 associated with the failure slip. The failure slip display unit 3430 includes a debugger control unit 3431, an editor control unit 3432, an application server control unit 3433, and a reproduction environment calling unit 3434. The reproduction environment calling unit 3434 is activated when the application screen display button 603 on the screen on which the failure slip 600 shown in FIG. 6 is displayed, and displays an execution screen of the reproduction environment WEB application with another browser. The reproduction environment calling unit 3434 displays a screen of a WEB application that operates in a reproduction environment (reproduction environment information) associated with the displayed failure slip. The debugger control unit 3431 executes debugging to a WEB application that operates in a reproduction environment (reproduction environment information) associated with the displayed failure slip.

  The failure form DB 3440 stores information related to the failure input from the screen on which the failure form 500 of FIG. 5 is displayed. The connection unit 3100, the related control unit 3300, and the failure slip control / management unit 3400 can use the WEB application technology and the functions provided by the WEB application server serving as the WEB application platform. The WEB application technology here is a general one such as a CGI program or a Java (registered trademark) servlet. For example, these functions can be realized as a Java (registered trademark) servlet program that operates on the WEB application server Tomcat. The DB 3213 and the trouble ticket DB 3440 can use a DB generally used in a WEB application system, such as a relational database.

  Here, the workflow in the present embodiment will be described with reference to FIG.

  FIG. 2 is a diagram illustrating an example of a process for creating a failure slip in software program development.

  P111, P121, P122, P123, P131, P132, and P141 are states on the workflow. P110, P120, P130, and P140 are phases in which each state is classified according to its property. Here, P110 is an evaluation phase in which a certain system / device / software / process is evaluated and a failure slip is issued. P120 is a failure handling phase in which the occurrence of a failure is confirmed from the contents of the failure vote created in P110 and the failure is corrected. P130 is a handling confirmation phase in which the handling of the fault discovered in P110 and dealt with in P120 is finished and it is confirmed that the same fault does not occur. P140 is set to an end phase in which the failure is dealt with and finished when the confirmation of the failure handling is completed in P130. A workflow holding each state of P110 to P140 and the phases P111 to P141 to which each state belongs is defined as one process P100.

  In the present embodiment, it is assumed that the workflow trouble ticket management system 3411 plays a role in trouble management for managing such trouble tickets and a series of processes P100. The workflow shown in FIG. 2 is one example, and the number, name, and role of each state, phase, and process are changed as necessary. In the present embodiment, work that is assumed to be executed in the evaluation phase P110 to the failure handling phase P120 will be described.

  FIG. 3 is a diagram showing a sequence between nodes when a series of operation events that generally occur in the evaluation phase P110 to the failure handling phase P120 in the WEB application development of FIG. 2 are received.

  The test execution S311, the new trouble slip creation S321, the issuance S331, the debug operation S341, the countermeasure request S351, and the source edit S361 are events that occur in response to a user operation. In the frame of each state (P111, P121, P122), an operation event that the user will normally perform when the trouble ticket is in that state is described. However, the relationship between the state and the operation event shown here is an example, and is not limited to the operation event described. Also, a request to the WEB application of the failure slip management system is given a parameter indicating a failure slip number 3511 (to be described later) by the failure slip number giving means 3413, so that it is always possible to determine which failure slip is related to the event. . However, in the case of creating a new trouble ticket, the trouble ticket number 3511 is not given. Hereinafter, the contents of each event will be described.

  The person in charge of the test performs a test on the test reproduction environment WEB application. The WEB browser 1100 of the client terminal 1000 transmits an operation event performed by the tester to the connection unit 3100 (S311). The connection unit 3100 transfers the received event to the test reproduction environment WEB application (test reproduction environment 3220) (S312).

  When the person in charge of the test finds a failure, the person in charge of the test clicks a new failure ticket creation button 401 on the failure ticket management system menu screen 400 shown in FIG. The WEB browser 1100 transmits a new trouble ticket creation event to the connection unit 3100 (S321). Next, the connection unit 3100 transfers the newly created failure slip event to the failure slip control / management unit 3400 (S322).

  The failure slip control / management unit 3400 assigns a failure slip number 3511 to the newly created failure slip (S323), and creates a failure slip 500 as shown in FIG. Subsequently, using the information (S324) regarding the reproduction environment 3210 generated by the related control unit 3300, the failure card control / management unit 3400 copies the test reproduction environment 3220 to generate the reproduction environment 3210 (S325).

  When the person in charge of the test finishes issuing the trouble ticket, the test person clicks an issue button 508 on the screen on which the trouble card 500 is displayed. The WEB browser 1100 transmits an issuance event to the connection unit 3100 (S331). Next, the connection unit 3100 transfers the issued event to the failure vote control / management unit 3400 (S332). The failure slip control / management unit 3400 changes the state of the failure slip 500 during analysis, and changes the person in charge to the person in charge of analysis. As a result, the failure slip 500 transitions to the failure slip 600.

  The person in charge of analysis performs a debugging operation on the development screen 2000 of FIG. The debug operation refers to all events such as setting a breakpoint and displaying a variable value at the time of a break. Receiving the debug operation event from the WEB browser 1100 (S341), the connection unit 3100 transfers the request to the failure slip control / management unit 3400 (S342). Here, since the parameter indicating the failure slip number 3511 is given to the request by the failure slip number assigning unit 3413, the failure slip control / management unit 3400 can acquire the failure slip number 3511. The failure slip control / management unit 3400 inquires the related control means 3300 about information associated with the failure slip number 3511 and acquires the related information (S344). Further, the failure ticket control / management unit 3400 accesses the reproduction environment 3210 using the acquired related information (S345).

  When the analysis work is finished, the analysis person clicks the countermeasure request button 605 on the screen on which the failure slip 600 is displayed. The WEB browser 1100 transmits a handling request event to the connection unit 3100 (S351), and the connecting unit 3100 transfers the handling event to the failure slip control / management unit 3400 (S352). The failure slip control / management unit 3400 shifts the state of the failure slip 600 to “handling” and changes the person in charge to the person in charge.

  The coping person edits the source code on the development screen 2000 of FIG. When confirming the editing, a save change button 2060 on the development screen 2000 is clicked. The WEB browser 1100 transmits a change saving event to the connection unit 3100 (S351), and the connection unit 3100 transfers the change event to the failure slip control / management unit 3400 (S352).

  The failure slip control / management unit 3400 acquires the failure slip number 3511 from the request, inquires the related control unit 3300 for related information of the failure slip number 3511, and acquires the related information (S363). Subsequently, the failure slip control / management unit 3400 uses the acquired related information to identify the corresponding source file in the reproduction environment 3210 and reflects the edited content (S364).

  FIG. 4 is a diagram showing an example of a menu screen of the trouble ticket management system.

  The failure slip management system menu screen 400 is a menu screen for searching for a new failure slip S321 for the evaluation target or a created failure slip. A new trouble ticket creation button 401 is a button for executing the new trouble slip creation S321. The trouble ticket search button 402 is a button for making a transition to a screen for searching for a trouble card. The trouble slip search function is a general function of the trouble slip workflow system, and the description thereof is omitted here.

  FIG. 5 is a diagram illustrating an example of a failure slip.

  The failure slip 500 is a failure slip in which detailed information related to the failure status generated in the software program, the handling of the failure, and the confirmation of the handling is recorded. Reference numeral 501 denotes a name for identifying a failure vote. In the present embodiment, a name for identifying a failure slip is represented by “Problem” + a unique failure slip number 3511. 502 indicates the current status of the trouble ticket, and 503 indicates that the person in charge is Evaluator. Although 502 and 503 are changed at any time due to the state transition of the trouble slip, 501 is not always changed. In 504 to 506, correspondence to the failure in each state is described. Reference numeral 507 denotes an edit button for switching the trouble slip editing / browsing state. The issue button 508 is a button for executing the state transition of the trouble ticket. Here, since the trouble slip is being created, it is a button for executing the event of issue S331.

  FIG. 6 is a diagram illustrating an example of a failure slip that has transitioned to an in-analysis state.

  The failure slip 600 is the same failure slip transitioned from the failure slip 500 of FIG. Whether or not the trouble slips are the same can be determined by whether or not the names identifying the trouble slips are the same. Reference numeral 601 represents that the status of the failure slip is being analyzed, and reference numeral 602 represents that the person in charge is Analyst.

  The application screen display button 603 is a button for displaying a screen of a reproduction environment WEB application associated with each trouble ticket. The development screen display button 604 is a button for displaying the development screen 2000 of FIG. Reference numeral 605 denotes a handling request button for causing the trouble ticket to transition to the handling state.

  FIG. 7 is a flowchart showing the operation of the connection unit 3100 when receiving a request from the WEB browser 1100.

  The connection unit 3100 receives a request from the WEB browser 1100 of the client terminal 1000 (S701). If the request is a request to the workflow failure slip management system 3411 (YES in S702), the request is transferred to the workflow failure slip management system 3411 (S703). On the other hand, if it is not a request to the workflow failure vote management system 3411 (NO in S702), it is determined whether the request is to the test reproduction environment WEB application (S704). If the request is for the test reproduction environment WEB application (YES in S704), the request is transferred to the test reproduction environment WEB application (S705). If not, the request is transferred to the reproduction environment WEB application associated with each failure slip. (S706).

  FIGS. 8, 9, and 10 are diagrams showing examples of requests to the failure form management system, the test reproduction environment WEB application, and the reproduction environment WEB application associated with the failure form, respectively. Which request is requested can be determined by the URL path pattern. In this embodiment, it can be distinguished by the port number immediately following the host name. For example, the port number “8080” is used in the trouble ticket management system, “8081” is used in the test reproduction environment WEB application, and “8082” and later are set to be used in the reproduction environment WEB application associated with each trouble form. Keep it. In this case, as shown in FIG. 8, it is possible to determine that a request having “8080” after “host name” + “: (colon)” is transferred to the failure slip management system. Similarly, when “8081” is continued, the reproduction environment WEB application for test is continued, and when the number after “8082” is continued, the reproduction environment WEB application associated with each trouble slip is judged and distributed. it can.

  Next, the operation when the reproduction environment 3210 is generated will be described with reference to FIG. Here, for example, tomcat (registered trademark) can be used as the WEB application server 3216.

  FIG. 19 is a diagram illustrating an example of contents stored in the association information storage unit 3500.

  The association information storage unit 3500 stores project name information 3510, port number information 3520, application server activation information 3530, DB information 3540, and final screen information 3550 as association information. The project name information 3510 holds the above-mentioned failure vote number 3511 and the name (3512) of the WEB application server project directory of the reproduction environment 3210. The port number information 3520 holds a failure vote number 3511 and port number information (3521 to 534) necessary for rewriting the WEB application server setting file 3215.

  The application server activation information 3530 holds a failure vote number 3511 and information (3531) indicating whether the WEB application server 3216 of the reproduction environment 3210 is activated or stopped. The DB information 3540 holds a failure vote number 3511 and information (3541, 3542) of the DB 3213 used in the reproduction environment 3210. The final screen information 3550 holds the failure vote number 3511 and the information (3551 to 553) of the source 3214 displayed last on the development screen (FIG. 20). Each of them has the information of the trouble ticket number 3511, and the information of the appropriate reproduction environment 3210 can be specified using the information as a key.

  FIG. 11 is a flowchart showing the operation of the workflow failure slip management system 3411 when a new failure slip creation (S321) request is received.

  The workflow failure slip management system 3411 that has received the request requests the failure slip number assigning unit 3413 to allocate a failure slip number 3511 that is a unique identifier in this failure slip management system (S1101). Then, a new failure slip is created using the failure slip number 3511 (S1102).

  Next, the workflow failure form management system 3411 requests the association control means 3300 to create association information for constructing the reproduction environment 3210 associated with the created failure form (S1103). At this time, the assigned failure vote number 3511 is transmitted, and the association control means 3300 generates necessary information in association with the failure vote number 3511 “001”, and stores this as association information. The failure slip management unit 3410 acquires the generated association information (S1104), and requests the reproduction environment generation unit 3420 to construct the reproduction environment 3210 using the association information (S1105).

  FIG. 12 shows the operation of the association control unit 3300 when receiving a request (S1103) from the workflow failure form management system 3411, generating unique association information for each failure form and storing it in the association information storage unit 3500. It is a flowchart.

  First, the association control unit 3300 determines a project name 3512 from the failure vote number 3511 (S1201) and registers it in the project name information 3510 in the association information storage unit 3500 (S1202). The project name 3512 needs to be determined so as not to be duplicated in the fault card management system. In the example illustrated in FIG. 19, the project name 3512 is set to “tomcat” + “failure vote number 3511” by utilizing the unique failure vote number 3511. Of course, the project name 3512 may be used by using the failure card number 3511 as it is. As described above, the information whose unique value is always determined from the failure vote number 3511 may not be stored in the storage medium as long as the rule definition is prepared. Also, the project name 3512 may be created using an algorithm that determines some unique value without using the failure slip number 3511. In that case, mapping is performed so that the failure slip number 3511 can be uniquely identified. It is necessary to memorize information.

  Next, the association control unit 3300 specifies information to be further registered in the association information storage unit 3500 (S1203). In this embodiment, port number information 3520 and DB information 3540 correspond to this. Next, it is determined whether the information to be registered is port number information 3520 (S1204). If it is port number information 3520 (YES in S1204), an unused port number is specified (S1205), and port number information 3520 is obtained. The port number is registered in (S1206). For example, when the trouble ticket number 3511 is “001” and the information to be registered is Connector port 3521 and the unused port number is 8082, 8082 is registered in the second row and first column of the table of port number information 3520. To do. If the information to be registered is not the port number information 3520 (NO in S1204), information is generated from the failure vote number 3511 (S1207), and the generated information is registered (S1208). For example, in the case of the connection ID 3541 of the DB information 3540, “dbid” + “failure vote number 3511” is registered in the association information storage unit 3500. S1203 to S1208 are repeated until all information to be registered is registered (S1209).

  FIG. 13 shows the operation of the association control unit 3300 that receives the request (S1104) from the workflow failure form management system 3411 and acquires information on the reproduction environment 3210 associated with the failure form created from the association information storage unit 3500. It is a flowchart.

  The association control unit 3300 obtains the failure vote number 3511 to be acquired (S1301), accesses the association information storage unit 3500, and acquires the corresponding association information using the failure vote number 3511 as a key (S1302).

  FIG. 14 is a flowchart showing the operation of the reproduction environment generation unit 3420 when receiving a request (S1106) from the workflow failure form management system 3411 and generating the reproduction environment 3210 associated with the failure form.

  First, a procedure in which the reproduction environment duplicating unit 3421 creates a new reproduction environment 3210 by copying the test reproduction environment 3220 will be described. First, the reproduction environment duplicating unit 3421 acquires the project name 3512 from the project name information 3510, and specifies the location (project directory generation destination) where the project is generated (S1401). For example, when the project name 3512 is tomcat001, the directory location for generating the project directory is set to “C: \ tools \ Apache Group”. As a result, “C: \ tools \ Apache Group \ tomcat001” can be specified as the project directory generation destination. Then, the test project directory is specified (S1402) and the copy is executed (S1403). The storage location of the project directory and information on the project directory for testing (project directory name, DB information, etc.) may be held as unique values by the reproduction environment duplicating means 3421 or may be managed separately.

  Next, the reproduction environment duplication unit 3421 copies the current state of the DB 3223 of the test reproduction environment 3220. First, the reproduction environment copying unit 3421 connects to the DB 3223 of the test reproduction environment 3220 and exports the current state. For example, when using an Oracle relational database product, if the connection ID of the DB 3223 of the test reproduction environment 3220 is “dbidtest”, “exp owner = dbidtest” is executed. This allows you to export the current state to an EXPDAT.DMP file.

  Next, the reproduction environment duplicating unit 3421 obtains a connection ID 3541 and a password 3542 for connecting to the DB 3213 of the reproduction environment 3210 from the DB information 3540 (S1404), and registers them in the DB 3213 of the reproduction environment 3210 for connection. (S1405). Then, EXPDAT. Exported earlier. Import the DMP file by executing “imp dbid001” (when the connection ID 3541 is “001”).

  The setting file rewriting unit 3422 rewrites information of setting files (WEB application server setting file 3215 and DB connection setting file 3211) necessary for operating each reproduction environment 3210 to a value suitable for each reproduction environment 3210. First, setting file rewrite information is specified (S1407). In this embodiment, it is assumed that the rewrite information of the WEB application server setting file 3215 is determined by the port number information 3520, and the setting file is rewritten using the information (S1408). The rewrite information of the DB connection setting file 3211 is determined by the DB information 3540.

  FIG. 15 is a diagram showing an example of the WEB application server setting file 3215 before rewriting, and FIG. 16 is a diagram showing an example of the WEB application server setting file 3215 after rewriting. As shown in the figure, it can be seen that the value of each port number has been rewritten. In order to operate a plurality of WEB application servers 3216 in the same machine, duplication of port numbers is not allowed, and this rewriting is necessary. 17 and 18 are diagrams showing examples of the DB connection setting file 3211 before and after rewriting, respectively. The value of “username” on the 5th line and the password on the 6th line are rewritten. As a result, connection to the DB 3213 prepared for each reproduction environment 3210 becomes possible.

  Returning to FIG. 14, when the setting file rewriting unit 3422 rewrites all setting files (S1409), the application server activation unit 3423 activates the WEB application server 3216 of the reproduction environment 3210 (S1407). Then, the activation status 3531 of the application server activation information 3530 is activated.

  FIG. 20 is a diagram showing an example of a development screen for operating the reproduction environment 3210.

  The development screen 2000 is displayed when the development screen display button 604 on the screen on which the failure slip 600 is displayed is clicked. For the reproduction environment 3210 associated with the failure slip 600, a debugging operation or This is a screen for performing source code editing operations. Reference numeral 2010 denotes a button group for instructing the WEB application server 3216, and includes a start button 2011 and a stop button 2012. Reference numeral 2020 denotes a group of buttons for executing instructions related to the debug operation, and includes a step-in button 2021, a step-over button 2022, and a step return button 2023. Reference numeral 2030 denotes a stack trace view that displays stack trace information of a WEB application. Reference numeral 2040 denotes a variable view that displays a variable value at a break point. A directory view 2080 displays the directory structure of the source 3214, and an editor view 2050 displays the file specified there. The save changes button 2060 is a button for saving the contents edited in the editor view 2050 in the reproduction environment 3210. Reference numeral 2070 denotes a console view that displays log information related to the WEB application server 3216.

  FIG. 21 is a diagram illustrating an example of a URL for requesting display of the development screen 2000.

  When the user clicks on the development screen display button 604 on the screen on which the failure slip 600 is displayed, the URL request shown in the figure is transmitted from the WEB browser 1100 to the workflow failure slip management system 3411 via the connection unit 3100. The The workflow failure slip management system 3411 that has received this request displays the development screen 2000. Here, the parameter “id = 001” indicates the failure slip number 3511 and is assigned by the failure slip number assigning means 3413. Further, the failure slip number assigning unit 3413 assigns a parameter indicating such a failure slip number 3511 to all events that occur on the development screen 2000. Therefore, it is possible to determine the failure vote number 3511 from the request, and use it to make an inquiry to the related control means 3300.

  FIG. 22 is a flowchart showing a flow from when the workflow failure slip management system 3411 receives a development screen 2000 display request until the created development screen 2000 is displayed.

  First, the workflow failure vote management system 3411 makes an inquiry to the association control unit 3300 and acquires association information corresponding to the failure vote number 3511 (S2201). Next, the workflow failure slip management system 3411 requests the failure slip display means 3430 to create each button and view constituting the development screen 2000 (S2201 to S2207). Finally, the views 2000 are combined to create a development screen 2000 (S2208).

  FIG. 23 is a flowchart showing the operation of the application server control unit 3433 when a request is received from the workflow trouble ticket management system 3411 (S2202) and a control button is created. The control buttons refer to the button group 2010 that issues a command to the WEB application server 3216 described above and the button group 2020 that issues a command related to the debug operation.

  The application server control means 3433 determines whether the WEB application server 3216 of the corresponding reproduction environment 3210 is activated from the application server activation information 3530 (S2031). If it is activated, the application server control unit 3433 disables the activation button 2011 from being pressed (S2302). Then, the stop button 2012, the step-in button 2021, the step-over button 2022, and the step return button 2023 can be pressed (S2303).

  On the other hand, when the WEB application server 3216 is in the stopped state in S2301, the application server control unit 3433 enables the start button 2011 to be pressed (S2304). Then, the stop button 2012, the step-in button 2021, the step over button 2022, and the step return button 2023 are disabled (S2305).

  FIG. 24 is a flowchart showing the operation of the editor control unit 3432 when receiving a request from the workflow failure vote management system 3411 (S2203) and generating the directory view 2080.

  The editor control unit 3432 identifies the location of the source directory based on the project name information 3510 (S2401). As in the case where the project directory generation location is specified (S1402), a template is prepared for the path to the source directory of the reproduction environment 3210, and the location can be specified by applying the project name 3512. It is. For example, template information “C: \ tools \ Apache Group \ tomcat000 \ webapps \ ROOT \ WEB-INF \ src” is stored, and the tomcat000 part is applied to the corresponding project name 3512. With this process, the location of the source directory can be specified.

  Next, the editor control unit 3432 analyzes the hierarchical structure of the source directory of the reproduction environment 3210 (S2402), and generates a tree view (S2403). At this point, no hierarchy is expanded. Thereafter, the expanded directory name 3553 of the final screen information 3550 is acquired, and it is checked whether the value exists (S2404). If the value exists (YES in S2404), the directory is expanded in the tree view (S2505). If no value exists, the state created in S2403 remains.

  FIG. 25 is a flowchart showing the operations of the editor control means 3432 and the debugger control means 3431 when the editor view 2050 is generated in response to a request from the workflow failure vote management system 3411 (S2204).

  First, the editor control unit 3432 determines from the application server activation information 3530 whether or not the WEB application server 3216 of the corresponding reproduction environment 3210 is activated (S2501). If it is activated, it is checked whether or not the debugger control means 3431 is in a break state (S2502 to S2504). For example, when JDB is used for the debugger 3250, the debugger connection port address 3534 of the port number information 3520 is used (S2502). If it is started with “y suspend = n 001”, it can be connected to the VM with “jdb -attach 1234” (S2053). Further, by executing the “where” command, it is possible to determine that the break state is obtained when a value (class name or the number of lines) can be specified, and that no break state can be determined when no value can be specified (S2504). In the break state, the class name and the number of lines are specified by the previous “where” command (S 2505). Based on the information, the file name and the number of lines at which the editor control unit 3432 breaks are specified (S2508), and an editor view 2050 that displays the break lines of the file is generated (S2509). If the WEB application server 3216 is in a stopped state or started but not in a break state (S2504), it is determined whether there is final screen information 3550 (S2506). If there is, the file to be displayed is specified from the information (S2507), and the editor view 2050 is generated (S2509). On the other hand, if there is no final screen information 3550, an empty editor view 2050 without file display is generated (S2509).

  FIG. 26 is a flowchart showing the operation of the debugger control means 3431 when receiving a request from the workflow failure vote management system 3411 (S2205) and generating the stack trace view 2030.

  First, the debugger control unit 3431 determines whether the WEB application server 3216 of the corresponding reproduction environment 3210 is activated from the application server activation information 3530 (S2601). If it is activated, it is further investigated whether or not it is in a break state (S2602 to S2604). If the break is in progress, the stack trace information is specified (S2065), and the stack trace view 2030 for displaying the information is generated (S2606). When the debugger 3250 is JDB, a list of threads currently being executed can be acquired with the “threads” command, and the stack of the current thread can be dumped with the “where” command. The list of currently executing threads here is the name, current state, and index that can be used for other commands. If the WEB application server 3216 is in a stopped state or is activated but not in a break state, an empty stack trace view 2030 is generated (S2606).

  FIG. 27 is a flowchart showing the operation of the debugger control means 3431 when receiving a request from the workflow failure vote management system 3411 (S2206) and generating the variable view 2040.

  First, the debugger control unit 3431 determines from the application server activation information 3530 whether or not the WEB application server 3216 of the corresponding reproduction environment 3210 is activated (S2701). If it is activated, it is further investigated whether or not it is in a break state (S2702 to S2704). If the break is in progress, the variable name and variable value in the break are specified (S2075), and a variable view 2040 for displaying the information is generated (S2706). When JDB is used for the debugger 3250, the current value of each field can be output with the “dump” command. If the WEB application server 3216 is in a stopped state or started but not in a break state, an empty variable view 2040 is generated (S2706).

  FIG. 28 is a flowchart showing the operation of the debugger control means 3431 when a console view 2070 is generated in response to a request from the workflow failure vote management system 3411 (S2207).

  First, the debugger control means 3431 determines whether or not the WEB application server 3216 of the corresponding reproduction environment 3210 is activated from the application server activation information 3530 (S2801). If it is running, the location of the log file of the WEB application server 3216 is specified using the project name information 3510 (S2802), the log file is acquired (S2803), and a console view 2070 that displays the contents is generated. (S2804). If the WEB application server 3216 is in a stopped state, an empty console view is generated (S2804).

  In this way, by associating the failure form with the reproduction environment constructed to deal with a certain failure, it is possible to efficiently take over the reproduction environment itself on the failure form management workflow. In addition, since the reproduction environment is always associated with the failure slip, there is no need to worry about the management load even if there are many reproduction environments.

  Since the reproduction environment is automatically generated for each failure vote, the load on the user to construct the environment can be reduced, and since there is a means for determining the generation destination, it is possible to save the user from having to specify each time. Furthermore, since only the current person in charge of the trouble ticket is allowed to access the reproduction environment associated with the trouble ticket, it is possible to prevent work conflicts among multiple users.

  In addition, since the interface for accessing the reproduction environment associated with the failure slip is provided, the user does not need to be aware of the location of the reproduction environment. There is no need to learn advanced remote control technology. Furthermore, by realizing the interface on the browser, the user can perform development work without being limited to the PC or the work place.

  Further, for example, a state in which a software program started in the debug state is just breaking can be sent to the next person in charge at the same time as the failure vote. In addition, source files that are in the middle of editing can be carried over as they are.

(Second Embodiment)
Next, as a second embodiment of the present invention, a case where the test reproduction environment 3220 dedicated to the test is not provided and the reproduction environment 3210 generated most recently plays the role of the test reproduction environment will be described. That is, the test reproduction environment 3210 is switched at the timing when the reproduction environment 3210 is newly generated. In this case, the reproduction environment 3210 generated by copying is not inherited, but the reproduction environment 3210 itself in which the failure has occurred is inherited in association with the failure slip in a state immediately after the failure has occurred. As a result, all the work including the execution of the test can be performed in one reproduction environment. In addition, about the same component as the said 1st Embodiment, the description is abbreviate | omitted using the same code | symbol. Only differences from the first embodiment will be described below.

  FIG. 29 is a diagram showing a configuration example of a software failure vote management system according to the second embodiment of the present invention.

  The difference from FIG. 1 is that test reproduction environment determination information 3600 and test reproduction environment determination means 3424 are added, and that no test reproduction environment 3220 is provided.

  In FIG. 29, test reproduction environment determination information 3600 stores identification information indicating which reproduction environment 3210 is currently used for testing among a plurality of reproduction environments stored in the reproduction environment information storage unit 3200. The test reproduction environment determination unit 3424 determines the generated reproduction environment 3210 to be used for testing at the timing when a new reproduction environment 3210 is generated, and rewrites the test reproduction environment determination information 3600.

  FIG. 30 is a diagram illustrating a sequence between nodes when a series of operation events is received in the second embodiment.

  The difference from FIG. 3 is that the connection unit 3100 that has received the request for the test execution S311 determines which reproduction environment 3210 is for testing. The other is that a series of failure handling operations for one failure, that is, test execution S311, debugging operation S341, and source editing S361, are performed on one reproduction environment 3210.

  Further, the difference is that the reproduction environment 3210 that is the replication source when the reproduction environment 3210 is newly generated is not dedicated to the test (S3001). FIG. 33 is a diagram showing an example of the test reproduction environment determination information 3600. As shown in FIG. 3300 stores the port number of the reproduction environment 3210 currently used for testing.

  FIG. 31 is a flowchart illustrating the operation of the connection unit 3100 when receiving a request from the WEB browser 1100 according to the second embodiment.

  The difference from FIG. 7 in the first embodiment is that S3101 for acquiring the test reproduction environment port number from the test reproduction environment determination information 3600 and S3102 for replacing the URL are added.

  FIG. 32 is a diagram illustrating a request example to the test reproduction environment WEB application according to the second embodiment. In the second embodiment, it is assumed that a request without a port number is set as a request to a reproduction environment WEB application that plays a role for testing.

  In FIG. 31, the connection unit 3100 that has received the request shown in FIG. 32 determines that the request is for the test reproduction environment WEB application from the path pattern (S704). Next, the connection unit 3100 acquires the test reproduction environment port number from the test reproduction environment determination information 3600 (S3101), and replaces the request with the port number added (FIG. 9) (S3102). And it transfers to the present test reproduction environment WEB application (S705).

  FIG. 34 is a flowchart showing the operation of the test reproduction environment determining means 3424.

  When the reproduction environment 3210 generated most recently is used for testing, S3401 is executed at the end of the flow for generating the reproduction environment 3210 in FIG. 14 (after S1410). That is, after the WEB application server 3216 of the newly generated reproduction environment 3210 is started, the port number is written in the test reproduction environment determination information 3600 (S3401). As a result, the test reproduction environment 3220 can be replaced.

(Third embodiment)
Next, as a third embodiment of the present invention, a case where the test reproduction environment 3220 is provided in the test server 5000 outside the failure slip management server 3000 will be described. In addition, it is assumed that the reproduction environment 3210 is generated by recording reproduction information necessary for reproducing the failure instead of copying the test reproduction environment 3220 when the failure occurs. In this case, the timing for constructing the reproduction environment 3210 can be performed at a timing other than the new failure slip creation S321. In this embodiment, it is assumed that the reproduction environment 3210 is generated when an event of issue S331 occurs. In addition, about the same component as the said 1st Embodiment, the description is abbreviate | omitted using the same code | symbol. Only differences from the first embodiment will be described below.

  FIG. 35 is a diagram showing a configuration example of a software failure vote management system according to the third embodiment of the present invention.

  The difference from FIG. 1 is that a configuration management system server 4000 (configuration management means) is added on the network 200, and a test reproduction environment 3220 is constructed on the test server 5000 outside the failure slip management server 3000. It is a point. Also, reproduction information 3450, reproduction information recording means 3414, and template environment 3260 are newly prepared, and reproduction information acquisition / generation means 3425 is a constituent element of reproduction environment generation means 3420 instead of reproduction environment duplication means 3421. Yes. Here, the configuration management system server 4000 is equipped with a general configuration management system capable of managing a revision number when calling a necessary file or registering data in the repository. An example of the configuration management system is CVS (Concurrent Versions System). The configuration management system server 4000 manages configuration management information for managing the configuration of the source code of the software program, and manages files (sources and the like) of the web application to be evaluated. The reproduction environment information stored in the reproduction environment information storage unit 3200 includes this configuration management information.

  The template environment 3260 has information such as basic software and setting files necessary for generating the reproduction environment 3210 stored in the reproduction environment information storage unit 3200, and is copied as a base of the reproduction environment 3210. The template environment 3260 includes a DB connection setting file 3261, a DB 3263, a WEB application server setting file 3265, and a WEB application server 3266. Each setting file of the template environment 3260 is preliminarily set with machine information and the like of the failure slip management system server. Therefore, when the reproduction environment 3210 is generated, the settings unique to each reproduction environment 3210 are the same as in the first embodiment. You only have to rewrite it.

  FIG. 36 is a diagram illustrating a sequence between nodes when a series of operation events is received in the third embodiment.

  In the failure slip control / management unit 3400, the reproduction information recording unit 3414 records the state of the test reproduction environment 3220 in the reproduction information 3450 (S3601) when a new failure slip is created (S321). Then, at the timing of issue S331, the reproduction environment acquisition / generation unit 3425 generates the reproduction environment 3210 using the reproduction information 3450 (S3602). Here, the reproduction information 3450 may be recorded in the failure form DB 3440 as information of the corresponding failure form.

  FIG. 37 is a diagram showing an example of the reproduction information 3450.

  In the reproduction information 3450, information necessary for generating the reproduction environment 3210 is stored. Reference numeral 3701 denotes the version of the application deployed in the test reproduction environment 3220 at the time when the failure occurs, and 3702 denotes the time when the failure occurs. This information is acquired by the reproduction information recording unit 3414 at the timing of the new trouble slip creation S321 and recorded in the reproduction information 3450 (S3601). The recorded information is used by the reproduction information acquisition / generation unit 3425 when the reproduction environment is generated (in the present embodiment, the timing of issue S331) (S3602).

  The reproduction information acquisition / generation unit 3425 creates a framework for the reproduction environment 3210 by copying the template environment 3260. Then, after acquiring the source for configuring the version 3701 of the application from the configuration management system server 4000, it is compiled and deployed. Subsequently, the state of the DB at the failure occurrence time is exported from the DB 3223 of the test server 5000 and imported to the DB 3213 of the reproduction environment 3210.

(Fourth embodiment)
Next, as a fourth embodiment, a case will be described in which request information at the time of occurrence of a failure is specified from the log information 3227 of the test reproduction environment 3220, and a function of regenerating with contents suitable for the reproduction environment 3210 is added. In addition, about the same component as the said 1st Embodiment, the description is abbreviate | omitted using the same code | symbol. Only differences from the first embodiment will be described below.

  FIG. 38 is a diagram showing a configuration example of a software failure vote management system according to the fourth embodiment of the present invention.

  The difference from FIG. 1 is that phenomenon reproduction request information 3460 and phenomenon reproduction request generation means 3426 are added. The phenomenon reproduction request generation unit 3426 regenerates a request at the time of failure occurrence into a phenomenon reproduction request suitable for the reproduction environment 3210. In the phenomenon reproduction request information 3460, the phenomenon reproduction request generated by the phenomenon reproduction request generation unit 3426 is registered.

  FIG. 39 is a flowchart showing the operation of the phenomenon reproduction request generation unit 3426. The phenomenon reproduction request is generated when the reproduction environment 3210 is generated. Specifically, it is assumed to be performed after S1409 in FIG. 14 described in the first embodiment.

  The phenomenon reproduction request generation unit 3426 specifies the location of the log information 3227 from the project name information 3510 (S3901). Next, the phenomenon reproduction request generation unit 3426 acquires a request when a failure occurs from the log information 3227 (S3902). For example, since the state immediately after the failure has been copied, the latest request is acquired.

  Next, the phenomenon reproduction request generation unit 3426 acquires the port number of the corresponding reproduction environment 3210 from the port number information 3520 (S3903), and generates a phenomenon reproduction request suitable for the reproduction environment from the request at the time of failure occurrence (S3904). ). For example, the request at the time of failure extracted from the log information at the time of failure is “http://abcproject.com:8081/servlet/abc?type=login&cmd=form” shown in FIG. 42, and the port of the reproduction environment 3210 When the number is 8082, the port number portion is rewritten. As a result, “http://abcproject.com:8082/servlet/abc?type=login&cmd=form” is generated. As a result, a request at the time of occurrence of a failure can be transmitted to the corresponding reproduction environment 3210. Finally, the phenomenon reproduction request generation unit 3426 registers the generated phenomenon reproduction request in the phenomenon reproduction request information 3460 (S3905).

  FIG. 40 is a diagram illustrating a sequence between nodes when a series of operation events is received in the fourth embodiment.

  The difference from FIG. 3 described in the first embodiment is that a phenomenon reproduction event S4001 and a request transmission S4002 when a failure occurs are added. When the person in charge of analysis clicks the phenomenon reproduction button 4101 on the screen on which the failure slip 4100 shown in FIG. 41 is displayed, the WEB browser 1100 transmits a phenomenon reproduction event S4001 to the connection unit 3100. The request transmitted here is a request for reproducing the phenomenon at the time of occurrence of the failure recorded in the phenomenon reproduction request information 3460. Upon receiving the phenomenon reproduction event (S4001), the connection unit 3100 transfers it to the WEB application server 3216 of the reproduction environment 3210 associated with the corresponding failure slip 4100 (S4002). As a result, the person in charge of analysis can confirm the phenomenon at the time of failure occurrence by simply clicking the button.

  FIG. 41 is a diagram illustrating an example of the failure slip in the analysis state to which the phenomenon reproduction button 4101 is added.

  When the phenomenon reproduction button 4101 is clicked, a phenomenon reproduction event S4001 occurs, and a failure occurrence request as shown in FIG. 43 is transmitted to the test reproduction environment WEB application associated with the corresponding failure slip 4100 ( S4002).

  FIG. 42 is a diagram illustrating a request example when a failure occurs extracted from the log information 3227 when the failure occurs.

  In FIG. 42, since it is a request to the test reproduction environment WEB application, the port number is 8081. The phenomenon reproduction request generation unit 3426 generates and records a request suitable for the reproduction environment 3210 by rewriting this port number with the port number of the corresponding reproduction environment 3210.

  FIG. 43 is a diagram showing an example of the phenomenon reproduction request information 3460. As shown in FIG.

  When the phenomenon reproduction button 4101 on the screen on which the failure slip 4100 is displayed is pressed, a phenomenon reproduction request 4301 is transmitted to the test reproduction environment WEB application. This makes it possible to easily check the failure phenomenon.

(Fifth embodiment)
Next, a case where each reproduction environment 3210 and the test reproduction environment 3220 use a common WEB application server 3216 will be described as a fifth embodiment. The software failure slip management system according to the fifth embodiment differs from the software failure slip management system in the first embodiment only in the configuration of the reproduction environment information storage means 3200, and the basic sequence such as the sequence between nodes is different. The general operation is the same as that of the first embodiment. About the same component as the said 1st Embodiment, the description is abbreviate | omitted using the same code | symbol. Only differences from the first embodiment will be described below.

  FIG. 44 is a diagram showing a configuration example of a software failure vote management system according to the fifth embodiment of the present invention.

  The difference from FIG. 1 is that the WEB application server 3216 and WEB application server setting file 3215 are not prepared for each reproduction environment 3210 and 3220 in the reproduction environment information storage means 3200, and are configured to be used in common. It is. In this case, it is not necessary to copy from the project directory of the WEB application server 3216, and copying may be performed in units of application directories.

  FIG. 45 is a diagram showing an example of application name information recorded in association with the failure vote number 3511 and the application name 4501. The application name information is managed by the association information storage unit 3500.

  FIG. 46 is a diagram showing an example of a request URL for the reproduction environment WEB application associated with the failure slip in the fifth embodiment.

  In the fifth embodiment, since the same WEB application server 3216 is used, the reproduction environment 3210 cannot be identified by the port number as shown in the first embodiment. Therefore, the URL is identified by including the application name. Specifically, “slash (/)” + “application name” follows the server host name. With this application name, it is possible to sort out which reproduction environment WEB application is a request.

  The object of the present invention is achieved by executing the following processing. That is, a storage medium that records a program code of software that realizes the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus is stored in the storage medium. This is the process of reading the code. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code and the storage medium storing the program code constitute the present invention.

  Moreover, the following can be used as a storage medium for supplying the program code. For example, floppy (registered trademark) disk, hard disk, magneto-optical disk, CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD + RW, magnetic tape, nonvolatile memory card, ROM or the like. Alternatively, the program code may be downloaded via a network.

  Further, the present invention includes a case where the function of the above-described embodiment is realized by executing the program code read by the computer. In addition, an OS (operating system) running on the computer performs part or all of the actual processing based on an instruction of the program code, and the functions of the above-described embodiments are realized by the processing. Is also included.

  Furthermore, a case where the functions of the above-described embodiment are realized by the following processing is also included in the present invention. That is, the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, based on the instruction of the program code, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing.

  Further, the present invention includes a case where the functions of the above-described embodiments are realized by executing the program code read by the computer. In addition, there is a case where the OS running on the computer performs part or all of the actual processing based on the instruction of the program code, and the functions of the above-described embodiments are realized by the processing. In this case, the program is supplied by downloading directly from a storage medium storing the program or from another computer or database (not shown) connected to the Internet, a commercial network, a local area network, or the like.

It is a figure showing an example of composition of a software trouble vote management system concerning a 1st embodiment of the present invention. It is a figure which shows an example of the creation process of the trouble ticket in software program development. It is a figure showing the sequence between each node when the series of operation event which generate | occur | produces in WEB application development of FIG. 2 is received. It is a figure which shows an example of the menu screen of a workflow failure vote management system. It is a figure which shows an example of a failure vote. It is a figure which shows an example of the trouble vote which changed to the in-analysis state. It is the flowchart which showed the operation | movement of the connection means when the request from a WEB browser is received. It is a figure which shows an example of request URL with respect to a workflow failure vote management system. It is a figure which shows an example of request URL with respect to the reproduction environment WEB application for a test. It is a figure which shows an example of request | requirement URL with respect to the reproduction environment WEB application linked | related with the failure slip. It is the flowchart which showed the operation | movement of the workflow trouble ticket management system when the new preparation request of a trouble card is received. It is the flowchart which showed the operation | movement of the related control means when determining and registering information required for reproduction environment production | generation. It is the flowchart which showed the operation | movement of the related control means at the time of acquisition of the correlation information corresponding to a failure vote. It is the flowchart which showed the operation | movement of the reproduction environment production | generation means at the time of reproduction environment production | generation. It is a figure which shows an example of the WEB application server setting file before rewriting. It is a figure which shows an example of the WEB application server setting file after rewriting. It is a figure which shows an example of DB connection setting file before rewriting. It is a figure which shows an example of DB connection setting file after rewriting. It is a figure which shows an example of the content memorize | stored in an association information storage means. It is a figure which shows an example of the screen for development for operating with respect to a reproduction environment. It is a figure which shows an example of URL which requests | requires the display of a development screen. It is a flowchart which shows operation | movement of the workflow failure vote management system at the time of a development screen display. It is a flowchart which shows operation | movement of the application server control means at the time of control button generation. It is a flowchart which shows operation | movement of the editor control means at the time of directory view production | generation. It is a flowchart which shows operation | movement of the debugger control means and editor control means at the time of editor view production | generation. It is a flowchart which shows operation | movement of the debugger control means at the time of stack trace view production | generation. It is a flowchart which shows operation | movement of the debugger control means at the time of variable view production | generation. It is a flowchart which shows operation | movement of the debugger control means at the time of console view production | generation. It is the figure which showed the structural example of the software failure vote management system which concerns on the 2nd Embodiment of this invention. It is a figure which shows the sequence of a system when each operation event in 2nd Embodiment is received. It is a flowchart which shows operation | movement of the connection means at the time of receiving the request in 2nd Embodiment. It is a figure which shows an example of request URL with respect to the test reproduction environment WEB application in 2nd Embodiment. It is a figure which shows an example of the reproduction environment determination information for a test. It is a flowchart which shows operation | movement of the reproduction environment determination means for a test at the time of rewriting of the reproduction environment determination information for a test. It is the figure which showed the example of a structure of the software failure vote management system which concerns on the 3rd Embodiment of this invention. It is a figure which shows the sequence of a system when each operation event in 3rd Embodiment is received. It is a figure which shows an example of reproduction information. It is the figure which showed the structural example of the software failure vote management system which concerns on the 4th Embodiment of this invention. It is a flowchart which shows operation | movement of the phenomenon reproduction request production | generation means at the time of phenomenon reproduction request production | generation. It is a figure which shows the sequence of the system when each operation event in 4th Embodiment is received. It is a figure which shows an example of the failure vote of the state in analysis in 4th Embodiment. It is a figure which shows an example of request URL at the time of failure occurrence in the test reproduction environment. It is a figure which shows an example of phenomenon reproduction request information. It is the figure which showed the example of a structure of the software failure vote management system which concerns on the 5th Embodiment of this invention. It is a figure which shows an example of application name information. It is a figure which shows an example of request | requirement URL with respect to the reproduction environment WEB application linked | related with the failure slip in 5th Embodiment.

Explanation of symbols

1000 Client terminal 3000 Fault card management server 3100 Connection unit 3200 Reproduction environment information storage unit 3210 Reproduction environment 3220 Test reproduction environment 3230 Editor 3240 Compiler 3250 Debugger 3260 Template environment 3300 Related control unit 3400 Fault card control / management unit 3410 Fault card management unit 3420 Reproduction environment generation means 3430 Failure form display means 3440 Failure form DB
3450 Reproduction environment 3460 Phenomenon reproduction request information 3500 Association information storage means 3600 Test reproduction environment determination information

Claims (35)

In a software fault card management system configured with a fault card management server for developing a software program and a client terminal connected to the server via a network,
The failure slip management server is a failure slip management means for managing a failure slip in which information relating to a failure that has occurred in the software program is recorded.
Reproduction environment generation means for generating a reproduction environment for reproducing the obstacle;
Reproduction environment information storage means for storing the generated at least one reproduction environment;
A software fault card management system, comprising: association control means for associating the generated reproduction environment with the fault card. The reproduction environment information storage means stores in advance a test reproduction environment of the software program,
2. The software failure ticket management system according to claim 1, wherein the reproduction environment generation unit generates the reproduction environment by copying the test reproduction environment when the failure ticket is newly created. Among the plurality of reproduction environments stored in the reproduction environment information storage means, test reproduction environment determination information for storing identification information indicating the reproduction environment for testing,
Reproducible environment determination means for determining the reproducible environment newly generated by the reproducible environment generating means for testing and rewriting the reproducible environment determining information for testing, further comprising:
2. The software failure voucher management system according to claim 1, wherein the association control unit associates the reproduction environment determined by the test reproduction environment determination unit with the failure voucher in a state immediately after the occurrence of the failure. Reproduction information recording means for recording reproduction information necessary for generating the reproduction environment at the time of newly creating the failure slip,
2. The software failure vote management system according to claim 1, wherein the reproduction environment generation unit generates the reproduction environment using the recorded reproduction information. A phenomenon reproduction request generating means for regenerating a request at the time of occurrence of the failure into a phenomenon reproduction request suitable for a reproduction environment;
The software failure vote management system according to claim 1, further comprising phenomenon reproduction request information in which the generated phenomenon reproduction request is registered.   6. The software failure ticket management system according to claim 1, wherein software and setting files for operating the reproduction environment are stored in the reproduction environment.   3. The software failure slip management system according to claim 1, wherein the reproduction environment information storage means stores common software and setting files for operating a plurality of the reproduction environments. A fault slip display means for displaying a fault slip managed by the fault slip management means on the client terminal;
The software according to any one of claims 1 to 7, further comprising a person-in-charge management unit that permits access only to a person in charge of the trouble ticket to the reproduction environment associated with the trouble ticket. Fault card management system.   9. The software failure slip management unit according to claim 8, wherein the failure slip display means includes reproduction environment calling means for reproducing the failure based on the reproduction environment information related to the failure slip displayed on the screen. system.   10. The trouble card display means comprises a debugger control means for executing debugging of the software program based on the reproduction environment information associated with the trouble card displayed on the screen. Software fault card management system.   11. The trouble card display means comprises editor control means for executing editing of the software program based on the reproduction environment information associated with the trouble card displayed on the screen. The software failure ticket management system according to any one of the above.   The failure slip display means includes application server control means for setting an application server for executing the software program based on the reproduction environment information associated with the failure slip displayed on the screen. The software failure vote management system according to any one of claims 8 to 11.   The software failure according to claim 6 or 7, wherein the reproduction environment generation means includes reproduction environment duplication means for duplicating the reproduction environment, and setting file rewriting means for rewriting the path and port number of the setting file. Vote management system.   14. The software failure ticket management system according to claim 13, wherein the reproduction environment generation unit associates the reproduction environment generated by the duplication with a failure ticket.   14. The software failure ticket management system according to claim 13, wherein the reproduction environment generation unit associates a reproduction environment of a copy source with a failure ticket.   16. The software trouble ticket management system according to claim 1, wherein the software program includes a WEB application. Configuration management means for managing configuration management information for managing the configuration of the source code of the software program,
5. The software failure vote management system according to claim 4, wherein the reproduction environment information stored by the reproduction environment information storage means includes the configuration management information. In the failure slip management method of a software failure slip management system configured with a failure slip management server for developing a software program and a client terminal connected to the server via a network,
A failure slip management step for managing a failure slip in which information about a failure that has occurred in the software program is recorded;
A reproduction environment generation step for generating a reproduction environment for reproducing the obstacle;
A reproduction environment information storage step of storing the generated at least one reproduction environment in a storage means;
A failure slip management method comprising a related control step of associating the generated reproduction environment with the failure slip. In the reproduction environment information storage step, the reproduction environment for testing the software program is stored in the storage means in advance,
19. The failure ticket management method according to claim 18, wherein the reproduction environment generation step generates the reproduction environment by copying a test reproduction environment stored in the storage unit when the failure ticket is newly created. The reproduction environment newly generated in the reproduction environment generation step is determined to be for testing, and the reproduction for testing stores identification information indicating the reproduction environment for testing among the plurality of reproduction environments stored in the storage unit A test reproduction environment determination step for rewriting the environment determination information is further provided.
19. The failure ticket management method according to claim 18, wherein the related control step associates the reproduction environment determined in the test reproduction environment determination step with the failure ticket in a state immediately after the failure occurs. It further comprises a reproduction information recording step for recording reproduction information necessary for generating the reproduction environment at the time of newly creating the failure slip,
19. The failure vote management method according to claim 18, wherein the reproduction environment generation step generates the reproduction environment using the recorded reproduction information.   19. A phenomenon reproduction request generation step of regenerating the request at the time of occurrence of the failure into a phenomenon reproduction request suitable for a reproduction environment, and registering the phenomenon reproduction request as phenomenon reproduction request information. 19. The trouble ticket management method according to 19.   23. The failure ticket management method according to claim 18, wherein software and a setting file for operating the reproduction environment are stored in the reproduction environment.   20. The trouble card management method according to claim 18, wherein the storage means stores common software and setting files for operating a plurality of reproduction environments. A failure slip display step for displaying the failure slip managed in the failure slip management step on the client terminal;
The failure according to any one of claims 18 to 24, further comprising: a person-in-charge management process for permitting access only to the person in charge of the trouble ticket to the reproduction environment associated with the trouble ticket. Vote management method.   26. The failure slip management method according to claim 25, wherein the failure slip display step includes a reproduction environment calling step for reproducing the failure based on the reproduction environment information associated with the failure slip displayed on the screen. .   27. The failure chart display step comprises a debugger control step of executing debugging of the software program based on the reproduction environment information associated with the failure chart displayed on the screen. Failure card management method.   28. The editor according to claim 25, wherein the failure slip display step includes an editor control step of executing editing of the software program based on the reproduction environment information associated with the failure slip displayed on the screen. The fault card management method according to any one of the above items.   The failure slip display step includes an application server control step of setting an application server for executing the software program based on the reproduction environment information associated with the failure slip displayed on the screen. The failure slip management method according to any one of claims 25 to 28.   25. The failure vote according to claim 23, wherein the reproduction environment generation step includes a reproduction environment duplication step of duplicating the reproduction environment, and a setting file rewriting step of rewriting a path and port number of the setting file. Management method.   31. The failure form management method according to claim 30, wherein the reproduction environment generation step associates the reproduction environment generated by the duplication with a failure form.   31. The failure ticket management method according to claim 30, wherein the reproduction environment generation step associates a reproduction environment of a copy source with a failure ticket.   33. The failure ticket management method according to claim 18, wherein the software program includes a WEB application. A configuration management step for managing configuration management information for managing the configuration of the source code of the software program;
22. The failure vote management method according to claim 21, wherein the reproduction environment information stored in the storage means includes the configuration management information.   35. A computer-readable program for causing a computer to execute the failure ticket management method according to claim 18.

Images