JP2009087289A - Document creation management system, terminal, server, document creation management method, and its program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To obtain not only whether a document to be referred is referred but also the level of the reference in creating a document. <P>SOLUTION: In this document creation management system, a server 1 includes: a transmission/reception part 11 receiving, from a developer terminal 2, a document in process of creation, a document in process of reference, and an operation event related to the document in process of reference; a storage part 14 for storing a document reference list 142 which stores information of documents to be referred in creating the document on a document basis; and a document reference situation check part 12 for determining whether all the documents to be referred in creating the document which are received from the developer terminal 2 are referred based the document reference information of the storage part 14, and storing, in the storage part, the operation event related to the document in process of reference along with the determination result. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to management of a document created by a developer or the like.

  Conventionally, many techniques related to document creation have been proposed. For example, Patent Document 1 relates to a document creation apparatus that creates a document related to a plurality of work items or processes. Even if the number of documents is enormous and the structure of the document group is complicated, these documents can be efficiently and error-corrected. There is disclosed a technique that can be managed without any problems.

  In this document creation apparatus, first, the input means inputs a work item or process corresponding to a document to be created. A document management information storage unit stores the document in association with the input work item or process. Further, the document selection unit selects a document to be created based on the work item or process input by the input unit and the contents of the document management information storage unit.

  In the technique of Patent Document 1, when a work item is selected from a list of work items displayed on the screen, a document related to the work item can be created and edited, and the work item is related to the work item. It is possible to display a work manual. In the system development according to the system development procedure, the documents that must be referred to when creating the deliverables and the achievements that must be completed before creating the deliverables. Things are decided. However, the technique of Patent Document 1 cannot check whether or not a document to be referred to according to such a system development procedure is actually appropriately referred to and created in an appropriate creation order.

On the other hand, Patent Document 2 discloses a technique for checking whether or not a document to be referred to is actually properly referred to and created in an appropriate creation order at the time of document creation regarding a document creation support / management system. Yes.
JP-A-8-202769 JP 2007-41640 A

  However, in the technique of Patent Document 2, whether or not the document to be referred to is actually referred is managed by information of “0 (not referenced)” and “1 (referenced)” (paragraph of Patent Document 2). Although it is known whether or not the document to be referred to has been accessed, it is unclear how much the document has been referred to, and it has not been sufficient for managing document creation.

  The present invention has been made in view of the above problems, and it is an object of the present invention to grasp not only whether or not a document to be referred to has been referred to but also the level of reference when the document is created.

In order to solve the above-described problem, the present invention provides a document creation comprising: a terminal where a user creates a document; and a server connected to the terminal via a communication network and managing information related to creation of the document by the terminal. It is a management system.
The terminal includes: a display unit that displays information; an input unit that allows the user to perform information input operations related to document creation; a document that is being created; a document that is being referenced for creation; and A document reference status detection unit that detects an operation event that is an operation content in the input unit related to a document, the document that is being created, the document that is being referenced, and the operation event that are detected by the document reference status detection unit. A terminal transmission / reception unit that transmits to the server.
The server stores the document being created, the document being referred to, and the server transmission / reception unit that receives the operation event from the terminal, and a document storing information on a document to be referred to when the document is created for each document. Based on the document reference information stored in the storage unit for storing reference information and the document reference information in the storage unit, it is determined whether or not all the documents to be referred to when creating the document being created received from the terminal have been referred to, and together with the determination result A document reference status check unit that stores the operation event in the storage unit.
Other means will be described later.

  According to the present invention, at the time of creating a document, it is possible to grasp not only whether or not the document to be referred to has been referred to but also the degree of reference.

Hereinafter, the best mode for carrying out the present invention (hereinafter referred to as “embodiment”) will be described in detail with reference to the drawings. It should be noted that drawings other than the referenced drawings are also referred to as appropriate.
In the present embodiment, a design document, a list, a drawing, and the like created by the developer according to the system development procedure are referred to as a “product (“ document ”in the claims”) ”.
In addition to the deliverables, a standard document, a procedure manual, a commentary, etc. prepared in advance as a system development procedure are collectively referred to as a “document”.

In general, documents can be classified into three types: “sentence”, “table”, and “figure”.
Also in the present embodiment, for example, a document composed of sentences consisting of chapters and sections, such as “product creation procedure manual” and “requirement definition document”, is referred to as “text”, and “interface list” and A document composed of a list such as “Data Item List” is called a “table”, and a document composed of a drawing such as “Information System Related Diagram” or “Function Information Related Diagram” is called a “table”. Called “Figure”.

In this embodiment, it is checked in real time according to the creation status of the product whether the developer is appropriately creating the product and referring to the document according to the system development procedure, and if the check is not satisfied, the developer An example of an information system development support system (document creation management system) and a method for displaying it as a message is used.
However, the technical idea of the present invention is not limited to this embodiment.

  FIG. 1 is a diagram illustrating a functional configuration example of an information system development support system according to the present embodiment. The information system development support system S includes a plurality of developer terminals 2 (terminals) and a server 1 connected to them via a communication network 3.

The developer terminal 2 is a computer device, and includes an input unit 21, a processing unit 200, a transmission / reception unit 24 (terminal transmission / reception unit), and a screen display unit 25 (display unit).
The input unit 21 is, for example, a mouse or a keyboard, and is used when a developer creates a product or refers to a document.

  The processing unit 200 implements various arithmetic processes using, for example, a CPU (Central Processing Unit) and a memory, and includes a document reference status detection unit 22 and a product content detection unit 23 (document content detection unit). The processing unit 200 appropriately performs processing other than the processing by the document reference status detection unit 22 and the product content detection unit 23.

The document reference status detection unit 22 detects an operation event such as a mouse operation or a keyboard operation when a developer refers to a document using the input unit 21, and acquires information on the document reference status.
The product content detection unit 23 detects an operation event such as a mouse operation or a keyboard operation when the developer creates a product using the input unit 21, and acquires the product content.
Details of the document reference status detection unit 22 and the deliverable content detection unit 23 will be described later.

The transmission / reception unit 24 transmits information about the document reference detected by the document reference status detection unit 22 and information such as the product content detected by the product content detection unit 23 to the server 1 or receives a message from the server 1. To do.
The screen display unit 25 displays a product being created, a document being referenced, a message from the server 1, and the like.

The server 1 is a computer device, and includes a transmission / reception unit 11 (server transmission / reception unit), a processing unit 100, and a storage unit 14.
The transmission / reception unit 11 receives information transmitted by the transmission / reception unit 24 of the developer terminal 2 or is created by the document reference status check unit 12 or the product content check unit 13 (document content check unit) described below. A message is transmitted to the developer terminal 2.

  The document reference status check unit 12 determines whether or not the developer has created the deliverables in an appropriate order according to the system development procedure based on the information regarding the document reference acquired by the document reference status detection unit 22. Check if the document is referenced, and if these checks are not met, create a message to that effect.

The product content check unit 13 checks whether the product content is appropriate based on the product content acquired by the product content detection unit 23. If the product content is not satisfied, the product content check unit 13 Create the indicated message.
Details of the document reference status check unit 12 and the product content check unit 13 will be described later.

The storage unit 14 includes a product related table 141 (document related information), a document reference table 142 (document reference information), a reference status table 143, a creation status table 144 (creation status information), and a content confirmation table (direct designation) 145 ( Content confirmation information), content confirmation table (indirect designation) 146 (content confirmation information), and all documents including deliverables are stored.
Note that the server 1 and the developer terminal 2 may be physically one device without the communication network 3 and may have the functions described above in one device.

The following (1) to (6) implementation methods in the server 1 and the developer terminal 2 will be described.
(1) Application on developer terminal 2 side (2) Application display screen (3) Document data content (4) Document file management (5) Document reference status detection (6) Deliverable content detection about

(1) About Application on Developer Terminal The application on the developer terminal 2 side that realizes the information system development support system S in this embodiment will be described.
This application may be a Web application on the WWW (World Wide Web) or a desktop application such as a Java (registered trademark) application operating on a client PC (Personal Computer).
When the information detected by the document reference status detection unit 22 or the product content detection unit 23 is transmitted from the developer terminal 2 to the server 1, the information is transmitted in real time by performing asynchronous communication.

At this time, if the above-mentioned application is provided as a Web application, the existing Ajax (Asynchronous Java (registered trademark) Script + XML (eXtensible Markup Language)) technology or Adobe (registered trademark) Flash (registered trademark) technology should be used. Can be realized.
On the other hand, if it is provided as a desktop application such as a Java (registered trademark) application, it can be realized by using an existing socket communication technology, a Web service technology, or the like in a client PC side program and a server side program.

Note that the application is used after user authentication is performed so that the user of the application (“developer” in the present embodiment) can be identified regardless of the application implementation format.
User authentication can be realized, for example, by issuing an account (user ID (IDentification) and password) to the user, and the user inputting the user ID and password when using the application.

(2) Application Display Screen FIG. 2 is a diagram showing an example of a display screen in the developer terminal of the present embodiment. This display screen is displayed on the screen display unit 25.
This display screen is assumed to be composed of a screen for a developer to create a product and a screen for referring to a document, and operates as one application 240. This application 240 is composed of five areas.

The first area of the application 240 is a deliverable editing area 241 for opening and editing a deliverable file.
The second area of the application 240 is a “new” button for creating a new deliverable file, an “open” button for opening a deliverable file and displaying it in the deliverable edit area 241, and a deliverable edit area 241. A menu area 242 includes a “save” button for saving the product file being edited and an “end” button for ending the application.
In addition to the above buttons, the menu area 242 moves a word search button in the product edit area 241, a button for changing settings such as display and format, and the display content to the next page or the previous page. A button for switching the display may be included.

The third area of the application 240 is a tab area 243 that displays a plurality of document names (document names that must be referred to when creating the deliverables) related to the deliverable edited in the deliverable edit area 241 in a tab format. It is.
As the document name to be displayed in the tab area 243, the document name related to the deliverable (the document name that must be referred to when creating the deliverable) according to the deliverable edited in the deliverable edit area 241 is the server 1. Automatically obtained from and displayed.
The developer can also prepare a document reading button that can display an arbitrary document name in the tab area 243 so that a document that is not displayed in the tab area 243 can be explicitly selected.

A fourth area of the application 240 is an item list area 244 for displaying a list of items constituting the document selected in the tab area 243.
For example, when the document type selected in the tab area 243 is a sentence, the item list area 244 displays a chapter or a section. When the document type is a table, the item list area 244 indicates a sheet constituting the table. If the document type is a figure, the page name (or page number) of the figure is displayed.

A fifth area of the application 240 is a reference document display area 245 for displaying specific contents of the item selected in the item list area 244.
Details of the contents displayed in the item list area 244 and the reference document display area 245 will be described later.

In the application 240 of the present embodiment, the screen for editing the product corresponds to the product editing area 241 and the menu area 242, and the screen for referring to the document is the tab area 243, the item list area 244, and the reference document. This corresponds to the display area 245.
Note that the application having the creation area and the application having the reference area exist as separate applications in the developer terminal 2, and the two applications can communicate with each other to communicate with each other. is there.

(3) Document Data Contents Documents (including deliverables) displayed in the deliverable edit area 241 and reference document display area 245 of the developer terminal 2 and data contents of the documents stored in the server 1 (deliverables) Will be explained.

  FIG. 3 is a diagram (reference numeral 1471) illustrating an example of a screen display of a document (sentence) displayed in the product edit area 241 and the reference document display area 245 of the developer terminal 2. Three items of “purpose”, “target range”, and “development period” are provided, and each character string is displayed corresponding to each item.

  FIG. 4 is a diagram (reference numeral 1472) showing an example of data contents (data structure) for the screen display of FIG. That is, in order to display the screen as shown in FIG. 3, when a markup language such as XML is used, it is expressed as shown in FIG.

  FIG. 5 is a diagram (reference numeral 1473) illustrating an example of a screen display of a document (table) displayed in the product edit area 241 and the reference document display area 245 of the developer terminal 2. Each character string is displayed in each column of “information name”, “link type”, and “format”.

  FIG. 6 is a diagram (reference numeral 1474) showing an example of data contents (data structure) for the screen display of FIG. That is, in order to display the screen as shown in FIG. 5, when a markup language such as XML is used, it is expressed as shown in FIG.

  FIG. 7 is a diagram (reference numeral 1475) showing an example of a screen display of a document (figure) displayed in the product edit area 241 and the reference document display area 245 of the developer terminal 2. The character strings of “estimation system” and “accounting system” are connected by a single arrow, and the character string of “estimate information” is appended.

  FIG. 8 is a diagram (reference numeral 1476) showing an example of data contents (data structure) for the screen display of FIG. That is, in order to display the screen as shown in FIG. 7, when a markup language such as XML is used, it is expressed as shown in FIG.

  As described above, the document referred to on the developer terminal 2 is displayed on the screen as shown in FIGS. 3, 5, and 7 by interpreting the data structures as shown in FIGS. 4, 6, and 8, respectively. The product created by the terminal 2 is transmitted to the server 1 as a data structure as shown in FIGS.

  As described above, since a document can be structured and expressed even if it is a text, a table, or a figure, the application realized on the developer terminal 2 side is a Web application. Alternatively, it may be a desktop application such as Java (registered trademark), that is, the document can be handled between the developer terminal 2 and the server 1 without depending on the application implementation method. That is, the structure and contents of the documents can be easily referred to each other.

(4) Document File Management A document management method in the storage unit 14 of the server 1 will be described.
If the document is a sentence, a folder is created for each document in the server 1, a subfolder is created for each chapter of the document, and the sentence (data) of the chapter is stored in the subfolder.

  For example, in the server 1, the deliverable “Procedure Creation Procedure Manual” is assigned to a folder “C: ¥ doc ¥ Product Creation Procedure Manual”, and “Chapter 2” of “Creative Creation Procedure Manual” is “C”. : \ Doc \ Product creation procedure manual \ 2 "and" 2.1 "are assigned to a subfolder" C: \ doc \ Product creation procedure manual \ 2 \ 1 "and the contents of" 2.1 "( For example, the data content as shown in FIG. 4 is stored in a file “C: ¥ doc ¥ product creation procedure ¥ 2 ¥ 1 ¥ doc.xml”.

When the document is a table, a subfolder is assigned for each sheet, and when the document is a diagram, the subfolder is assigned for each page, so that the document can be managed in the same manner as when the document is a sentence.
With the above management method, each document and its contents can be uniquely specified based on the stored file position.

Therefore, in the application 240 of the developer terminal 2, information regarding the document name displayed in the tab area 243 and the chapter or section (in the case of sentences) displayed in the item list area 244 can be uniquely specified.
For example, when displaying “Creation product creation procedure manual” in the tab area 243, “C: ¥ doc ¥ Product creation procedure manual” is associated and “Section 2.1” is displayed in the item list region 244. , By associating “C: ¥ doc ¥ product creation procedure document ¥ 2 ¥ 1,” when the developer selects “Section 2.1” from the item list area 244, the corresponding document “C: ¥ doc” “¥ product creation procedure manual ¥ 2 ¥ 1 ¥ doc.xml” is interpreted and displayed in the reference document display area 245.

This makes it possible to acquire information on which part (for example, which chapter or which section) of which document the developer is referring to.
It is also possible to uniquely identify a document by managing the document only by the file name of the document, not by a folder or subfolder management method.
For example, the contents of “Claim 2.1” in “Product Creation Procedure Manual” are “C: ¥ doc ¥ Product Creation Procedure Manual-2-1.xml”, and the contents of “2.2” are “C: It may be managed by storing it in a file “¥ doc ¥ product creation procedure manual-2-2.xml”.

(5) Document reference status detection The document reference status detection unit 22 in the developer terminal 2 detects an operation event caused by a mouse operation or a keyboard operation of the developer, and the developer determines the operation event according to the type and timing of the operation event. Information related to the document being referred to is acquired and transmitted to the server 1.

The operation event here refers to, for example, inputting characters from the keyboard in the product editing area 241, creating a diagram with the mouse, or clicking a document name (link) displayed on a tab in the tab area 243. Operations such as clicking on items (links of chapters, sections, etc.) displayed in the item list area 244, selecting the text being displayed in the reference document display area 245, and scrolling the display. . That is, as the operation event, a fact that can be grounds such as a high possibility that the developer has viewed the document can be adopted.
In the following (5-1) to (5-4), an operation event detected at the time of creating a product or referring to a document and a process at the time of detecting the event will be described.

(5-1) Display Switching When the document content displayed in the tab area 243 is clicked to change the item content displayed in the item list area 244, or the item name displayed in the item list area 244 When the display content of the reference document display area 245 is switched by clicking, the name of the product being created as information relating to document reference (the name of the product being edited in the product edit area 241 when clicked) , A reference document (when the tab area 243 is clicked, the name of the clicked document, when the item list area 244 is clicked, the document name that is active (selected) at that time in the tab area), the display item ( If the tab area 243 is clicked, it is undefined, and the item list area 244 is clicked. If it is, the clicked chapter or section (or item such as sheet or page)) and the developer name (the name of the developer using the application) are acquired and transmitted to the server 1.

  For example, when the developer “Yamaguchi” is editing the “information system related diagram” in the product edit area 241, the contents of “2.2” of the “product creation procedure manual” are referred to as the reference document display area. When “section 2.2” in the item list area 244 is clicked in the state where the “product creation procedure manual” displayed in the tab area 243 is displayed to be displayed in the H.245 information, information on document reference (Information system related diagram, product creation procedure manual, section 2.2, Yamaguchi) is acquired and transmitted to the server 1.

As described in “(4) Document file management” above, information such as “document creation procedure manual” and “section 2.2” such as reference documents and display items must be uniquely specified. It is possible to detect which location in which document the developer tried to refer to.
Further, the developer can specify by user authentication when using the application.

(5-2) Scroll, etc. Reference when scrolling the document displayed in the reference document display area 245, selecting a displayed character, or operating the mouse (pressing or releasing the mouse button, etc.) When an operation event occurs in the document display area 245, as in the case of (5-1) above, information regarding the document reference (the name of the product being created, the reference document, the display item, and the developer name) is acquired. To the server 1.

(5-3) Start writing, etc. When you start writing texts or diagrams in the deliverable editing area 241, start to enter the contents of the table items (cells), or the contents of all the items (cells) in the table When the entry is completed, as in the case of (5-1) above, the information related to the document reference (the name of the product being created, the reference document, the display item, and the developer name) is acquired and transmitted to the server 1.

(5-4) Character Number Threshold, etc. In the product editing area 241, when the number of keyboard inputs and the number of characters are counted and a predetermined threshold value is reached after the start of text input, (5-1) In the same manner as described above, information on a document reference (the name of a deliverable being created, a reference document, a display item, and a developer name) is acquired and transmitted to the server 1.
For example, when expecting an amount of about 400 characters on one A4 sheet as the amount of one section of a standard document to be created, 80% (320 characters) is set as a threshold, and when the threshold is reached, the document Information related to the reference is transmitted to the server 1.

  In addition, since the display of the document referred to when creating the same deliverable may be switched, within the application, when creating which deliverable, which part of which document It is referred to, and it is assumed that the input character is managed. That is, reference document information and operation events (such as mouse and keyboard operation information) are transmitted from the developer terminal 2 to the server 1, and the server 1 stores the reference document information and operation events in the storage unit 14. Then, by utilizing the operation event stored in the storage unit 14 of the server 1, it is possible to grasp not only whether or not the document to be referred to has been referred to but also the degree of reference when the document is created.

(6) About product content detection The product content detection unit 23 in the developer terminal 2 detects an operation event caused by a mouse operation or a keyboard operation of the developer, and the developer determines the operation event according to the type and timing of the operation event. The content of the created deliverable is acquired and transmitted to the server 1.
The operation event here refers to, for example, inputting characters from the keyboard in the product editing area 241, creating a diagram with the mouse, or clicking a document name (link) displayed on a tab in the tab area 243. In other words, an operation such as pressing a button in the menu area 242 to switch display contents in the product editing area 241 is performed.
In the following (6-1) and (6-2), an operation event detected at the time of creating a product and a process at the time of event detection will be described.

(6-1) Display switching, etc. When the display content of the product edit area 241 is switched by pressing the button in the menu area 242 or when editing of the product is finished, the product being created is generated as the product content. The name, data of the contents of the deliverable being created (for example, data as shown in FIGS. 4, 6, and 8) and the developer name (the name of the developer using the application) are acquired and transmitted to the server 1. .

  For example, when the developer “Yamaguchi” is editing the “requirement definition document” in the product edit area 241, the content of the product (requirement definition document, content data of the requirement definition document (for example, as shown in FIG. 4) Data) and Yamaguchi) are transmitted to the server 1.

(6-2) Completion of entry When all the contents of the table items (cells) have been entered in the deliverable editing area 241, as in (6-1) above, as the deliverable contents (results being created) (Product name, product content data, developer name) are acquired and transmitted to the server 1.

  In the following, the product relation table 141, the document reference table 142, the reference situation table 143, the creation situation table 144, the content confirmation table (direct designation) 145, and the content confirmation table (indirect designation) managed in the storage unit 14 of the server 1 will be described. 146 will be described.

FIG. 9 is a diagram illustrating an example of the product relation table 141 according to the present embodiment.
In FIG. 9, a column 1411 (hereinafter also referred to as a product 1411. The same applies to other columns (including other diagrams)) is a product that must be created by the developer, and a column 1412 is a table before the product is created. Is a pre-made work product that must be completed.
For example, it indicates that there is no deliverable that needs to be completed before creating the “project plan” described in the deliverable 1411 (described as “−” in the pre-created deliverable 1412).

On the other hand, the “project plan” must be completed before the “requirement definition document” described in the deliverable 1411 is created, and the “requirement definition document” and “function” Indicates that both information hierarchy diagrams must be completed.
The product-related table 141 is a table that is defined in advance before the developer creates a product, and is defined based on the system development procedure.
By using the product relation table 141, it is possible to represent all the products that the developer has to create and the order relationship in which the products are created.
In the product relation table 141, it is not particularly necessary that the vertical arrangement order of the products in the column 1411 coincide with the order to be created. The same applies to the document reference table 142 to the content confirmation table (indirect designation) 146.

FIG. 10 is a diagram illustrating an example of the document reference table 142 according to the present embodiment.
In FIG. 10, a column 1421 is a product that the developer must create, a column 1422 is the type of the product (“text”, “table”, “diagram”, etc.), and a column 1423 is the product. Person in charge (user identification information) to be created, column 1424 is a document that must be referred to when creating the product, column 1425 is described in column 1424 that must be referenced when creating the product This is the reference location of the document.
The reference location 1425 displays a chapter or section for text, a sheet for a table, a page for a figure, and the like.

When a specific reference location is not designated as the reference location 1425, “−” is written.
Further, even for the products described in the pre-created product 1412 of the product-related table 141, the reference document 1424 and the reference location 1425 of the document reference table 142 are explicitly described if reference is necessary.

  For example, the type of the product “information system related diagram” described in the product 1421 is “diagram”, and this product is created by either “Sato” or “Yamaguchi”. In order to create deliverables, it is necessary to refer to all of “Chapter 2” of “Function Requirements Creation Guide”, “Section 2.1” of “Product Creation Procedure Manual”, and “Business Function Hierarchy” Show.

The document reference table 142 is a table that is defined in advance before a developer creates a product, and is defined based on a system development procedure.
By using the document reference table 142, it is possible to represent a document that a developer must refer to when creating a product and a reference location thereof.

FIG. 11 is a diagram illustrating an example of the reference status table 143 according to the present embodiment.
In FIG. 11, a column 1431 is a deliverable that the developer must create, a column 1432 is a document that must be referred to when creating the deliverable, and a column 1433 is referenced when creating the deliverable. A reference location of a document to be stored, a column 1434 is a reference status of the reference document when the product is created.

Note that the deliverable 1431, reference document 1432, and reference location 1433 of the reference status table 143 have the same contents as the deliverable 1421, reference document 1424, and reference location 1425 of the document reference table 142.
The reference situation 1434 is represented by a set of (person in charge, situation), “person in charge” describes the person in charge 1423 of the product in the document reference table 142, and “situation” creates the product. When referring to the reference location of the reference document, “○” is indicated. When not referring to the reference document, “X” is indicated.

For example, when creating the “information system related diagram” described in the deliverable 1431, “Sat” and “Yamaguchi” both refer to “Chapter 2” of the “Function Requirements Creation Guide” (“○” Description).
In addition, when creating the same “information system related diagram”, “Sato” is not referred to in “Section 2.1” of the “Product Creation Procedure Manual” (denoted as “×”), but “Yamaguchi” Indicates that it is referred to (described as “◯”).

The deliverable 1431, the reference document 1432, and the reference location 1433 of the reference situation table 143 are defined in advance before the developer creates the deliverable, and the reference situation 1434 has contents when creating the deliverable or referring to the document. Update.
Therefore, the “situation” of the reference situation 1434 is “x” for all persons in charge at first.
By using the reference situation table 143, it is possible to indicate which document can be referred to when creating a product, and which document cannot be referred to.

FIG. 12 is a diagram showing an example of the creation status table 144 of the present embodiment.
In FIG. 12, a column 1441 is a deliverable that a developer must create, a column 1442 is a reference check that indicates whether or not a document necessary for creating the deliverable is appropriately referenced, and a column 1443 is the deliverable. Content check indicating whether the content of the product is appropriate, column 1444 indicates whether the product is appropriately referred to and necessary content based on the reference check 1442 and the content check 1443 It is a creation check.

  The reference check 1442 is described as “O” if the same person in charge refers to all reference documents regarding the deliverable based on the reference status 1434 of the reference status table 143, and “X” otherwise. To do. In other words, when there are a plurality of persons in charge, it is not necessary for everyone to refer to all the reference documents, and it is sufficient that one person refers to all the reference documents (in this case, the reference check 1442 is “○”). Become).

The content check 1443 determines that the content of the deliverable is appropriate if the key item or keyword specified at the time of creation of the deliverable or the keyword is appropriately included in the content of the deliverable. Otherwise, it is described as “x”.
Details of key items and keywords will be described later.

Furthermore, the creation check 1444 indicates that the creation of the deliverable is sufficient if both the reference check 1442 and the content check 1433 are “◯” (that is, all necessary documents are referenced and the content is appropriate). Considering it as “◯”, otherwise “X”.
For example, the “project plan” described in the deliverable 1441 refers to the “medium-term management plan” that must be referenced from the reference status table 143, so “Suzuki” refers to the reference check 1442 as “○”. Therefore, if the content check 1433 is also “◯”, the creation check 1444 is also “◯”.

  On the other hand, since the “information system related diagram” described in the deliverable 1441 does not refer to all the documents that should be referred to by both “Sato” and “Yamaguchi” from the reference status table 143, the creation check 1442 is “×”. The creation check 1444 is “×” regardless of whether the content check 1433 is “◯” or “×”.

The deliverable 1441 in the creation status table 144 is defined in advance before the developer creates the deliverable. The reference check 1442, the content check 1443, and the creation check 1444 are all described as “x” at the start of system development. In addition, the description is updated as the deliverables are created.
By using the creation status table 144, it is possible to represent the appropriateness of the document reference status at the time of creating the product, the appropriateness of the product content, and whether or not both are appropriate.

FIG. 13 is a diagram showing an example of the content confirmation table (direct designation) 145 of the present embodiment.
In FIG. 13, column 1451 is a deliverable that the developer must create, column 1452 is a chapter or section if the type of the deliverable is text, a sheet if it is a table, a page if it is a figure, or the like. A column 1453 is a key item that must be described in the location of the product, and a column 1454 is a keyword that must be described in the location of the product.
Note that the key item 1453 indicates that the key item must be specifically described, and the keyword 1454 indicates that the keyword itself must be described.

For example, an item “purpose” is described in “Chapter 1” of the “project plan” described in the product 1451, and this means that some description of the “purpose” must be performed.
That is, in FIG. 4, as the contents of “<item> purpose </ item>”, the description in the <text> tag positioned below it should not be empty.
In addition, the term “service” must be described in “section 5.2” of the “requirement definition document” described in the product 1451.

The key item 1453 and the keyword 1454 of the content confirmation table (direct specification) 145 are pre-defined before the developer creates the product, and the developer specifies the key item or keyword while creating the product. May be defined by
In the latter case, for example, when creating a table as shown in FIG. 5, if it is desired to always describe data related to “information name” using “information name” as a key item, the product edit area 241 ( In FIG. 2, “information name” is designated as a key item. The key item designation method can be realized by preparing a key item designation editing button in the menu area 242.

When a key item is designated, “key =“ on ”” is inserted as an attribute of the <item> tag as shown in FIG. 6 in the deliverable data, and the server 1 receives the deliverable data and confirms the contents. “Information name” is added to the key item of the table (direct specification) 145.
Even when a keyword is specified during creation of a deliverable, it can be realized in the same manner as the key item.
By using the content confirmation table (direct specification) 145, it is possible to specify key items and keywords that must be described in the deliverable.

FIG. 14 is a diagram illustrating an example of the content confirmation table (indirect designation) 146 according to the present embodiment.
In FIG. 14, column 1461 is a deliverable that the developer must create, column 1462 is a chapter or section if the deliverable type is text, a sheet if it is a table, a page if it is a figure, or the like. Where the contents are to be checked at a specific description location, column 1463 is a key item that must be described by a product that must refer to the location of the product, and column 1464 must refer to the location of the product. This is a keyword that must be described by the deliverable.
Note that the meanings of the key item 1463 and the keyword 1464 are the same as in the case of the content confirmation table (direct specification) 145, and a description thereof will be omitted.

  The method for specifying the key item 1463 and the keyword 1464 during creation of the deliverable is the same as that in the case of the content confirmation table (direct specification) 145. Specifically, for example, an attribute such as “key-indirect =“ on ”” is inserted into the <item> tag in the product data, and the product that refers to the product is always this key. Just indicate that the item or keyword must be described.

In addition, the deliverable that must refer to the location of the deliverable can be acquired by referring to the document reference table 142 (see FIG. 10).
If the key item or keyword of the product specified in the content confirmation table (direct specification) 145 must be described in the product that refers to the product, the content confirmation table (direct specification) 145 and The content confirmation table (indirect designation) 146 is a table having the same data.

For example, a product for which the “interface list” described in the product 1461 must be referred to must describe the contents of the data described in the “information name”.
By using the content confirmation table (indirect designation) 146, it becomes possible to designate key items and keywords that must be described in other deliverables referring to the deliverables.
By using both the above-mentioned content confirmation table (direct designation) 145 and content confirmation table (indirect designation) 146, the content of the product can be determined in the sense that necessary information is described as the content of the product. It is possible to check whether it is appropriate.

Next, the processing flow of the document reference status check unit 12 and the product content check unit 13 of the server 1 will be described.
FIG. 15 is a diagram showing a processing flow for checking the document reference status in the server 1 of the present embodiment.
This process flow is a process executed mainly by the document reference status check unit 12 every time information related to document reference is received from the developer terminal 2.

In step 1211, “created product name, reference document, display item, developer name” is received as information related to document reference from the developer terminal 2, and the product related table 141 and the creation status table 144 are referred to. Then, it is checked whether or not a product that must be completed before the received product has been created.
If it has been created (Yes in Step 1211), the process proceeds to Step 1212. If it has not been created (No in Step 1211), the process proceeds to Step 1213.

  For example, it is assumed that “information system related diagram, product creation procedure manual, section 2.1, Yamaguchi” is received from the developer terminal 2 as information related to document reference. The deliverables that must be completed prior to the “information system related diagram” are “requirement definition document” and “functional information hierarchy diagram” from the product related table 141. With reference to the creation check 1444 of the creation status table 144, it is checked whether the creation of the “requirement definition document” and the “function information hierarchy diagram” has been completed.

In step 1212, the document reference table 142 and the reference situation table 143 are referred to, and the information related to the document reference received in step 1211 is reflected in the reference situation 1434 of the reference situation table 143.
For example, when “information system related diagram, product creation procedure manual, section 2.1, Yamaguchi” is received as information related to document reference from developer terminal 2, the creation is completed before “information system related diagram”. The deliverables that must be included are the “requirement definition document” and the “functional information hierarchy diagram”. When the creation of both the “requirement definition document” and the “functional information hierarchy diagram” has been completed, the output is shown in the reference status table 143 The data reference status 1434 is updated to (Yamaguchi, ○), with the product 1431 being “information system related diagram”, the reference document 1432 being “product creation procedure”, and the reference location 1433 being “section 2.1”.

In step 1213, since the deliverables that should be completed before the deliverable received in step 1211 have not been created, a list of deliverables to be created is created as a message.
Thereafter, in step 1214, the message created in step 1213 is transmitted to the developer terminal 2. When the developer terminal 2 receives a message from the server 1, the message is displayed on the screen display unit 25 using a pop-up screen or the like.

In step 1215, the document reference table 142 and the reference situation table 143 are referred to, and it is checked whether or not all the documents to be referred to have been referenced for the deliverable being created received in step 1211.
If all are referenced (Yes in Step 1215), the process proceeds to Step 1216. If all are referenced (No in Step 1215), the process proceeds to Step 1217.

For example, by updating the reference status table 143 in the above step 1212, all the reference documents 1432 of the “information system related diagram” and the reference status 1434 of the reference location 1433 are all referred to by any one developer. If yes, go to Step 1216.
That is, if it is (Yamaguchi, ○) for all the reference situations 1434, it indicates that the developer “Yamaguchi” is referring to all documents to be referred to in creating the “information system related diagram”.
In step 1216, the reference check 1442 for the deliverable in the creation status table 144 is updated to “◯”, and the process ends.

In step 1217, since documents to be referred to by the deliverable received in step 1211 still remain, a list of documents to be referred to is created as a message.
Thereafter, in step 1218, the message created in step 1217 is transmitted to the developer terminal 2. When the developer terminal 2 receives a message from the server 1, the message is displayed on the screen display unit 25 using a pop-up screen or the like.

  Based on the above-described processing flow, based on the document reference status detected by the document reference status detection unit 22, whether the developer has created a product in an appropriate order according to the system development procedure, and appropriately refers to the document. If it is not appropriate, a message indicating that fact can be created and displayed on the developer terminal 2.

FIG. 16 is a diagram showing a processing flow for checking the product content in the server 1 of the present embodiment.
In this processing flow, each time the deliverable content is received from the developer terminal 2, the document reference status check unit 12 is mainly used for checking the document reference status, and the deliverable content check unit 13 is used for checking the deliverable content. This is a process executed mainly.

In step 1311, “product name being created, product content, developer name” is received from the developer terminal 2 as information related to the product content, and the product is stored in the storage unit 14.
In step 1312, based on the product content received in step 1311, it is checked whether the content of the product is described appropriately.

FIG. 17 is a diagram showing a processing flow for checking the key item of the product content and the keyword in step 1312 of FIG.
In step 1321, key items and keywords are extracted from the contents data of the deliverable received in step 1311, and the key items and keywords stored in the contents confirmation table (direct designation) 145 and the contents confirmation table (indirect designation) 146 are extracted. If the key item or keyword is newly added, deleted, or updated, the contents confirmation table (direct designation) 145 and the contents confirmation table (indirect designation) 146 are updated.

In step 1322, the content confirmation table (direct designation) 145 is referred to and it is checked whether or not the key items and keywords that should be described in the product are described in the received product content.
If all the key items and keywords that should be described in the product are described (Yes in step 1322), the process proceeds to step 1324, and if there are any key items or keywords that are not described (in step 1322). No) Proceed to step 1323.
For example, the received product is an “information system related diagram”, and the keyword “estimation system” is described in the “information system related diagram” as specified in the content confirmation table (direct specification) 145. If yes, go to Step 1324.

In step 1323, a list of key items or keywords not described in step 1322 is created as a message.
In step 1324, with reference to the content confirmation table (indirect designation) 146 and the document reference table 142, whether the key item or keyword required by the document that the product must refer to is described in the product. Check if.

If all the key items and keywords that should be described in the deliverable are described (Yes in step 1324), the process proceeds to step 1326, and if there are any key items or keywords that are not described (in step 1324). No) Proceed to step 1325.
For example, if the received product is an “information system related diagram” and the product that must be referred to when creating the “information system related diagram” is a “business function hierarchy diagram”, the content confirmation table (indirect It is checked whether or not the keyword “order request” specified in the “business function hierarchy diagram” 146 is described in the “information system related diagram”.

If the key items and keywords required by all deliverables that must be referred to when creating the “information system related diagram” are described in the “information system related diagram” (Yes in step 1324), Proceed to step 1326.
In step 1325, a list of key items or keywords not described in step 1324 is created as a message.

  In step 1326, it is determined whether or not both conditions (checks) in steps 1322 and 1324 are satisfied. If both conditions are satisfied (Yes in step 1326), it is assumed that the contents of the deliverable are described appropriately, and the process proceeds to step 1328. Otherwise (No in step 1326), the process proceeds to step 1327.

In step 1327, the message created in step 1323 and / or step 1325 is transmitted to the developer terminal 2.
When the developer terminal 2 receives a message from the server 1, the message is displayed on the screen display unit 25 using a pop-up screen or the like.

In step 1328, the content check 1443 of the creation status table 144 is updated. If the check in step 1326 is satisfied (Yes), the contents check 1443 of the deliverable is updated to “◯”, otherwise (No) is updated (or maintained) to “X”.
The processing flow of FIG. 17 makes it possible to check whether the received product content is appropriate. When this processing flow is completed, the process proceeds to step 1313 of FIG.

  In step 1313, with reference to the deliverable relation table 141, other deliverables that must be completed before the deliverable received in step 1311 are acquired, and the creation check 1444 of the creation status table 144 is referred to. To check whether these other artifacts have been created.

If all these other deliverables have been created (Yes in Step 1313), the process proceeds to Step 1315. Otherwise (No in Step 1313), the process proceeds to Step 1314.
For example, when the received product is an “information system related diagram”, a “requirement definition document” and a “functional information hierarchy diagram” are obtained from the product related table 141 (see FIG. 9) before the “information system related diagram”. From the creation status table 144 (see FIG. 12), it can be seen that the “requirement definition document” creation check 1444 is “◯”, but the “functional information hierarchy diagram” creation check 1444 is “×”. (Not shown in FIG. 12), it is determined No in step 1313, and the process proceeds to step 1314.
In step 1314, a list of deliverables that are not yet created in step 1313 is created as a message, and the process proceeds to step 1319.

In step 1315, the reference status table 143 is referred to obtain the reference status of the document that the deliverable received in step 1311 must refer to, and all the documents are referred to by one of the same developers. Check whether or not
If all the documents have been referred to (Yes in Step 1315), the process proceeds to Step 1317. Otherwise (No in Step 1315), the process proceeds to Step 1316.
For example, if the “information system related diagram” is all “referenced” by the same developer with respect to the reference status 1434 of all the documents to be referred to from the reference status table 143, “Yes” is determined in step 1315. Then, the process proceeds to Step 1317.
In step 1316, a list of documents not referenced in step 1315 is created as a message.

In step 1317, the creation check 1444 for the deliverable in the creation status table 144 is updated. This is because if the content check 1443 of the creation status table 144 is updated in step 1312, the creation check 1444 is affected.
In step 1318, it is checked whether or not the contents check 1443 and creation check 1444 of other deliverables are affected by the above-described steps (processes).

FIG. 18 is a diagram showing a first processing flow for checking the influence on other deliverables accompanying the update of the deliverable content in step 1318 of FIG.
In step 1331, the content confirmation table (direct designation) 145 and the content confirmation table (indirect designation) 146 are referenced to check whether or not the key item or keyword related to the deliverable has been updated. If it has been updated (Yes in Step 1331), the process proceeds to Step 1332. If not updated (No in Step 1331), the process in FIG.

In step 1332, referring to the product relation table 141, a product that should be created upon receipt of the product, that is, a product that is directly affected is acquired.
For example, if the deliverable is a “functional information hierarchy diagram”, the deliverables that must be created in response to the creation of the “functional information hierarchy diagram” can be obtained from the deliverable relation table (see FIG. 9). "It can be seen that it is.

In step 1333, for all deliverables acquired in step 1332, all developers in the reference status 1434 of the reference status table 143 are updated from “◯” to “X”.
In step 1334, when the reference situation table 143 is updated in step 1333, the reference check 1442 and the creation check 1444 of the creation situation table 144 are updated.

  In step 1335, the product creation status (reference check 1442 and creation check 1444) is also updated for the products that must be created upon receipt of the creation of these products by updating the product creation status in step 1334. Since there is a possibility of influence, the deliverable that is indirectly affected in this way is acquired with reference to the deliverable relation table 141 and the document reference table 142.

  For example, by updating the “functional information hierarchy diagram” in the product relation table 141, the “information system related diagram” is acquired as the product that is directly influenced in step 1332, and the “information system related diagram” is created. Has been updated, and in this step, an “information system related diagram” has to be generated and a product that has to be created (not shown in the product related table 141 in FIG. 9 but, for example, “network configuration table”). As a product that is indirectly affected.

In step 1336, it is determined whether or not a product that is indirectly influenced in step 1335 has been acquired. When the indirectly affected product is acquired (Yes in Step 1336), the process returns to Step 1333, and the processing from Step 1333 to Step 1335 is repeated for all the indirectly affected products.
If a product that is indirectly influenced in step 1335 is not acquired (No in step 1336), the process proceeds to step 1337.

In step 1337, the deliverables acquired in steps 1332 and 1335 are regarded as deliverables affected by the key item or keyword update, and a list of these deliverables is created as a message.
In step 1338, the message created in step 1337 is transmitted to the developer terminal 2.
When the developer terminal 2 receives a message from the server 1, the message is displayed on the screen display unit 25 using a pop-up screen or the like.

According to the processing flow of FIG. 18, it is possible to check whether the creation status of other deliverables is affected by updating the key items or keywords of the received deliverables.
When this processing flow is completed, the processing flow in FIG. 16 ends.
Whether or not the processing from step 1332 to step 1338 is performed is determined depending on whether the key item or the keyword is updated in step 1331. However, the processing from step 1332 to step 1338 may be performed without fail in the determination of step 1331 as long as the received product content is updated.

FIG. 19 is a diagram showing a second processing flow for checking the influence on other deliverables accompanying the update of the deliverable content in step 1318 of FIG.
In FIG. 19, another product specifying the same key item or keyword as the key item or keyword of the received product is acquired, and the influence on the other product is checked.

In step 1341, with reference to the contents confirmation table (direct designation) 145 and the contents confirmation table (indirect designation) 146, key items and keywords designated to be described in the deliverable are obtained, and these key items are obtained. And check whether there are other specified artifacts that are going to describe the keyword.
If such other deliverables exist (Yes in step 1341), the process proceeds to step 1342. If not (No in step 1341), the process of FIG.

In step 1342, the deliverable determined to exist in step 1341 is acquired.
The processing from step 1333 to step 1338 is the same as the processing from step 1333 to step 1338 in FIG.

According to the processing flow of FIG. 19, it is possible to check other deliverables that specify the same key item or keyword as the key item or keyword of the received deliverable.
When this processing flow is completed, the processing flow in FIG. 16 ends.
As described above, it is possible to check whether the contents of the created product are appropriate by the processing flow of FIG.

  As described above, according to the information system development support system S of the present embodiment, it is possible to grasp not only whether or not the document to be referred to is referred to but also the degree of reference when the document is created. In addition, the system development and product creation according to the system development procedure and project plan can be supported for the developer, so that the personality that depends on the ability and knowledge of the developer can be eliminated, It is possible to ensure that the quality of the product is above a certain level.

  In addition, whether the developer is performing system development or product creation in accordance with the system development procedure or project plan is not checked on an occasional basis through human intervention. Since the check is performed in real time, it is possible to reduce the work man-hours and management man-hours related to the verification and update of the deliverable contents.

  Each process in the server 1 and the developer terminal 2 can be realized by a predetermined person (such as a programmer) creating and executing a program to be executed by the CPU of the computer.

Although description of this embodiment is finished above, the aspect of the present invention is not limited to these.
For example, all the information in the content confirmation table (indirect designation) 146 can be absorbed by the content confirmation table (direct designation) 145, and the content confirmation table (indirect designation) 146 can be made unused.
In addition to XML, the data description may use other markup languages such as SGML (Standard Generalized Markup Language), or may use a language other than the markup language.
In addition, specific configurations of hardware, programs, display screens, and the like can be changed as appropriate without departing from the spirit of the present invention.

It is a figure which shows the function structural example of the information system development assistance system in this embodiment. It is a figure which shows an example of the display screen in the developer terminal of this embodiment. It is a figure which shows an example of the screen display of the document (sentence) of this embodiment. It is a figure which shows an example of the data content of the document (sentence) of this embodiment. It is a figure which shows an example of the screen display of the document (table | surface) of this embodiment. It is a figure which shows an example of the data content of the document (table | surface) of this embodiment. It is a figure which shows an example of the screen display of the document (diagram) of this embodiment. It is a figure which shows an example of the data content of the document (diagram) of this embodiment. It is a figure which shows an example of the product related table | surface of this embodiment. It is a figure which shows an example of the document reference table of this embodiment. It is a figure which shows an example of the reference condition table | surface of this embodiment. It is a figure which shows an example of the creation condition table | surface of this embodiment. It is a figure which shows an example of the content confirmation table | surface (direct specification) of this embodiment. It is a figure which shows an example of the content confirmation table | surface (indirect specification) of this embodiment. It is a figure which shows the processing flow which checks the document reference condition in the server of this embodiment. It is a figure which shows the processing flow which checks the product content in the server of this embodiment. It is a figure which shows the processing flow which checks the key item and keyword of a deliverable content in the process of FIG. It is a figure which shows the 1st processing flow which checks the influence on the other deliverables accompanying the update of deliverable content in the process of FIG. It is a figure which shows the 2nd processing flow which checks the influence on other deliverables accompanying the update of deliverable content in the process of FIG.

Explanation of symbols

1 Server 2 Developer terminal (terminal)
11 Transmitter / receiver (terminal transmitter / receiver)
12 Document reference status check section 13 Product content check section (document content check section)
14 storage unit 21 input unit 22 document reference status detection unit 23 product content detection unit (document content detection unit)
24 Transmission / reception unit (server transmission / reception unit)
25 Screen display part (display part)
100 Processing Unit S Information System Development Support System (Document Creation Management System)

Claims (16)

A document creation management system comprising: a terminal where a user creates a document; and a server that is connected to the terminal via a communication network and manages information related to creation of a document by the terminal,
The terminal
A display for displaying information;
An input unit for performing an information input operation related to creation of a document by the user;
A document reference status detection unit that detects a document being created, a document that is being referenced for creation of the document, and an operation event that is an operation content in the input unit related to the document that is being referenced;
A document transmitting / receiving unit that transmits the document being created, the document being referred to, and the operation event detected by the document reference status detecting unit;
The server
A server transmitting / receiving unit that receives the document being created, the document being referred to, and the operation event from the terminal;
A storage unit that stores document reference information that stores information on documents to be referred to when creating the document for each document;
Based on the document reference information in the storage unit, it is determined whether or not all the documents to be referred to when creating the document being generated received from the terminal have been referred to, and the operation event is stored in the storage unit together with the determination result And a document reference status check unit. In the server,
The storage unit further stores, for each document, document-related information that stores information on other documents that must be completed before the document is created,
The document reference status check unit determines whether or not the creation of another document that should be completed before the creation of the document being created received from the terminal is completed based on the document related information in the storage unit. The document creation management system according to claim 1, wherein determination is made. The operation event is an operation of the input unit that changes a display page of the document being referred to,
When the document reference status detection unit detects the operation event, the terminal transmission / reception unit includes a document being created at that time, display information of the document being referenced displayed after the display page is changed, and the user Send the identification information to the server,
The document reference status check unit of the server, together with the determination result of whether or not all the documents to be referred to when creating the document being created have been referred to, display information of the document being referenced displayed after the display page is changed The document creation management system according to claim 1, further comprising: storing the identification information of the user in the storage unit. The operation event is an operation by the input unit on a display area of the document being referred to,
The terminal transmission / reception unit, when the document reference status detection unit detects the operation event, the document being created at that time, the display information of the document being referenced being displayed in the display area, and the identification of the user Send information to the server,
The document reference status check unit of the server, together with a determination result of whether or not all the documents to be referred to when creating the document being created have been referenced, display information of the document being referenced being displayed in the display area, The document creation management system according to claim 1, wherein the user identification information is stored in the storage unit. The server
The storage unit further stores content confirmation information for storing key items that are essential items for each document and keywords that are essential words,
The document content check unit for determining whether or not the key item and the keyword exist in the document being created received from the terminal based on the content confirmation information in the storage unit. Item 2. The document creation management system according to Item 1. The server
The storage unit further stores content confirmation information for storing a key item that is an essential item for a document that references the document and a keyword that is an essential word for each document,
A document content check unit that determines whether the key item and the keyword exist in a document that refers to the document being created received from the terminal based on the content confirmation information in the storage unit. The document creation management system according to claim 1, wherein The document content check unit refers to the document related information, and affects the management status of other documents according to the determination result of whether the key item and the keyword exist in the document being created. 6. The document creation management system according to claim 5, wherein the document creation management system determines whether or not. The terminal
A document content detection unit for detecting the content of the document before switching when the document being created is switched to another document on the display unit;
The terminal transmission / reception unit, when the document content detection unit detects the content of the document before switching, transmits the content of the document before switching and the identification information of the user to the server,
The server
When the server transmission / reception unit receives the content of the document before switching from the terminal and the identification information of the user,
The document content check unit determines whether the key item and the keyword exist in the content of the document before switching based on the content confirmation information in the storage unit, and the determination result and the user identification Information is memorize | stored in the said memory | storage part. The document creation management system of Claim 5 characterized by the above-mentioned. The terminal
A document content detection unit that detects the content of the document at that time when the document being created has completed the entry of all the data of the table items in the display unit;
The terminal transmission / reception unit transmits the detected document content and the user identification information to the server when the document content detection unit detects the content of the document,
The server
When the server transmission / reception unit receives the content of the detected document and the identification information of the user from the terminal,
The document content check unit determines whether the key item and the keyword exist in the detected document content based on the content confirmation information in the storage unit, and the determination result and the user identification information Is stored in the storage unit. The document creation management system according to claim 5. In the server,
The storage unit further stores, for each document, creation status information for storing a document reference status to be referred to when the document is created, and the presence status of key items and keywords,
The document creation management according to claim 5, further comprising: a processing unit that determines that the creation of a document in which both the reference status and the existence status are satisfactory based on the creation status information of the storage unit. system. A terminal that connects to a server that manages information related to document creation via a communication network, and a user creates a document.
A display for displaying information;
An input unit for performing an information input operation related to creation of a document by the user;
A document reference status detection unit that detects a document being created, a document that is being referenced for creation of the document, and an operation event that is an operation content in the input unit related to the document that is being referenced;
A transmission / reception unit for transmitting / receiving information,
The transmission / reception unit transmits the document being created, the document being referred to, and the operation event detected by the document reference status detection unit to the server, so that the document being created is transmitted to the server. A terminal that determines whether or not all documents to be referred to at the time of creation have been referred to, and stores the operation event together with the determination result. A document creation management method using a terminal that is connected to a server that manages information related to document creation via a communication network, and a user creates a document.
The terminal
A display for displaying information;
An input unit for performing an information input operation related to creation of a document by the user;
A document reference status detection unit that detects a document being created, a document that is being referenced for creation of the document, and an operation event that is an operation content in the input unit related to the document that is being referenced;
A transmission / reception unit for transmitting / receiving information,
The transmission / reception unit transmits the document being created, the document being referenced, and the operation event detected by the document reference status detection unit to the server, whereby the document being created is transmitted to the server. A document creation management method, characterized in that it is determined whether or not all documents to be referred to at the time of creation have been referenced, and the operation event is stored together with the determination result.   A program for causing a computer to execute the document creation management method according to claim 12. A server that is connected to a terminal for creating a document through a communication network and manages information related to creation of a document by the terminal,
A transmission / reception unit that receives, from the terminal, a document being created, a document being referenced, and an operation event that is an operation content of the input unit of the terminal related to the document being referenced;
A storage unit that stores document reference information that stores information on documents to be referred to when creating the document for each document;
Based on the document reference information in the storage unit, it is determined whether or not all the documents to be referred to when creating the document being generated received from the terminal have been referred to, and the operation event is stored in the storage unit together with the determination result And a document reference status check unit. Document reference information that is connected to a terminal where a user creates a document via a communication network, manages information related to document creation by the terminal, and stores document information to be referred to when creating the document for each document. A document creation management method by a server having a storage unit for storing,
When the transmission / reception unit receives from the terminal a document being created, a document being referred to, and an operation event that is an operation content in the input unit of the terminal regarding the document being referred to,
Based on the document reference information in the storage unit, the document reference status check unit determines whether all documents to be referred to when creating the document being created received from the terminal have been referred to, and together with the determination result, the operation An event is stored in the storage unit. A document creation management method, comprising:   A program causing a computer to execute the document creation management method according to claim 15.

Images