JPH05233234A - Release processing system for software package - Google Patents

Abstract

PURPOSE:To prevent the omission of parts at the time of checking a change request and to prevent consistency between parts from being lost by holding the mutual relation of constitutional parts for a software package. CONSTITUTION:When a change request is generated, an object to be changed is checked. Namely a constitutional parts registering part 1-2 judges and registers new parts or not and a constitutional parts relation managing part 1-4 defines relation between existing parts and new parts and stores the defined relation in an external storage device 1-5. Whether the data of all parts based upon the change request have been inputted or not is judged. Then a changed object output/edition part 1-7 is driven and the registered changed parts and all parts relating to them are outputted to an output device 1-11. After completing the registration of all the changed parts, a release application part 1-9 is functioned to check whether the change request is to be released or not, check the existence of another change request and output the checked results to the output device 1-11.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software package release processing method for large-scale software consisting of a large number of components.

[0002]

2. Description of the Related Art A conventional technique will be described with reference to the processing procedure shown in FIG.

Conventionally, when a change request is made, the change target is first identified, and then the identified component is modified to comprehensively perform a function confirmation test and a degradation test. When a series of tests are completed, a list of changed properties is created from the components that were identified earlier and the components that were newly discovered during the test period, and the last update date and revision of the component were investigated and added to the list of changed properties. Was. Furthermore, based on this list of changed properties, a release application form was created and incorporated into the production system.

[0004]

In the above-mentioned conventional technique, the property to be changed out remains to be left out to the worker in charge of the change request, and there is a method other than finding out the part leaked out from the test in the test. There wasn't. Therefore, there is a problem that a backtracking man-hour such as identifying and modifying the changed property occurs during the test process.

Further, since an application is issued for each change request at the time of release, if the same part is modified by different change requests, one change request is completed but another change is completed. Regarding the requirement, there is a problem that only specific parts are advanced and the consistency between the parts is impaired.

[0006]

A software package release processing method according to the present invention comprises an input / output device for inputting and displaying component data of a software package, component data to be changed by customization, and release application data, and an input / output device. The component registration unit that registers the component input from the device, the component relationship management unit that manages the inclusion relation between the registered components, the external storage device that stores the component and the relationship between them, and the customization A change request registration unit that registers the change target parts, a change target property output editing unit for outputting the change requested parts and all related parts, and a change completion registering that the change target properties have been completed Registration department, release application registration department to incorporate change request into operating system, release to inquire about release availability It is characterized in that it comprises a release application output editing unit that outputs a confirmation, and an output device for printing the data after the output editing.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

(Structure) FIG. 1 shows a functional structure of the present invention.

In the figure, 1-1 is an input / output device, 1-2 is a component registration unit, 1-3 is a component storage unit, 1-4 is a component relationship management unit, 1-5 is an external storage device, 1-6 is a change request registration unit, 1-7 is a change target property output editing unit, 1-8 is a change completion registration unit, 1-9 is a release application registration unit, 1-1.
Reference numeral 0 represents a release application output editing unit, and 1-11 represents an output device.

(Function) The input / output device 1-1 is composed of a keyboard and a display, and displays each data of component registration, change request registration, release application, display of input data, and inquiry data of registration result.

The component registration unit 1-2 checks the duplication of the component name input from the keyboard and the omission of input of essential input items.

The component storage unit 1-3 edits the data delivered from the component registration unit 1-2 into a predetermined record format and stores it in the external storage device 1-5 together with other components.

The component relation management unit 1-4 manages the quoting relation between components such as the relation between the program source and the copy phrase, and stores the management information in the external storage device 1-5.

The external storage device 1-5 comprises a component management unit 1
-3 and the information created by the component relation management unit 1-4.

The change request registering unit 1-6 collects the change target parts identified based on the change request generated by the customization of the package as one management group and transfers them to the component storing unit 1-3, and also makes the change request. Assign a management number to each unit.

The change target property output editing unit 1-7 searches for the change target property based on the change request management number, and further searches for the parts in which the correction occurs consequentially from the component part relationship management unit 1-4. And edit it in a format to be output to the output device 1-11.

The change completion registration unit 1-8 checks the validity of the input from the change request management number and the correction completed component input from the keyboard, and if it is valid, the component storage unit 1-8.
Pass the completion data to 3.

The release application unit 1-9 checks whether all the change target parts are registered as completed from the change request management number of the release request, and when all the parts are under completion, the parts under this change request management number are checked. Check if it overlaps with another change request in process.

The release application output editing unit 1-10 outputs a list of parts to be changed whose change request management numbers have passed all checks in the release application unit 1-9 to the output device 1-11.
Edit the image for output to.

The output device 1-11 outputs the print data passed from the change target property output editing unit 1-7 and the release application output editing unit 1-10.

(Operation) Next, the operation of this embodiment will be described based on the functional block diagram of FIG. 1 and the processing procedure of FIG.

When a change request is issued in step 2-1,
In order to satisfy the applicable requirements, the property to be changed in step 2-2 is identified. Next, data is input from the input / output device 1-1 by direct modification component registration in step 2-3, and the modification request registration unit 1-6 is activated.

In step 2-4, it is judged whether or not the registration data is a newly created part, and if it is a new part, step 2
At -5, the component registration 1-2 is activated to register a new component. In step 2-6, following the component registration 2-5, the component relationship management unit 1-4 functions to define the relationship between the existing component and the new component. These data are stored in the external storage device 1-5 after the registration validity check is completed. In step 2-7, it is judged whether or not the data of all the parts based on the change request are input, and if there are unregistered parts, the processing from step 2-3 is repeated.

After the registration of all parts is completed, the next step 2-8
Then, the change target property output editing unit 1-7 is operated to print the changed parts registered in the data and the changed parts that have a ripple effect on the output device 1-11. When the change as the actual work and the test are completed in Step 2-9, Step 2-
At 10, the change completion unit 2-8 is operated, and the input / output device 1-
The change completed parts data is sequentially input from 1. Next, when registration of all completed parts is completed in step 2-11, the release application part 1-9 is made to function in step 2-12 to check whether or not the corresponding change request can be released. In this check, as shown in step 2-13, even if the component of the corresponding change request is being modified by another change request or the modification is completed, another change request is a partial release of some parts and is not released. Check if a match occurs.

If a problem occurs as a result of the check,
In step 2-14, the release application unit 1-9 creates correction management information about the relevant part, and outputs it to the output device 1-11 via the release application output editing unit 1-10.

Based on this output result, the change request in process is completed from step 2-9. If the check in the release application section 1-9 is normal, the release application form shown in step 2-15 is the release application output editing section 1-1.
0 is operated to output from the output device 1-11.

[0027]

As described above, according to the present invention, since the mutual relation of the components of the software package is maintained, the components secondarily generated when the change request is identified can be found without omission. The effect is that there is no backtracking in the process.

Furthermore, since the change status of the component parts is managed, incomplete release of a certain change request, which causes inconsistency of the entire software package, can be prevented.

[Brief description of drawings]

FIG. 1 illustrates the structure and function of the present invention.

FIG. 2 shows a processing procedure of the present invention.

FIG. 3 shows a processing procedure of a conventional technique.

[Explanation of symbols]

 1-1 Input / output device 1-2 Component registration unit 1-3 Component storage unit 1-4 Component relationship management unit 1-5 External storage device 1-6 Change request registration unit 1-7 Change target property output editing unit 1-8 Change completion registration section 1-9 Release application registration section 1-10 Release application output editing section 1-11 Output device

Claims (1)

[Claims] 1. An input / output device for inputting and displaying component data of a software package, component data to be changed by customization, and release application data, and a component registration unit for registering the component input from the input / output device. , A component relationship management unit that manages the inclusive relation between registered components, an external storage device that stores the components and their relationships, a change request registration unit that registers the change target component by customization, and a change request. Changed parts output editor to output all related parts and parts, a change completion register to register that the properties to be changed are completed, and a release application to incorporate the change request into the operating system. Registration section, release application output editing section that outputs release application to ask whether release is possible, and data after output editing A release processing method for a software package, which is provided with an output device for printing the.