JPH04326467A - Work guidance method - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed description of the invention]

0001

[Industrial Application Field] The present invention relates to a method of guiding work in the creation of specifications using an information processing device, and includes, for example, designing and developing an information processing system through the creation of a plurality of mutually related specifications and programs. The present invention relates to a work guidance method suitable for a support system for advancing work.

0002

2. Description of the Related Art In order to design and develop an information processing system, many specifications and programs must be created. Moreover, since they are intricately related to each other, computer support is required.

[0003] Conventionally, for example, information processing society
According to pages 587 to 590 of the 0th session, a process chart is stored that indicates the expected start and completion dates for each work item for system development, and the process chart is used to notify workers at the time of starting work. There was a system to display scheduled work.

[0004] Also, IBM SYSTEMS JO
URNAL, VOL29, NO2, 1990, P189
According to ~P208, there was a method of storing work relationships, displaying the work relationships, and starting the next work according to the operator's instructions.

[0005]

[Problems to be Solved by the Invention] However, in the prior art as seen in the above-mentioned Proceedings of the 30th National Conference of the Information Processing Society of Japan, work guidance was performed based on the schedule written in the process chart, so it was difficult to see how far the work actually progressed. I didn't take into account whether it was completed or not. Therefore, if the work is not progressing as planned, there is a problem in that the displayed work schedule does not reflect the actual situation.

[0006] Also, the above-mentioned IBM SYSTEMS J
In the conventional technology seen in OURNAL, in the related information between tasks, what is created in each task is not distinguished. Therefore, for example, the work of creating "A program specification" and the work of creating "B program specification" are both the same work of "program specification creation." Therefore, when displaying the work status to the worker, there is a problem in that the two tasks in the above example cannot be distinguished and displayed.

[0007]

[Means for Solving the Problems] In order to achieve the above object, the work guidance method of the present invention stores the relationship between data, and when a worker instructs that the work on a certain first data has been completed, the work guidance method of the present invention stores the relationship between data. Detect the work of the second data, check whether all other data works that affect the work of the second data have already been completed, and if completed, the work of the second data Since it has been found that it is now possible to start, this is displayed on the dialog terminal.

In a particularly desirable embodiment of the present invention, when a worker creates a work schedule that associates the data to be worked with the scheduled start date and scheduled end date of the work, according to the worker's instructions, The scheduled start date and scheduled end date in the work schedule information are associated with each other, and relationships between data are automatically detected from the correspondence.

[0009] Furthermore, judgment conditions for determining the working status of data based on the content of the data or whether or not the data exists are stored, and the working status of certain data is automatically determined using the determining conditions.

[0010]Furthermore, if the relationship between data is complex and difficult to create, the relationship between data types is created in advance, and this is used to automatically detect the relationship between data.

[0011] Furthermore, the relationship between the completed work and the work to be started next is displayed in an easy-to-understand manner using arrows connecting these works.

0012

[Operation] The work guidance method of the present invention detects the work to be performed next based on the actual progress of the work, so that practical guidance can be provided. Since this is checked even when multiple tasks affect one task, it is possible to deal with cases where the relationships between tasks are complex.

In particular, if the relationship between data is automatically detected from the correspondence between the scheduled start date and the scheduled end date of the work schedule, it is possible to specify the relationship between data and create the work schedule at the same time. This simplifies the work of other people.

[0014] Furthermore, by using a determination condition for determining the work status for data based on the content of the data or whether or not the data exists, it is possible to automatically determine the work status that was conventionally specified by the worker.

[0015]

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 flowchart showing one embodiment of the processing procedure when the present invention is applied to a specification creation support system, and FIG. 2 is a block diagram showing the configuration of the specification creation support system according to the present invention. It is a diagram.

In FIG. 2, reference numeral 1 denotes a CPU having a program-based sequential processing function, which controls the execution of the procedure shown in FIG. Reference numeral 2 denotes an interaction terminal having a keyboard, a mouse, and a monitor TV screen, which is used by a worker using the specification creation support system to input instructions and to display results to the worker. 3 is a program that implements the procedure shown in FIG. 4 is a file that holds the status information shown in FIG. 3, including the type 31 and name 32 of the specification document to be worked on
represents the correspondence between the person in charge of the work 33 and the state of the work 34. 5 is a file that holds the data-related information shown in FIG. 4, and indicates that work on the specification with the affected specification name 42 cannot be started unless the specification with the affected specification name 41 is completed. Reference numeral 9 denotes a file in which the specification creation support system holds specifications created in accordance with the instructions of the operator for editing work.

In FIG. 4, the correspondence between each row will be referred to as an influence relationship in the following explanation. For example, the influence relationship 43 requires that the creation of the “sales file update summary” is completed.”
This indicates the influence relationship that prevents the creation of "sales file update details" from being started.

The relationship shown in FIG. 4 is shown in FIG. In FIG. 5, the influence relationships 43 and 44 are represented by arrows 54 and 55, respectively. As can be seen from FIG. 5, in this embodiment, the "sales file update details" must be completed until the creation of both the "sales file update summary" 51 and the "sales file update function" 52 is completed.
It is assumed that the creation work of 53 cannot be started. Next, the first embodiment will be described in detail using FIGS. 1 to 6.

In FIG. 1, the user first inputs that the specification document called "sales file update function" has been completed (
100). This is the influence source specification. Next, status information 4
Change the status of the specification from "Work in progress" to "Complete"
(101). Next, when the data-related information 5 is searched for specifications that are affected by the "sales file update function" (102), "sales file update details" is found. Next, when searching for specifications that affect the "sales file update details" from the data related information 5 (104), "sales file update summary" is found, so the status of the "sales file update summary" is found from the status information 4. (106). Since the status is "completed", it was found that there is no problem with the influence of "sales file update summary" on "sales file update details". Since there are no other specifications that affect the "sales file update details" (104, 105), it has been found that the "sales file update details" can now start work. Therefore, next, the status of "sales file update details" in status information 4 is changed from "unable to work" to "in progress" (107).

[0021] If the status of "Sales file update summary" is "
If it is not "completed" (108), the status of "sales file update details" cannot be rewritten because the work of "sales file update details" cannot be started yet.

Next, we return to the beginning and search for other specifications that are affected by the "sales file update function" (102). Since there is no other matching item (103), the status information 4 is displayed on the dialog terminal 2 as shown in FIG. 6 (109), and the process ends.

According to this embodiment, the worker can know what work to do next by simply instructing the completion of the work. Therefore, there is no risk of erroneously starting work on specifications that have not yet reached the stage at which work should be started.

[0024] Information that guarantees the above effects is included in the data-related information. If it is difficult for the worker to create the data-related information, have it done by another person who is familiar with the work procedure.
For example, it may be performed by a manager who manages a plurality of workers. This allows a worker who is unfamiliar with the work to proceed with the work while viewing the list of work statuses displayed according to the settings of the administrator.

Next, a second embodiment will be explained using FIGS. 7 and 8.

In this embodiment, the number of types of states is increased and the data structure of data-related information is modified in order to deal with the case where there are multiple tasks for one specification.

For example, when a plurality of workers jointly develop a certain system, a task called a review occurs in which they mutually confirm the contents of the specifications in order to communicate. Since the review is performed after the specification is completed, two types of states are added, for example, "under review" and "review completed" as the next state following the "completed" state. Including the above three types of states, there are five types. The data related information uses five types of states, for example, as shown in FIG.

[0028] The data related information shown in FIG.
This indicates that the state of the specification name 706 of the affected specification is to be changed to state 707. For example, according to the influence relationship 701, when the status of the "Sales file update summary" becomes "Completed", the status of the "Sales file update function" is changed to "Working".
Make it. In addition, since the specification name 706 and status 707 of the affected specification are the same for the influence relationship 702 and the influence relationship 703, the status of the "Sales file update function" is "Completed" and the status of the "Sales file update summary" is " Review completed”
When this happens, the status of the "sales file update function" is set to "under review". For example, in the influence relationship 702, even though the status of the "sales file update function" is still "in progress", the influence relationship 703
The function is to prevent changes from being made while "under review".

It goes without saying that when the data related information 5 is as shown in FIG. 7, the number of types of status information 4 increases. Further, the processing procedure is also similar to the procedure shown in FIG. 1, but the difference is that state changes are defined as shown in FIG.

FIG. 8 shows how the state changes according to the example of FIG. For example, the status 802 indicates that the status of the "sales file update summary" is "in progress." At this time, when the state is changed to state 803 according to the operator's instructions (
812), the state is changed as in 815 according to the regulations in 701. In other words, the status of the "sales file update function"
Change from "Unable to work" to "Work in progress". This influence relationship is shown in the diagram at 821. Similarly, the influence due to the provisions of 702 and 703 is shown at 822. Influence relationship 819
and 820 indicate the influence of changes in the work status of other specifications. Due to such influences, state changes 811,
813, 815, 817 occur. Also, state change 812
, 814, 816, and 818 occur when the state is changed according to the operator's instructions.

According to the second embodiment, work guidance can be provided even when multiple tasks such as creation and review are required for one specification.

Next, a third embodiment will be explained using FIGS. 9 to 15.

In this embodiment, state number information 7 that associates states with state numbers is added (FIG. 9), and the state before change of the affected specification (current state 1004 in FIG. 10) can be limited. The data related information is modified as shown in FIG.

In the example shown in FIG. 9, the state numbers 1 to 5 are assigned, but they do not need to be consecutive numbers. However, it is convenient to set the order of the work flow and the order of the numbers so that they correspond, because for example, the completion of a task can be easily expressed as "3 or more."

In FIG. 10, a specified minimum state 1002 represents a condition regarding the state of the specification of the specification name 704 of the influence source specification, and specifies the minimum numerical value of the state number to which the influence spread is applied. For example, when the designated minimum state 1002 is designated as "3", all states of 3 or more are included. Specifically, it means three states: "completed", "under review", and "review completed".

[0036] This expression method is just one example, and it goes without saying that the degree of freedom can be further improved by providing a field for the maximum applicable state, for example to specify the maximum state number.

The current state 1004 of the affected specification is affected only when the specification with the specification name 706 matches the current state 1004 at the time before the specification follows changes in other work situations. Specify to receive.

[0038] There may be cases where it is not desired to specifically limit the current state 1004. In that case, for example, a special state number such as "0" may be designated as the current state 1004, and it may be determined whether or not it is "0" in the step of checking the current state.

The next state 1005 represents a new state that is set in the specification name 706 of the affected specification when all affected conditions are satisfied.

An influence relationship 1006 represents the influence relationships 702 and 703 as one influence relationship. In the representation method of FIG. 7, the influence relationship 702 is necessary to prevent the state of the "sales file update function" from being directly changed from "working" to "under review." In FIG. 10, since the current state 1004 of the affected specification can be specified, the expression is simplified accordingly.

Furthermore, when it is desired to apply the influence relationship shown in FIG. 4 to the second embodiment, the following problem arises. In FIG. 7, when "sales file update summary" and "sales file update function" are specified as the specification name 704 of the affected specification, and the status 705 of both is specified as "completed,"
"Review in progress" and "Review completed" are not included in the specification. Therefore, the status of the "Sales file update function" is "Completed".
The status of “Sales file update summary” is “Completed” before reaching
If the status of the two specifications mentioned above becomes "Completed" at the same time, the status of the two specifications will not change to "Completed" at the same time. Therefore, the status of "sales file update details" remains "unable to work" forever. The above problem can be solved by specifying the specified minimum state 1002 of the influence source specification in Figure 10.
3''.The reason why states are associated with numbers as shown in FIG. 9 is to enable the specified minimum state 1002 to be specified in this way.

The processing procedure of the third embodiment is shown in FIGS. 11 and 12.
FIG. 13 shows the system configuration. FIG. 11 shows the overall processing procedure, and FIG. 12 shows details of step 1105 and step 1108 in FIG.

A work area 6 is required to hold intermediate data during the processing steps shown in FIGS. 11 and 12. An example of the work area is shown in FIG. In FIG. 14, each column can store one name of a specification whose status has been changed.

FIG. 15 shows details of status information 4. state 1
501 represents the state by a state number.

[0045] The working state is now as shown in Fig. 15.
The operation of the third embodiment will be explained in detail in accordance with the processing procedures shown in FIGS. 11 and 12, taking as an example the case where the creation work of the "sales file update function" has been completed.

First, the work area 6 is blanked, and the name of the specification sheet whose work status has changed, "sales file update function", is stored in the first column (1101). Next, the status of the "sales file update function" is changed to "3" (1102). Next, in order to determine the end of the repetition, it is checked whether there is a specification name stored in the work area 6 (1103). Since the "sales file update function" is stored in the work area 6, the name is next obtained and deleted from the work area 6 (110
4). Using the resulting specification name "sales file update function" as input, the influence ripple processing shown in Figure 12 is performed (
1105).

In the influence ripple processing, first, it is checked whether there is an influence relationship in which the specification name 706 in FIG. 10 matches the input affected specification and the state of the affected specification matches the current state 1004 (1200). . If not, immediately end the impact ripple processing. If there is, then one influence relationship in which the specification name 706 in FIG. 10 matches the input affected specification and the state of the affected specification matches the current state 1004 is searched. In this case, the influence relationship 1006 applies, and the secondary influence specification is "sales file update summary." Next, obtain the status of the secondary impact specification from 1502 in FIG. 15 (1203)
. In this case, the state number is "5". The state number obtained as a result is the specified minimum state 1002 of the influence relationship 1006.
It is checked whether it matches the column of (1204). Since they match, other secondary impact specifications that affect the "sales file update function" are searched (1201). However, since nothing is found, the state "3" of the "sales file update function" is changed to the state "4" specified in the next state 1005 column of the influence relationship 1006 (1205). Since a change in status has occurred, the "sales file update function" is added to the work area 6 (1206), and the influence ripple processing is ended.

In step 1204, if the state of the secondary impact specification is not as specified, the conditions of the impact relationship are not satisfied. Therefore, it becomes clear that the input affected specifications are not affected, so the influence ripple processing is ended without doing anything.

Returning to FIG. 11, the specification obtained in step 1104 matches the contents of the specification name 704 column in FIG.
The state of the specification that is equal to or greater than the number in the field and indicated by the specification name 706 of the affected specification is the current state 100.
Search for one item that matches 4 (1106). In this case, the state of the "sales file update function" is "3" and the state of "sales file update details" is "1" from FIG. 15, so the influence relation 1008 applies. Therefore, the affected specification becomes "sales file update details".

Since there is a possibility that the state of the affected specifications obtained in step 1106 needs to be changed, the influence ripple processing shown in FIG. 12 is performed using the affected specifications as input (1108). In this case, the status of "sales file update details" is changed from "1" to "2", and "sales file update details" is added to the work area.

Next, in step 1106, other affected specifications are searched, but nothing is found (1106, 1107).
).

Next, one specification name is acquired from the work area (1104). Although the "sales file update function" is obtained, since it has already been processed, nothing happens in the influence ripple processing (1105), and there are no applicable specifications that will affect it (1106, 1107).

Next, one specification name is acquired from the work area (1104). "Sales file update details" can be obtained. Nothing happens in the influence ripple processing (1105). The influencing relationship 1009 corresponds to the specifications that have an influence. “Sales file update details 2” becomes the affected specification.

Next, influence ripple processing is performed for "sales file update details 2" (1108). In this case, the state is “1”
" has been changed from "2" to "Sales file update details 2"
is stored in the work area.

Thereafter, the same process is performed for all specifications stored in the work area, and when the work area becomes empty, the status information 4 is displayed on the dialog terminal 2 as shown in FIG.
9) Finish the process.

According to this embodiment, it is possible to guide the work when multiple works are required for one specification, and moreover, the second
This solves the problem that the embodiment described above could not deal with the influence relationship as shown in FIG. Also, compared to the second embodiment,
The data-related information 5 can be easily expressed, such as by reducing the number of influence-related items that need to be specified, so it is easy to create. Furthermore, since it is possible to deal with influence spillover caused indirectly by the influence of a certain influence relationship, more complex influence relationships can be automatically detected and more appropriate work guidance can be provided to workers.

Next, a fourth embodiment will be explained using FIG. 16.

This embodiment relates to the case where the specification creation support system has a function of supporting the creation of a work process chart, and the data-related information 5 required in the work guidance methods of the first to third embodiments. is automatically created when creating a work flow chart.

As an example of a function that supports creation of a work process chart, there is a work process chart editor that has functions for editing and printing a work process chart. FIG. 16 shows an example of the editing screen of the work process chart editor.

[0060] The scheduled start date 1607 indicates the scheduled date for starting work on the specification document ``sales file update summary'' 51. Similarly, a scheduled end date 1609 indicates the scheduled date to end work on the specification. A work line 1608 indicates the period during which work on the specifications is scheduled. An influence relationship line 1616 shows the influence from the scheduled end date 1609 to the scheduled start date 1613, and means that the work on the "sales file update details" 53 cannot be started until the work on the "sales file update summary" 51 is completed.

Next, the operation of the specification creation support system in the fourth embodiment will be explained using FIGS. 16 and 4.

First, the work process chart editor displays a work process chart as shown in FIG. 16 on the dialog terminal 2 according to the editing operation of the worker. At that time, work schedule information is stored based on the correspondence between the name in the specification name column 1603, the scheduled start date, and the scheduled end date, and data related information 5 is stored based on the correspondence between the specification name indicated by the start and end points of the influence relationship line. Remember. In this case, the data related information is as shown in FIG. 2, and it goes without saying that it can be applied to the first embodiment as is.

Next, work guidance is performed as in the first embodiment. At this time, in step 109 of FIG. 1, the scheduled work status is obtained by comparing the work schedule information with the date and time at that point, and by comparing the result with the status information 4, the work is scheduled. You can determine whether or not the process is progressing as expected. The results are displayed in addition to the display in FIG.

[0064] In the first to third embodiments, there was a problem in that it took time and effort to create the data-related information 5. According to this embodiment, data related information 5 is obtained from the created work schedule.
can be created automatically. The creation of a work schedule is more meaningful than the creation of data-related information because the work schedule can be used for other purposes, such as checking whether work is progressing as planned or summing up the number of people and time invested in development. be. In addition, since the worker can understand the difference between the work schedule and the work schedule, the worker can know which work to prioritize.

Furthermore, for example, for a task that has not been completed even after the scheduled end date, the number of days the work is delayed can be obtained by calculating the difference between the current date and time and the scheduled end date. By summing this for all operations, the total operation delay is obtained. By displaying the number of delayed days for each task or as an overall total, it is possible to quantitatively show the difference between the tasks and the schedule.

Next, a fifth embodiment will be explained using FIGS. 17 to 20, FIGS. 9 and 15.

In this embodiment, the work situation is automatically determined using the determination conditions shown in FIG. The system configuration of this embodiment is shown in FIG. 19, and the processing procedure is shown in FIG. 20.

[0068] In the following explanation, when a work is completed or a work is interrupted, this will be referred to as the end of the work.

FIG. 17 shows an example of a screen of a specification editor for editing a specification using an interactive terminal. Figure 18 shows judgment condition 7.
Here is an example.

In FIG. 17, a specification 1701 is a specification to be edited. Specification name 1702 is Specification 1
701 name is displayed. Column item 1702 displays the meaning of description column 1704. Similarly, column item 1703
indicates the meaning of the description column 1705. Description field 170
4 is associated with a column name "Creator Signature Column" and the description column 1705 is associated with a column name "Approver Signature Column".

In FIG. 18, specification name 1801 indicates the name of the specification to be determined. The column name 1802 indicates which description column therein is the target of determination. The minimum state 1803 indicates the minimum value that the state number of the specification should take when some characters or figures are written in the description field. Each line 1804 or 1805 indicates a condition, and if something is written in the column indicated by column name 1802 in the specification indicated by specification name 1801, the state of the specification is at least the minimum state. Indicates that it must be the number shown in 1803. If the number is less than or equal to the minimum state 1803, change the state number of the specification to the minimum state 180.
Change to number 3.

Next, the processing procedure of the fifth embodiment will be explained in detail using FIG. 20. In the explanation, assume the following case. That is, the status information 4 is as shown in FIG. 15, the status number information 7 is as shown in FIG. It is assumed that the work has been completed and the specifications have been stored in the specifications file 9.

First, the name "sales file update function" of the completed specification is acquired (2001). Next, from among the determination conditions 8, one is searched for whose content in the column of specification name 1801 in FIG. 18 matches "sales file update function" (2002). Condition 1804 applies. According to 1503 in Figure 15, the status of the “sales file update function” is “2”.
”, and according to condition 1804 it must be at least “3”, so it may be necessary to change it (2
005). The condition 1804 is that something is written in the "creator signature field" 1704 in FIG. 17 regarding the contents of the "sales file update function". According to FIG. 17, the condition is met (2006). Next, the judgment condition 8 is searched for the specification name 1801 and the minimum status 1803 that have the same content (2007), but since there is no matching item (2008), the “sales file update function” in the status information 4 is searched (2007). ” status is changed to “3” (2009).

Next, when searching for another condition (2002),
Condition 1805 is applicable (2003). Minimum state 180
Since column 3 is "5", there is a possibility that a change is necessary (2005). However, since "Approver signature field" 1705 is blank, condition 1805 is not satisfied (2
006).

Another search is made for another condition (2002), but since nothing is found (2003), the process is terminated.

In step 2005, the minimum state 18
If the specification of 03 is already satisfied, there is no need to change the state, and the process immediately moves to other conditions.

[0077] In step 2008, specification name 18
01 and the minimum state 1803 are both the same, it is assumed that all of these conditions must be satisfied. Therefore, the process returns to step 2006 to check the conditions.

[0078] By doing the above, a complex condition can be divided into a plurality of conditions and specified.

According to this embodiment, since the work status is automatically checked, there is no need for the operator to set the status every time he finishes editing.

[0080] In this embodiment, the determination is made based on whether something is written in a specified column of the specification, but there is also a method of determining, for example, based on whether or not the specification exists.

Another method is to prepare a judgment program for each specification, store the correspondence between the specification and the judgment program using judgment condition 8, and automatically start the judgment program using the correspondence. Furthermore, since specifications of the same type can often be judged by the same program, there is also a method of preparing a judgment program for each type of specification. If a judgment program is prepared, more complex conditions can be tested, and therefore more appropriate judgments can be made.

In addition, in FIG. 18, the minimum state number is specified by the minimum state 1803 for specifying a state change, but as seen in the current state 1004 and next state 1005 in FIG. It is also possible to change to the next state only when the current state of the book is equal to the specified state. This allows more complex specifications.

Next, a sixth embodiment will be explained using FIGS. 21 to 24, FIGS. 10 and 15.

[0084] In the second or third embodiment, there is a problem in that creating the data-related information 5 is difficult and complicated. This embodiment solves the above problem by using data type related information that specifies a relationship for each data type.

FIG. 21 shows an example of data type related information. FIG. 22 shows an example of data related information. As an example of data types, FIG. 15 shows an example showing a correspondence between a specification type 31 and a specification name 32.

In FIG. 21, a set of one row of data will be referred to as a type influence relationship in the following description. For example, “Program processing overview diagram” and “3”, “Program function explanation diagram” and “1”
The combination of " and "2" is a type-impact relationship. Specify the type of the specification of the impact source in the specification type name field 2101 of the impact source specification. Similarly, specify the specification type name of the affected specification. 210
In column 2, specify the type of specification document to be affected. For example, according to the type influence relationship 2103, the status number of the first specification belonging to the type "Program processing overview diagram" is "3".
If the above and the second specification related to the first specification belongs to the specification type "Program function explanation diagram" and the status of the second specification is "1", then the second specification Change the state of the book to "2".

FIG. 23 shows the configuration of the system. In FIG. 23, data-related intermediate information 11 is an intermediate output obtained by this embodiment, and has the same data structure and meaning as the data-related information shown in FIG. 10 used in the third embodiment. Therefore, after applying this embodiment, work guidance can be performed by applying the third embodiment to the data-related intermediate information 11.

FIG. 24 shows data-related intermediate information 11 obtained by applying this embodiment using FIGS. 21 and 22 as input.

Next, the processing procedure of the sixth embodiment will be explained.

First, one influence relationship is obtained from the data related information 5 shown in FIG. For example, the influence relationship 2201 corresponds to this. Next, the type of the affected specification name 41 of the affected relationship 2201 matches the specification type name 2101 of the affected specification in the data type related information 10, and the type of the affected specification name 42 of the affected relationship 2201 is data. A type influence relationship that matches the specification type name 2102 of the affected specification in the type related information 10 is searched from FIG. In this case, from FIG. 15, the type of "sales file update summary" is "program processing summary diagram" and the type of "sales file update function" is "program function explanation diagram", so the type influence relationship 210
3 and 2104 are applicable. For each of these,
Specify the specification type name 2101 of the affected specification as the affected relation 220
Replace with the affected specification name of 1 “Sales File Update Summary”. Similarly, for each of the type influence relations 2103 and 2104, the specification type name 2102 of the affected specification is replaced with the affected specification name "sales file update function" of the affected specification 2201. By the above processing, 24 in FIG.
01 and 1006 are obtained.

Next, when similar processing is performed on the remaining influence relationships 2202 in FIG. 22, 2402 and 2403 in FIG. 24 are obtained. By performing the same processing for all influence relationships as described above, data-related intermediate information 11 can be obtained.

Next, the data-related intermediate information 11 is changed to the third
A third example is performed as the data-related information 5 of the example, and the process ends.

According to this embodiment, the data-related intermediate information 11 shown in FIG. 24 can be obtained from the data-related information shown in FIG. 22. It is easier for an operator to specify data-related information than to directly specify data-related intermediate information 11.

At this time, the data type related information shown in FIG. 21 is required, but the reason why there is no problem with its creation will be explained below. When developing a new system, a new specification is always required, and in the third embodiment, it was necessary for the operator to create data-related intermediate information regarding the new specification. However, even when a new system is developed, the number of new specifications rarely increases. Therefore, once the data type related information is created, there is almost no need to change it. Moreover, the number of specification types is much smaller than the number of specifications, so it is easy to create.

In this embodiment, data-related intermediate information 11 is once created as an intermediate output, but for example, in step 1106 of FIG. 11 or step 1201 of FIG. 12, data type-related information of FIG. 21 and status information of FIG. 22 are directly combined. It can also be used to test the effects.

Next, a seventh embodiment will be explained using FIG. 25, FIG. 3, and FIG. 4.

[0097] This embodiment shows a contrivance for displaying the relationship between tasks in an easy-to-understand manner when displaying status information on the dialog terminal as in step 109 of FIG. 1, for example.

FIG. 25 shows an example of a display screen. FIG. 25 shows an example where the status information 4 is as shown in FIG. 3 and the data related information 5 is as shown in FIG. 4.

In FIG. 25, a solid line frame 2501 indicates that the work status of the specification document "sales file update summary" is "completed". A thick line frame 2502 indicates that the work status of the specification document "sales file update function" is "in progress." A broken line frame 2503 indicates that the work status of the specification document "sales file update details" is "unable to work." Thick arrow 2
504 and the solid line arrow 2505 indicate that there is an influence relationship between the specifications displayed at both ends of the arrow. In particular, the thick line arrow indicates that even though the work of the "sales file update summary" has been completed, the "sales file update details" ” indicates that it is not possible to work yet.

Next, the processing procedure of the seventh embodiment will be explained.

First, the specification name and the corresponding state are obtained from the state information 4. For example, according to FIG. 3, "sales file update summary" and "completed" correspond. Next, from this state, the type of frame line is determined as follows. That is, when the status is "completed", it is a thick line, when the status is "working", it is a solid line, and when the status is "unable to work", it is a broken line. In this case, the thick line corresponds. Next, display the specification name on the screen and surround it with a frame. The above processing is performed for all specifications included in status information 4.

Next, from the data related information 5, influence relationship 1
Get pieces. For example, according to FIG. 4, influence relationship 43 is applicable. Next, it is checked whether both the influence source specification name and the influence target specification name of the influence relation 43 are included in the status information 4. If it is not included, the process moves on to other influence relationships. in this case"
Since both "sales file update summary" and "sales file update function" are included in Figure 3, proceed to the next step. Next, if the status of the influence source specification name 41 of the influence relationship 43 is "completed" and the influence The status of the previous specification document name 42 is "Unable to work"
Check whether it is. Applicable in this case. Next, the type of arrow is determined as follows according to the inspection results. That is, if it is applicable, it is a bold line arrow, and if it is not applicable, it is a solid line arrow. Next, an arrow is displayed with the frame of the influence source specification name of the influence relation 43 displayed on the screen as the starting point and the frame of the influence destination specification name as the end point. The above processing is performed for all influence relationships of data-related information.

As described above, a screen like that shown in FIG. 25 is displayed, and the process ends.

According to this embodiment, the work status can be grasped at a glance. This is clear when comparing FIG. 3 and FIG. 25. Moreover, since the influence relationship shown in FIG. 4 is also displayed in FIG. 25, the relationship between the tasks can be read. Furthermore, Figure 25
According to , it can be seen that the solid line arrow pointing to "sales file update details" is the reason why the work cannot be performed. That is, it can be seen that once the work of the "sales file update function" is completed, the work of the "sales file update details" can be started. Therefore, the worker can know not only which tasks can be performed, but also which tasks should be prioritized.

Furthermore, when there are a large number of states as shown in FIG. 9, various effects occur between tasks. You can also add more types of arrows to display this. FIG. 26 shows arrow selection information that associates the state number of the affected specification, the state number of the affected specification, the color of the arrow, and the type of line of the arrow. If the arrow selection information is used in the step of determining the type of arrow described above to determine the type of arrow from the status of the affected specification and the status of the affected specification, it will be easier to understand the relationship between more complex tasks. Can be displayed.

[0106] Also, by first obtaining the worker's name, then obtaining the person in charge of the work from the person in charge column 33 in FIG. 3, comparing it with the worker name, and displaying only the matching tasks, It is also possible to display only the work that a person is responsible for.

[0107]

[Effects of the Invention] By simply inputting the work status of each work that the worker has performed, the worker can know what work to do next.

[0108] In particular, when a certain task cannot be started unless multiple other tasks are completed, or when the completion of a certain task allows multiple other tasks to be started, it is important to provide useful information to the worker. Can be provided. This is because it is difficult to grasp the relationship between such multiple tasks and the task status, and to accurately judge the task one should perform next.

Furthermore, since the step of storing the relationship between tasks and the step of storing the task situation are separate steps, it is not necessary that the operator inputting data in these two steps is the same person. Therefore, for example, a manager who manages a plurality of workers can input related information between tasks, and the worker who actually performed the task can input the work status. In this way, even a worker who is not familiar with the relationships between tasks and the flow of tasks can perform the tasks according to the task guidance provided based on the appropriate settings of the administrator.

[Brief explanation of drawings]

FIG. 1 is a flowchart showing the processing procedure of a first embodiment.

FIG. 2 is a block diagram showing a system configuration for realizing work guidance according to the first embodiment.

FIG. 3 is an example of status information.

FIG. 4 is an example of data related information.

FIG. 5 is a diagram showing the relationship between specifications.

FIG. 6 is an example of a work guidance screen display.

FIG. 7 is a second example of data-related information.

FIG. 8 is a diagram showing how the state changes.

FIG. 9 is an example of state number information.

FIG. 10 is a third example of data-related information.

FIG. 11 is a flowchart showing the processing procedure of the third embodiment.

FIG. 12 is a flowchart showing detailed processing procedures of the influence spread processing of FIG. 11;

FIG. 13 is a block diagram showing the configuration of a system for realizing a third embodiment.

FIG. 14 is an example of a work area.

FIG. 15 is a second example of status information.

FIG. 16 is an example of a screen display of a work process chart editor.

FIG. 17 is an example of a screen display of a specification editor.

FIG. 18 is an example of determination conditions.

FIG. 19 is a block diagram showing the configuration of a system for implementing the fifth embodiment.

FIG. 20 is a flowchart showing the processing procedure of the fifth embodiment.

FIG. 21 is an example of data type related information.

FIG. 22 is a fourth example of data-related information.

FIG. 23 is a block diagram showing the configuration of a system for realizing a sixth embodiment.

FIG. 24 is an example of data-related intermediate information.

FIG. 25 is a screen display example of the seventh embodiment.

FIG. 26 is an example of arrow selection information.

[Explanation of symbols]

1...CPU, 2...Interaction terminal, 3...Program, 4...Status information, 5...Data related information, 6...Work area, 7...Status number information, 8...Judgment condition, 9...Specification file, 10...Data type Related information, 11...Data related intermediate information.

Claims (5)

[Claims] Claim 1: A work guidance method in an information processing device having a computer and an interaction terminal, which includes data having system specifications or programs as contents and at least whether the work is "unable to work", "work in progress", or "completed". a step of storing state information representing correspondence with three types of states; and a data-related step of associating the first data with second data that follows and is affected by changes in the work status of the first data. a step of storing the information; a step of changing the state corresponding to the data in the state information to the state instructed by the worker when the worker creates the data; and if the state is "completed", detecting at least one piece of impact data that should be affected by following a change in the work status of the data from the data-related information; and 2) influencing the impact data from the data-related information. a step of detecting secondary influence data; a step of checking whether the status of all the detected secondary influence data is "completed"; and if the status of all the secondary influence data is "complete", the state is A work guidance method comprising the steps of: changing a state corresponding to the influence data in the information during work; and displaying the state information on an interaction terminal using a correspondence table between data names and states. . 2. According to claim 1, the step of storing work schedule information that associates target data to be worked with a scheduled start date and a scheduled end date of the work; and a step of storing work schedule information in accordance with instructions from a worker. a step of associating a scheduled end date of one target data with a scheduled start date of another target data; a step of creating data-related information from the correspondence; and a step of displaying the work schedule information on an interactive terminal. A work guidance method characterized by having the following. 3. The method according to claim 1, further comprising the step of storing judgment conditions for judging the working status of data based on the content of the data or whether the data exists, and determining the working status of certain data using the judgment conditions. A work guidance method comprising a step of determining. 4. In claim 1, the type of data, a specified state that specifies the state of the data, and the type of other data whose state is changed when certain data belonging to the type corresponds to the state designation. A work guidance method comprising: detecting influence data according to claim 1; and confirming secondary influence data using data type-related information that associates the changed state with the changed state. 5. According to claim 1, the step of displaying the name of the data or the name of the work to create the data on the interaction terminal, and changing the display color of the name so that the worker can recognize the state of the data. or a step of enclosing the name in a box, and a line segment connecting the data and the impact data to show the relationship between the data for which the work has been completed and the impact data for which work can be started by completing the work for the data. Or a work guidance method characterized by having a step indicated by an arrow.