JP2001005874A - Minute book managing system having document information managing function - Google Patents

Abstract

PROBLEM TO BE SOLVED: To manage a document, which is prepared or corrected with the progress of a development project, while relating it with the minute book of a review conference for that document. SOLUTION: A conference information table 17 stores information such as a minute book ID, the title of a conference and the date of the conference for each conference. An item/document correspondence table 119 stores a development item and the identifier of a corresponding document for each project. A document information table 120 stores the correspondence of the minute book ID and the identifier of the document. A proceeding information register part 112 registers the conference information and the identifier of the related document in the conference information table 117 and the document information table 120. When any project identifier is designated, a document preparation history extracting part 114 extracts the related minute book ID from the item/ document correspondence table 119 and the conference information table 117 and by referring to the conference information table 117, the version of the document and the conference information are correspondently displayed on a display 102.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for managing the minutes of a meeting, and more particularly to a system for managing the minutes of a meeting while maintaining the association with documents created or modified as the development project progresses.

[0002]

2. Description of the Related Art In the past, the management of the minutes created at the time of a meeting or meeting was often performed as follows. (1) Make minutes of each meeting / meeting using a word processor. (2) When distributing the minutes, distribute the minutes to concerned parties by communication means such as e-mail, or print and distribute on paper. (3) When storing the minutes, store the minutes as an electronic minutes file in a computer device such as a document file server, or store the minutes in a file printed on paper. At this time, documents such as design documents that have been discussed in the meeting are matched to the storage format of the minutes. If the storage format of the minutes is an electronic file, the electronic design document file is stored in a document file server. If the storage format of the minutes is paper, the design document is printed on paper and bound and stored together with the minutes file. (4) When managing different versions of design documents attached to the minutes, which are considered over multiple meetings, the electronic minutes file and minutes file stored on the document file server should be used together. Refer to the stored design document files one by one, or manually refer to the minutes printed on paper and the design documents bound together with the minutes, and use the contents described in the minutes as a clue. Create a change history table. (5) Electronic minutes files and minutes files stored on a document file server to determine the process of studying different design documents attached to the minutes, which have been reviewed over multiple meetings. Reference is made one by one to the design document file stored in conjunction with the above, or to manually refer to the minutes printed on paper and the design documents bound together with the minutes.

As a conventional technique for managing document information and minutes of a meeting, there is a technique described in, for example, JP-A-8-16578.

[0004]

According to the above-described conventional method, when managing design documents of different versions attached to the minutes prepared for each meeting, which are examined over a plurality of meetings, If you want to understand the history of the design document review, refer to the electronic minutes file stored on the document file server and the design document file stored together with the minutes file, or print them out on paper. It is troublesome to refer to each of the minutes and the design documents bound together with the minutes by hand, and to create a change history table based on the contents described in the minutes. was there.

[0005] Further, according to the technique described in Japanese Patent Application Laid-Open No. H8-16578, a registrant can obtain information on target document information and discussions, points to be pointed out, decisions made on the document, and the like. Can be associated with Therefore, it is possible to refer to individual materials for each meeting. However, it leaves the problem that it is not possible to display similar discussions and findings from all the meetings that have been held many times at once, or to list the progress of discussions on multiple documents.

[0006] It is an object of the present invention to provide a minutes management system that manages a document created or modified with the progress of a development project and the minutes of a review meeting of the document in association with each other.

Another object of the present invention is to manage a development item in a development project in association with a document to be created,
It is an object of the present invention to provide a minutes management system that manages development items, documents, and minutes in association with each other.

[0008]

According to the present invention, there is provided a storage means for storing meeting information having a project identifier, a meeting title, and a meeting execution date in association with an identifier of a document which is a subject of the meeting. And a processing means for extracting, when a project identifier is designated, the meeting information related to the designated project and the identifier of the corresponding document in association with each other.

According to the present invention, there is provided a first storage means for storing meeting information having a title of a meeting and an implementation date of the meeting in association with an identifier of a document which is a subject of the meeting, and a developing process for each project. Second storage means for storing the hierarchical items associated with and the identifiers of the documents in association with each other;
A minutes management system comprising, when a project identifier is designated, processing means for referring to the second storage means and extracting relevant meeting information via the identifier of a document related to the designated project. .

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The embodiments of the minutes management system according to the present invention will be described below in detail with reference to the drawings. The embodiment of the present invention described below transmits minutes and document information input in a predetermined format from a client computer to a server computer,
Register and store in a storage device in a prescribed data storage format. On the other hand, by comparing the target document name corresponding to the standard review item determined in advance by the server computer with the document name in the document information table, the document accumulated together with the minutes examined and discussed by multiple reviews A document creation history list that displays a list of the edition history and the minutes corresponding to the edition is displayed on the display device. Furthermore, when the user presses the change history button corresponding to the document name in the list from the document creation history list, a change history list is created and displayed in chronological order of the minutes of the meeting for reviewing the target document. I do.

FIG. 1 is a diagram showing a hardware configuration and functional blocks of a minutes management system according to the present embodiment. 1
Reference numeral 09 denotes a server computer, which is a central processing unit 11.
0, a main storage device 111, and an external storage device 116 such as a hard disk. The main storage device 111 stores programs of a proceeding information registration unit 112, a processing result transmission unit 113, a document creation history extraction unit 114, and a change history extraction unit 115.

The external storage device 116 stores a conference information table 117, a meeting contents table 118, an item document correspondence table 119, a document information table 120, and a document file 121.

Reference numeral 101 denotes an input of data and instructions from the user, and the minutes data is transmitted to the server computer 109.
And a client computer for displaying the processing result of the server computer to the central processing unit 1
05, a main storage device 106, an input device such as a mouse 104 and a keyboard 103 connected to the central processing unit 105, and a display device such as a display 102. The main storage device 106 stores a UI (user interface) unit 107 that receives input of data and instructions from a user and displays a processing result. A plurality of client computers 101 can be connected to a server computer 109 via a network 108.

Agenda information registration unit 112, processing result transmission unit 1
13. The programs of the document creation history extraction unit 114 and the change history extraction unit 115 are stored in a storage medium, and the main storage device 111 is connected via a drive unit connected to the central processing unit 110.
Or transmitted to the server computer 109 via a driving device connected to another computer, another computer, or a network, stored in the main storage device 111, and executed by the central processing unit 110.

FIG. 2 is a diagram showing the data structure of the conference information table 117. 201 is a minutes ID (identifier) for identifying the minutes, 202 is the name (identifier) of the project to which the meeting belongs, 203 is the title of the meeting, 20
Reference numeral 4 denotes the date of the meeting (execution date), and reference numeral 205 denotes attendees of the meeting. One line of information 201 to 206 forms one conference information record.

FIG. 3 is a diagram showing the data structure of the proceedings content table 118. As shown in FIG. 301 is a minutes ID for identifying the minutes, 302 is a number for identifying a paragraph in the same minutes, a number assigned to a small item corresponding to the minutes of the minutes, and 303 is described in the minutes. Major items,
304 is a small item described in the large item 303, 305 is a conclusion at the meeting described for the large item 303 or the small item 304, and 306 is a reason corresponding to the conclusion 305. Numerals 301 to 306 form one record by one line.

FIG. 4 is a diagram showing the data structure of the item document correspondence table 119. Item document correspondence table 119
Is a table provided for each project, in which standard large items and small items to be reviewed in the project are set, and a document name corresponding to the item is set. 401 is an ID for identifying each item,
402 is a classification of the development process of the project, 403 is a large item of standard development in the development process, 404 is a small item of standard development, and 405 is a target document name of a document describing the item. Reference numerals 401 to 405 form one record by one line. In the example shown in FIG. 4, the item whose ID is “1” is an item to be considered when designing the DB.
DB data item design is considered as a major item, and duplication of data items is examined as a minor item, and the examination results indicate that the results should be described in a document called “data item list”.

FIG. 5 is a diagram showing the data structure of the document information table 120. Reference numeral 501 denotes a minutes ID for identifying the minutes, 502 denotes a document name, and 503 denotes a document file name. The document name 502 is a user-friendly document name and does not include the version number of the document. The document file name 503 is an identifier of a file storing the document,
Includes the version number of the document. Only the document file name 503 or the document name 502 and the document file name 503 can be regarded as a document ID. 501-
A line 504 forms one document information record.

FIG. 6 is a diagram showing an example of data of a minutes registration screen displayed on the display 102. 601 is a conference title input field, 602 is a project name input field for the conference, 603 is a conference date input field, 604 is a conference attendee input field, 605 is a meeting content input field, Reference numeral 606 denotes a document name input field, and 607 denotes a document file name input field. Here, the proceedings contents input field 60
5 is input with a chapter number and a section number such as “1.” and “1.1”. A target document name input field 606 allows the user to select a document name from a pull-down menu. In the pull-down menu, all target document names 405 registered in the item document correspondence table 119 are displayed. By selecting the document name from the pull-down menu, the item of the item document correspondence table corresponding to the document name can be transcribed to the entry field 605 of the contents of the agenda. Reference numeral 608 denotes a reference button, which allows the user to reference a registered document file name. A registration button 609 is used to transmit the input contents to the server computer 109.

The contents of the agenda correspond to the target document. By inputting the agenda contents and pressing a registration button 609, the agenda contents are stored in the agenda contents table 118, and the correspondence between the minutes and the document information is obtained. Is registered in the document information table 120. It is possible to register a plurality of sets of proceedings contents and target documents for one proceedings. It is assumed that the draft of the target document is created before the meeting and registered in the document file 121. It is possible to modify the documents produced according to the conclusions of the meeting. The date of the meeting is deemed to be the date of preparation or amendment of the document.

Next, with reference to the flowchart of FIG. 7, a process for registering the minutes inputted by the user to the client computer 101 in the meeting information table 117, the meeting contents table 118 and the document information table 120 of the server computer 109. Will be described in detail.

First, the minutes information registration unit 112 displays a minutes registration screen on the display 102 of the client computer 101, and receives the contents (601 to 607) of the minutes input via this screen (step 90).
1). When the registration button 609 is pressed after the input, the client computer 101 transmits the input minutes (601 to 607) to the server computer 109 (step 902). The minutes information registration unit 112 of the server computer 109 receives the contents of the minutes (step 903), and stores the minutes ID2 in the meeting information table 117.
The minutes ID is determined so that 01 is unique (step 904).

Next, the proceedings information registration unit 112 proceeds to step 9
The contents of the minutes ID, title 601, project name 602, implementation date 603, and attendee 604 determined in step 04 are stored in the minutes ID 201, project name 202, title 203, implementation date 204, and attendee 205 of the conference information table 117. It is stored (step 905).

Next, regarding the contents of the proceedings 605 received,
The major item, the minor item, the conclusion and the reason are cut out and stored as the major item 303, the minor item 304, the conclusion 305 and the reason 306 of the agenda table 118, respectively. At this time, the minutes ID determined in step 904 is also minutes ID3.
01 is stored. If there are a plurality of large items or small items, a number unique to the contents of the meeting with the same minutes ID is stored in the number 302 (step 906). The cutout of a large item or a small item is performed based on a chapter number or a section number, for example, “1.” or “1.1”. The extraction of conclusions and reasons is performed based on, for example, “conclusion:” and “reason:”.

Next, the determined minutes ID is added to the contents of the input document name 606 and document file name 607 and stored in the minutes ID 501, the document name 502 and the document file name 503 of the document information table 120 ( Step 907). Steps 906 and 907 are repeated each time a registration button 609 is pressed for a plurality of agenda contents corresponding to the agenda contents and for each agenda content and target document input.

FIG. 8 is a diagram showing an example of data of a document creation history list screen displayed on the display 102. 7
Reference numeral 01 denotes a project name input field, and reference numeral 702 denotes a reference button, from which a registered project name can be referred. 703 is the serial number of the list, 704 is the document name,
Reference numeral 705 denotes the version of the document indicated by the document name 704, ie, the date of the meeting, and reference numeral 706 denotes the review minutes of the version of the document, ie, the title of the minutes at the time of the meeting. For the document displayed in the document name 704, several review meetings are held, and each time a document is created or modified, the document information table 120 indicates that the minutes and the minutes are linked. . The version may be the version identifier instead of the date. Reference numeral 707 denotes a change history button for creating and writing the document.
This button is used to display the history of the meeting that has been corrected.

Next, with reference to the flowchart of FIG. 9, the flow of processing when displaying the document creation history list using the information of the conference information table 117 and the document information table 120 stored in the server computer 109 will be described. This will be described in detail.

First, the document creation history extracting unit 114 displays a document creation history list on the display 102 of the client computer 101, and receives the input project name via this screen (step 1001). The document creation history extraction unit 114 receives this project name
(Step 1002).

Next, it is determined whether or not all document information records in the document information table 120 have been processed (step 1003). If all the document information records have been processed, the process jumps to step 1007. If not, the process jumps to step 1004. Next, the document name of the document information record is referred to the item document correspondence table 119 with reference to the item document correspondence table 119 having the input project name.
It is determined whether or not there is a record that matches the target document name (step 1004). If there is no record that matches, the processing target record in the document information table 120 is advanced to the next document information record, and the process jumps to step 1003. If they match, this means that the target document is associated with the minutes, so the minutes ID and the document name of the document information record are acquired from the document information table 120 (step 1005). Minutes I that are the same as the acquired minutes ID
The title 203 and the implementation date 204 are acquired with reference to the conference information record of the conference information table 117 having D (step 1006). When the end of the document information table 120 is reached, a document creation history list is created by arranging the acquired document names, conference dates, and titles, and the processing result sending unit 113 sends this to the client computer 101 (step 1007).

The UI unit 107 of the client computer 101 receives this document creation history list and displays it on the display 102.

FIG. 10 is a diagram showing an example of data on a change history list screen displayed on the display 102. The change history list arranges, as a change history of a specified document, the contents of the proceedings of a meeting for reviewing the document in chronological order. Reference numeral 801 denotes a target project name, and reference numeral 802 denotes a designated document name as a target of the change history list. 8
03 is the title of the review minutes 706, 804 is the major item / small item appearing in the agenda, 805 is the conclusion of the agenda, and 806 is the reason.

Next, with reference to the flowchart of FIG. 11, a process for displaying a document change history list using the minutes data of the meeting information table 117 and the meeting contents table 118 stored in the server computer 109. Will be described in detail.

First, the UI unit 107 is connected to the display 102.
Of the change history button 707 arranged below the document name in the document creation history list displayed in step (1) (step 1101). The UI unit 107 transmits the project name input to the project name input field 701 and the document name corresponding to the change history button 707 to the server computer 109 (step 1102). Server computer 10
The change history extracting unit 115 receives the project name and the document name (step 1103).

Next, it is determined whether or not all the document information records in the document information table 120 have been processed (step 1104). If all the document information records have been processed, the process jumps to step 1109. If not, the process proceeds to step 1105.

Next, the received document name and document information table 1
It is determined whether or not the document name of the document information record 20 matches (step 1105). If not, the record to be processed in the document information table 120 is advanced to the next document information record, and the process jumps to step 1104. If they match, the process jumps to step 1106.

Next, the minutes ID of the document information record having the matching document name is obtained (step 1106), and the meeting information table 1 having the same minutes ID as the obtained minutes ID is obtained.
The project name and the title are acquired for the 17 meeting information records (step 1107).

The minutes I which are the same as the minutes ID obtained in the same manner
A major item, a minor item, a conclusion, and a reason are obtained for all records of the agenda content table 118 having D (step 1108). When the end of the document information table 120 is reached, the acquired large items, small items, conclusions and reasons are sorted in ascending order of the minutes ID to create a change history list, and the processing result transmitting unit 113 (Step 1109).

The UI unit 107 of the client computer 101 displays this change history list on the display 102.

In the above embodiment, the document name 50 of the document information table 120 is entered via the target document name 405 of the item document correspondence table 119 based on the input project name.
2, the corresponding record in the meeting information table 117 and the meeting contents table 118 is accessed via the corresponding minutes ID, but the project name 202 is stored in each record of the meeting information table 117. Minutes I stored in the conference information table 117
The corresponding document name 502 of the document information table 120 may be accessed by D201. In this case, the present invention can be implemented without the item document correspondence table 119.
Further, the conference information table 117 and the document information table 12
0 into one table and the conference information table 117
Each record has a project name 202 and a title 20
3, implementation date 204, document name 502 and document file name 5
03 may be provided. The procedure for creating a document creation history list in the case where the item document correspondence table 119 is not provided is to extract a record having the project name 202 as the project name input from the conference information table 117,
Document name 502 and implementation date 2 for the extracted record group
When sorting is performed using 04 as a key, the meeting information records of the specified project are arranged in order of execution date for each document name, and a document creation history list shown in FIG. 8 can be created. When the meeting information table 117 and the meeting contents table 118 are separated, a change history list can be created by combining a meeting information record having the same minutes ID and a meeting contents record. When the conference information table 117 and the document information table 120 are separated, the above sort may be performed after combining the conference information record having the same minutes ID and the document information record.

By providing the item document correspondence table 119, hierarchical items such as large items, medium items, and small items can be set as standard review items according to each development process of each project. As shown in the data example of the table 118, the contents of the agenda can be divided by these hierarchized items, the relation between the development process and the development items becomes clear, and the correspondence between the items and the target document can be easily grasped. can do. In the case where the item document correspondence table 119 is provided and the target document name 40
It is as described above that the present invention can be implemented simply by providing a standard item table without providing 5.

In this embodiment, the server computer 10
9 and the client computer 101 are described as constituting a system by being connected by a network 108, but the system may be constituted by one computer including the functions of both computers.

[0042]

As described above, according to the present invention, a document created or modified with the progress of a development project and the minutes of a review meeting of the document are managed in association with each other. And a meeting reviewed for that version can be associated and displayed in chronological order. One document and one minutes each
It is possible to eliminate the work of referring to each item and taking the correspondence. In addition, since the development items in the development project and the documents to be created are managed in association with each other, the development items, the progress of the discussion at the meeting, and the relationship between the documents can be displayed in a list.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a hardware configuration and functional blocks of a minutes management system according to an embodiment.

FIG. 2 is a diagram illustrating a data configuration of a conference information table 117 according to the embodiment.

FIG. 3 is a diagram showing a data configuration of a meeting content table 118 according to the embodiment.

FIG. 4 is a diagram showing a data configuration of an item document correspondence table 119 according to the embodiment.

FIG. 5 is a diagram illustrating a data configuration of a document information table 120 according to the embodiment.

FIG. 6 is a diagram showing a data example of a minutes registration screen.

FIG. 7 is a flowchart illustrating a process flow of a proceedings information registration unit 112 according to the embodiment.

FIG. 8 is a diagram illustrating a data example of a document creation history list screen.

FIG. 9 is a flowchart illustrating a processing flow of a document creation history extraction unit 114 according to the embodiment.

FIG. 10 is a diagram showing a data example of a change history list screen.

FIG. 11 is a flowchart illustrating a processing flow of a change history extraction unit 115 according to the embodiment.

[Explanation of symbols]

112: meeting information registration unit, 114: document creation history extraction unit, 115: change history extraction unit, 117: meeting information table, 118: meeting contents table, 119: item document correspondence table, 120: document information table

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/30 G06F 15/20 570R 590E 596A 15/40 310F 370A 15/401 310C 15/403 380D 380E (72 ) Inventor Hiroshi Kudo 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture F-term in System Development Laboratory, Hitachi, Ltd. 5B082 AA11 EA01 EA09 EA10 EA12 GA05 GA14 GC01 HA08

Claims (5)

[Claims] A storage means for storing meeting information having a project identifier, a meeting title, and a meeting execution date in correspondence with an identifier of a document which is a subject of the meeting, and a project identifier is designated. And a processing means for extracting the meeting information related to the designated project and the corresponding document identifier in association with each other. 2. The minutes management system according to claim 1, further comprising means for displaying said title in association with a version identifier of said document. 3. The minutes management system according to claim 2, further comprising: minutes of said meeting as said meeting information, and means for displaying said minutes of content in association with said version identifier. 4. A first storage means for storing meeting information having a meeting title and a meeting execution date and an identifier of a document which has been a subject of the meeting in association with each other, and a hierarchy associated with a development process for each project. Second storage means for storing the converted items and document identifiers in association with each other, and when a project identifier is specified, refers to the second storage means to store a document identifier related to the specified project. Processing means for extracting the relevant conference information via the Internet. 5. A storage medium for storing a computer-readable program, the program comprising, when a project identifier is designated, conference information including a project identifier, a conference title, and a conference implementation date. Program means for extracting the meeting information related to the specified project and the corresponding document identifier by referring to the storage means for storing the identifier of the document that has been the meeting in association with the document information; Storage means for storing a program, comprising: program means for displaying the title in association with the version identifier of the document.