JPH0895776A - Software process management device - Google Patents

Abstract

PURPOSE: To provide the software process management device which can greatly decrease management man-hours and easily maintain the consistency of the operation states and product information of processes by setting the processes in software product generation support tool units and managing their operation states. CONSTITUTION: A process management part 1-1 edits respective pieces of information in a process management file 1-3, containing process names and project names set corresponding to respective use operations of a software product generation support tool group 2-1 and state information showing the operation states of the processes of the respective projects, according to the progress states of the projects, and an alteration management part 1-2 actuates corresponding software product generation support tools according to the state information of the processes to indicate the latest operation.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software process management device, and in particular, it consistently supports software development from upstream processes to downstream processes, and software product information created / updated in the work of a certain process. In the integrated software development support system that cites or refers to the product deliverable information of the software created / updated in the work of the subsequent process, the change synchronization of the product deliverable information of the preceding process and the deliverable product information of the subsequent process The present invention relates to a software process control device having both.

[0002]

2. Description of the Related Art In an integrated software development support system, software product information created / updated in a certain process work is quoted or referenced in software product information created in a subsequent process work. Starts the work of the succeeding process after the work of the preceding process is completed.

When the product information of the preceding process is corrected after the work of the subsequent process is started, the product information of the software created / updated in the work of the preceding process and the software created / updated in the work of the subsequent process There may be inconsistency with the product information in.

As a conventional technique for preventing this contradiction, as shown in Japanese Patent Laid-Open No. 4-326467, state information is provided in the specification which is a logical unit of software product information, and the specification unit is used. There is a change management system that manages the process and guides the work.

In this method, as the status information of the specification, a classification such as "work not possible", "work in progress", and "completion" is set. When the work of a certain process is completed, the state of the specifications created / updated in the process is set to "complete", and the state of the specifications of the subsequent process is changed to "work in progress".

On the contrary, when the work is started or the work is started again in order to correct the specifications created / updated in the work of the completed process, the state of the specifications created / updated in the process Is changed to "work in progress", and the specification state of the subsequent process is changed to "work not possible".

As disclosed in Japanese Patent Laid-Open No. 4-364530, the logical relationship between the specifications of the preceding process and the specifications of the succeeding process is defined in advance in a relation table, and the specifications of the preceding process are updated. If there is a change, there is also a change management method in which the specification of the subsequent process is registered in the change table to detect the specification that needs to be changed and also guide the work to the specification unit.

Furthermore, the IBM SYSTEM JOUR
NAL, vol29, no2, 1990, pp189-
According to 208, there is also a method of storing a work relationship, displaying the work relationship, and guiding the work.

[0009]

In a large-scale system, specifications of thousands to tens of thousands are created, but the conventional software process management shown in the above-mentioned JP-A-4-326467 and 4-364530. The method has a problem that it takes a huge amount of time to set the state information for each specification because the change is managed in specification units.

Furthermore, since the dependency relation of the specification must be defined in advance, there is a problem that the larger the system, the more man-hours are required to manage this dependency relation.

The above-mentioned IBM SYSTEM JO
In the conventional technology seen in URNAL, the operator designates the work based on the displayed process information, so that the operator misunderstands or overlooks it, and a plurality of workers work at the same time. There is a problem in that there may be a contradiction between the deliverable information of the software created / updated in the work of the process to be performed and the deliverable information of the software created / updated in the work of the subsequent process.

Further, since the status information of the specification is used only for change management, there is a problem that the information for the process management function for managing the progress status must be separately registered.

An object of the present invention is to set a process for each software product creation support tool and manage this work state, thereby significantly reducing the management man-hours, the work state of the process, and the work product between processes. An object of the present invention is to provide an efficient software process control device capable of easily maintaining the consistency of information.

[0014]

A software process control apparatus according to the first aspect of the present invention comprises a plurality of software product creation support tools used for software creation, and work for using the software product creation support tools. A process management file that stores the process name of the process, the project name of the project to be managed, and status information indicating the work status of each process of each project, and the new installation of the project and its work. A process management means for editing each information of the process management file according to the progress status, and a software product creation support tool corresponding to the process according to the status information of the process with reference to the process management file. It is configured to include a change management unit that starts up and instructs an update operation.

In the software process management apparatus of the second invention, in the first invention, the process management means uses, as the status information indicating the work status of the process, the unstarted status in which the work of the process is not performed at all. First information indicating, second information indicating that the work of the process is started and not completed yet, and third information indicating that all the work of the process is completed And at least, and the work state information of the subsequent process immediately after the work state information of the preceding process changes from the second information to the third information and the work state information indicates the first information is changed to the second information. When the state information is edited so that it can be changed, and when the preceding step whose state information is already the third information is executed again, the state information of this step is changed from the third information to the second information and the subsequent step All 3 or 2nd information is 1st information It is characterized by editing the state information to change.

[0016]

Embodiments of the present invention will now be described with reference to the drawings.

The software is created through the phases of system analysis, system outline design, system detail design, etc., but an integrated software development support system that consistently supports development from upstream processes to downstream processes. Provides the necessary software deliverable creation support tools that support all phase operations except the manufacturing process.

FIG. 11 shows an example of a software product creation support tool corresponding to each software creation phase. In other words, system structure analysis tools and data analysis tools for system analysis phases, flow design tools for system outline design phases, program design, screen design, file design, record design, form design, table design, system detailed design phase. Pattern design and component design tools are available.

Although the order relation of each phase is predetermined, there is no particular order of the work in each phase, and the tool use order may be defined when the development project is introduced.

The present invention is a software process management device that manages software processes by using the operation of using each tool as a unit process.

FIG. 1 is a block diagram showing an embodiment of the software process control apparatus of the present invention.

The software process management apparatus of FIG. 1 is configured to include a software process management unit 1 and a software deliverable creation support unit 2, and the software process management unit 1 is changed from the process management unit 1-1. The software product creation support unit 2 is composed of a management unit 1-2 and a process management file 1-3.
Is composed of a repository 2-0 and a software deliverable creation support tool group 2-1. The repository 2-0 stores a plurality of specifications 2-0-1.

The process management file 1-3 stores the name of the project to be managed and the status information of each process of the project. Here, each process of the project is set for each operation of using the software deliverable creation support tool.

FIG. 2 shows an example of the process control file 1-3.

In FIG. 2, the process control file 1-3 is provided.
Is project name 1-3-1, process name 1-3-2
And the work status 1-3-3 of each process in each project.

In addition to the above, the actual process management file 1-3 stores general process management information such as manager information, personnel information, schedule management information, scale information and quality information.

In FIG. 2, the project name 1-3-1 is project A, project B and project Z, and the process name 1-3-2 is program outline design process (of the system outline design phase flow design tool of FIG. 11). (Corresponding to use work), screen design process (corresponding to use work of screen design tool of system detail design phase of FIG. 11) and program detailed design process (corresponding to use work of program design tool of system detail design phase of FIG. 11) Etc. are registered.

The work content of each process is a creation / correction work of a specification which is software product information by a corresponding software product creation support tool, and the relationship between the software product creation support tool and the specification is 1 to n (n: 0 or more), and in many cases, n is plural.

In the work status 1-3-3, any one of "completed", "working", "not started", and "no work" is set.

When the work status 1-3-3 is "completed", it indicates that the specification creation / correction work in the relevant process is all completed.

When the working state 1-3-3 is "working",
Indicates that one or more specifications are being created or modified in the relevant process.

When the work state 1-3-3 is "not yet started",
It indicates that the specification has not been created or modified in the relevant process.

When the work state 1-3-3 is "no work",
Indicates that there is no specification corresponding to the applicable process.

The process control section 1-1 includes a process control file 1-
Edit 3. That is, the process control file 1-3
In addition to updating general process control information such as addition, correction and deletion of project information, manager information, personnel information, schedule management information, scale information, quality information,
There is a correction function for work status 1-3-3 related to change management.

When the change management unit 1-2 receives a work request based on the project name, process name, etc., the process management file 1-
The work state of the process corresponding to the request stored in No. 3 is referred to, and the software deliverable creation support tool is activated accordingly.

Software artifact creation support tool group 2-
The software product creation support tool corresponding to each process is stored in 1, and the software product creation support tool corresponding to the process name requested by the change management unit 1-2 is selected. Work such as reference update of the corresponding specifications in the repository 2-0.

Next, the operation of this embodiment will be described.

The manager edits the process management file 1-3 using the process management section 1-1 based on the report from the worker.

The operator designates a project name, a process name, and a specification name, and activates any one of the software deliverable creation support tool group 2-1 by the change management unit 1.
-2 request.

When the worker makes a specification update request, the change management section 1-2 searches the process management file 1-3 and confirms the work status of the process of the project. The work status of the relevant process of the relevant project is "Complete", "
In case of "not started" and "no work", the worker is notified of that fact and the software product creation support tool is not started. The work status of the relevant process of the project is "work in progress". In the case of, since the work can be started, the corresponding software deliverable creation support tool is started in the update mode.

When the worker makes a reference request for specifications, the change management unit 1-2 activates the software deliverable creation support tool in the reference mode regardless of the work state of the process.

Next, the editing operation for correcting the work status 1-3-3 will be described with reference to FIGS.

FIG. 3 is an explanatory diagram showing work states 1-3-3 when a project is newly registered. When a new project is registered, the work status of the process 1-3
-3 is "not yet started".

FIG. 4 is an explanatory diagram when changing the work state 1-3-3 of each process according to the form of the project. After newly registering the project, the manager changes the work status 1-3-3 to "no work" if there is a process with no work. Even if it is found that there is no work while the project is proceeding, the work status 1-3-
Change 3 to "no work".

FIGS. 5 and 6 are explanatory views showing work states 1-3-3 when the work of each process is started.

When starting the work of the process, the manager requests the process management section 1-1 to change the work state 5-2 of the process to "working". The process management section 1-1 confirms that the work state 5-2 of the relevant process is “not started” and that the work state 5-1 of the preceding process of the relevant process is “complete”, Change the working state 5-2 of "to""working". As shown in FIG. 6, the work state 6- of the preceding process
When 2 is "no work", it is confirmed that the work status 6-1 of the preceding process is "complete".

FIG. 7, FIG. 8 and FIG. 9 are explanatory views showing the change of the work state 1-3-3 when the work is completed.

When all specification creation / correction work of the process is completed, the manager changes the work status 7-1 of the process to "complete" as shown in FIG.
Request to 1. The process management section 1-1 confirms that the work state 7-1 of the relevant process is "working", and changes the work state 7-1 of the relevant process to "completed". When the work of the subsequent process is continuously started, the work state 8-1 of the process is set to "complete" and the work state 8-2 of the subsequent process is set to "working" as shown in FIG. change. As shown in FIG. 9, when the work state 9-2 of the subsequent process is "no work", the work state 9-3 of the subsequent process is further "working".
Change to.

FIG. 10 is an explanatory diagram showing a change of the work state 1-3-3 when the work is backtracked due to the detection of an error or the like.

When returning, the working state 10-1 of the returning process is changed to "working", and the state of the processes other than "no work" among all the succeeding processes of the returning process is "not started". Change to ″.

As described above, the software process management apparatus of the present embodiment significantly reduces the management man-hour by setting the process for each software deliverable creation support tool and managing this work state. It is possible to easily maintain the consistency of the work state of the process and the product information between the processes.

[0052]

As described above, in the software process control apparatus of the present invention, conventionally, the change control unit refers to the work status of the process registered by the process control unit, so that it is realized separately. There is an effect that software process management becomes efficient by integrating process management and change management.

Further, since the process control information and the change control information are centrally controlled by the software process control section, the IB
Misunderstandings and oversights of workers seen in M SYSTEM JOURNAL, and multiple workers working at the same time, result information of software created and updated in the work of the preceding process and subsequent processes This has the effect of eliminating the risk of so-called double maintenance by eliminating the possibility of inconsistencies in the product information of software created and updated during work.

Further, by maintaining the consistency of the work states of the continuous processes, it becomes possible to clearly indicate the process requiring the work, and it becomes easy to maintain the consistency of the product information between the continuous processes. There is an effect.

Further, JP-A-4-326467 and JP-A-4-32667
As in -364530, instead of change management based on the dependency relationship of the specification, focusing on the relationship between the specification and the software deliverable creation support tool that supports the update of the specification, the dependency relationship of the tool (= process) corresponding to the specification The change management eliminates the need for managing dependency relationships of specifications of tens to thousands, and does not significantly increase management man-hours even when the system becomes large in scale.

[Brief description of drawings]

FIG. 1 is a configuration diagram showing an embodiment of a software process control device of the present invention.

FIG. 2 is a file content diagram showing the content of a process control file.

FIG. 3 is a work state setting diagram at the time of newly registering a project.

FIG. 4 is a work state setting diagram when there is a process without work.

FIG. 5 is a work state setting diagram at the start of work of a process.

FIG. 6 is a work state setting diagram at the start of work of a process.

FIG. 7 is a work state setting diagram upon completion of work of a process.

FIG. 8 is a work state setting diagram at the time of starting work of a subsequent process when work of a process is completed.

FIG. 9 is a work state setting diagram at the time of starting work of a subsequent process when work of a process is completed.

FIG. 10 is a work state setting diagram when the work returns.

FIG. 11 is a use tool diagram corresponding to phases showing an example of a software deliverable creation support tool used for software development phases.

[Explanation of symbols]

1 Software Process Management Department 1-1 Process Management Department 1-2 Change Management Department 1-3 Process Management File 1-3-1 Project Name 1-3-2 Process Name 1-3-3, 4-1, 5- 1, 5-2, 6-1, 6-
2, 6-3, 7-1, 8-1, 8-2, 9-1, 9-
2, 9-3, 10-1, 10-2 Work status 2 Software artifact creation support unit 2-0 Repository 2-0-1 Specifications 2-1 Software artifact creation support tools

Claims (2)

[Claims] 1. A plurality of software deliverable creation support tools used for software creation, a process name and a management target of a process set corresponding to the use work of each software deliverable creation support tool. A process management file storing a project name of a project and status information indicating a work status of each process of each project, and a process of editing each information of the process management file according to new establishment of the project and its work progress status Management means, and change management means for referring to the process management file and activating the software deliverable creation support tool corresponding to the process according to the state information of the process and instructing an update operation. And software process control equipment. 2. The process management means has, as status information indicating a work state of a process, first information indicating a state in which no work has been performed yet for the process and work for the process has been started yet. It has at least second information indicating that the work that has not been completed is in progress and third information that indicates that all the work of the process has been completed, and the work state information of the preceding process is the second information. The state information is edited so that the work state information of the succeeding process immediately after the work state information indicates the first information after the information becomes the third information is changed to the second information, and the state information is already set to the third information. When the preceding process, which is the information of the above process, is executed again, the state information of this process is changed from the third information to the second information, and all the third or second information of the subsequent process is changed to the first information. 2. The status information is edited in the field. On-board software process control device.