JPH0816558A - Document preparation supporting system - Google Patents

Abstract

PURPOSE:To relieve the burden of a document preparing person at the time of preparing a document by preparing an arbitrary part of a document as a separate file, using the file as parts or processing the substance of an arbitrary part of the document as parts as it is and preparing the document by utilizing these parts. CONSTITUTION:A document XXX 101 stored in a document data base is displayed, a starting point 102 and a termination point 103 of the document XXX 101 are designated and the range of content fghi 104 desired to be made parts is designated in a document XXX 105. A parts file YYY 107 is prepared by surrounding before and behind the designated range by prescribed marks 108 and 109. Next, a prescribed mark 106 is inserted into the original document XXX 105 and the contents stored in the parts file is automatically deleted from the original document. Thus, because the storage location of a substance can be recognized by the mark 106 as to the contents deleted from the original document XXX 105, the existent contents can be constructed of parts without entirely losing the information before parts processing at the time of a reference.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a text creation support system using a computer, and in particular, it is possible to divide a text into parts, to compose another text using the partsized text, and to create a plurality of texts. The present invention relates to a text creation support system that uses the relationships between the elements described above.

[0002]

2. Description of the Related Art In recent years, computerized textual information has become common. In particular, recently, it is about to go beyond the stage of simply using a computer to create sentences, and to go further into the stage of improving the sentence creating function, standardizing the sentence information format, and ensuring the quality of sentences.

Under such circumstances, in order to improve the function of creating texts, there is a movement to convert existing texts into parts. This kind of movement has come to the fore, because in the case of multiple documents created in a certain fixed flow, the same or related content is often described repeatedly, so the text is not This is because it is considered that the efficiency of creating a new sentence can be improved by recreating the text and reusing the component.

Further, in order to guarantee the quality of text, a standardized markup language (SGML: Stan) which is an international standard.
dard Generalized Markup Language) has begun to standardize sentence structures. This kind of movement has emerged because in order to guarantee the quality of the text, the text is standardized,
This is because it is considered necessary to make sure that the necessary contents have already been described.

[0005]

By the way, when a sentence is divided into parts, in order to accurately inherit the sentence information, it is necessary to match the version numbers between the sentence to be a part and the document in which the part is reused. It is necessary to take.

In order to guarantee the quality of text, it is necessary not only to check the text structure but also to confirm that the content is correct and complete.
However, there is no conventional example of a text creation support system that considers even matching of version numbers and confirmation of text content.

The present invention has been made in view of the above-mentioned circumstances, and makes it possible to create a document by converting an existing document into a component and reusing the component, and to create a document between a plurality of created documents. An object of the present invention is to provide a document creation support system capable of supporting confirmation of document contents, confirmation of consistency between parts and version numbers, confirmation of description contents and prevention of description omission.

It is an object of the present invention to provide a text creation support system which can check the consistency between parts and version numbers and can check the document contents among a plurality of created documents. .

[0009]

The text creation support system of the present invention is configured as follows to solve the above-mentioned problems.

(1) That is, the first text creation support system of the present invention is a text creation support system for converting at least a part of contents described in a document into parts,
When the content to be made into a part is specified for the document, the part has the content of the part, the name indicating that the part is held, the document name of the document that refers to the part, and the identifier according to the type of the part. Along with the possession mark, it is recorded in a file separate from the document and indicates the name of the part, the file name and file format of the file that stores the content of the part, the identifier according to the type of the part, and the part A part reference mark having version number information is added to a position where a part of the document is designated, and the content of the part is deleted from the document (corresponding to claim 1).

(2) Further, the second text creation support system of the present invention is a text creation support system that makes at least a part of the contents described in one document into a component so that another document can refer to it. Then, when the content to be made into a component is specified for one document, a component having a name indicating that the component is owned, a document name of a document that refers to the component, and an identifier according to the type of the component A holding mark is added before and after the part, the name indicating that the part is referenced, the part-holding document name, the file format of the document holding the part, the identifier according to the part type, and the version number of the part It is characterized by including inserting a part reference mark having information and a position where a part of another document is referred to (corresponding to claim 2).

(3) The third sentence creation support system of the present invention is the sentence creation support system of (1) or (2), wherein when the content of the part is changed in the document referring to the part, Save the file or document with version control under version control, update the version information of the part in the part reference mark, and refer to the original version of the part The version number information of the parts is updated (corresponding to claim 3).

(4) Next, the fourth text creation support system of the present invention is the text creation support system according to any one of (1) to (3), wherein the content of the part is changed in the document referring to the part. If you do, save the file or document that has the part under version management, update the version information of the part in the part reference mark, and check that the original version of the part exists in another document. The version number information of the component in the component reference mark is updated (corresponding to claim 4).

(5) Next, the fifth sentence creation support system of the present invention changes the content of a part in a document that refers to the part in the text creation support system according to any one of (1) to (3). When updating, it is possible to select whether to update the information in the component holding mark existing in the file or document containing the component. When updating, save the file or document containing the component under version number control. Then, the version number information in the part reference mark is updated, and the version number information of the part in the part reference mark existing in another document that refers to the original version number of the part is updated. It is characterized in that a file or document having a part is stored under version number management, the version number information in the part reference mark is updated, and the part holding document name is deleted (corresponding to claim 5).

(6) Next, a sixth sentence creation support system of the present invention, in the sentence creation support system according to any one of (1) to (5), sets the content of a part in a file or a document having the part. When changing, the version number information of the component in the component reference mark is updated for all the documents that refer to this component (corresponding to claim 6).

(7) Next, the seventh text creation support system of the present invention is the text creation support system according to any one of (1) to (5), wherein the content of the part is included in a file or a document having the part. When changing, it is possible to select for each document whether or not to update the contents of the document that refers to this part. When updating, the part version information in the part reference mark is updated and not updated. In this case, the component version number information in the component reference mark is not updated, and the corresponding document name is deleted from the component reference document name in the component holding mark existing in the document having the changed component (claim 7). Corresponding to).

(8) Next, the eighth sentence creation support system of the present invention is the sentence creation support system according to any one of (1) to (7), wherein elements described in one document and other elements are described. When an element described in a document is described in an associated manner, a name indicating that the element is associated with another document, an identifier, and a file name of another document are placed before and after the element in one document. Is added, and before and after an element in another document, a takeover destination mark having a name indicating that the element is inherited from another document, an identifier, and a file name of one document is added. It is characterized by adding (corresponding to claim 8).

(9) Next, a ninth sentence creation support system of the present invention is the sentence creation support system according to any one of (1) to (8), wherein a plurality of documents are sequentially read according to a certain flow. When creating, a name that indicates that the description of an element is suspended before and after the element when the content of the element that must be described in one document in the flow cannot be described for some reason. And a process control mark having an identifier and information indicating a time or work at which the description of the element must be completed (corresponding to claim 9).

(Embodiment of the Invention) In the inventions (1) to (9) described above, one document may be stored in one file, or may be stored in a plurality of files in a distributed manner. You may do it.

[0020]

According to the first sentence creation support system of the present invention, the content of a component and the component possession mark are recorded in a file different from the document by designating the content to be segmented for the sentence. It Next, a part reference mark is added to the position where the part of the document is designated. Further, the content of the part is deleted from the document.

According to the second text creation support system of the present invention, the content holding mark is added before and after the component by specifying the content to be componentized for one document. Next, a part reference mark is inserted at a position where a part of another document is referred to.

According to the third sentence creation support system of the present invention, when a document is displayed, the content of the component is displayed instead of the component reference mark. According to the fourth sentence creation support system of the present invention, when the content of a part is changed in a document that refers to the part, a file or a document having the part is stored under version number management. Next, the version number information of the component in the component reference mark is updated. Then, the version number information of the part in the part reference mark existing in another document that refers to the original version number of the part is updated.

According to the fifth sentence creation support system of the present invention, when the content of a component is changed in a document that refers to the component, when the information in the component holding mark is updated,
A file or document having parts is saved under version control. Next, the version number information in the part reference mark is updated, and the version number information of the part in the part reference mark existing in another document that refers to the original version number of the part is updated.
On the other hand, when the information in the parts holding mark is not updated, the file or document having the parts is saved under version number management. Next, the version number information in the component reference mark is updated and the component holding document name is deleted.

According to the sixth sentence creation support system of the present invention, when the content of a component is changed in a file or a document having the component, the component reference mark is applied to all documents that refer to this component. The version number information of the parts inside is updated.

According to the seventh sentence creation support system of the present invention, when the content of the document referring to the component is updated, the component version number information in the component reference mark is updated. On the other hand, if the contents of the document referencing the part are not updated, the part version number information in the part reference mark is not updated, and the part reference document name in the part holding mark existing in the document having the changed part The document name is deleted.

According to the eighth sentence creation support system of the present invention, a takeover source mark is added before and after an element in one document. Then, a takeover destination mark is added before and after an element in another document.

According to the ninth sentence creation support system of the present invention, a process control mark is added before and after an element that must be described in one document in the flow.

[0028]

Embodiments of the present invention will be described below with reference to the drawings. <System Configuration of Embodiment> FIG. 2 is a system configuration diagram of the text creation support system of the present invention. As is clear from FIG. 2, the main storage device 1 is provided in this system. The main storage device 1 includes a program of the present system, a structured document management database device program, a version number management device program, and a mark input device program. A central processing unit (CPU) 2 that executes a system program is connected to the main storage device 1. An input / output control device 3 for controlling input / output between a non-volatile memory and a volatile memory is connected to the CPU 2.

Here, the structured document management database device stores the structured document and manages the version number for each structure. Note that "structured document" means "a document in which the logical content is subdivided (preface, body, postscript, etc.) and hierarchically (department, chapter, section, paragraph, etc.) and described". To do.

Here, the non-volatile memory stores the design information of the document, and is composed of a document file 6, a parts file 7, a holding time limit management information file 3 and a document development process information file 9.

Further, the volatile memory is a display text content buffer 10, a designated range buffer 11 for temporarily accumulating user input information and information regarding processing in the present system,
Specified range content buffer 12, in-mark information buffer 1
3, a document list buffer 14, an element list buffer 15, and a component position management information buffer 16.

The input / output control device 3 is connected to a keyboard 5 for the user to input various information and a display 6 for displaying the contents of a document to be created, information about the document and a message to the user.

[0033]

First Embodiment Next, a first embodiment will be described with reference to FIG. The first embodiment is an example in which a part of the contents described in the document is made into a component.

First, the document XXX (101) stored in the document database is displayed. And document XX
By specifying the start point (102) and the end point (103) for X, the content "fghi" (10
Specify the range of 4).

Then, the mark <ext name = XX
X id = 002 (108) and </ ext> (10
In 9), a part file YYY that encloses the front and back of the specified range is generated (107). Here, "ext" in the mark is
A name indicating that the element is referred to in another document, "name =
“XXX” is a document name of a reference source document, and “id = 002” is an identifier of a component element (information for uniquely defining and discriminating each element).

Next, the mark <ref is added to the original document XXX.
name = YYY ver = 1.0 type = te
Insert xt id = 002> (106) and automatically delete the contents stored in the part file from the original document.
Here, “ref” in the mark is a name indicating that another document is referred to, “name = YYY” is a file name of the generated component, “ver = 1.0” is version information of the component,
"Type = text" is the file format of the component, "id
= 002 ”is a component element identifier.

By the above processing, the original document XXX (10
Since the contents deleted from 5) can recognize the storage position of the substance by the mark, the existing contents can be composed of the parts without losing the information before the parts conversion at the time of reference.

FIG. 4 is a flowchart showing the flow of the above processing. In FIG. 4, the (reference) original document is first displayed (S401). Next, the component registration start position is designated (S402) and the component registration end position is designated (S403). Then, the component is created (S4
04). Next, a mark is inserted into the (reference) original document (S405). Finally, the component contents are deleted from the (reference) original document (S406).

It should be noted that the mark <ref from the part reference source document
It is possible to display the reference destination part list (111) by reading the information of the reference destination document name and the component element identifier included in the>. Further, the reference source document list (112) can be displayed by reading the information of the reference source document name and the component element identifier included in the mark <ext> from the reference destination component. Further, the reference destination parts list (111) and the reference source document list (112)
It is also possible to display each entity from, and it is also possible to mutually confirm the usage status of the parts.

The flow of the above processing is shown in flowcharts in FIGS. 5 and 6. As shown in FIG. 5, the reference source document is first displayed (S501). Next, the referenced component is selected (S502). Finally, the reference destination part is displayed (S503).

Further, as shown in FIG. 6, the parts are first displayed (S601). Next, a reference source document list is displayed (S602). Then, the reference source document is selected (S6).
03). Here, the display portion is selected (S60
4) If the reference source part is selected, the reference source element list screen is displayed (S605). Then, the reference source element is selected (S606). Finally, the reference source part is displayed (S607).

On the other hand, when the entire reference source document is selected in S604, the reference source document is displayed (S608).
Then, the referent part is displayed (S609).

[0043]

Second Embodiment Next, a second embodiment will be described with reference to FIG. In the second embodiment, a part of the contents described in the document XXX (201) is used as a part of another document YYY (2).
04) is an example of the case of use.

First, the documents XXX (201) and YYY
(204) is displayed. Then, by designating the start point (202) and the end point (203) for the document XXX, the parts to be treated as parts are designated.

Then, the part to be treated as a part is marked <ext name = XXX id = 003> (20
7) and </ ext> (208) (see 206). Here, “ext” in the mark is a name meaning that it is referred to as a component from the outside, “name = Y”.
“YY” is the document name of the reference source document, and “id = 003” is the component element identifier.

Next, the part reference source file YYY (20
In 9), specify the position (205) where you want to refer to the part, and mark <ref name = XXX ver = 1.0 t
Insert ype = text id = 003> (210). Here, “ref” in the mark indicates a name that refers to a component, “name = XXX” is a file name in which the reference component exists, “id = 003” is an element identifier of the reference component, and “ver = 1” . ”Is the version number information of the referenced part,
“Type = text” is the file format information of the referenced part.

By the above processing, even if the entity of the component exists in the reference destination file, the component reference source file
The mark allows the storage position of the component to be recognized, and the document can be composed of the component without having the entity of the component.

FIG. 8 is a flow chart showing the flow of the above processing. As shown in FIG. 8, the reference source document is first displayed (S801). Next, the reference document is selected (S802). Then, the referenced document is displayed (S803). Next, the component reference start position is designated (S
804), and the part reference end position is designated (S).
805). Then, a mark is inserted in the reference document (S806). Finally, a mark is inserted in the reference source document (S807).

It should be noted that the mark <ref from the parts reference document
It is possible to display the reference destination part list (111) by reading the information of the reference destination document name and the component element identifier included in>.

The reference source document list (112) can also be displayed by reading the information of the reference source document name and component element identifier contained in the mark <ext> from the reference destination component.

Further, displaying each entity from the reference destination parts list (111) and the reference source document list (112),
It is also possible to mutually confirm the usage status of parts. As described above, FIG. 9 is a flowchart showing the flow of the process when confirming the reference destination part, and FIG. 10 is a flowchart showing the flow of the process when confirming the reference source document. .

First, in FIG. 9, the reference document is first displayed (S901). Next, the referenced element is selected (S902). Here, the display portion is selected (S9
03), if the entire reference document is selected, the entire reference document is displayed (S904). On the other hand, if the reference element is selected in S903, the reference element is displayed (S905).

In FIG. 10, the referenced document is first displayed (S1001). Next, the reference destination element is designated (S1002). Then, the reference document list is displayed (S1003). Next, the reference source document is selected (S1).
004). Here, the display portion is selected (S100
5) If the reference source part is selected, the reference source element list is displayed (S1006). Next, the reference destination element is selected (S1007). Finally, the reference source part is displayed (S1008). On the other hand, when the entire reference source document is selected, the reference source document is displayed first (S100).
9). Finally, the referent part is displayed (S1110).

[0054]

Third Embodiment Next, a third embodiment will be described with reference to FIG. First, when the document YYY (304) to be displayed on the screen is designated, a buffer for the document YYY is generated, and the document YYY is generated.
"ABCDE" on the first line of is read into the buffer. Next, the mark <ref> (305) is read and “re
It is recognized that the document YYY refers to a component in another document by the mark name “f”.

Next, the attributes contained in the mark <ref> (305) are read, and the document XXX, version 1.
0, type text, id 003,
The mark <ext> of the document XXX (301) is searched, and the element having the id attribute 003 is searched for in the mark <ext>.

The mark <ext name = YYY i described at the start position and end position of the search result
Document XXX corresponding to the contents by recognizing the range of elements by d = 003> (302) and </ ext> (303)
"Fghi" on the fourth line of is read into the buffer. Finally, "JKLMNO" in the last line of the document YYY is fetched in the buffer.

By the above processing, the document YYY is displayed on the screen in the form of incorporating the parts (306). Further, when the component element is read into the buffer, the component start position and end position in the buffer are stored in byte positions (307), and the component element in the display content of the reference source document is recognized.

FIG. 12 is a flow chart showing the flow of the above processing. In FIG. 12, the document buffer to be displayed first is generated (S1201). Next, the display document (reference source) is read (S1202), the reference mark attribute is read (S1203), and the component element (reference destination) is read (S1204). Then, the reference destination element is inserted into the corresponding portion of the display document buffer (S120).
5). Next, the component position storage area is set (S120).
6). Finally, the contents of the document buffer are displayed (S120).
7).

[0059]

Fourth Embodiment Next, a fourth embodiment will be described with reference to FIG. The fourth embodiment uses the document YYY (404) and the document ZZZ.
In this example, (406) refers to an element (hereinafter referred to as a reference destination part) in the document XXX (401).

First, "fghi" (see 407), which is the content of the reference destination part in the document XXX, is converted into "FGHI" (40
8)), it is determined from the component position management area whether the updated portion is a component.

If the updated portion is not a part, editing can be continued as it is. If the updated portion corresponds to a part, the mark <ref> (405) existing in the reference source document YYY (404) is added. Referenced document name nam included
e = XXX, component element identifier id = 003, and version number information ver = 1.0 are read. In addition, mark <ref
> Indicates that the component is referenced.

Then, the document XXX (401) is searched,
A mark included in the document XXX and having a matching id <ext
The range enclosed by the> (402) and the mark </ ext> (403) is recognized as a component, and the component update is started. The mark <ext> indicates that it is referenced from another document.

At this time, based on the document names YYY and ZZZ of the reference source document included in the mark <ext>, the mark <ref> (present in all the documents (411, 414) referencing the part is indicated. (412, 415) automatically updates all the version number information (413, 416) of the parts included in 412, 415).

Here, it is also possible to select, for each document, whether or not to update the contents of the document that refers to the part. Which of these updates is selected is designated by, for example, a conversational window (409).

Then, when the update of all the other documents that refer to the part in the document XXX (410) is selected, the marks <ref> (present in the reference source documents YYY (411) and ZZZ (414) are selected. The version number information ver (413, 416) of the component included in 412, 415) is updated from "1.0" to "1.1" in all the referencing documents.

Next, a description will be given of the processing in the case of selecting, for each document, the update of the document that refers to the part in the document XXX (417). However, the reference source document YYY (420) does not update the referenced component, and the reference source document ZZZ (4
In step 23), the referenced parts are updated.

First, regarding the document YYY (420),
The version number information ver (422) of the component included in the mark <ref> (421) is not updated and the previous version number is taken over and saved.

On the other hand, for the document ZZZ (423),
The version number information ver (425) of the part included in the mark <ref> (424) existing in the same document is updated. As a result, even if the reference destination part is updated, the parts before and after the update can be freely selected. In this case, in the referenced document XXX (417), the other document name (418, 419) to which the part is referenced is the version number of the part specified in the reference source document YYY, ZZZ (420, 423). It is automatically rewritten accordingly. This makes it possible to eliminate the misalignment between the document and the parts without directly considering the editing of the parts.

FIG. 14 is a flowchart showing the flow of the above processing. In FIG. 14, the reference source document is first displayed (S1401). Next, it is determined whether the updated part is the "reference target part" or the "reference source document" (S1402). If it is determined that the "reference source document is the entire document" in S1402, the process returns to S1401. If it is determined in S1402 that it is a "referenced part", the referenced part is updated (S1403). Then, it is determined whether the other document that refers to the reference destination part is "updated all documents at once" or "updated for each document" (S1404).

When "all document batch update" is selected in S1404, the reference marks in the (reference source) other documents are searched for for all the reference source other documents (S140).
5) Update the version number attribute of the reference mark (S140)
6). Note that steps S1405 to S1406 are repeatedly executed.

On the other hand, when "update for each document" is selected in S1404, it is determined whether or not the selected other reference source document is to be updated (S140).
7). If it is determined to update in S1407, the reference mark in the document is searched (S1408). Then, the version number attribute of the reference mark is updated (S1409). S
If it is determined not to update in 1407 and after S1409, the reference source document name in the component is updated (S141).
0). Note that S1407 to S1410 are repeatedly executed.

[0072]

Fifth Embodiment Next, a fifth embodiment will be described with reference to FIG. The fifth embodiment is a document YYY (505) and a document ZZZ.
In this example, (507) refers to an element (hereinafter referred to as a reference destination part) in the document XXX (501).

First, "fghi" (see 509), which is the content of the reference destination part in the document XXX, is converted into "FGHI" (51
(See 0)), the mark <ext> existing in the document XXX (501) including the part to be changed.
Document names YYY and Z of the reference source document included in (502)
Based on ZZ (504), marks <ref> existing in all documents (505, 507) that refer to the document.
All the version number information of the parts included in (506, 508) is automatically updated. The mark <ext> indicates that the document is referenced by another document, and the mark <ref> indicates that the component is referenced.

Here, it is also possible to select, for each document, whether or not to update the contents of the document referring to the component.
Which of these updates is selected is specified by, for example, a conversational window (511).

Then, when the update of all other documents that refer to the parts in the document XXX (512) is selected, the marks <ref> (present in the reference source documents YYY (513) and ZZZ (516) are selected. The version number information ver (515, 518) of the component included in 514, 517) is updated from "1.0" to "1.1" in all the referencing documents.

Next, a description will be given of the processing in the case of selecting, for each document, the update of the document which refers to the part in the document YYY (522). However, the reference source document YYY (420) does not update the referenced component, and the reference source document ZZZ (4
In step 23), the referenced parts are updated.

First, regarding the document YYY (522),
The version number information ver (524) of the component included in the mark <ref> (528) is not updated and the previous version number is taken over and stored as it is.

On the other hand, for the document ZZZ (525),
The version number information ver (527) of the part included in the mark <ref> (526) existing in the same document is updated. As a result, even if the referenced part is updated, the parts before and after the update can be freely selected. In this case, another document name (5
20, 521) is automatically rewritten according to the version number of the component specified in the reference source document (522, 525).
As a result, it is possible to eliminate the deviation of the consistency between the document and the part that occurs when the part is updated.

FIG. 16 is a flow chart showing the flow of the above processing. In FIG. 16, the reference source document is displayed first (S1601). Next, it is determined whether the updated part is the "reference target part" or the "reference source document" (S1602). If it is determined in S1602 that the document is the "reference source document", the process returns to S1601. If it is determined in S1602 that it is a "reference destination component", the reference destination component is updated (S1603). Then, it is determined whether the other document which refers to the reference destination part is "updated all documents at once" or "updated for each document" (S1604).

When "update all documents collectively" is selected in S1604, all reference source other documents are searched for reference marks in (reference source) other documents (S160).
5) The version number attribute of the reference mark is updated (S160).
6). Note that S1605 to S1606 are repeatedly executed.

On the other hand, when "update for each document" is selected in S1604, it is determined whether or not the selected reference source other document is to be updated (S160).
7). If it is determined to update in S1607, the reference mark in the document is searched (S1608). Then, the version number attribute of the reference mark is updated (S1609). S
When it is determined that the update is not performed in 1607 and after S1609, the reference source document name in the component is updated (S161).
0). Note that S1607 to S1610 are repeatedly executed.

[0082]

Sixth Embodiment Next, a sixth embodiment will be described with reference to FIG. The sixth embodiment sets a certain document XXX (601) in the setting of element information that is mutually related between a plurality of documents.
A description about the element (602) described therein (the contents described in each document may not be exactly the same because they are mutually related elements) is described in another document YYY (603).
Is also an example (see 604).

First, the mark <rel id = 003 is added to the element (608) in the takeover source document XXX (605).
name = YYY> (606) and </ rel> (60
7) is added to surround the element range before and after. The mark <ref> indicates that the component is referenced, and r
el is a name indicating that the element is inherited to another document, id =
003 is the identifier of the element, and name = YYY is the document name of the takeover destination document.

Further, in the related element (612) of the takeover destination document YYY (609), the mark <refrel ri is set.
d = 003 name = XXX> (610) and </ rr
By adding efrel> (611), the front and back of the range are enclosed, and the relationship between the elements (608, 612) between the plural documents XXX and YYY is stored. In the mark, "refrel" is a name indicating that the element is inherited from another document, "rid = 003" is an identifier of the mark attached to the inheritance source element, and "name = XX".
“X” is the document name of the takeover source document.

FIG. 18 is a flow chart showing the flow of the above processing. In FIG. 18, the takeover source document and the takeover destination document are displayed first (S1801). Then, the start position and the end position of the takeover source element are designated (S1802). Next, the start mark and end mark of the takeover destination element are inserted (S1803). And
The start position and end position of the takeover destination element are designated (S1804). Next, the start mark and end mark of the takeover destination element are inserted (S8005).

When referring to the related element that has been taken over, first, the displayed original document XXX (6
Specify the element of 05) and select the command for displaying the list of transfer destinations. Then, a list (613) of document names using the related element is displayed. Here, when the destination document name YYY (614) of the related element to be referred to is selected, it is inherited from the inheritance source document / element (608) based on the above information (the mark added to the inheritance source and the mark added to the inheritance destination). The location of the destination document / element (612) can be traced and the content of each element can be displayed (615). As a result, the description state of the contents that require the description of the related elements is confirmed, and the omission of the description of the mutually related necessary items is prevented.

FIG. 19 is a flow chart showing the flow of processing when referring to the contents of the takeover destination element. In FIG. 19, the takeover source document is first displayed (S1901). Next, the reference command of the takeover destination element is selected (S1902). Then, a list of takeover destination documents is displayed (S1903). Next, the takeover destination document is selected (S1904). Then, a list of takeover destination elements is displayed (S1905). Next, the takeover destination element is selected (S1906). Finally, the takeover destination element is displayed (S1907).

[0088]

Seventh Embodiment Next, a seventh embodiment will be described with reference to FIG. The seventh embodiment is an example in which a plurality of documents are sequentially created in accordance with a predetermined flow. Specifically, document XXX to document YYY, and document YY
A document ZZZ is created from Y. That is, it can be said that these document contents are related to each other, the document YYY is a detailed version of the document XXX, and the document ZZZ is a detailed version of the document YYY (see 701).

First, a document type created in a series of operations (in the above example, a document type such as a basic design document, a functional design document, a detailed design document), a document creation order, and an identifier for defining a series of work flows. Information is created in advance as a document development process management information file (710). Here, the information of the identifier is, for example, id = 1 of the above flow, and id = for another flow.
2 uniquely defines the flow (see 711). Then, when the editing of a certain document is started, it is judged from the document type of the document to which flow the document belongs, and the document type and the creation order created in the flow are recognized.

Next, when temporarily holding an element that must be described in a certain document XXX (702), mark <holding time limit = FD id = 002> (7
04) and </ reservation> (705) are inserted before and after the place where the element should originally be described, thereby suspending the description of the element. Here, "Hold" in the mark
Is a name indicating that the description of the element is reserved, "id = 00"
“2” is the identifier of the suspended element, and “deadline = FD” is the deadline as information for indicating the time when the description of the suspended element must be completed, that is, the functional design document (FD).
This indicates that the description of the suspended element must be completed before the start of the creation of the document YYY created in the process.

Furthermore, for each flow, the document name in which the pending element to be resolved by the designated deadline exists, the identifier of the pending element, the deadline indicating the completion time of the description of the pending element, and the status flag (1 A pending term management file (712) for storing: resolved, 0: unresolved is created.

FIG. 21 is a flow chart showing the flow of processing when the element suspension is set as described above. In FIG. 21, a document is first created (S210).
1). Next, the reserved element start position is designated (S210).
Along with 2), the reserved element end position is designated (S21).
03). Then, a holding mark is inserted (S210).
4). Finally, the hold time limit management file is set (S2
105).

When the document YY (706) of a certain process is created, when the document creation is selected, the document type is discriminated, and whether the document is designated as the deadline of the hold deadline management file is checked. Check automatically. If it is not specified, the document YYY can be created as it is. However, if the process is specified as the hold time limit, the status flag (713) in the hold time limit management file (712) indicates that the elements held in the document XXX Check if the description is complete. If there is no reserved element, document Y
You can start creating YY.

However, if there is a reserved element, a warning (707) indicating that the reserved element must be described and a list of undescribed elements (708) are displayed, and the corresponding portion of the document including each element is displayed. Is displayed in an editable state (706) to prompt the description of descriptable elements. As a result, if there is a reserved element that has not been described by the deadline, it is possible to prevent omission of the description of the element that should be described in the document by preventing the next work.

Further, FIG. 22 is a flow chart showing the flow of processing in the case where the omission of the description of the pending element is pointed out and the description of the pending element is completed. As shown in FIG. 22, first, the creation of the document of the next process, which has the holding deadline, is started (S2201). Next, it is determined whether the description state of the reservation element is "undescribed" or "description completed" (S2202). "Not described" in S2202
If it is determined that the description request message is displayed (S2203). Next, it is determined whether the reserved element is “described” or “not described” (S2204). S2204
If it is determined to be "describe" in step 2, the edit screen of the document including the holding element is displayed (S2205). Then, the description of the holding element is completed (S2206), and the process returns to S2202.

On the other hand, if it is determined in S2202 that "described", the document of the process designated as the hold time limit is edited (S2207). After S2207 and S22
When it is determined in "04" that "not described", the editing of the document of the process designated as the holding deadline ends (S2).
208).

[0097]

According to the sentence creation support system of the present invention, an arbitrary part of a document is created as a separate file and made into a part, or an arbitrary part of a document is treated as a part without changing the entity, and these parts are handled. By using the document to create the document, it is possible to reduce the burden on the document creator when creating the document.

Further, according to the text creation support system of the present invention, when the document composed of the parts is updated and the part is updated, the version numbers of the parts and the document using the parts are synchronized. As a result, it is possible to confirm the consistency between the parts and the version numbers. This also prevents inconsistency in the description content between the document and the part.

Further, according to the text creation support system of the present invention, it is possible to confirm the document contents among a plurality of created documents by associating the related elements among the plurality of documents. There is.

Then, by temporarily suspending the essential elements in the document and setting the suspending deadline, when starting the document work of a certain process, it is possible to confirm the suspending element for which the process is due. As a result, it is possible to prevent the omission of description of essential elements.

[Brief description of drawings]

FIG. 1 is a diagram showing a principle flow of the present invention.

FIG. 2 is a configuration block diagram of an embodiment of the present invention.

FIG. 3 is a diagram illustrating a first embodiment.

FIG. 4 is a flowchart showing a flow of processing in the first embodiment.

FIG. 5 is a flowchart showing a flow of processing in the first embodiment.

FIG. 6 is a flowchart showing the flow of processing in the first embodiment.

FIG. 7 is a diagram illustrating a second embodiment.

FIG. 8 is a flowchart showing a processing flow in the second embodiment.

FIG. 9 is a flowchart showing the flow of processing in the second embodiment.

FIG. 10 is a flowchart showing a processing flow in the second embodiment.

FIG. 11 is a diagram illustrating a third embodiment.

FIG. 12 is a flowchart showing the flow of processing in the third embodiment.

FIG. 13 is a diagram illustrating a fourth embodiment.

FIG. 14 is a flowchart showing a processing flow in the fourth embodiment.

FIG. 15 is a diagram illustrating a fifth embodiment.

FIG. 16 is a flowchart showing a flow of processing in the fifth embodiment.

FIG. 17 is a diagram illustrating a sixth embodiment.

FIG. 18 is a flowchart showing a processing flow in the sixth embodiment.

FIG. 19 is a flowchart showing the flow of processing in the sixth embodiment.

FIG. 20 is a diagram illustrating a seventh embodiment.

FIG. 21 is a flowchart showing the flow of processing in the seventh embodiment.

FIG. 22 is a flowchart showing the flow of processing in the seventh embodiment.

[Explanation of symbols]

 1 ... Main storage device 2 ... CPU 3 ... Input / output control device 4 ... Display 5 ... Keyboard 6 ... Document file 7 ... Parts file 8 ... Holding date management information File 9 ... Document development process information file 10 ... Displayed document content buffer 11 ... Specified range buffer 12 ... Specified range content buffer 13 ... In-mark information buffer 14 ... Document list buffer 15. ..Element list buffer 16 ... Part position management information buffer

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Tetsuji Haraguchi 1015 Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa, Fujitsu Kansai Communication Systems Co., Ltd. Communication system Co., Ltd.

Claims (9)

[Claims] 1. A text creation support system for converting at least a part of the contents described in a document into parts, and when the contents to be made into parts are specified for a document, the contents of the parts are retained. The name indicating that the part, the document name of the document that refers to the part, and the part holding mark that has an identifier according to the type of the part are recorded in a file separate from the document and the name that indicates that the part is referenced. , A component reference mark having a file name and file format of a file storing the content of the component, an identifier according to the component type, and version information of the component is added to the position where the component of the document is designated, A text creation support system characterized by including deleting the content of a part from a document. 2. A text creation support system in which at least a part of the contents described in one document is made into a component so that other documents can refer to the contents, and the contents to be made into a component for one document are specified. Then, a component holding mark having a name indicating that the component is owned, a document name of a document that refers to the component, and an identifier corresponding to the type of the component is added before and after the component, and the component is referenced. A name indicating that
It is characterized by including a part reference mark having a file format of a document holding the part, an identifier corresponding to the type of the part, and version information of the part at a position where the part of another document is referred to. A text creation support system. 3. The method according to claim 1 or 2, wherein when displaying a document that refers to a component, a file or document having the component is read and the content of the component is displayed without displaying the component reference mark. Characteristic writing support system. 4. The file according to any one of claims 1 to 3, when the content of a part is changed in a document referencing the part, a file or a document having the part is stored under version number management The text creation support system characterized by updating the version number information of the part, and updating the version number information of the part in the part reference mark existing in another document that refers to the original version number of the part. 5. In any one of claims 1 to 3, when changing the content of a part in a document that refers to the part, whether to update the information in the part holding mark existing in the file having the part or in the document. Can be selected.When updating, save the file or document containing the part under version management, update the version information in the part reference mark, and refer to the original version of the part. The version number information of the part in the part reference mark existing in another document is updated.If not updated, the file or document containing the part is saved under version number management and the version number information in the part reference mark is updated. A text creation support system characterized by updating the part name and deleting the part holding document name. 6. The component reference mark according to any one of claims 1 to 5, when the content of a component is changed in a file or a document having the component, A text creation support system characterized by updating version information of parts. 7. The method according to any one of claims 1 to 5, wherein when the content of a part is changed in a file or a document having the part, whether or not to update the content of the document that refers to this part is determined for each document. If you want to update, update the component version information in the component reference mark.If you do not update it, do not update the component version number information in the component reference mark and it exists in the document that has the changed component. A document creation support system characterized by deleting a relevant document name from a component reference document name in a component possession mark. 8. In any one of claims 1 to 7, when an element described in one document and an element described in another document are described in association with each other, before and after the element in one document , A name indicating that the element is associated with another document, an identifier, and a takeover source mark having a file name of the other document are added, and the element is separated from the other document before and after the element in the other document. A sentence creation support system characterized by adding a takeover destination mark having a name indicating that the document has been taken over, an identifier, and a file name of one document. 9. The content according to any one of claims 1 to 8, when a plurality of documents are sequentially created in accordance with a certain flow, the contents of elements that must be described in one document in the flow are Before and after the element, if it cannot be described for some reason, it has a name indicating that the element description is to be deferred, an identifier, and information indicating when or when the element description should be completed. A text creation support system characterized by adding a process control mark.