JP2003345592A - Software product managing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that it is impossible to manage software product information such as program information or specifications from a change request side, or that it is impossible to manage the condition of a change request. <P>SOLUTION: This software product managing system is provided with a registering part 21 for inputting the designation and version information of software product information to be changed and the designation of a change request from an input device 10 to generate change request information, a change request managing part 31 for storing the change request information, and an editing part 22 for inputting the change request information from the change request managing part 31, and for acquiring the software product information from a software product storing part 32 by using the designation and version information of the software product information included in the change request information to execute the change request, and for, at completing the change request with respect to all the software product information included in the change request information, setting the executing condition information of the change request as the completion of execution. <P>COPYRIGHT: (C)2004,JPO

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a software configuration management device for managing software development products such as source programs and specifications.

[0002]

2. Description of the Related Art A software system which performs a predetermined function by being incorporated in a general-purpose computer or an information home appliance generally includes a plurality of source programs, and each source program is described in a predetermined programming language. At the time of execution, the source program is converted into an executable object format and executed.
In the development of software systems that fulfill certain functions, it is widely practiced to apply the same kind of software to different models with slightly different functions. For this reason, many versions are created during the software development process. When a change needs to be made to the software due to a specification change, a defect correction, or the like, a change request is transmitted to a developer in charge of a source program or the like that requires the change, and the change operation is performed. In general, changes made to software often involve a plurality of specifications and source programs, and if the changes among a plurality of objects to be changed are not synchronized, a problem may occur in the software. For example, if there are three objects to be changed in one change request and only two of them are correctly registered, but the other one is not correctly registered, a problem occurs in the software. To ensure software configuration management without inconsistencies between changed versions, not only manage individual versions, but also associate source program and specification versions from the change request side. Need to be managed. Conventionally, as a technology for managing such a number of versions of a software product, Japanese Patent Laid-Open No. 7-23977 is disclosed.
There are six. FIG. 12 is a diagram showing an example of a system block diagram of a software system management device disclosed in JP-A-7-239776. FIG. 13 is a diagram showing an example of the contents of the configuration specification information section 921 of JP-A-7-239776. FIG.
Is the revision management information section 9 of JP-A-7-239776.
FIG. 22 is a diagram showing an example of the contents of No. 22. JP-A-7-239776
According to the invention, when a new software system is released, an operator uses a keyboard 94 and a flexible (floppy (registered trademark)) disk 96 to output the system name and system revision of the software system to be released, and the software system. The registration data including the specification name and specification / revision of the specification corresponding one-to-one with the source program constituting the above and the contents of the specification are input to the management device 91. Thereby, the management device 91 starts the data registration unit 911. The activated data registration unit 911 stores the system name and the system revision for each release destination, and the specification name and the specification / revision for each system revision, as shown in FIG. register. As shown in FIG. 14, the name of the specification, all existing specifications / revisions, and the contents of the specification are registered in the revision management information section 922 for each specification. The data reference means 912
According to a data reference request from an input device such as a keyboard 94, the configuration specification information section 921 and the revision management information section 92
2 is output to the display device 93, and the specification name of the two software systems, the difference between the specification and the revision, or the content of the specification is additionally output to the display device 93 from the input device. As described above, the invention of Japanese Patent Application Laid-Open No. 7-239776
There is disclosed a technology for managing software from a specification corresponding to one-to-one. For this reason, Japanese Patent Application Laid-Open No. 7-2397
It is considered that the invention of 76 does not manage the software development product from the side of the change request. Japanese Patent Application Laid-Open No. 9-212352 discloses a program development support system for integrally managing various kinds of information (resource information) used for program creation and program document creation when developing a computer program. . The invention of Japanese Patent Application Laid-Open No. 9-212352 discloses a storage unit for storing program development information, a generation unit for creating attribute information of the program development information and related information between the program development information, and a program development information generated by the generation unit. Means for assigning a unique number to the resource and managing the attribute information and the related information as one resource for program development, and system component means for generating a system component from the resource using the related information. It is provided with.

[0003]

The above-mentioned invention for managing the conventional software development product has the following problems. 1. There is no standard way to integrate specifications and software programs. For this reason, the location of the specification corresponding to the specific version of the source program cannot be determined. 2. Even if the source program is revised for bug fixes or specification changes, the corresponding specification documents may not be completely revised. For this reason, the change information between the specification and each version of the software program becomes inconsistent, and rework is likely to occur at the time of repairing or testing the source program. 3. In the software development process, many change requests are generated in response to defect corrections and specification changes, and many versions of specifications and source programs are generated. When a defect is found in the source program and the repair is performed, a repair history is created. When the specification is changed, the corresponding source program also needs to be changed. In general, one change request often covers not only a single source program or a single specification but also a plurality of managed objects. On the other hand, on the same source program, on the one hand, there is often performed a work of repairing a defect, and on the other hand, adding a function by changing a specification, and merging the added change later. For this reason, the work content is complicated and the execution is likely to be omitted. Even though the defective program has been corrected correctly, an error may occur such as incorrectly including an uncorrected version. 4. Even though individual source programs and specifications are correctly managed, only version control of specific artifacts may take precedence, while other artifacts may be left with the old version. Matching may not be achieved. General-purpose processing can be reused, but since the functions differ little by little depending on the product model, the processing content and file structure will also change slightly accordingly. In order to prevent the wrong version from being mixed into the officially released version, it is necessary to clarify the change items while accumulating the change history at each point in the development process so that reliable management work can be performed.

The present invention has been made to solve such a conventional problem, and an object of the present invention is to make it possible to manage software development products based on a change request.
A software configuration management device is provided.

[0005]

A plurality of program information for each version according to the present invention and a plurality of document information for each version related to the plurality of program information for each version are managed as software product information. A software product storage system that stores the software product information based on the name and version information of the software product information, and a predetermined software stored in the software product storage unit. When the content of the product information changes, the name of the change request of the generated change request, the name of one or more software product information that needs to be changed by the generated change request, and one or more 1 representing each version of software product information
An input device for inputting one or more version information, and execution status information indicating an execution status of a change request with respect to the change request name input from the input device, and from the set execution status information and the input device, A registration unit that generates change request information from the input software product information name, version information, and change request name; a change request management unit that stores the change request information generated by the registration unit; Inputting predetermined change request information from the change request information stored in the section using the change request name, and converting the input change request information into one or more software product information names and one or more version information; Obtain software product information from the software product storage unit based on the above, and execute a change request on the obtained software product information to make a change. When the execution of the change request is completed, the version information of the software product information for which the execution of the change request has been completed is updated, and the version information thus updated is updated as the changed version information, and the change request information is updated. When the execution of the change request is completed for all of one or more pieces of software product information included in the information, the execution state information is reset to the content indicating that the execution of the change request is completed, and And an editing unit for storing the change request information in the change request management unit.

The software product management system according to the present invention further comprises a dependency management unit for managing a dependency between a plurality of pieces of software product information,
The registration unit obtains, from the dependency management unit, the name of another piece of software product information having a dependency relationship with the input software product information using the name of the software product information input from the input device. Then, the name of another acquired software product information is added to the change request information.

Further, the software product management system according to the present invention further comprises a configuration specification management unit for managing version information for each software product information,
The editing unit updates version information managed by the configuration specification management unit with respect to software product information included in the change request information for which execution of the change request has been completed.

Further, in the software product management system according to the present invention, the registration unit may specify whether or not execution of the software product information change request is completed for each name of the software product information. Completion information is generated and added to the change request information, and the editing unit outputs, to the input device, information indicating that execution of a change request is temporarily completed for predetermined software product information of the change request information. And setting the content indicating that the execution of the change request is temporarily completed in the product-specific completion information of the designated software product information.

Also, in the software product management system according to the present invention, when the editing unit inputs the software product information from the software product storage unit, exclusive access control is performed on the input software product information. Is performed.

Further, in the software product management system according to the present invention, the registration unit inputs, from the input device, information instructing to refer to the change request information stored in the change request management unit. Obtain change request information from the change request management unit based on the instructed information,
Rewriting of the acquired change request information is performed, and the rewritten change request information is stored in the change request management unit as new change request information.

Further, in the software product management system according to the present invention, when the editing unit adds the version information managed by the configuration specification management unit, the change request name is stored in association with the version information. Then, the software product management system is further notified by the change request management unit that the execution of the change request has been completed for all of the one or more software product information included in the change request information. In this case, a change request name of software product information is obtained from the configuration specification management unit using all names and version information of one or more software product information included in the change request information, and the obtained change It has a verification unit that verifies the consistency of version information of software product information by comparing request names. That.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 An example of a software product management system according to the present invention will be described with reference to the drawings. FIG. 1 is a block diagram of the software product management system according to the first embodiment. In FIG. 1, an input device 10 includes a keyboard 11 and a mouse 12. The input device 10 is a device for inputting a change request name, a name of a software product, version information of a software product, and the like using a keyboard 11 and a mouse 12 when the content of the software product is changed. is there. Also, when actually executing a change request for a software product, information for designating change request information for which a change request is to be made is input. 20 is a management device,
A registration unit 21 and an editing unit 22 are provided. The registration unit 21 generates change request information based on the change request name, the name of the software product, and the version information input from the input device 10, and registers the change request information in the change request management unit. The editing unit 22 receives the instruction from the input device 10, extracts the change request information registered in the change request management unit, and extracts the actual software result from the name and version information of the software product included in the change request information. The product information is extracted from the software product storage unit, changed, and the version information of the changed software product is updated and stored as a new software product in the software product storage unit. According to the present invention, a program product described in a predetermined programming language or a specification for generating a program is used as a software product. The name of the software product indicates the name of the program information or the specification, or the name of the stored file. Reference numeral 30 denotes a storage device, which includes a change request management unit 31 and a software product storage unit 32. The change request management unit 31 stores the change request information generated by the registration unit 21.
The change request management unit 31 stores change request information using the change request name as a key. For this reason, when acquiring predetermined change request information from the change request management unit 31, it is possible to access the requested change request information by designating the change request name. The software product storage unit 32 stores program information and specifications, which are software products, as a file for each version. The software artifacts stored in the software artifact storage unit 32 are the names of the software artifacts,
Alternatively, it can be accessed by the name of the file. Also, at that time, by specifying the version information, it is possible to access the software product of the specified version. 50 is a display device. The display device 50 displays change request information and displays and edits software products.

FIG. 2 is a flowchart illustrating a procedure from registration of change request information to execution of a change request for a software product, generation and storage of a new software product according to the first embodiment. is there. FIG. 3 is a flowchart illustrating a procedure from the extraction of the change request information to the execution of the change request for the software product information. FIG. 4 is a diagram illustrating an example of the change request information according to the first embodiment. FIG. 5 is a diagram illustrating the change request information after the execution of the change request according to the first embodiment is completed.

An execution procedure of a change request for a software product will be described with reference to FIGS. For example, when a specification change occurs in a system composed of a plurality of programs, the user first investigates the influence range of the specification change. Investigation of the scope of influence refers to specifying program information or specifications that need to be changed in content according to the generated change request. Further, since it is considered that there are a plurality of versions of the program information and the specification, when investigating the influence range, it is also examined at the same time which version needs to be changed. As a result of the investigation, the name (or file name) and the version of the program information and the name of the specification (or the file name) and the version of the program information requiring the change request are described in the “version at the start” in FIG. It is assumed that the name can be specified. For example, "GA001.doc @ main @ 1" in "version at start" indicates the file name and version of the specification. “$ 1” indicates the version, and other information “GA001.d
"oc @ main" indicates the file name of the specification. The user inputs from the input device 10 the name and version information of the software product whose contents need to be changed in response to the generated change request. Further, in order to identify the generated change request, a change request name is input at the same time. Further, if necessary, information describing the details of the change can be input (S1). The registration unit 21 inputs the change request name, the name of the software product, and the version information input from the input device 10 (1 in FIG. 1). When the change request name, the name of the software product, the version information, and the like are input from the input device 10, the change request has not yet been actually performed on the software product, so the registration unit 21 , The “initial state” is set as the execution state information. This corresponds to the “execution state flag” in FIG. When the execution state information is in the initial state, the change request is not executed, so that the version of the software product is the same as the version information input from the input device 10. For this reason, the registration unit 21 sets the version information for the input name of the software product as changed version information. The post-change version information corresponds to the “current version” in FIG. The registration unit 21 generates the change request information 41 as shown in FIG. 4 using the change request name, the execution state information, the name of the software product, the version information of the software product, and the changed version information, The change request information is registered in the change request management unit 31 (S2, 2 in FIG. 1). At this time, the change request information is registered using the change request name as a key. After the change request is registered in the change request management unit 31, the user retrieves the change request information in order to actually execute the change request on the software product (S
3, 3 in FIG. The user specifies a change request name from the input device 10 to retrieve the change request information. The designated change request name is passed to the editing unit 22. In addition,
A user who investigates the range of influence of the generated change request, a user who inputs the name of the change request and the name and version information of the software product to be changed from the input device,
The user who takes out the registered change request information and actually executes the change request on the software product may be the same user or a different user. Also,
After the registration of the change request information, it is possible to execute a change request for an actual software product according to the schedule of the user. When receiving the change request name from the input device 10, the editing unit 22 acquires the change request information of the input change request name from the change request management unit 31. The user executes a change request for all software products included in the acquired change request information (S4, S5). As shown in FIG. 4, when a plurality of software products are changed, the software products may be changed in any order, but the change requests are executed in the order registered in the change request information. This can minimize the omission of the execution of the change request. Further, unless the execution of the change request is completed for at least one or more software products included in the change request information, the execution of the change request for the change request information cannot be completed.

The procedure for executing a change request for each software product included in the change request information will be described with reference to the flowchart of FIG. The editing unit 22 is instructed by the user from the input device 10 for the name and version information of the software product that executes the change request (S10). The editing unit 22 acquires the corresponding software product information from the software product storage unit 32 using the designated software name and version information (S11, FIG. 1).
4). At this time, the editing unit 22 acquires the software product information using the exclusive access control, thereby preventing another user from simultaneously executing a change request for the software product information.
When acquiring the software product information from the software product storage unit 32, the editing unit 22 acquires the software product information in an editable state. This allows the user to execute a change request on the software product information. The user executes a change request for the software product information extracted by the editing unit 22 so as to be editable (S12). Software artifact information
Since the information is displayed on the display device 50, the user updates the software product information by changing the information content or adding the content using the existing editor function. When notified of the completion of the execution of the change request for the software product information by the user, the editing unit 22 writes the software product information that has executed the change request into the software product storage unit 32 (S13, 5 in FIG. 1). ).
The software product information that has performed the change request must be additionally registered in the software product storage unit 32 as software product information different from the software information before the change request is performed. At this time, the name of the software product information to be additionally registered is the same as the name of the software product information before executing the change request, and the version information is increased and additionally registered as another software product information. For example, the name of the software product information "GA001.doc @ main @ 1" in FIG.
After the execution of the change request, “GA001.d
oc @ main @ 2 "is registered. in this way,
The version information is updated from "$ 1" to "$ 2" and registered as another software product information (S1
3). As described above, the editing unit 22 also updates the changed version information of the change request information (S14). Editing part 22
Performs addition to the software product storage unit 32 and also sets changed version information of the change request information. FIG. 5 shows the change request information 40 in which the changed version information is set. In the “current version” of the change request information 40, the name and version information of the software product whose execution of the change request has been completed are set. For example,
Regarding “GA001.doc@main”, the version information was “$ 1” before the execution of the change request.
After the execution of the change request, the version is set to "$ 2". The processes from S10 to S14 are sequentially performed on all the software products included in the change request information. When completing the execution of the change request for all the software artifacts included in the change request information, the editing unit 22 sets the execution state information (execution state flag) to “completed state” (S6). Then, the change request information is written back to the change request management unit 31 (S7).

As described above, by generating change request information for the generated change request and storing the generated change request information in the change request management unit 31, the change request information can be centrally managed. Whether the software product information is actually changed in response to the generated change request can be grasped by checking the execution state information of the change request information. In addition, by simultaneously registering the program information and the specification as one software request subject to the change request for one change request,
For example, it is possible to eliminate inconsistency between related software product information, such as a case where only the program information is changed and the specification is not changed. In addition, by including the version information before the change and the version information after the change in the change request information, it is possible to easily grasp the contents of the change request that caused the version of the software product information to be upgraded. . Further, since the change request information is registered in the change request management unit 31 using the change request name as a key, the name and version information of the software product which has been changed in response to a specific change request can be easily grasped. can do. As a result, by using the software product management system of the present invention for predetermined management of, for example, a business system, it is possible to easily manage and execute a change request generated in the business system.

Embodiment 2 FIG. In the first embodiment, when extracting predetermined software product information from the software product storage unit 32, the editing unit 22 acquires software product information using exclusive access control. However, it is also possible to acquire software product information without using exclusive access control. in this case,
It is conceivable that another user accesses the same software product information at the same timing in an editable state. Therefore, when changing the software product information, the user needs to know by some means whether or not another user is accessing the same software product information in an editable state. If another user is accessing the same software product information in an editable state, it is necessary to perform a process of merging the changed contents of each other to eliminate the conflict with one piece of software product information.

Further, it is assumed that it is possible to acquire software product information acquired in a state where one user can edit the software product information in a state where another user can only refer to the information as in the related art.

Embodiment 3 In the third embodiment, an example will be described in which the storage device 30 of the software product management system includes a dependency management unit and a configuration specification management unit, and the registration unit 21 includes a dependency extraction unit. FIG. 6 is a block diagram of a software product management system according to the third embodiment. The difference between the first embodiment and FIG.
Is provided with the dependency extraction unit 23, and the storage device 30 is provided with the dependency management unit 33 and the configuration specification management unit 34. The dependency management unit 33 stores information for managing the dependency between program information as software products, information for managing the dependency between specifications, and information for managing the relationship between program information and specifications. Things. Also,
The configuration specification management unit 34 stores version information for managing each version of program information and specifications, which are software products. Dependency management unit 3
3 conventionally stores information for managing the relationship between programs, the relationship between programs and specifications, and the relationship between specifications, and the configuration specification management unit 34 stores the software product. Conventionally, there is a system for managing and storing version information of each of programs and specifications. Dependency extraction unit 23
Refers to the dependency management unit 33 based on the name of the software product input by the user from the input device 10 and determines the name of another software product having a dependency with the name of the input software product. The acquired information is displayed on the display device 50 to indicate the name of another software product that has a dependency on the user. By providing the dependency extraction unit 23 and the dependency management unit 33, the user can specify a software product having a wide range of influence without investigating all software products to be requested for change. The dependency extraction unit 23 automatically searches for another software product having a dependency relationship with the specified software product, and can present the search result to the user. Thus, even if the user has a leak in the investigation of the influence range, the leak can be compensated for by the dependency extracting unit 23.

The input of version information for another software product having a dependency extracted by the dependency extraction unit 23 is performed by investigating which version the user makes a change request to and inputting the version information. A method of directly inputting from the device 10 and a configuration specification management unit 34
There is a method of acquiring and setting version information of a software product based on a specific rule from version information of each software product managed by the software. Rules for acquiring version information from the configuration specification management unit 34 are determined in advance such that the latest version information of the software product is acquired.
Get it automatically. Alternatively, by storing the version information and the version information having the dependency in the dependency management unit 33 together with the dependency, the version information is acquired from the dependency management unit 33 together with the name of the software product. You may do it.

Embodiment 4 FIG. In the fourth embodiment, product-specific completion information for setting information indicating that the execution of the change request has been temporarily completed is provided for each software product name in the change request information, and the software product included in the change request information is provided. An example of a software product management system that completes execution of a change request by setting the execution of a change request to be tentatively completed according to an instruction from a user for some software products in the name of the product is described. I do.

FIG. 7 is a diagram showing an example of change request information according to the fourth embodiment. The difference between the change request information 42 of FIG. 7 and the change request information 41 of the first embodiment shown in FIG. 4 is that new product-specific completion information (a temporary completion flag of the change request information 42) is provided for each software product name. ), And
That is, it is possible to set the “temporary completion state” in the execution state information. In the software artifact management system described in the first embodiment, when the execution of the change request is completed for all of the software artifacts listed in the name of the software artifact included in the change request information, the execution state information Is set to “completed state”, the execution of the change request can be completed. For this reason, the change request is executed only for a part of the software products included in the change request information, and the change request is executed for the remaining part of the software products even if the change request is made later. Execution could not be completed. However, when a change request occurs in the system and the response is urgent, only the program information is changed in advance, and the specification corresponding to the changed program information is later changed. Is often performed. In order to deal with such a case, product-specific completion information is provided for each software product name in the change request information. When creating the change request information, the registration unit 21 sets, for example, “0” as an initial value in the product-specific completion information (“temporary completion flag” in FIG. 7) for each software product name (“0”). Is a value indicating that no flag is set). When the user retrieves the change request information registered by the user and actually executes the change request on the software product, the user sets the provisional completion from the name of the software product included in the retrieved change request information. The input device 10 specifies the name of the software product to be executed, and inputs information indicating that the execution of the change request is temporarily completed together with the name of the specified software product. Upon receiving from the input device 10 the information instructing that the execution of the change request is temporarily completed and the name of the software product, the editing unit 22 includes, among the software products included in the change request information, the specified software product. The value of the product-specific completion information of the product name is set to “1”. The product-specific completion information of the software product that has actually executed the change request is set to “0” with the initial value.
When the editing unit 22 is notified of the completion of the execution of the change request from the user from the input device 10, the editing unit 22 sets execution state information (execution state flag). At this time, all the software results included in the change request information are set. If the value of the product-specific completion information for the product name is “0 (initial value)”, “completion state” is set. If “1” is set in at least one product-specific completion information, “temporary completion status” is set in the execution status information. After the setting, the change request information is written back to the change request management unit 31.

As a result, by searching the change request information registered in the change request management unit 31 for change request information in which the execution state information (execution state flag) is set to “temporarily completed state”. It can be confirmed that the execution of the change request has not been completed for some of the software artifacts. This provides a means for easily confirming, for example, even if only the program information is changed in advance and the execution of the change request is not completed for the related specification. Thus, the inconsistency between the program information and the specification can be immediately eliminated.

Embodiment 5 In the fifth embodiment, the change request information stored in the change request management unit 31 is extracted, the contents of the extracted change request information are changed, new change request information is generated, and the change request information is transmitted to the change request management unit 31. A software product management system for registering new change request information will be described.

FIG. 8 is a block diagram of a software product management system according to the fifth embodiment. Embodiment 1
The difference between FIG. 1 and FIG. 8 is that the registration unit 21 includes a reference unit 24. The reference unit 24 receives a reference instruction of change request information from a user from the input device 10. The information instructed by the user is information instructing to refer to the change request information and a change request name to be referred to. Reference unit 24
Extracts the change request information of the designated change request name from the change request management unit 31 (8 in FIG. 8). The acquired change request information is displayed on the display device 50. The user rewrites the content of the displayed change request information, and when the rewrite is completed, instructs registration of the change request information. As for the content of the change request information to be rewritten, at least the change request name is rewritten. Since the change request name is the key of the change request information,
Duplication is not allowed. The reference unit 24 registers the rewritten new change request information in the change request management unit 31 (9 in FIG. 8). When registering new change request information, the reference unit 24 sets the execution state information to “initial state”. For example, when a change request is generated for a change request that has occurred in the past, since the software product to be executed with the change request is often the same, the already registered change request information is used. In this case, the change request information can be set more quickly and accurately than when the change request name, the name of the software product, and the version information are input again.

Embodiment 6 FIG. In the sixth embodiment, when the editing unit 22 is notified that the execution of the change request has been completed for all the software artifacts included in the change request information, it is notified that the execution of the change request has been completed. An example of a software product management system including a verification unit that verifies the consistency of version information for the software product that has been created will be described.

FIG. 9 is a block diagram of a software product management system according to the sixth embodiment. The difference between FIG. 1 and FIG. 9 is that the management device 20 includes a compatibility verification unit 25. In addition, as shown in FIG. 10, the configuration specification management unit 34 stores the name of the change request corresponding to the version information. When adding version information to the configuration specification management unit 34, the editing unit 22 according to the sixth embodiment stores the name of the change request from which the version to be added is generated in association with the version information. By storing the change request name in association with the version information,
It is possible to easily manage which of the generated change requests caused the version to be generated. FIG. 11 is a diagram illustrating the result of verifying the consistency of version information for each software product by the compatibility verification unit 25.

The editing unit 22 activates the compatibility verification unit 25 when notified by the user that the execution of the change request for all the software products included in the change request information is completed. For example, it is assumed that the change request information for which the execution of the change request has been completed is created as shown in FIG. The suitability verification unit 25 acquires the names and version information of the nine pieces of software product information indicated in “current version” from the change request information 40 in FIG. Then, referring to the configuration specification management unit 34 based on the name of the acquired software product, a search is made for version information corresponding to the name of each piece of software product information. From the configuration specification management unit 34. For example, in the change request information 40 of FIG. 5, “GA001.doc @
Software product information with the name of "main"
The version information is “$ 2”. Then, for the software product whose version information is “$ 2”, the change request name is “Cha
nge-Req1. " Change request information 4
0, the change request name is “Change-Req” for the version information indicated in “current version”.
"1" is stored in the configuration specification management unit 34. The compatibility verification unit 25 checks the "current version" of the change request information 40.
FIG. 11 shows an example in which the version information and the name of the change request are extracted from the name of the software product shown in FIG.
Shown in In FIG. 11, 70 indicates the name of the software product, and 71 indicates the version information for the name of each software product. This version information must match the version information indicated in the "current version" of the change request information 40.
Reference numeral 72 denotes a name of a change request stored in the configuration specification management unit 34 corresponding to each version information 71 of the name 70 of the software product. In FIG. 11, version information 7 for each software product name is shown.
1, the same change request name “Change-Req
1 "is stored. For this reason, for the name of each software product, the version information indicated in the “current version” of the change request information 40 and the version information stored in the configuration specification management unit 34 must be consistent. Can be verified. For example, if the user has forgotten to execute the change request for the software name “GA002.doc”, the current version information of the name of the corresponding software product in the change request information 40 includes the version at the start. Information is set. FIG.
According to the change request information 40 of “GA002.doc @
The version information at the start of “¥ main” is “$ 3”. For this reason, the conformity verification unit 25 transmits the configuration specification management unit 3
4, a change request name whose version information is “$ 3” is acquired for the software product having the name “GA002.doc@main”. The change request name whose version information is “$ 3” includes “Change-Re
If “q0” is stored correspondingly, the compatibility verification unit 25
A change request name corresponding to the version information obtained by
The name of the change request for the version information set in the “current version” of the change request information 40 no longer matches. That is, the change request name acquired by the compatibility verification unit 25 is “Change-Req0”, and the change request name of “GA002.doc@main” in the change request information 40 is “Change-Req1”.
It turns out that they do not match. Therefore, the conformity verification unit 2
5 warns the user that the execution of the change request is missing for some software products in the change request information, or that another software product may have been changed by mistake. I do.

The editing unit 22 completes the execution of the change request information when the verification result by the compatibility verification unit 25 is correct. When the verification result is incorrect, the editing unit 22 waits for an instruction from the user for a warning. I do. As described above, by providing the conformity verification unit 25, it is possible to confirm that the execution of the change request has been securely performed for all the software products included in the change request information. For this reason, it is possible to prevent a change request from being missed for the software product registered in the change request information.

[0030]

As described above, the software product management system of the present invention creates change request information for software product information for which a change request has occurred, thereby preventing the execution of a change request for software product information. There is an effect that can be prevented. Further, since the version information is stored for the software product of the change request information, the version information before executing the change request and the version information after executing the change request can be managed. Also, since the change request name is included in the change request information and stored, even if a large number of change requests occur, which software product information is changed for which change request, and what version information corresponds to it. There is an effect that it can be easily managed whether or not there is. Also, since the execution status information is provided in the change request information, the execution status information of the change request information stored in the change request management unit is checked,
There is an effect that it is possible to easily ascertain a case where the change request has already been executed and a case where the change request has not been executed yet. As a result, there is an effect that software configuration management can be reliably performed without inconsistency between versions. Further, there is an effect that the information of the software product and the version information can be managed in association with each other from the change request side. In addition, since program information and specifications, which are software product information, can be registered as change request information, whether or not execution of a change request for specifications as well as program information has been executed or not executed There is an effect that can be managed.

Further, the user may specify only a part of the software product information to be executed to execute the change request generated, but only specify a part of the software product information. Automatically obtain the software product information, and add the obtained software product information to the change request information. For this reason, even when the investigation for determining the change target by the user is omitted, there is an effect that the system can compensate for the omission.

Also, since the configuration specification management unit manages version information for each piece of software product information,
There is an effect that it is possible to easily grasp which version exists in the software product information. Also, when another software product information that has a dependency relationship with the software product information is automatically acquired by the system, the version information existing in the acquired other software product information can be confirmed. It is possible to provide a predetermined rule for automatically determining which version information is to be a target of a change request, and to execute predetermined change information according to the rule.

Product-specific completion information is provided for each name of each software product information in the change request information. As a result, of the software product information included in the change request information, a change request is executed in advance for some software product information, and for the remaining software product information,
It is possible to set as if the execution of the change request was completed. Thus, for example, it is possible to execute the change request in advance of only the program information in the software product information, and to execute the change request later in the specification. Therefore, there is an effect that the execution of the change request can be performed flexibly according to the schedule of the user.

When accessing the software product information, the editing unit performs exclusive access control to access the software product information. Therefore, when one user is accessing predetermined software product information in the editing state, other users can input the software product information only in the reference state. Therefore, for the user who executes the change request,
It is possible to reliably guarantee the contents of the execution result.

Further, the change request information that has already been registered can be taken out and rewritten, and the rewritten change request information can be stored in the change request management unit as new change request information. For this reason, if another change request occurs for the same software product information as the software product information of the change request information that occurred in the past, the registered change request information is registered without entering the software product information again. , It is possible to generate change request information for a new change request simply by rewriting the change request name, the execution state information, and the description of the change request.

Further, the configuration specification management unit stores the change request name in association with the version information, and includes the verification unit, so that all the software product information included in the change request information has the change request. Can be verified by using the change request name. For this reason, it is possible to reliably guarantee the version information of each piece of software product information.

[Brief description of the drawings]

FIG. 1 is a block diagram of a software product management system according to a first embodiment;

FIG. 2 is a flowchart illustrating a procedure from generation of change request information to execution of a change request according to the first embodiment;

FIG. 3 is a flowchart showing a procedure for executing a change request according to the first embodiment;

FIG. 4 is a diagram showing an example of change request information according to the first embodiment.

FIG. 5 is a diagram illustrating change request information after the change request according to the first embodiment is executed.

FIG. 6 is a block diagram of a software product management system according to a third embodiment.

FIG. 7 shows an example of change request information according to the fourth embodiment.

FIG. 8 is a block diagram of a software product management system according to a fifth embodiment.

FIG. 9 is a block diagram of a software product management system according to a sixth embodiment.

FIG. 10 is a diagram showing information stored in a configuration specification management unit according to the sixth embodiment.

FIG. 11 is a diagram illustrating a verification result by a conformity verification unit according to the sixth embodiment.

FIG. 12 is a system configuration block diagram of a conventional example.

FIG. 13 is a diagram showing an example of the contents of a configuration specification information section in a conventional example.

FIG. 14 is a diagram showing an example of the contents of a division management information section of a conventional example.

[Explanation of symbols]

1,2,3,4,5,6,7,8,9,60,61 Information flow, 10 input device, 11 keyboard, 12
Mouse, 20 management device, 21 registration unit, 22 editing unit,
23 Dependency extraction unit, 24 reference unit, 25 compatibility verification unit, 30 storage device, 31 change request management unit, 32 software product storage unit, 33 dependency relationship management unit, 34
Configuration specification management unit, 40, 41, 42 change request information,
50 display device, 70 name of software product, 71
Version information, 72 change request name.

Claims (7)

[Claims] 1. A software product management system for managing, as software product information, a plurality of program information for each version and a plurality of document information for each version related to the plurality of program information for each version, A software product storage unit that stores the software product information based on the name and version information of the software product information; and a change in content of predetermined software product information stored in the software product storage unit. When it occurs, the name of the change request of the generated change request, the name of one or more software product information whose contents need to be changed by the generated change request, and each of the one or more software product information An input to input one or more version information indicating a version The execution status information indicating the execution status of the change request is set for the change request name input from the input device, and the set execution status information and the name and version of the software product information input from the input device A registration unit that generates change request information from the information and the change request name; a change request management unit that stores the change request information generated by the registration unit; and a predetermined request from the change request information stored in the change request management unit. Is input using the change request name, and software is stored in the software product storage unit based on one or more software product information names and one or more version information of the input change request information. Acquires product information, executes a change request on the acquired software product information, and completes the execution of the change request. Updating the version information of the software product information whose execution has been completed and updating the changed version information as the changed version information, and updating one or more pieces of software product information included in the change request information When the execution of the change request is completed for all of the above, the execution state information is reset to the content indicating that the execution of the change request is completed, and the change request information is stored in the change request management unit. A software product management system comprising an editing unit. 2. The software product management system according to claim 2, further comprising a dependency management unit that manages a dependency relationship between a plurality of pieces of software product information, wherein the registration unit includes a software product input from the input device. Obtain the name of another software product information that has a dependency on the software product information input using the name of the information from the dependency management unit, and change the name of the obtained other software product information to the above. 2. The software product management system according to claim 1, wherein the software product management system is added to the request information. 3. The software product management system further comprises a configuration specification management unit that manages version information for each piece of software product information, wherein the editing unit adds to the change request information for which execution of the change request has been completed. 2. The software product management system according to claim 1, wherein version information managed by the configuration specification management unit is updated for the included software product information. 4. The registration unit generates product-specific completion information indicating whether or not execution of a change request for software product information has been completed for each name of the software product information, and stores the completion information in the change request information. In addition, the editing unit inputs, from the input device, information indicating that the execution of the change request is temporarily completed with respect to the predetermined software product information of the change request information. 2. The software product management system according to claim 1, wherein a content indicating that the execution of the change request is temporarily completed is set in the product-specific completion information of the information. 5. An editing unit according to claim 1, wherein said software product information is input from said software product storage unit.
2. The software product management system according to claim 1, wherein exclusive access control is performed on the input software product information. 6. The change unit inputs information instructing to refer to the change request information stored in the change request management unit from the input device, and based on the instructed information, changes the change request. Acquiring the change request information from the management unit, rewriting the acquired change request information, and storing the rewritten change request information as new change request information in the change request management unit. Item 2. The software product management system according to Item 1. 7. The editing unit, when adding version information managed by the configuration specification management unit, stores a change request name in association with the version information, and the software product management system further includes: And when the change request management unit notifies the completion of the execution of the change request for all of the one or more pieces of software product information included in the change request information, the one included in the change request information The software product information change request name is obtained from the above configuration specification management unit using all the names and the version information of the above software product information, and the obtained change request names are compared, and the software product information is obtained. 4. The software product management system according to claim 3, further comprising a verification unit for verifying the consistency of the version information of the software.