JP4484148B2 - SI target file and SI related file management system - Google Patents

Description

  The present invention relates to an executable file or environment setting file that is an SI (system integration) target, and a file management technique such as a source file or a text file related to the SI target file.

  As a conventional technology relating to release management, for example, the one described in Patent Document 1 below is known.

The device described in Patent Document 1 relates to a system management apparatus that links a schedule management function, a property payout / refund function, and a release request function with the branch number assigned for each release phase and creation / addition function as a key. This is because the source code registered in the file release schedule is issued after formulating the release schedule for refurbishing the source, the source code that has been issued is copied from the source master, and development work is performed. A series of processes of copying the source code, refunding the source code, and setting the refunded source code as a release target is automatically performed using the release phase and branch number as a key.
Japanese Patent Laid-Open No. 2002-312169

  However, the technique described in Patent Document 1 is based on the assumption that the source code to be created and modified is determined at the stage of formulating the release schedule, and when a specification change or function addition occurs unexpectedly You have to change the release schedule. In addition, since there is only one branch number assigned to one source code in one phase work, there is a means to associate all the modification contents with the modification file when modifying the same file with multiple modification contents in the same phase. There is a problem of not. In addition, the release file to be extracted is only the source code, and it is impossible to extract the compiled executable file whose operation has been confirmed in the test process after development. Need arises. Furthermore, there is no consideration for the case where a person other than the system administrator performs SI work for the production environment, and mistakes caused by manual intervention when a person with little system understanding performs release work. There is a problem that may occur.

  An object of the present invention is to solve the above-mentioned problems, and in particular, sudden specification changes, function additions, bug countermeasures, and SI implementation phases of SI target files in customer requests after entering the system development process. Even if a change occurs, it is not necessary to change the registered information, and the SI target file extraction work can be performed without manual work, thereby causing an SI leak for the SI target file. In addition, even a person who has little understanding of the system development environment and generated source code has a mechanism that can accurately perform SI work to the production environment, making mistakes in the process from system development work to SI time An object of the present invention is to provide an SI target file management system for the purpose of prevention.

  In order to achieve the above-described object, the present invention provides an SI-related file creation / update work, a file version management work for an SI-related file, additional specification information, and a bug information registration work by using the work management number as a key. It is characterized in that creation / update information, file version management information of SI-related files, additional specification information, and bug information are automatically associated. In addition, work management numbers that must be selected before new creation and update processing of SI-related files are automatically assigned to each line of source code that has been modified (added / changed / deleted) when data is saved after the work is completed. Associate both work management number and source code. Furthermore, after system development, the SI person in charge selects the work management number used during system development on the screen, and automatically extracts the latest version of the SI-related file associated with the selected work management number, Further, a search is made for a path such as a storage location of the SI target file designated in advance, and the SI target file is automatically extracted. In addition, an SI object file checklist describing the extracted SI object file is automatically generated.

  According to the present invention, with respect to creation and update of SI-related files, file version management work of SI-related files, additional specification information and bug information registration work, creation and update information of SI-related files, using the work management number as a key, Since file version management information, additional specification information, and bug information of SI-related files are automatically linked, system developers can always share consistent and accurate information, which occurs due to inconsistencies in management information It is possible to prevent mistakes that occur.

  Also, instead of predetermining the SI schedule and determining the source code for SI before system development, select the SI target function after system development, and select the SI target file associated with the function. Can be extracted, and one SI related file can be managed with multiple work management numbers, so after entering the system development process, sudden specification changes, function additions and bugs in customer requests Even if the countermeasures and the SI implementation phase of the SI target file are changed, it is not necessary to change the registered information, and the work man-hours can be reduced for the file management work that occurs due to the change work or function addition. It is possible to prevent the occurrence of problems due to mistakes during SI.

  Then, by selecting a work management number on the screen, the function of automatically outputting an SI target file whose operation has been confirmed can be obtained without omission with minimum manual work.

  In addition, the function to output the SI target file checklist that describes information about the SI target file enables the system development environment and generated source code to be accurately SI work can be performed to the production environment.

  Hereinafter, an embodiment for carrying out the present invention will be specifically described with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of an SI target file and an SI related file management system according to an embodiment of the present invention. As shown in FIG. 1, the SI target file and SI related file management system includes an information processing / management unit 1, a database 2, and a physical directory 3. The database 2 includes additional specification information and bug information storage area 21, work management information storage area 22, and file version information storage area 23. The physical directory 3 includes directories for storing files of the source master group 31, the difference source group 32, the temporary file group 33 for each person in charge, and the SI target file group 34.

  FIG. 2 is a diagram showing a table configuration in the database 2 and the physical directory 3 in FIG. Additional specification information and bug information table 211 is provided in additional specification information and bug information storage area 21. The work management information storage area 22 includes a work management number table 221, an SI related file table 222, a file management information detail table 223, and a file path information table 224. The file version information storage area 23 is provided with a version information table 231 and a version information history table 232.

  The SI target file is an executable file or environment setting file that is an SI (system integration) target. SI-related files are source files and text files related to SI target files.

  In system development, the person in charge of development develops SI-related files such as several source programs according to the required specifications. An SI target file is generated based on the developed SI related file (for example, the source program is converted into an executable program). When development progresses to a predetermined stage, the administrator extracts the latest SI target file, for example, and performs system integration, thereby constructing a system according to the required specifications.

  By the way, in the development stage, various additional specifications are added and corrections for bug countermeasures occur. In the system of this embodiment, a work management number is assigned to each additional specification information and bug information, and the SI target file and the SI related file are managed by the work management number. For example, when a certain additional specification A is added to a system under development, one work management number is given to the additional specification A, and the developer in charge adds a source program to add the additional specification A. When correction (addition / change / deletion) is performed, the work management number is assigned to the addition / change / deletion portion of the source code for management. Therefore, the developer can recognize at a glance which part in the source program corresponds to which additional specification by referring to this work management number. The same applies to bug information. By referring to the work management number, it is possible to recognize at a glance which part of the source program corresponds to which bug countermeasure.

  When performing SI, for example, it is desired to construct a system that includes additional specification A but not additional specification B, or to construct a system that includes bug countermeasures for bug information C but does not include bug countermeasures for bug information D. There are various demands. In the system of the present embodiment, the above-described work management number can be designated and SI can be instructed, so that a system reflecting the work of an arbitrary work management number can be easily constructed.

  Furthermore, since the SI target file and the SI related file are managed by the above-mentioned work management number, a check list in which the file name, the storage path and the related work management number are easily described for the file designated as the SI target is easily obtained. Can be output. As a result, even a person in charge who has little understanding of the system can easily perform the release work.

  The information processing / management unit 1 will be described in detail with reference to FIGS. 1 and 2. The information processing / management unit 1 includes additional specification information and bug information management function 11, and SI target file and SI related file information management function 12. The additional specification information and bug information management function 11 includes a data editing / display function 111 and a data registration function 112. The data editing / display function 111 is a function for editing information on additional specifications by a customer and bug information generated during a test, and displaying saved data. The data registration function 112 stores the data edited by the data editing / display function 111 in the additional specification information and bug information storage area 21 of the database 2 (specifically, the additional specification information and bug information table 211 shown in FIG. 2), At the same time, a unique work management number associated with the registration of the additional specification information and bug information is stored in the work management information storage area 22 (specifically, the work management number table 221 shown in FIG. 2).

  The SI target file and SI related file information management function 12 includes a data display / edit function 121, a file version information management function 122, a data registration function 123, an SI target file output function 124, and an SI target file checklist output function 125. .

  The data display / editing function 121 automatically creates a document creation / editing / display function equivalent to that of general document creation software for SI-related files, or automatically creates / changes a line that has been added / changed / deleted. Provides a function to display the set work management number. For example, this function 121 is used when a developer in charge creates and edits a source program. The data display / editing function 121 will be described later with reference to FIG.

  The file version information management function 122 provides a function for managing version information of SI-related files such as source programs. Specifically, the file version information management function 122 stores the master file in the source master group 31 when newly registering the master (SI related file) of the source program. In addition, the difference between files generated when checking out a file before modification and when checking in a file after modification is stored in the difference source group 32. Check-out and check-in refer to procedures for starting and ending modification of SI related files. For example, when a certain source program is modified, the master file of the source program is checked out (read out) from the source master group 31 and modified using the data display / editing function 121 described above. Check in (write) to 31. The file version information management function 122 manages the version using the version information table 231 and the version information history table 232 when reading and writing the files of the source master group 31 and the difference source group 32 described above. In order to prevent a person other than the checkout processor from modifying the master file, a predetermined flag is provided in the version information table 231 shown in FIG. 2 of the file version information storage area 23 of the database 2 so that the source file can be checked out. It has a mechanism to turn on the flag and turn it off at check-in. Only those who have officially checked out can modify the master file with this flag turned on, and others cannot access it.

  Further, the file version information management function 122 stores information (file name and the like) of SI-related files such as a newly saved source master in the SI-related file table 222 shown in FIG. Also, association information that associates the work management number in the work management number table 221 with the SI related file name in the SI related file table 222 is stored in the file management information detail table 223.

  The data registration function 123 temporarily registers the source correction information related to the SI target file in the temporary file group 33 for each person in charge in the physical directory 3 without using the file version information registration function.

  The SI target file output function 124 outputs an SI target file corresponding to the SI related file in which the work of the work management number selected on the predetermined screen by the administrator is reflected. The screen for selecting the work management number by the administrator will be described in detail with reference to FIG. When the output of the SI target file is instructed, the SI target file output function 124 extracts the latest version information of the SI related file from the file management information detailed table 223 and the version information history table 232 shown in FIG. Based on the path information about the storage destination of the SI target file registered in the file path information table 224 in FIG. 2 in advance, the executable file that is the SI target is automatically stored in the SI target file group 34 of the physical directory 3. Output to.

  The SI target file check list output function 125 outputs the SI target file check list 4 related to the SI target file output to the SI target file group 34. The SI target file checklist 4 will be described in detail with reference to FIG.

  The data display / edit function 121 will be described in detail with reference to FIG. FIG. 3 shows a state after the completion of correction with the work management number xxx002 on the 4th and 13th lines of the SI related file (source program) saved with the work management number xxx001. In this display example 5, 51 indicates the display of each line of the source code, and 52 indicates the display of the work management number assigned to each line. In a state before the work management number xxx002 is corrected, since the work management number xxx001 is stored, each line of the SI related file (source program) is assigned with the work management number xxx001. Here, it is assumed that the person in charge of development corrects this SI-related file for a certain additional specification or bug countermeasure. At this time, the person in charge of development first declares and opens the SI-related file with work management number xxx002. In the opened state, the work management numbers on the 4th and 13th lines are displayed as xxx001. Here, when the fourth and thirteenth lines are corrected and stored as shown in FIG. 3, work management numbers xxx002 are assigned to these lines, and the state shown in FIG. 3 is obtained. As described above, since the work management number is assigned to each line of the SI related file, it is possible to recognize at a glance which work management number was used for editing each line.

  Next, the SI target file output function 124 will be described in detail. FIG. 4 is an example 6 of a screen displayed when an administrator extracts an SI target file. Since the work management number selection pull-down 61 is displayed by a predetermined operation, the administrator selects a work management number to be extracted from the SI target file from the displayed work management numbers. A plurality of work management numbers can be selected. Selecting a work management number means that an instruction to output an SI target file corresponding to an SI-related file reflecting the additional specification and bug countermeasures corresponding to the work management number is given. Here, it is assumed that the work management numbers xxx01, xxx02, and xxx05 are selected.

  FIG. 5 shows a processing flow when the work management number to be extracted from the SI target file is selected as shown in FIG.

  When a plurality of work management numbers are selected (L1), loop processing (L2) for the selected work management numbers is performed. Among the processes of L2, for one work management number, first, loop processing (L21) is performed for the file to which the work management number is assigned, and the next work management number is searched (L22). When the loop processing (L2) for all work management is completed, the process proceeds to L3. In the process of L21, first, it is determined whether or not the file registered with the selected work management number is the latest version (L211). If it is not the latest version, a check flag is set and stored in the memory on the memory (L214). In the case of the latest version, it is determined whether or not the file has a check flag already set (L212), and if applicable, processing for removing the check flag is executed (L213). Thereafter, the process proceeds to the process of the next file to which the target work management number is allocated (L215), and this process is repeated for the files to which the target work management number is allocated (L21). When the process is repeated up to the last file, the process of L1 is further repeated for the selected work management number (L2). When all the processes corresponding to the selected work management number are completed, it is determined whether there is a file with a check flag finally set (L3), and if it does not exist, the SI target file is output (L4). If the file exists, the version and work management number of the file with the check flag that is close to the latest version is displayed (L5), and if the worker determines that the file is to be output (L6), the target When it is determined that the file is output and not output (L6), the series of operations are canceled and the target file is not output (L7).

  The SI target file output processing by the SI target file output function 124 will be specifically described. FIG. 6 shows Example 7 of the version information table 231. Even if the file names are the same, there is one file entity for each different version. The column of work management number is a work management number included in the file of the version with the file name. For example, xxx01 and xxx05 are described as work management numbers corresponding to the version 2 file of the file name ReleaseServlet2.java, and this file reflects work management numbers xxx01 and xxx05 (that is, the work management number) It means that additional specifications corresponding to the management number and bug countermeasures have been taken). In short, the process of FIG. 5 described above does not include all the work management numbers that are not specified by including at least one of the work management numbers specified as the extraction target with reference to the version information table as shown in FIG. This is a process of extracting a file having a file name and version. When the file with such a file name and version is the latest version, the latest version file is output as an SI target by the processing of L211, L212, L213, L3, and L4. When there are a plurality of files having such file names and versions, the latest version is selected by the system administrator at L5 and L6 and output as an SI target. Note that the latest version may be automatically extracted without causing the system administrator to make a selection like L5 and L6.

  It is assumed that the version information of the SI related file is in the state shown in FIG. 6 and the work management numbers xxx01, xxx02, and xxx05 are selected as SI target file output targets as shown in FIG. In this case, according to the processing flow of FIG. 5, first, SI related files of item numbers 1, 2, 4 to 6, 9, and 10 in FIG. In these item numbers, the latest version of the file includes at least one of the above-described work management numbers xxx01, xxx02, and xxx05, and does not include any other work management number. On the other hand, for the SI-related files of Nos. 3 and 7, the latest version of the file is not subject to extraction (because it includes work management numbers other than the specified work management number), so the system administrator can extract it. Make a decision. In item number 3, since the file of version 3 is the file closest to the latest version, the system administrator is made to determine whether or not to extract this file. In item No. 7, since the file of version 1 is the file closest to the latest version, the system administrator determines whether or not to extract this file. When the system administrator decides the extraction, as a result, the corresponding files of the item numbers 3 and 7 are extracted as the SI related files of the item numbers 1, 2, 4 to 6, 9, and 10 described above. Become.

  For each SI-related file to be extracted, the SI target file search destination path registered in the file path information table 224 of FIG. The target file is read and stored in the SI target file group 34. As a result, the SI target file corresponding to the designated work management number is extracted.

  FIG. 7 shows an example of the SI target file checklist 8 related to the SI target file extracted as described above. The system administrator can output the SI target file checklist 8 describing information corresponding to the SI target file output as described above as shown in FIG. 7 by a predetermined operation. Note that the version information of each SI target file may be included in the list of FIG.

  FIG. 8 shows an outline of the data flow of the SI target file and SI related file management system according to the present embodiment described with reference to FIGS. With reference to FIG. 8, a specific operation example by the system of this embodiment will be described.

  Information such as the master file storage destination path, the difference file storage destination path, and the SI target file output destination path is registered in the file path information table 224 in advance by the file path information registration process (P1). When an additional specification or bug information is generated, the developer or system administrator uses the additional specification information and bug information management function 11 to store the additional specification information and additional specification information in the bug information storage area 21. And stored in the bug information table 211 (P2-1). At this time, a work management number (for example, “xxx01”) corresponding to the additional specification information or bug information is attached, and the work management number is registered as master information in the work management number table 221 of the work management information storage area 22 (P2). -2). The work management number can be assigned in any way, but it is preferable to store the last work management number for each file and automatically assign the next work management number.

  Next, the person in charge of development creates and edits an SI related file corresponding to the work management number. For example, if the work management number corresponds to the additional specification, it means that the source is created / modified for the additional specification, and if the work management number corresponds to the bug information, the bug countermeasure It is to create and modify the source for. Therefore, if a source program is newly added, the file name (SI related file name) of the source program is registered as master information in the SI related file table 222 (P3-1). At this time, information on the work management number (for example, “xxx01”) selected as the work target is acquired from the work management number list registered in the work management number table 221, and the management information of the created SI related file is acquired. Details are registered in the file management information table 223 (P3-2, P3-3). With this file management information table 223, the correspondence between the work management number and the file name can be taken. Further, based on the work management number, the file name of the created SI-related file is registered in the additional specification information and bug information table 211 together with other information such as countermeasure contents (P3-4). Further, the version information is registered in the version information table 231 (P3-5), and at this time, the master file storage destination path and the difference file storage destination path registered in P1 are referred to (P3-6). When modifying an existing source for the work of the work management number instead of adding a new source program, select a source file (SI-related file) to be modified from the SI-related file table 222 ( P3-1), select a work management number to be worked from the work management number table 221, register them in the file management information table 223 and take correspondence (P3-2, P3-3), version information table 231 and additional specification information and bug information table 211 are also updated (P3-4, P3-5, P3-6).

  In the case of creating a new SI-related file, when the developer in charge inputs the source code on the screen as shown in FIG. 3, the work management number selected above is assigned to each line. When modifying an existing SI related file, a screen as shown in FIG. 3 is displayed based on the information in the version information table 231 created here. Specifically, the master file or the merged master file and difference file is displayed as shown in each line display 51, and the work management number (for example, “xxx01”) when created or updated is the work management number for each line. A display 52 is displayed. When the developer in charge adds, changes, or deletes the source code on this screen, the work management number selected above is attached to the corrected portion. When saving a newly created or modified SI-related file, the updated information is newly registered in the version information table 231 based on the version information registered in P3, and the version information history is registered in the version information history table 232 (P4). Based on the information in the version information history table 232 created here, a version information list shown in FIG. 6 is created. During the SI target file checklist output process, the SI target file checklist 4 shown in FIG. 7 is displayed based on the SI target file output destination path information registered in P1 and the work management number and file name referenced from the table 232. Output (P5).

It is a block diagram which shows the structure of the SI object file and SI related file management system which are one Embodiment of this invention. It is explanatory drawing for demonstrating the table | surface which each database hold | maintains, its relation, and the physical directory relevant to the table. It is explanatory drawing for demonstrating the display and edit function of SI related file. It is explanatory drawing for demonstrating the extraction method of SI related file. It is a flowchart which shows the outline | summary of the extraction process of SI related file. It is an example of version management information of an SI related file. It is an example of an SI object file check list. It is explanatory drawing for demonstrating the data flow outline | summary of the SI object file and SI related file management system which are one Embodiment of this invention.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Information processing / management part, 11 ... Additional specification information and bug information management function, 111 ... Data display / edit function, 112 ... Data registration function, 12 ... SI object file and SI related file information management function, 121 ... Data display Editing function, 122 ... File version information management function, 123 ... Data registration function, 124 ... SI target file output function, 125 ... SI target file checklist output function, 2 ... Database, 21 ... Additional specification information and bug management information storage 211, additional specification information and bug information table, 22 ... work management information storage area, 221 ... work management number table, 222 ... SI related file table, 223 ... file management information detail table, 224 ... file path information table, 23 ... file version storage, 231 ... barge Information table, 232 ... version information history table, 3 ... physical directory, 31 ... source master group, 32 ... differential source group, 33 ... temporary file group by person in charge, 34 ... SI target file group, 4 ... SI target file check List, 5 ... SI related file display / edit editor, 51 ... SI related file display / edit section, 52 ... Work management number display section, 6 ... SI management file extraction work management number selection screen, 61 ... SI target file extraction Work management number selection pull-down, 7 ... SI related file version information list (example), 8 ... SI target file check list (example).

Claims (3)

SI target file and SI related file management for managing SI target files such as executable files and environment setting files that are SI (system integration) targets, and SI related files such as source files and text files related to the SI target files A system,
Means for registering additional specification information and bug information;
Means for registering work management numbers for each additional specification information and bug information registered;
When the work management number is selected, an SI related file is added / changed / deleted, and when there is an instruction to save the SI related file after the work is completed, to each line where the addition / change / delete is performed Means for additionally writing the selected work management number;
When the work management number is selected and an SI related file is added / changed / deleted, and when there is an instruction to save the SI related file after the work is completed, the selected work management number, the SI to be saved Means for storing the file name of the related file and the file version information in association with the updated version;
Means for displaying the contents of the SI related file together with the work management number assigned to each line ;
Means for accepting selection of a work management number to be extracted;
Means for extracting the latest version of the SI-related file that includes at least one of the work management numbers selected as the extraction target and does not include the unselected work management number. SI target file and SI related file management system. The SI object file and SI related file management system according to claim 1 , further comprising:
If the SI related file that includes at least one of the work management numbers selected as the extraction target and does not include the unselected work management number is not the latest version, Among the SI target file and the SI, there is provided means for displaying information on a file closest to the latest version, receiving a selection from the displayed file by a system administrator, and extracting the selected file. Associated file management system. In the SI object file and SI related file management system according to claim 1 or 2 ,
Registered when the SI target file corresponding to the extracted SI related file is added / changed / deleted for the SI target file name, the file storage destination path, and the SI related file corresponding to the SI target file An SI object file and SI related file management system comprising means for outputting an SI object file check list in which the work management numbers described are written without omission.

Images