JP2008176587A - File management system by storage structure of document, file management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a management system capable of easily finding out directories and holders to store documents and documents related thereto even if the documents are related to each other. <P>SOLUTION: The file management system comprises a document management matrix storage part 146 for storing classification information in which a plurality of classification items is conformed to a plurality of attributes in the classification items and relevant information in which the plurality of attributes in the classification items is related to each other for each classification item, and a holder generation part for generating a file storage holder for storing the attributes from the classification information and the relevant information. The system constitutes and displays a relation between a hierarchical structure having any one attribute stored in the file storage holder as a route and an attribute related to the attribute concerned. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a management system for various documents used in system design and the like. More specifically, a file storage folder for storing documents is structured according to the system to be designed, and files are managed by this file storage folder. It relates to a file management system.

  In recent years, companies and retailers have been required to meet customer expectations by enabling customers to select from a number of options for products desired by customers in order to meet the diverse needs of customers. Is coming. And it is also necessary to deliver this customer's products as quickly as possible. For this reason, it is necessary to design and construct a system requested by the user according to the business condition corresponding to each business type more promptly and taking into account customer needs. For this purpose, system engineers, programmers, and the like who are involved in this system construction need to refer to and create various documents in order to make the system more friendly to customers. Normally, documents are stored as files, and stored in a directory or folder having a hierarchical structure configured according to the contents of the files. The method of managing files in this hierarchical structure is to search in which directory or folder the created file should be stored and in which directory or folder the desired file is stored as the number of layers in the hierarchical structure increases. Becomes difficult.

A method for visually facilitating storage and retrieval of this file is described in, for example, Japanese Patent Laid-Open No. 2001-43231. In the invention described in this publication, a hierarchical structure is displayed in a tree shape, and a file is stored in a page which is the final branch of the tree.
Japanese Patent Laid-Open No. 2001-43231.

  In the invention of the above publication, each file is independent from each other, and one file can be associated with one directory or folder. Therefore, the hierarchical structure can also be configured in a simple tree shape. However, in the case of system design etc., a document describing a certain function is closely related to other documents in the system design. It becomes a tree structure. Therefore, it has been difficult to visually understand the storage and retrieval of such complicatedly related documents.

  An object of the present invention is to provide a management system that can easily find a directory, a folder, and a related document in which the document is stored even if the documents are related to each other.

  The file management system according to the present invention provides a classification information in which a plurality of classification items are associated with a plurality of attributes in the classification items, and an association between the plurality of attributes in the classification items for each classification item. A document management matrix storage unit for storing the associated information, and a folder generation unit for generating a file storage folder for storing the attribute from the classification information and the related information stored in the document management matrix storage unit And a hierarchical structure having one of the attributes stored in the file storage folder as a root or an attribute related to the attribute is configured and displayed.

  The file management method according to the present invention generates classification information by associating a plurality of classification items with a plurality of attributes in the classification items, and the plurality of attributes in the classification items for each classification item. Corresponding associations are generated and related information is generated, a file storage folder for storing the plurality of attributes is generated from the classification information and the related information, and any attribute stored in the file generation folder is Selecting and configuring an association between a hierarchical structure rooted at the selected attribute or an attribute associated with the attribute, and displaying the association between the hierarchical structure or an attribute associated with the attribute It is characterized by.

  In the configuration according to the present invention, since folders storing complicatedly related documents are stored and stored for each category and each relationship, a desired folder can be displayed in a hierarchy or a directory. It has an effect that can be easily done.

  The present invention is a file management system that enables various documents created when a system is constructed to be stored, updated, searched, and the like in a predetermined folder, and includes a predetermined folder of the document and other related folders. This makes it easy to see the relationship visually and facilitates processing such as storing, updating, and searching.

  FIG. 1 is a diagram showing a configuration example of a file management system according to the present invention. In FIG. 1, the file management system 100 is connected to an operation terminal 120 via a communication line 110, and the operation terminal 130 is a file It is configured to connect directly to the management system 100. The file management system 100 may be configured to connect only one of the operation terminal 120 or the operation terminal 130.

  The file management system 100 illustrated in the present invention includes a communication interface unit 140 for communicating with the operation terminal 120, the operation terminal 130, and other systems (not shown). Users of the operation terminal 120 and operation terminal 130 using this file management system 100 register an account and password in advance via the registration authentication unit 150, and the registration data is stored in the user data storage unit 152. . When transmitting / receiving data to / from the operation terminal 120 and the operation terminal 130 via the communication interface unit 140, the operation terminal 120, the operation terminal 130, and User registration and authentication are performed by the registration authentication unit 150, and the authentication unit 150 allows the authenticated operation terminal 120, operation terminal 130, and user to access the file management system 100. Data from the operation terminal 120 and the operation terminal 130 authenticated by the file management system 100 includes a CPU that controls and processes each unit of the file management system 100, a ROM that stores programs, a RAM that temporarily stores data, and the like The desired data is sent from the document management matrix storage unit 146 and the document storage unit 144 to the operation terminal 120 and the operation terminal 130, and the data from the operation terminal 120 and the operation terminal 130 Is converted into a predetermined format by the document management unit 142 and stored in the document management matrix storage unit 146 and the document storage unit 144.

  In FIG. 1, the user data storage unit 152, the document management matrix storage unit 146, and the document storage unit 144 are illustrated as individual storage units. However, the user data storage unit 152, the document management matrix storage unit 146, and the document storage unit 144 are not necessarily provided separately. The data may be stored in a distributed manner. Further, the operation terminal 120, the operation terminal 130, and the user to be used are provided with restrictions, and data related to the restrictions is configured to be stored in the user data storage unit 152 as registered data. You may make it regulate the data range and operation content (only reference of a document, a change of a document, etc.) which the terminal 120, the operation terminal 130, and a user can utilize.

  Next, file storage folder generation processing and the like according to the present invention will be described with reference to FIGS.

  FIG. 2 is a table in which various documents necessary to construct a system according to a customer are classified into system construction procedures and documents for system construction. The first classification 210 is a classification related to the process sequence of system construction. The first classification 210 includes a process (A) 212 corresponding to the classification name, a system analysis 214 which is an attribute belonging to this classification, and a user interface 216. , System design 218, program design 220, and the like are registered as attribute names. The second classification 230 includes a process (B) 232 corresponding to the classification name, a business requirement definition 234 corresponding to the process (A) 214 of the first classification 210, a screen layout design document 236 corresponding to the user interface 216, and the like. A job list 238 corresponding to the system design 218 and an application structure design document 240 corresponding to the program design 220 are registered as attributes. The third classification 250 handles documents in which the name is a function 252 and the contents to be constructed are classified by function, and the attributes are this function (A), function (B), etc. (A) etc. 254 are attribute names corresponding to the following contents, for example.

  As a specific example, a case will be described in which an ordering / ordering system for house interior products (hereinafter referred to as an ordering / ordering system) is constructed. In this ordering system, when a customer visits a showroom or the like and purchases a desired product, the product is estimated and ordered, or the contractor receives an order for the product from the customer. This is a system for conducting business. Hereinafter, a case where a customer visits a showroom and purchases a desired product will be described.

  In this specific example, the system is required to have the following functions.

  Function (A): Customer information registration. In this function A, business negotiations are numbered, and customer information such as the customer's address, telephone number, and housing of the current house is registered in the case of rehome.

  Function (B): Proposal plan creation function. In this function B, a proposal plan is numbered, and product information such as a product series corresponding to a product desired by the customer and a product color pattern is registered. In this proposal plan, a plurality of pieces of product information corresponding to various plans such as high-end products, standard products, and function-oriented products may be registered.

  Function (C): Estimating function. In this function C, for example, when the customer wants to re-home around the water, estimate for each product such as kitchen, bathtub, toilet, etc., which is the product to be re-homed, estimate the cost of incidental work, etc. Create an estimate statement for the customer's desired product. In this estimate, most of the products are standard products, and the door handle can be replaced with a standard product.

Function (D): Ordering function. This is a function for deciding which plan to order and placing an order, and the ordering information is transmitted to the ordering party.
Function (E): Form creation function. This is a function for creating a proposal such as a proposal for each plan to be proposed, an order specification for a product supplier, and a drawing.

  In the fourth classification 260, the name is called a platform 262, and attributes such as Windows (trademark) and UNIX (trademark) 264, which are OS names used in the system to be constructed, are used.

  A file storage folder generation process for storing the attributes of each category shown in FIG. 2 will be described with reference to FIGS. In this embodiment, various input operations for file storage folder generation processing are performed from the input / output device (not shown) of the file management system 100 shown in FIG. 1, the operation terminal 120 or the operation terminal 130. Is called. When the process is started (step 300), first, registration of a category and attributes within the category are registered. An example of the input screen for this registration is shown in FIG. In the present embodiment shown in FIG. 4, the input item names of classification 342 and name 346 are displayed on the screen 340, input fields 344 and 348 are provided on the right side, and the attribute name is input below the attribute name 350. An input field 352 is provided. You can also enter the item name directly in each entry field 344, 348, 352, and by clicking the pull-down menu button displayed in the inverted triangle on the right side of each entry field, you can use the class name and name that you use regularly. Each attribute name is displayed, and a desired item can be selected from the displayed items by designating the desired item with an input means such as a mouse.

  Next, the input field of the upper class relation 354 specifies how the attribute name input to the input field 352 is related to the upper class, “None” 356, “Yes” 358. , Click any of “All” 360 to use. “None” 356 indicates that the input attribute name is not related to the higher level classification, “Yes” 358 indicates that the input attribute name is related to a certain attribute of the higher level classification, and “All” 360 Indicates that it is related to all higher classifications.

  The display field 372 in the display frame 370 is displayed according to “No” 356, “Yes” 358, and “All” 360 selected in the input field 352. The “system analysis” 374, “user interface” 376, and “system design” 378 displayed in the display frame 370 sequentially display the attribute names input from the input field 352.

  The state shown in FIG. 4 will be described in more detail. This display state shows a state where each attribute name of the first classification in FIG. 2 is being input, and the input field 344 displays “first classification”. ”Is displayed in the input field 348,“ Process (A) ”is displayed, and“ System Design ”is input in the input field 352. The attribute names input in these input fields 352 are displayed in the display frame 370 in order.

  In this first classification, since there is no upper classification, “none” 356 of the upper classification relation 354 is clicked (indicated by a halftone dot in the figure). Accordingly, the input field 372 displays “no upper related classification”.

  When the attribute name “program design” shown in FIG. 2 has been entered in the input field 352, clicking on the confirm button 380 in FIG. 4 completes the registration of the first classification, and each attribute name is entered in FIG. Each attribute name is processed by the document management unit 142 and stored in the document management matrix storage unit 146.

  Next, registration of each attribute name of the second classification in FIG. 2 will be described with reference to FIG. The display screen of FIG. 5 is the same as that of FIG. As shown in FIG. 2, the business requirement definition 234 corresponds to each attribute of the second category with respect to the system analysis 214. Therefore, “second classification” is input in the input field 344, the process (B) is input in the input field 348, and the attribute name of the second classification 230 is input in the input field 352 (“concept relation diagram” in the drawing). "Enter.) Since each attribute name of the second classification 230 is related to each attribute name of the first classification 210 that is the higher classification, “Yes” 358 of the higher classification relation 354 is selected.

  Therefore, when this “present” 358 is selected, the display column 372 inputs the upper classification name and attribute name, and then inputs each attribute name from the input column 352. FIG. 5 shows that “business requirement definition”, “business operation requirement”, “concept related diagram”, and the like input from the input field 352 are displayed in the display frame 370. When the attribute name related to the input field 352 has been entered, the confirm button 380 is clicked. When this confirmation button 380 is clicked, the registration of the attribute names of the second classification related to the first classification step (A) system analysis is completed, and the attribute names input and associated with each other are displayed in the document management section of FIG. 142 is associated with the upper classification and stored in the document management matrix storage unit 146.

  Next, registration of each attribute name of the third classification in FIG. 2 will be described with reference to FIG. The display screen of FIG. 6 is the same as that of FIG. 4 and FIG. As shown in FIG. 2, since the attributes of the third category are all related to the attribute names of the first category 210 and the second category 230, which are the higher-level categories, "360" is clicked, and in response to this, the input field 372 displays "All relations to the upper class". The attribute names input in the input field 352 are sequentially displayed in the display frame 370. When the necessary attribute names are registered, when the confirmation button 380 is clicked, the input attribute names are displayed in the document management of FIG. The unit 142 associates with the upper classification and stores it in the document management matrix storage unit 146.

  Further, since the fourth classification 260 shown in FIG. 2 is related to all of the upper classifications, the input attribute names are input by the document management unit 142 of FIG. 1 in the same manner as the third classification 250 described in FIG. Are associated with the upper classification and stored in the document management matrix storage unit 146.

  Next, returning to FIG. 3, the step 304 for registering the association of attributes between the categories will be described with reference to FIGS.

  FIG. 7 is a diagram showing the relationship between the attributes of the first classification. As shown in FIG. 4, the order of inputting the attribute names of the first classification is determined by the document management unit 142 shown in FIG. It is stored in the document management matrix storage unit 146 in the form of a link between the attributes of the first category. FIG. 7 shows the relationship.

  FIG. 8 shows the relationship between the attribute names of the second classification shown in FIG. That is, the design result advanced in the order of the screen layout design document 420 and the screen function specification document 422 and the design result advanced in the order of the data structure specification document 430 and the data specification document 432 are combined, and then the application structure. Work on the design document 424 and the like proceeds.

  Thus, the case where the association between the attributes described in FIG. 8 is registered will be described with reference to FIG. FIG. 9A is substantially the same as the screen described in FIG. 4, and is that a display frame 371 is used instead of the upper classification relation 354 and the display frame 370 in the screen of FIG. 4. In the input fields 344 and 348, the classification names and names of the attributes to be associated are input, and the attribute names are sequentially input in the input field 352. In FIG. 9A, the attribute names input from the input field 352 are displayed in the display frame 371 as a screen layout design document 382A, a screen function specification document 383A, and an application structure design document 384 in this order. Following the application structure design document 384A, desired attribute names may be sequentially input. When the input is completed, when the confirmation button 380 is clicked, the attribute name input and displayed is once held in the document management unit 142 of FIG.

  Next, in FIG. 9B, attribute name data structure specification 382B, data specification 383B, and application structure design 384B are sequentially input and displayed. When the confirmation button 380 is clicked at this time, the attribute name input and displayed is the attribute name input in FIG. 9A temporarily held in the document management unit 142 in FIG. 1 and the attribute name in FIG. 8), the related data between the attributes shown in FIG. 8 having the same attribute name as a node is generated and stored in the document management matrix storage unit of FIG.

  Next, returning to FIG. 3, step 306 of generating a file storage folder from the classification and the related information will be described. Regarding the attribute name of the first category, the relation between the first category is determined by the input shown in FIG. 4 and the processing in the document management unit 142 of FIG. 1, and the attribute name of the second category is shown in FIG. In the input method shown in FIG. 5, the relationship with the attribute name of the first category is determined by the processing in the document management unit 142 in FIG. 1, and the input shown in FIG. 6 is used for the third and fourth categories. The method is associated with each attribute name of the upper classification by the processing in the document management unit 142 in FIG. 1 and stored in the document management matrix storage unit 146 in FIG.

  Since the attribute for each category is associated with the inside and outside of each category, a folder corresponding to each attribute corresponding to FIG. 10 is configured by the document management unit 142 and stored in the document management matrix storage unit 146. By associating the folder with each folder assigned to the attribute, the structure of the file storage folder 800 shown in FIG. 10 can be generated.

  In FIG. 10, folders such as system analysis 813 to program design 816 are stored in the name first classification 812, and folders 823 to 832 are stored in the name second classification 822 in association with the upper classification. In the third and fourth classifications 842 and 852, each function is stored in association with each folder of the upper classification. Note that only some of the attributes in the fourth classification 852 are shown.

  Next, a procedure for searching for each folder configured as described above will be described with reference to FIG. The file search process is performed under the control of the document management unit 142 in FIG. 1. When the search process is started in step 500, the process proceeds to the class designation step 502 and the classification is designated as shown in FIG. A category selection screen 550 serving as a search axis is displayed on the monitor screen of the operation terminals 120, 130, etc., and a category name is selected in a drop menu format on the selection screen 554 below the category name column 552.

  In step 504, detailed search conditions are designated. A selection screen 570 displayed on the monitor screen of the operation terminals 120, 130, etc. at this time is shown in FIG. In the lower part of the condition designation column 572 for each category, the first category 574 to the fourth category 580 are displayed with category names and names, and designated items are selected and displayed in a drop menu format in each left column. FIG. 13 shows an example in which no designation is selected for the first classification 574 and the second classification 576, the function (A) is selected for the third classification 578, and no designation is selected for the fourth classification.

  When the search condition is specified, whether the display format of the search result is hierarchical display or directory display is displayed on the monitor screen of the operation terminals 120, 130, etc. When the hierarchical display is selected, the hierarchical display shown in FIG. 14 is displayed in step 508. In this display, a hierarchical structure starting from the function (A) that is the search axis of the search condition is displayed. FIG. 15 is another display example showing the search result of the hierarchical structure. The difference from FIG. 14 is that a display 710 showing the search conditions and the like is also displayed on the display screen 700.

  Next, when the directory flow display is selected in step 506 of FIG. 11, the directory display of each folder as shown in FIG. This directory display is displayed based on FIG. 7 and FIG. As shown in FIG. 16, the directory display may be a display format showing the relationship between the attributes. In addition to this FIG. 16, the search condition 762 may be displayed on the display screen 752 as shown in FIG. .

  Next, returning to FIG. 11, the file created in the predetermined directory in step 510 is registered, and the process ends in step 514.

  When managing various types of documents related to system design, classify tasks related to system design, classify attributes for each category, create association folders, create storage folders, and search Enables hierarchical display and directory display.

Diagram showing an example of system configuration Diagram showing an example of classification and its attributes The figure which shows the flowchart of the production | generation process of a file storage folder The figure which shows an example of the input screen which registers the attribute in a classification The figure which shows an example of the input screen which registers and relates the attribute in a classification | category The figure which shows an example of the input screen which registers and relates the attribute in a classification | category Diagram showing examples of associations of attributes in a classification Diagram showing examples of associations of attributes in a classification The figure which shows an example of the input screen which relates the attribute in a classification | category Diagram showing file storage structure The figure which shows the flowchart of file search processing The figure which shows an example of the selection screen of the classification | category used as a search axis Figure showing an example of the search condition specification screen Diagram showing an example of hierarchical display Figure showing a display example of search results Figure showing a display example of search results Figure showing a display example of search results

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 File management system 120 Operation terminal 130 Operation terminal 142 Document management part 800 File storage folder

Claims (5)

Stores classification information in which a plurality of classification items are associated with a plurality of attributes in the classification items, and related information in which associations between the plurality of attributes in the classification items are associated with each classification item. A document management matrix storage unit;
A folder generation unit for generating a file storage folder for storing the attribute from the classification information and related information stored in the document management matrix storage unit;
A file management system comprising and displaying a hierarchical structure having any attribute stored in the file storage folder as a root or an attribute related to the attribute. The file management system according to claim 1, wherein the attribute includes information corresponding to a design process, a document created in the process, a function, and a platform. The file management system according to claim 2, wherein the association with the attribute related to the attribute is displayed in the order of the design process. A plurality of classification items and a plurality of attributes in the classification items are associated to generate classification information,
Corresponding association between the plurality of attributes in the classification item for each classification item to generate related information,
A file storage folder for storing the plurality of attributes is generated from the classification information and the related information,
Select one of the attributes stored in the file generation folder,
Configure a hierarchy between the selected attribute as a root or an association between attributes associated with the attribute;
A file management method comprising: displaying the association between the hierarchical structure or attributes associated with the attribute. A program for executing the file management method according to claim 4 on a computer.

Images