JP4369864B2 - Component management system and component management program - Google Patents

Description

  The present invention relates to a component management system, a component management method, and a component management program for managing software components in cooperation with a project management system in software development.

In Patent Document 1, in a system for sharing a document among a plurality of users, a document is searched by specifying a condition, and the searched document is registered in a database (DB) together with a condition used for the search. When creating a new document, the user inputs a search condition and searches the database for a document corresponding to the input search condition. Then, instead of creating a new document from scratch, a document is created using the retrieved document.
JP 2002-169814 A

  Assume that multiple projects are in progress in software development. Here, a project is a combination of a plurality of programs or an activity for developing them. For example, in Project A, it is assumed that a class is designed in object-oriented programming and a component called Class A is developed. Project B also designs a class and develops a component called Class B. Here, a component is a part of a program such as a class or a function, and can be a unit of software development.

  Even if class A and class B are components that perform the same processing, information cannot be shared between project A and project B, so they are created as separate components. Such a phenomenon occurs in proportion to the number of projects, and wastes man-hours.

  In the prior art, as described above, components (common components) that can be used in a plurality of projects are stored and shared in a database, and components created in past projects can be used in other projects. However, there is a problem that it is difficult to use the common component because there is no information on what function the component has, when it was created by whom, and in what project. In addition, in the conventional technology, because the component being created is not registered in the database, between the projects that are progressing simultaneously as in the above example, the component that creates the same function separately was there.

  An object of the present invention is to manage a common component and various information related to the common component in a database, and promote reuse of the common component.

The component management system according to the present invention includes:
A component management system that manages a part of a program as a reusable component by connecting to a project management database that manages project information that shows the characteristics of a project that combines multiple programs. Component management database to
A project information acquisition unit that acquires, from the project management database, project information input by a user regarding a new project including a component that has not been created;
A keyword extraction unit for extracting keywords included in the project information acquired by the project information acquisition unit;
Using the keyword extracted by the keyword extraction unit, a search unit that searches the component management database for a component that is assumed to be usable in the new project;
And an output unit that outputs a list of components searched by the search unit to a user.

The project information further includes:
Including use-scheduled component information indicating a component scheduled to be used by the user in the new project;
The component management system further includes:
Use schedule component information acquisition unit for acquiring use schedule component information input by the user regarding the new project from the project management database;
A utilization-scheduled component information registration unit that registers the utilization-scheduled component information acquired by the utilization-scheduled component information acquisition unit in the component management database;

The project information further includes:
Including creation-scheduled component information indicating a component scheduled to be created by the user in the new project;
The component management system further includes:
A creation-scheduled component information acquisition unit that acquires the creation-scheduled component information input by the user regarding the new project from the project management database;
A creation-scheduled component information registration unit that registers the creation-scheduled component information acquired by the creation-scheduled component information acquisition unit in the component management database.

The component management system further includes:
A keyword acquisition unit for acquiring a keyword input by a user;
The search unit
Using the keyword acquired by the keyword acquisition unit, search for the component from the component management database,
The output unit is
A list of components searched by the search unit is displayed to a user.

The component management database is
Manage components by grouping them into specific groups,
The component management system further includes:
A group specifying unit for specifying a group selected by the user;
The search unit
Search the component management database for components belonging to the group specified by the group specifying unit,
The output unit is
A list of components searched by the search unit is displayed to a user.

The project information acquisition unit
Obtain project information entered by the user from the project management database regarding the completed project including the completed component,
The project information further includes:
Including creation component information indicating a component that the user has created in the completed project,
The component management system further includes:
A creation component information acquisition unit that acquires creation component information input by the user regarding the completed project from the project management database;
A file request unit for notifying a user of a storage request for a file when a file related to the component indicated in the generated component information acquired by the generated component information acquisition unit is not stored in a predetermined location;
A creation component information registration unit for registering the creation component information in the component management database when a file related to the component indicated by the creation component information obtained by the creation component information acquisition unit is stored in a predetermined location; It is characterized by providing.

The component management database is
Manages history information indicating component usage history,
The project information further includes:
Including used component information indicating a component used by the user in the completed project;
The component management system further includes:
A usage component information acquisition unit that acquires usage component information input by the user regarding the completed project from the project management database;
A usage component information registration unit that registers the usage component information acquired by the usage component information acquisition unit in the component management database and updates the history information regarding the usage history of the component indicated in the usage component information.
The output unit is
A list of components searched by the search unit with reference to the history information is arranged and output in order of frequency of use.

A component management program according to the present invention includes:
A component management database that connects to a project management database that manages project information that shows the characteristics of a project that combines multiple programs, manages a part of the program as a reusable component, and manages information about the component together with the component In the component management program that connects to
A project information acquisition process for acquiring, from the project management database, project information input by a user regarding a project including a component that has not been completed (hereinafter referred to as a new project);
A keyword extraction process for extracting keywords included in the project information acquired by the project information acquisition process;
Using the keyword extracted by the keyword extraction process, a search process for searching the component management database for a component that is assumed to be usable in the new project;
The computer may execute an output process for outputting a list of components searched by the search process to a user.

The project information further includes:
Including use-scheduled component information indicating a component scheduled to be used by the user in the new project;
The component management program further includes:
Use schedule component information acquisition processing for acquiring use schedule component information input by the user regarding the new project from the project management database;
The use schedule component information registration process for registering the use schedule component information acquired by the use schedule component information acquisition process in the component management database is executed by a computer.

The project information further includes:
Including creation-scheduled component information indicating a component scheduled to be created by the user in the new project;
The component management program further includes:
Creation schedule component information acquisition processing for acquiring creation schedule component information input by the user regarding the new project from the project management database;
A creation schedule component information registration process for registering the creation schedule component information acquired by the creation schedule component information acquisition process in the component management database is executed by a computer.

  In the present invention, the component management database manages information related to common components together with the common components, the project information acquisition unit acquires project information related to a new project managed in the project management database, and the keyword extraction unit includes keywords included in the project information. , And the search unit searches for common components using the extracted keywords, and the output unit outputs a list of searched common components to the user to encourage use in a new project. Can be promoted.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description of each embodiment, a Java (registered trademark) class, which is an object-oriented programming language, is used as an example of a component, but a class or function of another language may be used.

  FIG. 1 is a diagram showing an example of an appearance of a component management system in each of the following embodiments.

  1, the component management system 100 includes a system unit 910, a CRT (Cathode Ray Tube) display device 901, a keyboard (K / B) 902, a mouse 903, a compact disk device (CDD) 905, and a printer device 906. Are connected by a cable. Further, the component management system 100 is connected to the FAX machine 932 and the telephone 931 by a cable, and is connected to the Internet 940 via a local area network (LAN) 942 and a gateway 941.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of a component management system in each of the following embodiments.

  In FIG. 2, the component management system 100 includes a CPU (Central Processing Unit) 911 that executes a program. The CPU 911 is connected to the ROM 913, RAM 914, communication board 915, CRT display device 901, K / B 902, mouse 903, FDD (Flexible Disk Drive) 904, magnetic disk device 920, CDD 905, and printer device 906 via the bus 912. Yes.

  The RAM 914 is an example of a volatile memory. The ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are examples of nonvolatile memories. These are examples of a storage device or a storage unit.

  The communication board 915 is connected to a FAX machine 932, a telephone 931, a LAN 942, and the like.

  For example, the communication board 915, K / B 902, FDD 904, and the like are examples of the input unit. For example, the communication board 915, the CRT display device 901, and the like are examples of an output unit, a registration notification unit, and a file request unit.

  Here, the communication board 915 is not limited to the LAN 942 but may be directly connected to the Internet 940 or a WAN (Wide Area Network) such as ISDN (Integrated Services Digital Network). When the component management system 100 is directly connected to a WAN such as the Internet 940 or ISDN, the component management system 100 is connected to the WAN such as the Internet 940 or ISDN, and the gateway 941 is unnecessary.

  The magnetic disk device 920 stores an operating system (OS) 921, a window system 922, a program group 923, and a file group 924. The program group 923 is executed by the CPU 911, the OS 921, and the window system 922.

  The program group 923 stores a program for executing a function described as “unit” in the description of each embodiment described below. The program is read and executed by the CPU 911.

  In the file group 924, what is described as “determination result of”, “calculation result of”, and “processing result of” in the description of each embodiment described below is stored as “˜file”. ing. The file group 924 includes a database composed of a plurality of tables, and each table or part of the table is stored as a file.

  In addition, arrows in the flowcharts described in the description of each embodiment described below mainly indicate input / output of data, and for the input / output of the data, data includes a magnetic disk device 920, an FD (Flexible Disk), It is recorded on other recording media such as an optical disc, CD (compact disc), MD (mini disc), and DVD (Digital Versatile Disk). Alternatively, it is transmitted through a signal line or other transmission medium.

  In addition, what is described as “unit” in the description of each embodiment described below may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented by software alone, hardware alone, a combination of software and hardware, or a combination of firmware.

  A program for implementing each embodiment described below also includes a magnetic disk device 920, an FD (Flexible Disk), an optical disk, a CD (Compact Disk), an MD (Mini Disk), a DVD (Digital Versatile Disk), and the like. You may memorize | store using the recording device by another recording medium.

Embodiment 1 FIG.
First, the configuration of the component management system according to the present embodiment will be described.

  FIG. 3 is a block diagram showing the configuration of the component management system according to the present embodiment.

  The component management system 100 manages common components in the component management database 150 in cooperation with a project management system including the project management database 50. The project management system manages project information.

  In the component management system 100, the project information acquisition unit 101 acquires project information from the project management database 50. In the present embodiment, the project information acquisition unit 101 registers the acquired project information in the component management database 150. The keyword extraction unit 102 extracts keywords from the project information acquired by the project information acquisition unit 101, and the search unit 103 searches the component management database 150 for common components using the extracted keywords. The output unit 104 notifies the user who created the project information of the search result by e-mail. The output unit 104 may display the search result on a display or the like.

  A user of the component management system 100 inputs a keyword via an input unit (not shown). The keyword acquisition unit 105 acquires a keyword input by the user, and the search unit 103 searches the common component from the component management database 150 using the keyword. The output unit 104 displays the search result on a display or the like. The output unit 104 may notify the user of the search result by e-mail.

  The scheduled use component information acquisition unit 107 acquires the scheduled use component information from the project management database 50, and the scheduled use component information registration unit 108 registers the scheduled use component information in the component management database 150. The creation schedule component information acquisition unit 109 acquires the creation schedule component information from the project management database 50, and the creation schedule component information registration unit 110 registers the creation schedule component information in the component management database 150. The usage component information acquisition unit 111 acquires the usage component information from the project management database 50, and the usage component information registration unit 112 registers the usage component information in the component management database 150. The created component information acquisition unit 113 acquires the created component information from the project management database 50, and the created component information registration unit 114 registers the created component information in the component management database 150.

  When the created component information is newly registered in the component management database 150, the registration notifying unit 115 notifies the newly registered information to the contacts of a plurality of users registered in advance by e-mail.

  Further, in order to store as a common component, a file (related file) related to the newly created component is stored in a predetermined location. If the related file is not stored in a predetermined location when registering the created component information, the file request unit 116 notifies the user of a request to store the related file by e-mail.

  Next, the operation of the component management system 100 when a new project is started will be described.

  FIG. 4 is a diagram illustrating an example of screen transition when the user searches for a common component.

  A project leader (hereinafter referred to as a user) who is a user of the project management system and the component management system 100 inputs a keyword related to the project to the search screen 201 when starting a new project. At this time, a plurality of keywords may be input, or a conditional expression may be input as in a general search system. When the search process of the component management system 100 is completed, a list of common components corresponding to the input condition is displayed on the search result screen 202. In the example of FIG. 4, each common component is displayed with a class name, and a link is pasted to each class name. The user confirms information on each class on the detailed screen 203 by following the link. The search screen 201, the search result screen 202, and the detail screen 203 are output using, for example, a Web browser.

  FIG. 5 is a flowchart showing an operation of the component management system 100 when a keyword search for a common component by a user is processed by the screen transition shown in FIG.

  When a keyword is input by the user, in the component management system 100, the keyword acquisition unit 105 acquires the keyword input by the user (step S101). The search unit 103 searches the component management database 150 for a common component using the keyword acquired by the keyword acquisition unit 105 (step S102). The output unit 104 displays the search result of the search unit 103 (step S103).

  When starting a new project, the user creates a project plan in addition to performing the above search. In this embodiment, it is assumed that a project plan is created by creating a project plan, and the project plan is an input unit (not shown) having an interface such as a “project plan sheet” (hereinafter referred to as project plan). It is input from the input section) and created. The user inputs the project plan from the project plan input unit using his / her own terminal or the like. Thereafter, the project information included in the input project plan and the project completion report described later is centrally managed by the project management system.

  The user should make sure that the project plan contains the image of the system to be developed in the new project and the project plan, and that the basic policy, work procedure, process, quality, cost, and system for efficient system production work. Enter. For example, as a project outline, an outline is entered for basic matters such as a system outline, purpose, and characteristics, and a basic policy for promoting the project. In addition, as system basic matters, the contents of the system to be developed such as the system outline, structure, function, configuration (hardware, software), etc. are input. In addition, as the project promotion plan, input how to proceed with the development, such as work process, system, and quality target.

  Further, the user determines common components that can be used for the new project from the result of the above search. Then, the component that is scheduled to be used, the component that is scheduled to be newly created, and the component that is to be updated and used (currently scheduled to be updated) are input to the usage common component sheet.

  6 and 7 are diagrams illustrating an example of an input screen for a common usage component sheet. The search for the common component shown in FIGS. 4 and 5 is executed at any time when the common component sheet is input.

  In the example of FIG. 6, the user inputs “class name to be used” and “function outline” as information (component information to be used) regarding the components to be used on the input screen 204. In “class name scheduled to be used”, the class name of the component scheduled to be used determined with reference to the search result on the search screen 201 in FIG. 4 is entered, or the search result on the search screen 201 can be transferred. . In addition, in “Function overview”, “Function overview” corresponding to the class name and stored in the component management database 150 is displayed.

  The user further inputs “update scheduled class name” as information related to the component scheduled to be updated (included in the usage scheduled component information and the creation scheduled component information). The “update scheduled class name” may be configured so that the class name of the update scheduled component determined with reference to the search result on the search screen 201 in FIG. 4 is transcribed. . In “Function overview”, “Function overview” corresponding to the class name and stored in the component management database 150 is displayed. However, the update function may be rewritten by the user.

  In the example of FIG. 7, the user enters “class name”, “function”, “keyword”, “classification”, “creator affiliation”, “ Enter Creator Name. In "Class name", enter the class name of the component to be created. In “Function”, an outline of the function of the component to be created is input. In “Keyword”, a keyword related to a component to be created is input. In “Classification”, a group to which a component to be created belongs is input. In “Creator affiliation”, the department name of the person who creates the component to be created is entered. In the “name of creator”, the name of the person who creates the component to be created is entered.

  When the user finishes inputting the project plan and the common component sheet, the user registers them in the project management system from a registration screen (not shown).

  FIG. 8 is a flowchart showing the operation of the project management system when registering project information and component information.

  When the user inputs the project plan and the common usage component sheet, the project management system acquires the project plan entered by the user (step S201) and registers it in the project management database 50 (step S202). Further, the project management system acquires the use common component sheet input by the user (step S203) and registers it in the project management database 50 (step S204).

  The component management system 100 polls the project management system, acquires the project plan document registered in the project management system and the use common component sheet by batch processing, extracts the information contained therein, and manages the component. Register in the database 150. This registration process may be a process performed interactively with the user, for example, instead of a batch process.

  FIG. 9 is a flowchart showing the operation of the component management system 100 when processing registration of project information and component information.

  First, in the component management system 100, the project information acquisition unit 101 searches for unprocessed project plans registered in the project management database 50 (step S301). When there is an unprocessed project plan, the following processing is performed for the number of project plans, that is, the number of new projects.

  The project information acquisition unit 101 acquires an unprocessed project plan from the project management database 50 (step S302). The scheduled use component information acquisition unit 107 and the scheduled creation component information acquisition unit 109 acquire the usage common component sheet from the project management database 50 (step S303). The component management system 100 extracts information from the acquired project plan and the use common component sheet and registers it in the component management database 150 (step S304).

  FIG. 10 is a flowchart showing the operation of the component management system 100 when performing the registration process in step S304 of FIG.

  At the beginning of the registration process, the project information acquisition unit 101 registers the project information extracted from the project plan in the component management database 150 (step S311).

  If the component to be used has not been input to the use common component sheet, the keyword extracting unit 102 extracts a keyword from the system summary description described in the project plan (step S312). The search unit 103 searches the component management database 150 for common components using the keywords extracted by the keyword extraction unit 102 (step S313). The output unit 104 notifies the user of the search result of the search unit 103 by e-mail (step S314).

  The scheduled use component information registration unit 108 registers the component information in the component management database 150 if the scheduled use component or the update scheduled component is input to the use common component sheet. If the component information to be created is input, the component information is registered in the component management database 150 (step S315).

  FIG. 11 is a diagram illustrating an example of processing from step S311 to step S313 in FIG.

  In the example of FIG. 11, when the component to be used is not entered in the use common component sheet, the component management system 100 uses, for example, “print” from the project name described in the project plan and the system summary description. The keyword is extracted. Then, the component management database 150 is searched with the keyword “print”. At this time, all the items in the component management database 150 may be searched. For example, only the “system overview” may be searched. As a result, a common component with the class name “print.class” is retrieved from the component management database 150, and the component management system 100 notifies the user by e-mail in order to encourage the use of this common component in a new project. . The user who has received the e-mail selects what is likely to be used in the new project from the notified list of common components, and actually uses it.

  Thus, even if the user does not search for the component himself, the search result is automatically notified, so that the use of the common component can be expected.

  Also, by managing not only information about the components that have already been created but also information on components that are being created (scheduled to be newly created), it is possible to further prevent duplicate creation of similar components and improve the reusability of common components To do.

  Next, the operation of the component management system 100 when the project is completed will be described.

  When the project is completed, the user creates a project completion report.

  In order to grasp and evaluate the achievement status of the target plan of the project, the user describes the evaluation and consideration of the plan and the actual result and how to proceed with the project in the project completion report. For example, the production scale, process, quality, etc. in the actual development are described as the project results. In addition, as an evaluation of the project, an evaluation for each of productivity, process, quality, profit and loss, and comprehensive evaluation are described. Furthermore, based on the evaluation results, future issues and measures will be described.

  In addition, the user inputs an actual usage record of the common component corresponding to the contents described in the usage common component sheet to the usage common component performance sheet.

  12 and 13 are diagrams illustrating an example of the input screen of the use common component result sheet.

  In the example of FIG. 12, the user inputs “used class name” and “functional outline” as information (used component information) regarding the used component on the input screen 205. In the “used class name”, the class name of the component used is input with reference to the result of the keyword search or the notification of the automatic search result by e-mail. In “Function Summary”, the function of the used component is input.

  The user further includes “existing class name”, “new class name”, “update content”, “keyword”, “updater affiliation” as information on the updated component (included in the used component information and created component information). , And input "updater name". In the “existing class name”, the class name of the component updated with reference to the result of the keyword search or the notification of the automatic search result by e-mail is input. In "New class name", enter the updated class name. In “update content”, the updated content is entered. In “Keyword”, the keyword to be added as a result of the update is input. In “Updater Affiliation”, the department name of the person who updated the component is entered. In “Updater Name”, the name of the person who updated the component is entered.

  In the example of FIG. 13, the user has “class name”, “function”, “keyword”, “classification”, “creator affiliation”, “creator” as information (created component information) regarding the newly created component on the input screen 205. Enter your name. In "Class name", enter the class name of the created component. In “Function”, enter the function outline of the created component. In “Keyword”, a keyword related to the created component is entered. In “Category”, enter the group to which the created component belongs. In “Creator Affiliation”, enter the department name of the person who created the component. In the “name of creator”, the name of the person who created the component is entered.

  When the user finishes inputting the project completion report and the used common component result sheet, the user registers them in the project management system from a registration screen (not shown).

  FIG. 14 is a flowchart showing the operation of the project management system when updating project information and component information.

  When the user inputs the project completion report and the common component result sheet, the project management system acquires the project completion report input by the user (step S401) and registers it in the project management database 50 (step S402). Registering a project completion report that includes part of the project information is the same as updating the project information. Further, the project management system acquires the use common component result sheet input by the user (step S403) and registers it in the project management database 50 (step S404). Registering a common usage component result sheet including a part of component information is the same as updating component information.

  The component management system 100 polls the project management system, obtains a project completion report and a common usage component result sheet registered in the project management system by batch processing, and extracts information included in these reports. Information registered in the component management database 150 or information registered in the component management database 150 is updated. This update process (including the process of registration) may be a process performed interactively with the user, for example, instead of a batch process.

  FIG. 15 is a flowchart showing the operation of the component management system 100 when processing update of project information and component information.

  First, in the component management system 100, the project information acquisition unit 101 searches for an unprocessed project completion report registered in the project management database 50 (step S501). When there is an unprocessed project completion report, the following processing is performed for the number of project completion reports, that is, the number of completed projects (completed projects).

  The project information acquisition unit 101 acquires an unprocessed project completion report from the project management database 50 (step S502). The used component information acquisition unit 111 and the created component information acquisition unit 113 acquire the used common component result sheet from the project management database 50 (step S503). The component management system 100 extracts information from the acquired project completion report and the used common component result sheet and registers it in the component management database 150, or updates information registered in the component management database 150 (step S504).

  Upon completion of processing for all completed projects, the registration notifying unit 115, if there is a component registered in the component management database 150 or a component that has been updated in the component management database 150 in this processing. Is sent to all users registered in the component management database 150 by e-mail (step S505).

  FIG. 16 is a diagram showing an example of a notification screen displaying the e-mail transmitted in step S505 of FIG.

  In the example of FIG. 16, the user is notified by e-mail of a list of newly registered components and updated components, and the contents are displayed on the notification screen 206.

  In this way, when there is a newly registered or updated common component, all users are automatically notified, so that a new common component can be used at any time and the use of the common component is enlightened. be able to.

  FIG. 17 is a flowchart showing the operation of the component management system 100 when the update process of step S504 of FIG. 15 is performed.

  When the used component is entered in the used common component result sheet, the used component information registration unit 112 updates the usage history (history information) of the common component held in the component management database 150 (step S511).

  When the newly created component is input to the use common component result sheet and the related file is not stored in the predetermined folder (directory), the file request unit 116 requests the user to store the related file in the folder. Is notified by e-mail (step S512). This e-mail continues to be delivered periodically until the associated file is saved. Here, the related file includes a source file of a newly created component, a module, a specification, a test procedure, and the like.

  If the newly created component is not entered in the usage common component achievement sheet, or if the newly created component is entered in the usage common component achievement sheet and the related file is saved in the specified folder, the created component information is registered. The unit 114 updates the component information registered in the component management database 150, or registers new component information in the component management database 150 (step S513). Then, the project information acquisition unit 101 updates the project information in the component management database 150 based on the information extracted from the project completion report (step S514).

  FIG. 18 is a diagram showing an example of a notification screen displaying the e-mail transmitted in step S512 of FIG.

  In the example of FIG. 18, the user is notified by e-mail of a list of newly created components and updated components whose related files are not stored in a predetermined folder, and the contents are displayed on the notification screen 206.

  As described above, in the present embodiment, project information such as a project plan and a project completion report created when the component management system 100 constructs a system is used, and the common component is shared with the common component in the component management database 150. It is possible to refer to information about who created and used each common component, and in which project, by managing information on the project and project information. In addition, since it is possible to acquire information such as usage records and system examples necessary when using the common component, it is possible to improve the reliability and quality of the common component. In addition, the number of man-hours for a project can be reduced by preventing duplicate creation of similar components.

Embodiment 2. FIG.
The difference between the present embodiment and the first embodiment will be described.

  FIG. 19 is a block diagram showing a configuration of the component management system according to the present embodiment.

  The component management system 100 classifies common components into a plurality of groups in advance and manages them in the component management database 150.

  The user of the component management system 100 selects a group for classifying the common components via an input unit (not shown). The group specifying unit 106 specifies a group selected by the user, and the search unit 103 searches the component management database 150 for common components belonging to this group. The output unit 104 displays the search result on a display or the like.

  FIG. 20 is a diagram illustrating an example of screen transition when the user searches for a common component.

  When starting a new project, the user selects a group of components related to the project on the search screen 201 instead of searching using keywords, and searches for components belonging to the group. When the search process of the component management system 100 is completed, a list of common components belonging to the selected group is displayed on the search screen 201. In the example of FIG. 20, each common component is displayed with a class name, and a link is attached to each class name. The user confirms information on each class on the detailed screen 203 by following the link. The search screen 201 and detail screen 203 are output using, for example, a Web browser.

  FIG. 21 is a flowchart showing the operation of the component management system 100 when processing a group search for common components by the user.

  When the user selects a group, in the component management system 100, the group specifying unit 106 acquires the name of the group selected by the user or other information for identifying the group, and specifies the selected group (step S601). The search unit 103 searches the component management database 150 for common components belonging to the group specified by the group specifying unit 106 (step S602). The output unit 104 displays the search result of the search unit 103 (step S603).

  Thus, by classifying the common components into groups and making it possible to refer to the list of common components for each group, the convenience of the function of searching for common components is improved.

  The above group search may be used in combination with the keyword search described in the first embodiment. Further, a search (hereinafter referred to as a priority search) may be performed based on the usage history of the common component held in the component management database 150. For example, you can search for common components based on usage records and usage examples, or record the number of searches up to the previous time and keywords used in keyword searches, and preferentially display common components corresponding to keywords that are frequently used. Or by calculating the search frequency and component usage frequency from the usage history and displaying them in descending order of frequency. Further, by preparing separate administrator and user rights, the items that can be displayed during search, such as the creator of the common component and the customer name of a project that uses the common component, may be limited.

Embodiment 3 FIG.
The configuration of the component management system according to the present embodiment is the same as the configuration of the first embodiment shown in FIG. 3 or the second embodiment shown in FIG. In the present embodiment, a specific configuration example of the component management database 150 is shown.

  FIG. 22 is a diagram illustrating an example of the configuration of the component management database 150. In FIG. 22, TBL is a table, PK is a primary key, FK is a foreign key, and KL is a KilloLine (source code). A line connecting the tables indicates a parent-child relationship, and a side where two lines intersecting the ends are a parent table, and a side where the ends are branched into three lines is a child table. Also, if there is a circle in the branching part on the child table side, it means that there are zero or more records corresponding to the parent table record, and if there is one intersecting line, the record in the parent table 1 indicates that one record exists in the child table.

  Hereinafter, details of operation steps of the component management system 100 described with reference to the flowcharts in the first and second embodiments when the component management database 150 is configured as illustrated in FIG. 22 will be described.

  The flowchart of FIG. 5 shows the operation of the component management system 100 when processing a keyword search for common components by the user.

  In step S102, the search unit 103 adds a search condition number (number) to the keyword acquired by the keyword acquisition unit 105 and adds it to the search keyword table (an example is shown in FIG. 23). Further, the search date and the search type are added to the search condition table (an example is shown in FIG. 24) in association with the search condition No. Next, a keyword that matches the keyword added to the search keyword table is acquired from the keyword table (an example is shown in FIG. 25). Then, the group ID corresponding to the keyword acquired from the keyword table is acquired from the group keyword table (an example is shown in FIG. 26). Then, the package name corresponding to the group ID acquired from the group keyword table is acquired from the group package information table (an example is shown in FIG. 27). Then, the class name corresponding to the package name acquired from the group package information table is acquired from the class information table (an example is shown in FIG. 28). Finally, a list of class names acquired from the class information table is passed to the output unit 104.

  Although not shown, after the output unit 104 displays a list of class names in step S103, when the user selects a class name from the list, class information corresponding to the selected class name is acquired from the class information table. And displayed by the output unit 104. Further, the class name and the package name corresponding to the class name are added to the search result table (an example is shown in FIG. 29) by the search unit 103 together with the search condition No. given to the keyword in step S102.

  Here, instead of setting the class name as the search target, the package name may be set as the search target. In that case, during the above operation, in the process of acquiring the class information, the package information stored in the common component information table (an example is shown in FIG. 30) is acquired instead of the class information.

  The search keyword table, search condition table, and search result table are referred to when a priority search is performed.

  The flowchart of FIG. 10 shows the operation of the component management system 100 when performing the registration process of step S304 of FIG.

  In step S311, the project information acquisition unit 101 assigns a project ID to the project information extracted from the project plan and adds it to the project information table (an example is shown in FIG. 31).

  In step S312, the keyword extraction unit 102 acquires a system overview of the project information table, and breaks down the business operation character string into words. Then, a word as a keyword candidate is added to the business keyword table (an example is shown in FIG. 32) together with the project ID given to the project information in step S311.

  In step S313, the search unit 103 acquires a keyword corresponding to the project ID assigned to the project information in step S311 from the business keyword table. Next, a keyword that matches the keyword acquired from the business keyword table is acquired from the keyword table. Then, the group ID corresponding to the keyword acquired from the keyword table is acquired from the group keyword table. Then, the package name corresponding to the group ID acquired from the group keyword table is acquired from the group package information table. Then, the class name corresponding to the package name acquired from the group package information table is acquired from the class information table. Finally, a list of class names acquired from the class information table is passed to the output unit 104.

  In step S314, the output unit 104 acquires a user ID corresponding to the project ID assigned to the project information in step S311 from the project information table, and sets an email address corresponding to the user ID in the user table (example in FIG. 33). Obtained from). Then, an e-mail including the search result of the search unit 103 is created and transmitted to the e-mail address acquired from the user table.

  In step S315, the scheduled use component information registration unit 108 adds the scheduled component information and the scheduled update component information to the scheduled use component table (an example is shown in FIG. 34). Further, the creation schedule component information registration unit 110 adds the creation schedule component information to the use schedule component table. Further, the status of the class information table is updated for the component scheduled to be updated, and the class information is added to the class information table for the component scheduled to be newly created. Here, a field for inputting package information may be provided in the use common component sheet shown in FIGS. 6 and 7 to add or update package information in the common component information table.

  The flowchart in FIG. 17 shows the operation of the component management system 100 when performing the update process in step S504 in FIG.

  In step S511, the use component information registration unit 112 adds the use component information to the use result component table (an example is shown in FIG. 35).

  In step S512, the file request unit 116 acquires a user ID from the project information table, and acquires a mail address corresponding to the user ID from the user table. Then, an e-mail including a request to save the related file in a predetermined folder is created and transmitted to the e-mail address acquired from the user table.

  In step S513, the creation component information registration unit 114 adds the creation component information to the use result component table. Further, the class information in the class information table is updated for the updated component and the newly created component. However, class information is added to the class information table for components that are not scheduled to be newly created.

  In step S514, the project information acquisition unit 101 updates the project information in the project information table based on the information extracted from the project completion report.

  The flowchart of FIG. 21 shows the operation of the component management system 100 when the group search for common components by the user is processed.

  Although not shown, before the group is selected by the user, the output unit 104 displays a list of group names acquired from the group table (an example is shown in FIG. 36).

  In step S601, the group specifying unit 106 acquires the group ID of the group selected by the user.

  In step S602, the search unit 103 acquires a package name corresponding to the group ID acquired by the group specifying unit 106 from the group package information table. Then, the class name corresponding to the package name acquired from the group package information table is acquired from the class information table. Finally, a list of class names acquired from the class information table is passed to the output unit 104.

  In the component management database 150 shown in FIG. 22, the use scheduled component table and the use result component table are configured as separate tables. However, the same table is used and the component table registered by the use schedule information is used. You may comprise so that it may update with performance information.

The figure which shows an example of the external appearance of the component management system in Embodiment 1-3. FIG. 4 is a diagram illustrating an example of a hardware configuration of a component management system according to the first to third embodiments. 1 is a block diagram showing a configuration of a component management system according to Embodiment 1. FIG. FIG. 6 shows an example of screen transition when a user searches for a common component in the first embodiment. 5 is a flowchart showing an operation of the component management system when processing a keyword search for a common component by a user in the first embodiment. The figure which shows an example of the input screen (1/2) of the utilization common component sheet | seat in Embodiment 1. FIG. The figure which shows an example of the input screen (2/2) of the utilization common component sheet | seat in Embodiment 1. FIG. 5 is a flowchart showing the operation of the project management system when registering project information and component information in the first embodiment. 5 is a flowchart showing the operation of the component management system when processing registration of project information and component information in the first embodiment. 10 is a flowchart showing the operation of the component management system when performing the registration process in step S304 of FIG. The figure which shows an example of the process from step S311 of FIG. 10 to step S313. The figure which shows an example of the input screen (1/2) of the utilization common component performance sheet in Embodiment 1. FIG. The figure which shows an example of the input screen (2/2) of the utilization common component performance sheet | seat in Embodiment 1. FIG. 3 is a flowchart showing the operation of the project management system when updating project information and component information in the first embodiment. 5 is a flowchart showing the operation of the component management system when processing update of project information and component information in the first embodiment. The figure which shows an example of the notification screen which displayed the electronic mail transmitted by step S505 of FIG. The flowchart which shows operation | movement of the component management system 100 at the time of performing the update process of FIG.15 S504. The figure which shows an example of the notification screen which displayed the email transmitted by FIG.17 S512. FIG. 4 is a block diagram showing a configuration of a component management system according to Embodiment 2. FIG. 10 shows an example of screen transition when a user searches for a common component in the second embodiment. 9 is a flowchart showing an operation of a component management system when processing a group search for common components by a user in the second embodiment. FIG. 10 is a diagram illustrating an example of a configuration of a component management database according to the third embodiment. An example of a search keyword table. An example of a search condition table. An example of a keyword table. An example of a group keyword table. An example of a group package information table. An example of a class information table. An example of a search result table. An example of a common component information table. An example of a project information table. An example of a business keyword table. An example of a user table. An example of a use schedule component table. An example of a utilization result component table. An example of a group table.

Explanation of symbols

  50 Project management database, 100 Component management system, 101 Project information acquisition unit, 102 Keyword extraction unit, 103 Search unit, 104 Output unit, 105 Keyword acquisition unit, 106 Group identification unit, 107 Scheduled component information acquisition unit, 108 Scheduled use Component information registration unit, 109 Scheduled component information acquisition unit, 110 Scheduled component information registration unit, 111 Usage component information acquisition unit, 112 Usage component information registration unit, 113 Creation component information acquisition unit, 114 Creation component information registration unit, 115 Registration notification section, 116 file request section, 150 component management database, 201 search screen, 202 search result screen, 203 detail screen, 204 205 input screen, 206 notification screen, 901 CRT display device, 902 K / B, 903 mouse, 904 FDD, 905 CDD, 906 printer device, 910 system unit, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board 920, magnetic disk unit, 921 OS, 922 window system, 923 program group, 924 file group, 931 telephone, 932 FAX machine, 940 Internet, 941 gateway, 942 LAN.

Claims (9)

Connected to a project management database that stores project information indicating the function of a project that combines multiple programs, the name of the component that is part of one of the programs, the function of the component, the keyword corresponding to the component, and the component A component management system for managing component information indicating the creator of the project and a project developed using the component,
The project management database further includes created component information indicating the name of the component that has been created in the completed project in which creation of all components has been completed, the function of the component, the keyword corresponding to the component, and the creator of the component. Is registered,
The component management system includes:
A component management database for storing component information;
A creation component information acquisition unit that acquires the creation component information from the project management database when creation component information of a component that has been created in the completed project is registered in the project management database;
If the source file of the component, wherein the creating component information acquisition unit acquires the creation component information is not stored in a predetermined location, a file request portion to be notified by e-mail storage requirements of the source file to the user,
When the source file is stored in the predetermined location, the name of the component, the function of the component, the keyword corresponding to the component, and the component indicated by the created component information acquired by the created component information acquisition unit A creation component information registration unit for registering component information indicating the completed project as a project developed using the component in the component management database.
When project information of a new project having a component that has not been created is registered in the project management database, a project information acquisition unit that acquires project information of the new project from the project management database;
A keyword extraction unit for extracting a word representing the function of the new project from the project information of the new project acquired by the project information acquisition unit;
A search unit that acquires from the component management database the name of the component indicated by the component information in which the word extracted by the keyword extraction unit is indicated as a keyword;
A list of component names acquired by the search unit is output to the user. When a component name is selected from the list by the user, component information of the component for which the name is selected is obtained from the component management database. A component management system comprising: an output unit that acquires and outputs the acquired component information to a user. The component management system according to claim 1, wherein the file request unit continues to notify the storage request periodically by e-mail until the source file is stored in the predetermined location. The component management system further includes:
A creation planned component information registration unit for registering component information of components scheduled to be created in another new project in the component management database;
The search unit registers the component name indicated by the component information in which the word extracted by the keyword extraction unit is indicated as a keyword, the component information registered by the creation component information registration unit, and the creation scheduled component information registration The component management system according to claim 1, wherein the component management system is acquired from component information stored in the component management database, including component information registered by a unit.   The component management system according to claim 3, wherein the component information further indicates whether or not the component has been created.   The component management system according to claim 3 or 4, wherein the component information of the component scheduled to be created further indicates a scheduled date of completion of the component creation. The component management system further includes:
When a keyword is input by the user, the device includes a keyword acquisition unit that acquires the input keyword,
The component management according to claim 1, wherein the search unit acquires a name of a component indicated by component information in which the keyword acquired by the keyword acquisition unit is indicated. system. The component information further indicates a group to which the component belongs,
The said search part acquires the name of the component shown by the component information in which the selected group is shown, when a group is selected by the user. Component management system as described in The component management database further stores history information indicating the usage history of each component,
The component management system further includes:
When the component information of the component used in the project is input by the user, the usage component information registration unit for updating the history information stored in the component management database indicating the usage history of the used component is provided.
The output unit refers to history information stored in the component management database and outputs a list of component names acquired by the search unit in order of frequency of component use. The component management system in any one of 7 to 7. A computer connected to a project management database that stores project information indicating the function of a project combining multiple programs, the name of the component that is part of any program, the function of the component, and the keyword corresponding to the component A component management program executed by a computer including a component management database that stores component information indicating the creator of the component and a project developed using the component,
In the project management database, the created component information indicating the name of the component that has been created in the completed project in which the creation of all components has been completed, the function of the component, the keyword corresponding to the component, and the creator of the component Is registered,
The component management program is:
When the creation component information of the component that has been created in the completed project is registered in the project management database, a creation component information acquisition process for obtaining the creation component information from the project management database;
If the source file of the component, wherein the creating component information acquisition process acquires the creation component information is not stored in a predetermined location, and file request process to be notified by e-mail storage requirements of the source file to the user,
When the source file is stored in the predetermined location, the name of the component, the function of the component, the keyword corresponding to the component, and the component indicated by the created component information acquired by the created component information acquisition process Creating component information registration processing for registering component information indicating the completed project as a project developed using the component in the component management database,
When project information of a new project having a component that has not been created is registered in the project management database, a project information acquisition process for acquiring the project information of the new project from the project management database;
A keyword extraction process for extracting a word representing the function of the new project from the project information of the new project acquired by the project information acquisition process;
A search process for acquiring from the component management database the name of the component indicated by the component information in which the word extracted by the keyword extraction process is indicated as a keyword;
A list of component names acquired by the search process is output to the user. When a component name is selected from the list by the user, component information of the component for which the name is selected is output from the component management database. A component management program for causing a computer to execute an output process of acquiring and outputting the acquired component information to a user.

Images