JP7326803B2 - Document management device, document management method, and program - Google Patents

Description

The present invention relates to a document management apparatus, document management method, and program.

When changing a document, the author must make the changes consistent with the document as a whole and with other documents. Therefore, it is necessary for the author to identify the impact range of the change from the document and related documents, and consider the impact and change on the relevant part.

However, when there is a huge amount of documents, it is a heavy burden for the author to search for relevant parts from them and confirm the necessity of change for each part.

Also, the document to be changed may be referenced by documents that the author does not recognize, and in that case, there is a high possibility that the contents of the referencing document will be inconsistent.

For example, Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2010-108206) and Patent Document 2 (Japanese Unexamined Patent Application Publication No. 2010-257369) have been proposed as techniques for specifying the range of influence when a specific document is changed.

In Japanese Patent Application Laid-Open No. 2002-200000, the influence range of a change is specified by providing a document file with information on documents on which the document depends and documents on which the document depends.

In Japanese Patent Application Laid-Open No. 2002-201000, the range of influence of a change is specified by directly registering in the system other documents that are affected when a certain document is changed.

However, in any of the above patent documents, all reachable ranges by documents or link information registered in the system are detected as influence ranges. Therefore, even a portion that is not actually affected is detected.

In addition, in these mechanisms, even if changes that do not affect other documents, such as correction of typographical errors and layout changes, other documents are detected as affected documents.

Therefore, in the above patent document, when the author makes a change, it is necessary to check all the documents detected by the system and examine whether or not each document needs to be changed, which is time-consuming.

An object of the present disclosure is to provide a technique for solving any of the problems described above.

According to a first aspect of the present disclosure, a document element storage unit that stores a plurality of document elements, a relationship information storage unit that stores relationship information regarding relationships between the plurality of document elements, and a plurality of document elements. a change type acquiring unit that acquires a change type for any one of the document elements; A document management comprising: an impact range identification unit that identifies; and an action determination unit that determines, based on the type of change, whether to notify the author of the document element identified by the impact range identification unit. An apparatus is provided.
According to a second aspect of the present disclosure, a change type acquisition step of acquiring a change type for any one of a plurality of document elements; an impact range identifying step of identifying a document element having a relationship with the document element to be changed among the plurality of document elements; and a document identified in the impact range identifying step based on the type of change. and an action decision step of deciding whether to notify the author of the element.

According to the present invention, for types of changes that do not affect other document elements, such as layout changes and corrections of typographical errors, the author of the document element is not notified at all. can be effectively reduced.

3 is a functional block diagram of the document management device; FIG. 3 is a functional block diagram of the document management device; FIG. FIG. 4 is a diagram illustrating a definition of a document; FIG. 11 is a diagram illustrating types of change of document elements; FIG. 4 is a diagram illustrating relationships between document elements; It is a figure which illustrates action DB. 4 is a control flow when registering a document in the document management apparatus; FIG. 10 is a control flow when changing a document element of a document registered in the document management apparatus; FIG. It is a control flow when specifying a document element related to a document element to be changed. FIG. 2 is a diagram illustrating several documents; FIG. 4 is a diagram illustrating a document element DB; It is a figure which illustrates relationship information DB. It is a figure which illustrates relationship information DB by which relationship information was added by the user. FIG. 10 is a diagram showing how document elements that are related to document element No. 6 are extracted. FIG. 10 is a diagram showing how document elements that are related to document element No. 6 are extracted. FIG. 10 is a diagram showing actions extracted from an action DB for each related document element;

(First embodiment)
A first embodiment will be described below with reference to FIG. As shown in FIG. 1, the document management apparatus 100 includes a CPU 100a as a central processing unit, a read/write RAM 100b, and a read-only ROM 100c. Then, the CPU 100a reads and executes the control program stored in the ROM 100c. The control program causes hardware such as the CPU 100a to function as a document element DB 102, a relational information DB 103, a change type acquisition section 104, an influence range identification section 105, and an action determination section .

The document element DB 102 is a specific example of a document element storage unit and stores a plurality of document elements.

The relational information DB 103 is a specific example of a relational information storage unit, and stores relational information relating to relationships between a plurality of document elements.

The change type obtaining unit 104 obtains a change type for any one of the document elements among the plurality of document elements.

Based on the relational information stored in the relational information DB 103, the influence range identification unit 105 identifies a document element having a relation with the document element to be changed among the plurality of document elements.

Based on the change type acquired by the change type acquisition unit 104, the action determination unit 106 determines whether to notify the author of the document element identified by the influence range identification unit 105. FIG.

According to the above configuration, if there is a type of change that does not affect other document elements, such as a layout change or correction of an error, the author of the document element will not be notified. Man-hours can be effectively reduced.

(Second embodiment)
The second embodiment will be described below with reference to FIGS. 2 to 16. FIG. As shown in FIG. 2, the document management apparatus 1 includes a CPU 1a as a central processing unit, a RAM 1b for free reading and writing, and a ROM 1c for reading only. Then, the CPU 1a reads and executes the control program stored in the ROM 1c. The control program causes hardware such as the CPU 1 a to function as a document registration section 2 , a relationship registration section 3 , a change type acquisition section 4 , an influence range identification section 5 , an action determination section 6 and an action execution section 7 . The control program also causes hardware such as the CPU 1a to function as the document storage unit 10, the document element DB 11, the relationship information DB 12, and the action DB 13. FIG.

The document registration section 2 registers an input document input by the user in the document storage section 10 . The document registration unit 2 also divides the input document into document elements and registers the document elements in the document element DB 11 and the relational information DB 12 .

The relationship registration unit 3 generates relationship information about relationships existing between a plurality of document elements registered in the document element DB 11 and registers the relationship information in the relationship information DB 12 . The relationship registration unit 3 also registers individual relationship information input by the user in the relationship information DB 12 .

A change type acquisition unit 4 acquires a change type for any one of a plurality of document elements.

Based on the relationship information, the influence range specifying unit 5 specifies at least one document element having a relationship with the document element to be changed among the plurality of document elements.

The action determining unit 6 determines whether to notify the author of the document element specified by the influence range specifying unit 5 based on the type of change.

Action executing section 7 executes the action determined by action determining section 6 . Specifically, for example, the action execution unit 7 notifies the author of the document element specified by the influence range specifying unit 5 of the change of the document element. Further, the action execution unit 7 presents a document including the document element specified by the influence range specifying unit 5 to the user, and saves the document changed by the user.

Document storage unit 10 stores a plurality of documents managed by document management apparatus 1 .

The document element DB 11 is a specific example of a document element storage unit. The document element DB 11 is a DB that stores a plurality of document elements forming each document. A specific example of the document element DB 11 is shown in FIG. The document element DB 11 includes, as fields, an identifier that uniquely identifies the document element, a key for the user to identify the document element (for example, a file name and characters in the document), and author information of the document element. .

FIG. 3 shows the definition of a document. As shown in FIG. 3, the smallest unit of information that can be handled as independent information is described as one topic, and similar topics are grouped together as document elements. The text of a topic consists of content such as natural language and data such as tables, or a combination of links to other documents. In the following description, a group of documents such as chapters and sections is defined as a document element. Yet another chunk may be the document element. For example, document elements can be freely defined by dividing a document into arbitrary ranges and assigning tags indicating that they are document elements to each range.

The relationship information DB 12 is a specific example of a relationship information storage unit. The relational information DB 12 stores relational information relating to relationships between a plurality of document elements registered in the document element DB 11 . A specific example of the relationship information DB 12 is shown in FIG. The relationship information DB 12 includes, as fields, the identifiers of the document elements of the relationship source and the relationship destination, and the type of relationship between them.

FIG. 5 illustrates relationships indicated by relationship information. A master-detail relationship is a relationship in which when one document element is changed, the other document element must be changed. In other words, a master-slave relationship is a relationship in which when the content of one is changed, the other must also be changed.

A detailed relationship is a relationship in which a supplementary description of one document element is described in the other document element. In other words, the detailed relationship is a relationship in which the contents to be described in one are requested to be described in the other.

A reference relationship is a relationship in which one document element has a description that instructs the other document element to refer to the other document element. In other words, a reference relationship is a relationship in which the content described in one is described in a form that refers to the other.

The action DB 13 stores actions executed by the action execution unit 7 when changing a document. A specific example of the action DB 13 is shown in FIG. Fields of the action DB 13 include the type of relationship between document elements, direction of relationship, type of change, pre-action, and post-action. A pre-action is an action performed by the action executing section 7 before the user decides to change, and a post-action is an action performed by the action executing section 7 after the user decides to change. Note that FIG. 4 exemplifies the types of changes to document elements.

Next, referring to FIG. 7, the operation of the document registration unit 2 when newly registering a document in the document management apparatus 1 will be described.

S60:
First, the document registration section 2 registers an input document input by the user in the document storage section 10 .

S61:
Next, the document registration unit 2 divides the document into chapters, sections, and paragraphs, and registers each of them in the document element DB 11 as document elements.

S62:
Next, the relationship registering unit 3 registers one document element such as from a paragraph to a section or from a section to a chapter among the plurality of document elements registered by the document registering unit 2, and a document element higher than that document element. is registered in the relationship information DB 12 as relationship information.

S63:
Further, the relationship registration unit 3 requests the user to input relationship information on the relationship between the document elements registered in the document element DB 11 in order to supplement the relationship information automatically registered in step S62. . The relationship registration unit 3 registers relationship information input by the user in the relationship information DB 12 .

Next, the operation of the document management apparatus 1 when changing document elements registered in the document element DB 11 will be described with reference to FIG.

S71:
First, the influence range identification unit 5 acquires document elements to be changed by the user from the document element DB 11 .

S72:
Next, the influence range identification unit 5 refers to the relationship information DB 12 to acquire the document elements that can be affected by the change of the document elements and the types of relationships with the document elements. Details of S72 will be described later.

S73:
Next, the change type acquiring unit 4 acquires the type of change of the document element by the user.

S74:
Next, the action determining unit 6 acquires the corresponding action from the action DB 13 based on the type of change.

S75:
Next, the action executing section 7 executes the pre-action among the actions acquired in step S74.

S76:
Next, the action execution unit 7 confirms with the user whether or not to execute the change.

S77:
Next, when the user selects change execution, the action execution unit 7 executes the post-action among the actions acquired in step S74.

S78:
The action executing section 7 also registers the changed document in the document storage section 10 .

Next, the control flow regarding acquisition of relational information (S72) in FIG. 8 will be described with reference to FIG.

S81:
First, the influence range identification unit 5 refers to the relationship information DB 12 and checks whether or not there is a record having the document element acquired in step S71 as the relationship source or relationship destination. However, at this time, the relation type of the upper document is excluded because it is processed separately in step S83.

S82:
If the record exists (S81: YES), the influence range specifying unit 5 holds all document elements having a relationship with the document element to be changed, the direction of the relationship, and the type of the relationship. If the record does not exist (S81: NO), the influence range identification unit 5 advances the process to S83.

S83:
Next, the influence range identification unit 5 refers to the relationship information DB 12 and checks whether there is a document element that is higher than the document element to be changed.

If there is a higher-level document element (S83: YES), the scope-of-influence identification unit 5 regards the document element as the document element to be changed and returns the process to S81. If the upper document element does not exist (S83: NO), the scope-of-influence identification unit 5 terminates acquisition of the relationship information, and executes the next process (S73 in FIG. 8).

An example of document system application will be described below using a design document example in IT system development. Examples of applicable documents are shown in FIG. FIG. 10 shows a requirement definition document, a function design document, a detailed design document, another document X, and a reference document Y as specific examples of documents.

FIG. 11 shows the document element DB 11 in which the document elements of each document are registered. FIG. 12 shows the relationship information DB 12 automatically generated by the relationship registration unit 3. As shown in FIG. FIG. 13 shows the relational information DB 12 after the relational information has been supplemented by the user.

As an example of change, the case of changing the topic of "1.1 Function A1" in the function design document will be described below. "1.1 Function A1" in the function design document corresponds to document element No. 6 in the document element DB 11 shown in FIG.

In this case, the influence range identification unit 5 refers to the relationship information DB 12 shown in FIG. The existing document element is acquired as shown in FIG. 14 (S81: YES, S82). 13, and acquires document element No. 5 and document element No. 4 as document elements higher than document element No. 6 (S83: YES). Further, the influence range identification unit 5 refers to the relationship information DB 12 shown in FIG. 13 and acquires the document element No. 2 as the document element to which the document element No. 4 or No. 5 is the source or destination of the relationship. (S81: YES, S82). FIG. 15 shows the relevant information extracted in relation to the document element No. 6 by the sound range specifying unit 5 in this way. In the related document column shown in FIG. 15, the document elements affected by changing document element No. 6 are extracted.

Next, the action determination unit 6 acquires the corresponding action from the action DB 13 based on the document element affected by the change of the document element No. 6 and the type of change to the document element No. 6. Actions acquired here are shown in FIG.

Next, the action execution unit 7 executes the acquired action. Specifically, the action execution unit 7 first executes the pre-action shown in FIG. 16 . That is, the action execution unit 7 presents the contents of "1. Requirement A", "1.1 Details A1", and "Another Document X" to the user who is going to change the document element No. 6, and prompts the user to , to recognize the document elements affected by the change in document element number 6.

Next, the user confirms the contents presented by the action executing section 7 and selects whether to continue to change the document element No. 6 or cancel the change.

If the user selects to execute the change, the action executing section 7 executes the post-action shown in FIG. 16 after the change by the user. That is, the action execution unit 7 notifies the author of "1.1 Details A11" and "Another Document X" that "1.1 Function A1" in the function design document has been changed.

According to the above configuration, since the notification itself is not performed for the types of changes that do not affect other document elements, such as layout changes and error corrections, it is possible to further effectively reduce the author's checking man-hours.

The second embodiment has been described above. The second embodiment has the following features.

That is, the document management apparatus 1 includes a document element DB 11 as a document element storage section, a relationship information DB 12 as a relationship information storage section, a change type acquisition section 4, an influence range identification section 5, and an action determination section 6. FIG. The document element DB 11 stores a plurality of document elements. The relational information DB 12 stores relational information relating to relationships between a plurality of document elements. A change type acquisition unit 4 acquires a change type for any one of a plurality of document elements. Based on the relationship information, the influence range specifying unit 5 specifies document elements that have a relationship with the document element to be changed among the plurality of document elements. The action determining unit 6 determines whether to notify the author of the document element specified by the influence range specifying unit 5 based on the type of change. According to the above configuration, since the notification itself is not performed for the types of changes that do not affect other document elements, such as layout changes and error corrections, it is possible to further effectively reduce the author's checking man-hours.

Also, the relationship indicated by the relationship information includes at least one of the following.
(1) A master-slave relationship that requires modification of one document element when the other document element is modified.
(2) A detailed relationship in which a supplementary description of one document element is described in the other document element.
(3) A reference relationship in which one document element has a description indicating reference to the other document element.

Also, the type of change includes at least one of addition, deletion, and change.

The document management method includes a change type acquisition step (S73), an impact range identification step (S72), and an action determination step (S74). According to the above-described method, since the notification itself is not performed for the types of changes that do not affect other document elements, such as layout changes and error corrections, it is possible to further effectively reduce the author's checking man-hours.

For example, the second embodiment can be modified as follows.

For example, the document management apparatus 1 may have a document editing function.

This document editing function is assumed to have a function of creating related documents by specifying document elements. By doing so, the user can perform the operation of registering the related information (S63) at the same time as the document is edited.

Also, selection results of user selection (S76) at the time of document change may be accumulated. By doing so, it becomes possible to recommend a response to the user when the same change is made next time.

In the above examples, the programs can be stored and delivered to computers using various types of non-transitory computer readable media. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (eg, floppy disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg, magneto-optical disks). Examples of non-transitory computer-readable media further include CD-ROM (Read Only Memory), CD-R, CD-R/W, semiconductor memory (eg, mask ROM). Examples further include PROM (Programmable ROM), EPROM (Erasable PROM), Flash ROM, RAM (random access memory). The program may also be delivered to the computer on various types of transitory computer readable medium. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. Transitory computer-readable media can deliver the program to the computer via wired channels, such as wires and optical fibers, or wireless channels.

100 document management device 102 document element DB
103 Relationship information DB
104 Change type acquisition unit 105 Influence range identification unit 106 Action determination unit

Claims (5)

a document element storage unit that stores a plurality of document elements;
a relationship information storage unit that stores relationship information relating to relationships between the plurality of document elements;
a change type acquisition unit that acquires a change type for any one of the plurality of document elements;
an impact range identification unit that identifies, based on the relationship information, a document element having a relationship with the document element to be changed among the plurality of document elements;
an action execution unit that executes a pre-action and a post-action based on the type of change;
with
The pre-action is an action executed by the action execution unit before a user decides to make a change. making the user aware of the document elements affected by the change;
The post-action is an action executed by the action execution unit after the user decides to change, and notifies the author of the document element identified by the scope of influence identification unit.
Document management device. The document management device according to claim 1,
The relationship indicated by the relationship information is
a master-detail relationship that requires one document element to change when the other document element changes,
a detailed relationship in which the supplemental description of one document element is given in the other document element;
a reference relationship in which one document element has a statement pointing to a reference to the other document element;
including at least one of
Document management device. The document management device according to claim 1 or 2,
The type of change includes at least one of addition, deletion, and change,
Document management device. a change type obtaining step in which the computer obtains a change type for any one of the plurality of document elements;
an impact range identification step in which a computer identifies, from among the plurality of document elements, a document element having a relationship with the document element to be changed, based on relationship information about the relationship between the plurality of document elements;
an action execution step in which a computer executes a pre-action and a post-action based on the type of change;
including
The preliminary action is an action to be executed in the action execution step before the user decides to change, and by presenting the contents of the document element identified in the impact range identification step to the user, making the user aware of the document elements affected by the change;
The post-action is an action to be executed in the action execution step after the user decides to change, and notifies the author of the document element identified in the impact range identification step.
Document management method. A program for causing a computer to execute the document management method according to claim 4.

Images