JP5222778B2 - Delivery creation support system and support method - Google Patents

Description

  The present invention relates to a delivery creation support system and support method, and in particular, a rule extracted from an example of an adaptation module or delivery product in another project when a core system or the like as a delivery product was developed in the past and a manually registered rule The present invention relates to a delivery creation support system and a support method for supporting creation of a delivery by software so that a delivery can be created from information on a project such as an adapted module and information on a project work folder.

  Conventionally, scratch development, which has been the mainstream in the development of mission-critical business systems using software, has been enormous in development costs because it has been necessary to understand customer business and build customer-specific systems each time. Therefore, for the development of core business systems, etc., build solutions such as packages as systems, select the necessary modules to adapt to the system to be developed for each business system development project, such as financial accounting, receivables and debts, By developing on the basis of a package including these modules, many package development techniques have been used in order to perform system development at a low cost in a short period of time.

  However, the package that is developed does not adapt to the package, that is, includes modules that are not necessary for the user, so when the system development company delivers the product to the customer, the module that does not apply is included. It was necessary to select and prepare the delivery items so that they would not. This work occurs every time because the adaptation module and the delivery object differ from project to project, and requires a great deal of cost.

  On the other hand, there is known a related art relating to a delivery creation support system that can solve the above-mentioned problems of creating a delivery in a certain degree. This conventional technique is to acquire files including documents and images and arrange them in a predetermined directory structure, and confirm the contents of the delivery by displaying the inspection result from the order specification and the delivery. That's it. However, such a system according to the prior art is not necessarily effective when the delivery object varies from project to project.

  In addition, as a prior art regarding a delivery creation support system, for example, techniques described in Patent Documents 1 and 2 are known.

JP 2004-240991 A JP 2002-63236 A

  As described above, the conventional method of developing a business system by repeating a package development project is a system project to be developed that is the same module as the module included in the past project. In that case, although there are many cases where equivalent deliveries have been created in the past, there is a problem that the cost for creating the deliveries becomes enormous because they are not used. ing. Further, the prior art described in the above-mentioned patent publications 1 and 2 has a problem that it cannot always be said to be effective when a delivery object is different for each project.

  In view of the problems of the prior art as described above, the object of the present invention is to provide delivery information from project information such as an adaptation module included in another past project and a module adapted from an example of delivery and a work folder of the project. An object of the present invention is to provide a delivery creation support system and a support method for providing support when developing and creating a delivery by software by automatic selection.

  According to the present invention, the object is a delivery creation support system for supporting delivery creation by software, and a case delivery fetching means for fetching past delivery information by another project when the delivery is developed in the past. And using the rules managed by the rule management means for managing the delivery creation rules extracted from the captured past delivery examples and the delivery creation rules entered by the user, the rules managed by the rule management means, Deliverable discriminating means for selecting a delivery target from information on another project and input project work folder, delivery evaluation means for allowing the user to evaluate the result of the selected delivery target, and a delivery target evaluated by the user This is achieved by providing a delivery creation means for creating a delivery according to the above.

  According to the present invention, a core business system as software by automatically selecting deliverables from project information and project work folders such as adaptation modules and delivery modules included in other past projects, and project work folders. It is possible to effectively support the creation of deliverables by developing the above.

It is a block diagram which shows the structure of the delivery creation support system by one Embodiment of this invention. It is a figure explaining the structure of a project table. It is a figure explaining the structure of a delivery object determination table. It is a figure which shows the structure of a rule table. It is a flowchart explaining the whole processing operation | movement until a user registers the example of the past delivery, and creates a delivery from a project work folder after extracting the example of a delivery in embodiment of this invention. It is a figure which shows the menu screen image of a delivery creation system. It is a figure which shows the screen image of example delivery taking-in. It is a figure which shows the screen image of rule management. It is a figure which shows the screen image of rule registration. It is a figure which shows the screen image of a delivery determination. It is a figure which shows the screen image of delivery evaluation. It is a flowchart explaining the processing operation | movement which reconfigure | reconstructs the rule in step 57 of the flow shown in FIG. It is a figure which shows the screen image of delivery creation.

  Hereinafter, embodiments of a delivery creation support system and support method according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing the configuration of a delivery creation support system according to an embodiment of the present invention.

  A delivery creation support system according to an embodiment of the present invention is constructed in an information processing apparatus 1 including a main memory 2, a storage device 3 such as an HDD, a CPU (not shown), an input / output device, and the like. The information processing apparatus 1 is used as a client terminal used by a user, and a delivery creation support system according to an embodiment of the present invention includes a delivery creation system 10 configured as a program in the main memory 2, and a storage device. 3 includes a database 11 that can be shared and used by a plurality of users stored in the database 3.

  The delivery creation system 10 includes a case delivery capture function unit 12 that captures information about past deliveries and projects, management of rules extracted from past deliveries, rule management for manual registration, correction, and deletion of rules. Using the rules extracted from the past delivery items, the function unit 13, the delivery judgment function unit 14 that performs delivery target judgment on files existing in the project work folder, and the results judged by the delivery judgment function unit 14 A delivery evaluation function unit 15 that is evaluated by the user, and a delivery creation function unit 16 that creates a delivery from the project work folder using a result evaluated by the delivery evaluation function unit 15. Each of these functional units 12 to 16 is configured as a program, and can be implemented by a CPU included in the information processing apparatus 1 to realize a necessary function.

  The database 11 stored in the storage device 3 includes a project DB based on a project table 17 that manages project information, a directory structure of past deliverables, a delivery target judgment table 18 that manages delivery judgment, and past deliveries. And a rule table 19 for managing rules manually registered by the user from the rule management function unit 13.

  The delivery creation support system according to the embodiment of the present invention configured as described above outputs information on a new delivery as input of past delivery information and project work folder information as examples. However, these input information and output information are exchanged with an input / output device (not shown) included in the information processing apparatus 1 shown in FIG. 1 constituting the delivery creation support system according to the embodiment of the present invention. Alternatively, it may be exchanged with another terminal device (not shown) connected to the information processing apparatus 1 shown in FIG. 1 via a communication line or the like.

  FIG. 2 is a diagram for explaining the configuration of the project table 17. The project table 17 is a table for managing project information such as an adaptation module, a project start date, and an end date, and includes a project ID 20, a project name 21, an adaptation module 22, a start date 23, an end date 24, and a delivery date 25. The case classification 26 is held as attribute information.

  In the above description, the project ID 20 is a code that uniquely represents a project and is a primary key. The project name 21 is a project name in Japanese. The adaptation module 22 is an item in which a module adapted to the target project is set, and the module is defined separately. The case classification 26 is an item for distinguishing whether the target record is registered as a past case or a target for creating a delivery, and the case values are “example” and “delivery”. Exists.

  FIG. 3 is a diagram for explaining the configuration of the delivery target determination table 18. This delivery object judgment table 18 is a table for managing the directory structure, file structure, and judgment result of data acquired from the delivery items and project work folders registered as past cases. The project ID 30, the folder path 31, and the file name 32 are managed. , Extension 33, determination category 34, and rule No. 35 are held as attribute information.

  In the above description, the determination category 34 is a category for determining whether or not the target record is the target of the delivery, and there are “target” and “non-target” as the category values. The determination category 34 is always “target” in the case of data registered as a past case. Rule No. 35 is set with a rule No. adapted for automatic determination of deliverables.

  FIG. 4 is a diagram showing the configuration of the rule table 19. This rule table 19 is a table for managing rules extracted from past delivery examples and rules manually registered by the user. Rule No. 40, adaptation module 41, start date 42, end date 43, delivery The date 44, the rule 45, the determination category 46, and the automatic creation category 47 are held as attribute information.

  In the above description, rule No. 40 is an item that is uniquely and automatically assigned by the system and is a primary key. The rule 45 is expressed by a combination of data of a folder path 31, file name 32, and extension 33, which are attributes of the delivery target determination table 18, and a part of the data. The rule stored in the rule table is the adaptation module 41. , A start date 42, an end date 43, a delivery date 44, a rule 45, and a rule for creating a delivery item from a combination of six attributes of a determination category 46. For example, the adaptation module 41 is “receivable module”, the start date 42, the end date 43, and the delivery date 44 are both blank, the rule 45 is “src \ jp \ co \ aaa \ unit \ proc \ rp”, and the judgment category 46 is “ If it is “Target”, a file that includes “src \ jp \ co \ aaa \ unit \ proc \ rp” in the folder path expresses a rule that if “Loan Module” is applied, it is a delivery target. Yes. The automatic creation category 47 is a category indicating whether the rule is extracted from a past delivery example or a rule manually registered by the user, and there are “automatic” and “manual” as category values.

  FIG. 5 is a flowchart for explaining the overall processing operation from when a user registers an example of a past delivery, extracts a rule, and creates a delivery from a project work folder in the embodiment of the present invention. Fig. 7 is a diagram showing a menu screen image of the delivery creation system, Fig. 7 is a diagram showing a screen image for example delivery, Fig. 8 is a diagram showing a screen for rule management, and Fig. 9 is a diagram showing a screen image for rule registration. 10 is a diagram showing a screen image for delivery determination, FIG. 11 is a diagram showing a screen image for delivery evaluation, and FIG. 12 is a diagram for explaining the processing operation for reconfiguring the rules in step 57 of the flow shown in FIG. FIG. 13 is a flowchart showing a delivery creation screen image. Next, processing for reconfiguring the screen images shown in FIGS. 6 to 11 and 13 and the rules shown in FIG. Referring to the low, the user shown in FIG. 5 to register the case in the past of deliverables, a description will be given of the overall processing operation from the project work folder after extracting the rules until you create the deliverables.

(1) First, the user displays the menu screen of the delivery creation system. On the menu screen of the delivery creation system, as shown in FIG. 6, the screen image is a case delivery delivery button 60, rule management button 61, delivery discrimination button 62, delivery evaluation button 63, delivery creation button. 64 is arranged, and when each button is pressed, a transition is made to a delivery take-in screen, a rule management screen, a delivery judgment screen, a delivery evaluation screen, and a delivery creation screen, which will be described later (step 50).

(2) In the processing of step 50, when the case delivery take-in button 60 on the delivery creation system screen is pressed, it is determined whether or not there is a past delivery case in the inputted case. (Step 51).

(3) If there is a past delivery case in the determination in step 51, the process proceeds to the case delivery process using the case delivery take-in screen, and the case delivery process (Step 52).

  As shown in FIG. 7, the image of the delivery take-in screen displayed in the case delivery take-in process at step 52 is a project ID column 70, a project name column 71, an adaptive module list box 72, a project period. A From field 73, a project period To field 74, a delivery date field 75, a case delivery path field 76, a case delivery path help button 77, and an import button 78 are arranged. When a value is set in each of the above-described input fields and the import button 78 is pressed, a project ID field 70, a project name field 71, an adaptive module list box 72, a project period From field 73, a project period To field 74, a delivery date field The project information input to 75 is registered in the project table 17, and the file information below the case delivery path field 76 is registered in the delivery target determination table 18. At that time, “example” is registered in the case classification 26 of the project table 17, and “target” is registered in the determination classification 34 of the delivery target determination table 18.

(4) If there is no past delivery case in the determination in step 51, or after the processing in step 52, it is determined whether or not the user manually registers the rule (step 53). .

(5) If it is determined in step 53 that the user manually registers the rule, the rule management screen transits to the rule registration screen (step 54).

  In the rule management screen displayed in the process of step 54, as shown in FIG. 8, the screen image is an adaptive module list box column 800, a project period From column 801, a project period To column 802, a delivery date column 803, a rule. A column 804, a determination list box 805, an automatically created classification list box 806, a search button 807, a new registration button 808, a correction button 809, a delete button 810, and a detail line 811 are arranged. A plurality of records including 812, rule number label 813, adaptive module list box 814, rule column 815, determination list box 816, and automatically created classification label 817 are arranged.

  When the search condition is set in the input fields 800 to 806 in the header part of the rule management screen as described above and the search button 807 is pressed, the search result is displayed in the detail line 811. When the search result selection check box 812 is selected, the content of the target record is corrected and the correction button 809 is pressed, the correction content is reflected in the rule table 19. Further, when the search result selection check box 812 is selected and the delete button 810 is pressed, the target record is deleted from the rule table 19. Further, when a new registration button 808 is pressed, the screen changes to a rule registration screen. In the rule registration screen, as shown in FIG. 9, the screen image of the adaptation module list box 90, project period From column 91, project period To column 92, delivery date column 93, rule column 94, judgment list box 95, registration A button 96 is arranged. When a value is set for each input item and the registration button 96 is pressed, the contents are registered in the rule table 19.

(6) If it is determined in step 53 that the user does not register the rule manually, or after the process in step 54, that is, the past case is registered in the case delivery acquisition process in step 52. After registering the rule in the rule registration process, the delivery determination process is performed to re-extract the rule, and the delivery is determined from the input project work folder (step 55).

  As shown in FIG. 10, the delivery determination screen displayed in the process of step 55 includes a project ID column 100, a project name column 101, an adaptive module list box 102, a project period From column 103, a project period, as shown in FIG. A To field 104, a delivery date field 105, a work folder path field 106, a work folder path help button 107, and a determination button 108 are arranged. When a value is set in each input field as described above and the determination button 108 is pressed. , The project ID field 100, the project name field 101, the adaptation module list box 102, the project period From field 103, the project period To field 104, and the project information entered in the delivery date field 105 are stored in the project table 17 and the work folder path field 106. The following file information There are respectively registered in the delivery target determination table 18. At that time, registration is performed without setting a value in the determination section 34 of the delivery object determination table 18. This is because the subsequent processing is performed according to the rules.

  After the registration process described above, the delivery object determination is performed according to the rules registered in the rule table 19 with respect to the record having the project ID 30 of the delivery object determination table 18 as the determination target project ID. In this determination, a delivery target is determined using a record in which the determination category 46 existing in the rule table 19 is “target”. Specifically, when the adaptation module 41, the start date 42, the end date 43, and the delivery date 44, which are project information in the rule table 19, are the same as the corresponding corresponding items in the delivery target determination table 18, and the rule When the rule 45 of the table 19 is included in the value obtained by concatenating the values of the folder path 31, the file name 32, and the extension 33 in the delivery target determination table 18 in the same order, the determination target of the delivery target determination table 18 includes “target”, Set and update rule No. adapted to rule No. 35. However, when the item of the rule table 19 is blank, it is not included in the extraction condition. Next, using the record whose determination classification exists in the rule table 19 is “non-target”, the non-delivery target is determined. The determination method is the same as that of the “target” described above.

(7) Next, the result of the delivery determination process in step 55 is evaluated by the delivery evaluation process. By this delivery evaluation process, the user manually corrects the record that could not be determined by the delivery determination process in step 55 and the record that the system erroneously determined (step 56).

  As shown in FIG. 11, the screen image of the delivery evaluation screen displayed in the process of step 56 is a project ID column 1100, a project ID search help button 1101, a folder path column 1102, a file name column 1103, an extension. A column 1104, a determination list box 1105, a search button 1106, a correction button 1107, and a detail unit 1008 are arranged. The detail unit 1108 includes a selection check box 1109, a folder path column 1110, a file name column 1111, and an extension column 1112. A determination list box 1113 is arranged.

  When the search condition is set in the input fields 1100 and 1102 to 1105 in the header part of the delivery evaluation screen described above and the search button 1106 is pressed, the search result is displayed in the detail part 1108. When the search result selection check box 1109 is selected, the content of the target record is corrected and the correction button 1107 is pressed, the correction content is reflected in the delivery target determination table 18.

(8) After the correction contents are reflected in the delivery target determination table 18 in the process of step 506, the rule re-extraction process is performed next. This rule re-extraction process is a process of deleting a record in which the automatic creation section 47 of the rule table 19 is “automatic”, and reconfiguring the rule using the records of the project table 17 and the delivery target determination table 18. is there. The details of this process will be described later with reference to the flow shown in FIG. 12 (step 57).

(9) The delivery target is evaluated in the delivery evaluation process in step 56, and after the delivery is confirmed, the delivery automatic creation process is performed to create the delivery (step 58).

  As shown in FIG. 13, the delivery creation screen displayed in the process of step 58 has a screen image of a project ID column 130, a project ID help button 131, a creation destination column 132, a creation destination help button 133, and a creation button. When the creation button 134 is pressed after inputting necessary data for each item, the deliverables are selected from the project work folder according to the data of the delivery target determination table 18 in the directory specified in the creation destination field 132. To create a delivery.

  By repeating the processing operation shown in FIG. 5 described above, the accuracy of the extracted rules can be improved, and the delivery can be correctly created.

  Next, with reference to the flow shown in FIG. 12, the processing operation for reconfiguring the rule in step 57 described with reference to FIG. 5 will be described.

(1) First, a hypothesis is created from the items in the delivery object determination table 18 and the project table 17. This hypothesis is configured by a combination of any of the adaptation module 22, the start date 23, the end date 24, the delivery date 25 and the rule that are items of the project table 17, and the rule is a folder that is an item of the delivery target determination table 18. The path 31, the file name 32, and the combination of the values of the extension 33, or a part of them (step 120).

(2) Next, as a result of creating a hypothesis in the processing of step 120, it is possible to create a hypothesis, determine whether the hypothesis exists, and if the created hypothesis exists, create it Verification of the hypothesis is performed by determining whether or not the hypothesis matches a past delivery case (steps 121 and 122).

(3) In the verification at step 122, if the hypothesis matches the past delivery case, the hypothesis is adopted and the hypothesis is set as a rule. If the hypothesis does not match the past delivery case, the hypothesis is rejected and deleted (steps 123 and 124).

(4) After the processing of step 123 or step 124, the processing returns to the processing from step 121 and the processing for the next hypothesis is continued. After all hypotheses have been verified, the created rule is verified. Then, in this verification, rules including duplicates and other rules are extracted, those rules are deleted, and the processing here is terminated (step 125).

  Each process in the above-described embodiment of the present invention is configured by a program and can be executed by a CPU included in the present invention. These programs are stored in a recording medium such as an FD, CDROM, or DVD. It can be provided and can be provided by digital information via a network.

10 Delivery creation system 11 DB
12 Case Delivery Function Part 13 Rule Management Function Part 14 Delivery Identification Function Part 15 Delivery Evaluation Function Part 16 Delivery Creation Function Part 17 Project Table 18 Delivery Target Determination Table 19 Rule Table

Claims (3)

In the delivery creation support system that supports creation of deliverables by software,
Example delivery capture means that captures past delivery information from another project when the delivery was developed in the past, delivery creation rules extracted from the imported past delivery examples, and input by the user A rule management means for managing creation rules, and a delivery item discrimination means for selecting a delivery target from the information on the different project and the inputted project work folder information using the rules managed by the rule management means; A delivery creation support system comprising: delivery evaluation means for allowing a user to evaluate a result of a selected delivery target; and delivery creation means for creating a delivery according to a delivery target evaluated by the user.   The delivery creation support system according to claim 1, further comprising means for re-extracting a delivery creation rule according to a delivery target evaluated by the user. In the delivery creation support method that supports creation of delivery by software,
Incorporating information on past deliveries from different projects when developing deliveries in the past, managing the delivery creation rules extracted from the imported past delivery cases and the delivery creation rules entered by the user, Using the managed rules, the delivery target is selected from the information on the different project and the input project work folder information, the result of the selected delivery target is evaluated by the user, and the delivery evaluated by the user A delivery creation support method characterized by creating a delivery according to a target.

Images