JPH04367049A - Design changing task control system - Google Patents

Abstract

PURPOSE:To attain the automatic control of the status and to facilitate the control of the design change information at the controlling side by informing the controlling side of each change of the status of the design changing task to the change information received from the controlling side in a transmitting destination system and registering automatically the changed status into a control table at the controlling side. CONSTITUTION:Receiving the change information, a changed area system 209 registers the change information register number, the title and the controlling area name in a changed area change information control table 207. A changed area user registers the status under study for the change contents into the status of the table 207 as long as the relevant area is affected by reference to the received change information. Then the system 209 informs a controlling side system 208 of the change information register number, the changed area name, the status, and the date. The system 208 registers automatically the status in a controlling side change information control table 203 based on the information received from the system 209. This registration is repeated until the change is complete.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the management of change work when a design is changed, and particularly to a system for managing change notifications by status registration.

0002

2. Description of the Related Art In software development work, it is very rare for the software design to remain unchanged from the start to the end of the development work, and usually some design changes occur during the development process. When there is a change in software design, the impact often extends beyond a single worker. If multiple workers are affected, it is necessary to notify all affected workers of the impact.

[0003] Conventionally, changes have been communicated by telephone or in writing. Furthermore, when each worker is working on a specific terminal device, there is a technology that automatically sends a message to the terminal of the worker to inform them that there has been a change. As a known example, there is a technique described in Japanese Patent Laid-Open No. 1-292529, for example.

0004

SUMMARY OF THE INVENTION In the above-mentioned prior art, the status of the message destination cannot be managed by simply sending a message notifying that there has been a change. Therefore,
For example, if a message is ignored by the destination, the management source cannot know the status.

An object of the present invention is to automate the status management of issued change notifications and to facilitate the management of design change information at a management source.

[0006]

[Means for Solving the Problem] In order to solve the above object, in the present invention, after a management source sends a change notification, a system to which the change notification is sent (hereinafter referred to as a changed department system)
Each time the status of the design change work changes in response to a change notification sent from the management source, the system notifies the management system of the status. The management system receives the status of the changed department and automatically registers it in the management change notification management table.

[0007]

[Operation] Since the change department notifies the management system of the status every time the status of the design change work changes, the management system can always grasp and manage the latest status.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a processing flowchart of the present invention.

The flow of processing is described with the left side representing the management source and the right side representing the modifying department. The details will be described later.

FIG. 2 shows an example of a system configuration for implementing the present invention.

In the figure, 201 is a management source workstation. 202 is a management source auxiliary storage device. 203 is a management source change notification management table. 204 is a communication network. The management source and the changing department communicate with each other via this communication network. 205 is a workstation of the change department. 206 is an auxiliary storage device of the changing department. 207 is a changed department change notification management table. 208 is a management source system. 209 is a changing department system. 210
is the managing user. 211 is a changing department user. There is one managing system 208 and one managing user 210. Change department system 209, change department user 211
may be multiple.

FIG. 3 shows a design change management source change notification management table.

301 in the figure is the change notification registration number. It is. 302 is the title of the change notification. 303 is a modification department name. The management workstation sends a change notification to the department written in the changed department name 303. When sending one change notification to multiple departments, specify multiple departments. 304 is the status of the change notification. 305
is the date when the status was registered. Status 304
has a history in pairs with date 305.

FIG. 4 shows a changed department change notification management table.

In the figure, 301, 302, 304, and 305 are the same as in FIG. 403 is the name of the department that manages the change notification.

FIG. 5 shows a status transition diagram of change notification.

As an example, the status transition of a change notification at the management source will be explained. When a change notification is sent, the status is set to "under investigation of impact" 501. From the change department:
When the status of "No influence" is notified, the status is set to "No influence" 502. When the change department notifies you of the status "Considering changes", the status is set to "Considering changes" 503. Further, when the change department notifies the status of "change work in progress", the status is set to "change work in progress" 504. When the status of "change complete" is notified from the changing department, the status is set to "change complete" 505. The same applies to status transitions in changed departments.

FIG. 6 shows a change notification status summary table.

[0020] The management system aggregates the statuses notified from the changing department's system and manages the progress of the design change work. 601 is a change notification status summary table. 602 is the date. Aggregate status based on the date shown in this row. 603 is the status. Change notifications are aggregated for each status from 501 to 505. 604 is the total.

FIG. 7 shows a change notification status summary diagram. This figure is a graph of the change notification status summary table 601 as it is. The management system outputs such a graph.

Next, the detailed processing flow will be explained along the processing flowchart of FIG.

When some change occurs in the design information at the management source (step 101), the management user 210 creates a change notification (step 102), and enters the change notification registration number in the management source change notification management table 203. 301, title 302, and changing department name 303 are registered (step 103). Status 30 of the change notification at this time
4 is set to 501 "Impact investigation in progress". The changing department name is the department that is thought to be affected by the design change, but there may be multiple departments that are thought to be affected. The management source system 208 adds the change notification registration number to the change department name 303 written in the management source change notification management table 203. 30
1. Send a change notification along with the title 302 and the name of the managing department (step 104).

[0024] Received change notification (step 105)
The department system 209 records the change notification registration number in the changed department change notification management table 207. 301, title 302
, and the managing department name 403 (Step 10)
6). At this time, the status 304 of the change notification is "under investigation of impact" 501. The changed department user (211) looks at the sent change notification and investigates whether the department is affected (step 107), and if there is no impact, the changed department change notification management table 207 status 304 is determined.
"No influence" 503 is registered in the field, and the current date is registered in the date 305 (step 108). If there is an impact, the status 503 of "Consideration of change" is registered in the status 304 of the changed department change notification management table 207 (step 108). When the status registration (step 108) is completed, the changed department system 209 sends the change notification registration number to the management system 208. 301, the changed department name 303, the status 304, and the date 305 are notified (step 109).

In the management source system 208, the change notification registration No. notified from the change department system 209. 301,
Change department name 303 and status 304 and date 3
05, the status is automatically registered in the management source change notification management table 203 (step 110).

In the department to be changed, if the change does not affect the department, the work ends (step 119). If the department is affected, the changed department user 211 starts considering the change (step 111). Once the details of the change have been decided, the changing department user (211) adds the next status "Change in progress" to the changing department change notification management table 207.
504 status and today's date are registered (step 112). When the status registration (step 112) is completed, the changed department system 209 sends the change notification registration number to the management system 208. 301, change department name 303, and status 304 of “change in progress” 504 and date 3
05 (step 113).

In the management source system 208, the change notification registration No. notified from the change department. 301, change department name 30
3 and the status 304 of “Currently working on changes” 504,
The status is automatically registered in the management source change notification management table 203 (step 114).

The changing department user 211 starts the changing work (step 115). When the change is completed, the user of the changed department registers the status 304 of "change complete" 505 and the current date 305 in the changed department change notification management table 203 (step 116). When the status registration (step 116) is completed, the changed department system 209 registers the change notification registration number. 301, the name of the department to be changed, the status 304 of "change completed", and the date 305 to the management system 2.
08 (step 117). This completes the work of the changing department (step 120).

In the management source system 208, the change notification registration No. notified from the change department. 301, change department name 30
3 and “change completed” 505 status 304 and date 30
5, the status is automatically registered in the management source change notification management table 203 (step 118).

Furthermore, if a design change occurs in a department other than the management source, the content of the change is notified to the management source by some method. Thereafter, change notifications are created and managed in the same manner as in the above embodiment.

[0031] Through the above processing, the managing user 210 can always grasp the status of change work in the changing department by looking at the managing source change notification management table 203.

Furthermore, the management source change notification management table 20
3, the management source system creates a change notification status summary table 601. Change notification status summary table 601
The change notification status summary diagram is a graph (Figure 7)
It is. The management user 210 can know the status transition by looking at the change notification status summary table 601 and the change notification status summary chart.

[0033] Note that steps 102, 103, and 10 above
A program to support the human tasks 7, 111, and 115 may be prepared, and the changing department may change the status when the human task on this program is completed. for example,
Cross-reference information about data, information about dependencies of specifications, related information about specification change ripples, etc. are prepared in advance, and change notifications are automatically created in step 102, and furthermore, in step 103, when there is an impact, The departments that are likely to be affected are automatically determined and automatically registered in the change notification management table. Step 107, Step 111
, and step 115 as well.

Furthermore, although five statuses are set in the above embodiment, the number of statuses and the way they change may be changed.

Next, a second embodiment of the present invention will be described.

[0036] In the above embodiment, there was one management source, but if there are multiple management sources, change notifications sent by each department are managed in the management source change notification management table 203, and each department receives the change notifications. Change notifications are managed in a changed department change notification management table 207. That is, both the management source change notification management table 203 and the changing department change notification management table 207 exist in both the management source auxiliary storage device 202 and the changing department auxiliary storage device 206. At this time, the managing department name 403 of the changed department management table 207 contains the managing department name of each change notification.

Next, a third embodiment of the present invention will be explained.

Using one workstation or one large computer, the change department communicates with the administrator through an online terminal. There is no auxiliary storage device 206 in the changing department. In this case, both the management source change notification management table 203 and the changed department change notification management table 207 are in the auxiliary storage device 202 of the management source, and the same management as described above is performed.

The same applies when the terminal of the changing department is offline.

Next, a fourth embodiment of the present invention will be described.

Using one workstation or one large computer, the change department communicates with the administrator through an online terminal. There is no auxiliary storage device 206 in the changing department. In this case, the change department change notification management table 207 is not provided, and only the management source change notification management table 203 in the auxiliary storage device 202 is used to manage change notifications. The changed department system 209 uses the management source change notification management table 203
Among the change notifications registered in , only the change notifications with the department name 303 are displayed to the change department user 211 . The display format is the same as the changed department change notification management table 207. The same applies if the terminal of the changing department is offline.

Next, a fifth embodiment of the present invention will be described.

[0043] In the embodiment described above, the status of design change work in software development is managed by the management source, but this system can be applied to fields other than software development to manage work. For example, in a publishing company, when a manuscript is being proofread by multiple departments, this system can be used to monitor the progress of the proofreading. In this case, the status transition diagram of FIG. 5 has status contents and transitions suitable for managing the proofreading state of the manuscript.

Next, a sixth embodiment of the present invention will be described.

[0045] In the above-mentioned embodiment, change notifications were sent using a communication network, but notifications of the contents of changes themselves are sent by telephone or in writing, and only status management is performed using this system. In this case, in the change notification sending step 104 of FIG. 1, the change notification registration No. 301, only the title 302 is sent to the changed department system 209, and the change notification reception step 10
In step 5, only those sent will be received.

[0046]

According to the present invention, the status management of issued change notifications is automated, and the management of design change information at the management source is facilitated.

[Brief explanation of drawings]

FIG. 1 is a processing flowchart of an embodiment of the present invention.

FIG. 2 is a system configuration diagram showing an example of the system of the present invention.

FIG. 3 is a management source change notification management table of a management source.

FIG. 4 is a change department change notification management table for a changed department.

FIG. 5 is a status transition diagram in one embodiment of the present invention.

FIG. 6 is a change notification status summary table.

FIG. 7 is a change notification status summary diagram.

[Explanation of symbols]

101... Change occurrence step 102... Change notification creation step 103... Management source change notification management table registration step 104... Change notification sending step 105... Change notification receiving step 106... ...Change department change notification management table registration step 107...Impact status investigation step 108...Impact status determination step 109...Start of change content review or no impact notification step 110...Status registration Step 111...
Change content review step 112... Change content determination step 113... Change work start step 114... Status registration step 115...
Change work step 116... Change completion step 117... Change completion notification step 118... Status registration step 119...
End step 120... End step 201... Management source workstation 202...
-Manager auxiliary storage device 203...Manager change notification management table 204...
...Communication network 205...Change department workstation 206...
...Changed department auxiliary storage device 207...Changed department change notification management table 208.
...Managing system 209...Changing department system 210...Managing user 211...Changing department user 301...Change notification registration No. 302...Change notification title 303...Change notification changing department name 304...Change notification status 305...Status registration date 403...Change notification management source department name 501... Impact investigation in progress status 502...No impact status 503...Change contents under consideration status 504...
・Change status 505...Change completion status 601...Change notification status summary table 602...
・Date 603...Status 604...Total

Claims (6)

[Claims] Claim 1: In a system consisting of a plurality of information processing devices connected through a communication line, the same number of tables as the plurality of information processing devices are provided, one of the plurality of information processing devices is designated as a management side, and the remaining on the changing side, one of the above tables
One table is set as a first table, and the remaining table is set as a second table, and the information processing device on the changing side receives design change information from the information processing device on the management side and writes the status to the design information on the second table. If the status of this design change information changes, the status is sent to the information processing device on the management side, and the information processing device on the management side,
When design change information is sent to the changing information processing device and a status is assigned and managed to the design change information on the first table, and the status is received from the changing information processing device, this status A design change work management method characterized by updating the status of the first table. 2. The information processing device on the changing side has means for supporting human work corresponding to each status in the second table, and updates the status when the work is completed on this support means. 2. A design change work management system according to claim 1. 3. The information processing device on the management side has a means for automatically creating design change information, and transmits the design change information created using this means to the information processing device on the change side, and also writes the information in the first table. 2. The design change work management system according to claim 1, wherein the design change work management method is managed using the following. 4. In a system consisting of a plurality of information processing devices connected via a communication line, the number of first and second tables is the same as the number of the plurality of information processing devices, and each of the plurality of information processing devices is configured to have a design change. In addition to transmitting the information to another information processing device, the design change information is given a status and managed in the first table, and when the design change information is received from another information processing device, the design change information is is assigned a status and managed in the second table, and
Every time the status of the design change information in the table changes,
When the status is transmitted to the information processing device that is the transmission source of the design change information and the status is received, the first
A design change work management method characterized by updating the status of corresponding design change information in a table. 5. The information processing device includes means for supporting human work corresponding to each status in the second table, and updates the status when the work is completed on the support means. 5. The design change work management system according to claim 4. 6. The information processing device has a means for automatically creating design change information, and transmits the design change information created using this means to another information processing device and manages it using the first table. 5. The design change work management system according to claim 4.