Design item management system

Abstract

To provide a system capable of outputting information allowing cross-checking of design items related to a plurality of development themes.SOLUTION: When a terminal 40 requests transmission of list information of items corresponding to a designated development theme, a display control unit 15 requests generation of the list information of the items corresponding to the designated development theme to a generation unit 16. The generation unit 16 generates information on items related to a selected development theme (item information), and also generates information on other development themes (contention information) of acquired items based on a development theme item related information DB 13 and an item dictionary DB 11. The generation unit 16 generates information in which the item information and the contention information are associated with each other, and sends the information (item list information) to the display control unit 15.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology for managing design items, and more particularly to a technology that is effective when applied to a system for managing design items. [Background technology]

[0002] Typically, in system development, a design document is created for each development unit, such as a function. This created design document (for example, information including design items such as code used in the function) is stored as a database. Patent Document 1 describes a technology for managing design documents in a database in this way.

[0003] Patent Document 1 describes that a virtual folder associated with a design document is provided, and the version of the virtual folder is changed and managed in accordance with a change in the version of each design document. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-252719 Summary of the Invention [Problem to be solved by the invention]

[0005] As described above, version management can prevent inconsistencies between multiple files.

[0006] When enhancing a system, development of multiple development themes (themes related to the functions of the development target) often progresses in parallel. Common design items may be used across multiple development themes, and in order to develop appropriately, it is desirable to be able to cross-sectionally check the development themes that correspond to a certain design item.

[0007] SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide a system that can output information that allows cross-sectional confirmation of design items related to multiple development themes.

[0008] The above and other objects and novel features of the present invention will become apparent from the description of this specification and the accompanying drawings. [Means for solving the problem]

[0009] Among the inventions disclosed in this application, the outline of representative inventions will be briefly explained as follows.

[0010] A design item management system according to a representative embodiment of the present invention is a design item management system for managing design items, and includes: a design item information storage unit that stores design item information, which is information about design items; a development theme item information storage unit that stores development theme item information, which is information that associates design items with information about development themes, which are themes related to functions to be developed; a generation unit that generates information about design items corresponding to a selected development theme and information about other development themes that correspond to the design items, based on the design item information stored in the design item information storage unit and the development theme item information stored in the development theme item information storage unit; and an output unit that outputs the information generated by the generation unit. [Effects of the Invention]

[0011] The effects obtained by the representative inventions disclosed in this application will be briefly explained as follows.

[0012] That is, according to the representative embodiment of the present invention, it is possible to output information that allows cross-sectional confirmation of design items related to a plurality of development themes. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating an outline of a configuration example of a design item management system according to an embodiment of the present invention. [Figure 2]FIG. 2 is a diagram showing an outline of the data structure of data stored in an item dictionary DB 11. [Figure 3] FIG. 2 is a diagram showing an outline of the data structure of data stored in a development theme DB 12. [Figure 4] 10 is a diagram showing an outline of the data structure of data stored in a development theme item related information DB 13. FIG. [Figure 5] 1 is a diagram showing an outline of the data structure of data stored in a design document information DB 14. FIG. [Figure 6] FIG. 10 is a diagram showing an example of a screen displaying a list of development themes; [Figure 7] 10 is an example of a screen displaying a list of items corresponding to a specified development theme. [Figure 8] FIG. 10 is a diagram outlining an example of a process flow for outputting information that allows cross-sectional confirmation of development themes corresponding to each design item. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In all drawings used to explain the embodiments, the same parts are generally designated by the same reference numerals, and repeated explanations will be omitted. However, parts that have been designated and explained in one drawing may be referred to by the same reference numerals in the explanation of other drawings, although they will not be shown again.

[0015] The design item management system, which is one embodiment of the present invention, is a system that manages system design items (for example, design items such as code information). This design item management system stores development themes (themes related to the functions to be developed) at the time of enhancement, etc., in association with the design items used in the development themes, and outputs information that allows cross-sectional confirmation of the development themes corresponding to each design item.

[0016] As described above, the development theme is a theme related to the function of the development target, and indicates, for example, a theme related to system enhancement (system modification, repair, and expansion).

[0017] When enhancing, development of multiple development themes may proceed in parallel. Each development theme may have common items, and those items may need to be modified in each development theme. As mentioned above, when development of multiple development themes proceeds in parallel, there is a possibility that modifications have already been made in other development themes. Furthermore, modifying a specific design item in one development theme may have an impact on other development themes.

[0018] The design item management system provides information that makes it possible to easily identify development themes that are affected by a given design item.

[0019] <System configuration (overview)> 1 is a diagram showing an overview of an example of the configuration of a design item management system according to one embodiment of the present invention. The design item management system 1 includes, for example, a design item management server 10 and a terminal 40 such as a personal computer owned by a user 4 who is a designer and which can connect to the design item management server 10 via a network 30 such as the Internet.

[0020] The design item management server 10 is, for example, a server system made up of server devices and virtual servers built on a cloud computing service, and stores design item information of the system.

[0021] The terminal 40 requests the design item management server 10 to display information relating to the development theme and design items in response to an input operation by the user 4. The terminal 40 also requests the modification of design items relating to the development theme.

[0022] <Functional description of the design item management server> Next, the functions of the design item management server 10 will be described. The design item management server 10 realizes the functions of each unit described below by executing middleware such as an OS (Operating System), a DBMS (Database Management System), and a Web server program, which are deployed in memory, and software running on these, using a central processing unit (CPU) (not shown). In this embodiment, the design item management server 10 has data stores such as an item dictionary DB 11 (design item information storage unit), a development theme DB 12, a development theme item related information DB 13 (development theme item information storage unit), and a design document information DB 14, which are recorded in a storage device such as a hard disk drive (HDD) (not shown). In addition, the design item management server 10 has units such as a display control unit 15 (output unit) and a generation unit 16, which are implemented as software, as shown in the figure.

[0023] The item dictionary DB11 is a database that stores design item information, which is information related to design items, and is a publicly known item dictionary. The structure of the information stored in the item dictionary DB11 will be explained using Figure 2. Figure 2 is a diagram showing an overview of the data structure of the data stored in the item dictionary DB11. As shown in Figure 2, the item dictionary DB11 stores information including item keys, item IDs, item names, item descriptions, and the number of digits.

[0024] The item key is information for identifying each design item. The item key is information that is set each time a design item is set, and is automatically assigned by the design item management server 10. The item ID is the ID of each item, and is input from the terminal 40 in response to an input operation, etc., by the user 4. The item name is input from the terminal 40 in response to an input operation, etc., by the user 4. The item description is input from the terminal 40 in response to an input operation, etc., by the user 4. The item description is information for explaining the item, such as a definition of the values ​​that the item can take and information indicated by the item code. The number of digits is the number of digits of the item, and is input from the terminal 40 in response to an input operation, etc., by the user 4. The item dictionary DB 11 may further store information related to items. For example, information on code conditions (such as the range of values ​​allowed for the code and restrictions on the value of the first digit) may be included.

[0025] Returning to FIG. 1, the development theme DB 12 is a database that stores attribute information of development themes. The structure of the information stored in the development theme DB 12 will be explained using FIG. 3. FIG. 3 is a diagram showing an overview of the data structure of the data stored in the development theme DB 12. As shown in FIG. 3, the development theme DB 12 stores information including a development theme key, a development theme number, a development theme name, a team in charge of the development theme, and a release date. The development theme key is information that identifies a development theme. The development theme key is automatically assigned by the design item management server 10.

[0026] The development theme number is information for identifying the development theme from the user's perspective. The development theme number is input from the terminal 40 in response to an input operation or the like of the user 4. The development theme name is a name indicating the development theme, and is input from the terminal 40 in response to an input operation or the like of the user 4, for example.

[0027] The responsible team indicates the team in charge of the development theme, and is input from the terminal 40 in response to an input operation by the user 4 or the like.

[0028] The release date of the development theme indicates the release date of the development theme, and is input from the terminal 40 in response to an input operation by the user 4 or the like.

[0029] Returning to FIG. 1, the development theme item related information DB13 is a database that stores information associating development themes with design items (development theme item information that is information associating design items with information related to development themes).

[0030] Here, the structure of information stored in the development theme item related information DB 13 will be explained using Fig. 4. Fig. 4 is a diagram showing an outline of the data structure of data stored in the development theme item related information DB 13. As shown in Fig. 4, the development theme item related information DB 13 stores information including a development theme key, an item key, a status, and edit contents.

[0031] The development theme key is information for identifying the development theme, similar to the development theme key shown in Figure 3. The item key is information for identifying each design item, similar to the item key shown in Figure 2. The status indicates the editing status of the item corresponding to the item key. For example, the status is entered with information indicating "editing (editable state)" or "design completed (item content finalized)".

[0032] The edited content is information indicating the change content of the item corresponding to the item key. For example, if the number of digits of the code is changed, the number of digits before the change and the number of digits after the change are input.

[0033] Returning to Fig. 1, the design document information DB 14 is a database that stores information related to design documents. Here, the structure of the information stored in the design document information DB 14 will be explained using Fig. 5. Fig. 5 is a diagram showing an overview of the data structure of the data stored in the design document information DB 14. As shown in Fig. 5, the design document information DB 14 stores information including a development theme key, an item key, and a design document key.

[0034] The development theme key is information for identifying a development theme, similar to the development theme key shown in Fig. 3. The item key is information for identifying each design item, similar to the item key shown in Fig. 2. The design document key is information for identifying a design document. Furthermore, the design document information DB14 may include information relating to the content of the design document corresponding to the design document key (for example, information on the person responsible for managing the design document and the layout of the design document, etc.).

[0035] 1, the display control unit 15 is a part that displays and outputs various screens in response to requests from the terminal 40. When the display control unit 15 receives a display request for a development theme list screen from the terminal 40, it requests the generation unit 16 to generate list information of the development themes.

[0036] When the display control unit 15 acquires the list information of the development themes from the generation unit 16, it outputs a screen of the acquired list information of the development themes (development theme list screen) to the terminal 40. Here, an example of the screen of the list information of the development themes will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the screen of the list information of the development themes.

[0037] As shown in Figure 6, the screen for the list information of development themes is based on the data stored in the development theme DB12 (data including development theme number, development theme name, responsible team, and release date) as shown in Figure 3.

[0038] On the screen for the list information of development themes, each development theme can be selected. When a development theme is designated by an input operation of the user of the terminal 40, the terminal 40 requests transmission of list information of items corresponding to the designated development theme.

[0039] When the display control unit 15 receives a request from the terminal 40 to send list information of items corresponding to a specified development theme, it requests the generation unit 16 to generate list information of items corresponding to the specified development theme.

[0040] When the display control unit 15 acquires the list information of items corresponding to the specified development theme from the generation unit 16, it outputs a screen of the list information of items corresponding to the specified development theme to the terminal 40. Here, an example of the screen of the list information of items corresponding to the specified development theme will be described with reference to Fig. 7 .

[0041] Figure 7 shows an example of a screen displaying a list of items corresponding to a specified development theme. The development theme name is "X-X Check Compatible" (release date: December 1, 2017).

[0042] 7, the database includes check boxes 60 for selecting items, and item information including an item key, an item ID, an item name, and a status for each item. The item key, item ID, and item name of the item information are based on data stored in the item dictionary DB 11 and the development theme item related information DB 13. The status of the item information is based on data stored in the development theme item related information DB 13.

[0043] 7, information (competitive information) about other development theme items corresponding to each item includes the development theme name, status, and release date. The development theme name, status, and release date are based on data stored in the development theme DB 12 and the development theme item related information DB 13.

[0044] In the example of Figure 7, the data with item key "01002" has item ID "UKETK_NO", item name "Reception NO", and status in the development theme "XX check compatible" is "Under editing". In addition, the conflict information shows that there is also an item with the same item key in the development theme name "XX check compatible" (release date 2017 / 11 / 10), and the status of the "XX check compatible" item is "Design complete".

[0045] Here, "editing" in the status indicates that it is in the design stage, and "design completed" indicates that it is currently being coded or tested.

[0046] Although not displayed on the screen shown in Fig. 7, another screen (for example, the screen in Fig. 6) may be displayed at the same time indicating that the release date of the "X / △ check compatible" development theme is December 1, 2017. Also, the screen in Fig. 7 may include information indicating that the release date of the "X / △ check compatible" development theme is December 1, 2017.

[0047] 7 also includes check boxes 60 for selecting each item, and a search button 70 for requesting a search for design information of the item selected in the check box 60.

[0048] When the search button 70 is pressed with any of the check boxes 60 selected, the display control unit 15 requests a list of design document information for the selected item from the generation unit 16. Then, the display control unit 15 outputs a screen showing the list of design document information acquired from the generation unit 16 to the terminal 40.

[0049] In this way, the display control unit 15 outputs the information generated by the generation unit 16.

[0050] Returning to FIG. 1, the generation unit 16 is a part that searches various databases in response to a request from the display control unit 15 and sends the search results to the display control unit 15.

[0051] When the generation unit 16 receives a request to generate list information of development themes from the display control unit 15, it references the development theme DB 12 to generate list information of development themes and sends the generated list information of development themes to the display control unit 15. For example, the generation unit 16 generates list information of the development theme key, development theme No., development theme name, responsible team, and release date from the development theme DB 12 as the list information of development themes.

[0052] Furthermore, when the generation unit 16 receives a request to generate list information of items corresponding to a specified development theme, it refers to the development theme item related information DB 13 and acquires first information (development theme key, item key, status, etc.) corresponding to the development theme key of the specified development theme. Furthermore, the generation unit 16 refers to the item dictionary DB 11 and acquires an item key, item ID, and item name corresponding to the item key of the information (first information) acquired from the development theme item related information DB 13. This allows the generation unit 16 to generate the item information shown in FIG. 7.

[0053] Furthermore, the generation unit 16 refers to the development theme item related information DB 13 to acquire second information (development theme key, item key, status, etc.) that corresponds to an item key in information corresponding to the development theme key of the above-mentioned specified development theme and has a development theme key different from the specified development theme. The generation unit 16 refers to the development theme DB 12 to acquire a development theme name and release date that correspond to the development theme key of the second information. This allows the generation unit 16 to generate the competitive information shown in FIG. 7.

[0054] As described above, the generation unit 16 refers to various databases and sends information associating the item information and competitive information shown in Figure 7 to the display control unit 15 as list information of items corresponding to the specified development theme.

[0055] In this way, the generation unit 16 generates information on the design items corresponding to the selected development theme (item information in Figure 7) and information on other development themes corresponding to the design items (competitive information in Figure 7) based on the item dictionary DB11 and the development theme item related information DB13.

[0056] Furthermore, the development theme item related information DB 13 has a status indicating the editing status of the design item, and the generating unit 16 generates information including the status information as the conflict information in FIG.

[0057] The development theme DB 12 stores release dates, and the generation unit 16 generates information including the release dates of the development themes as the competitive information in FIG.

[0058] When the generation unit 16 receives a request for a list of design document information for the selected item, it refers to the design document information DB 14, acquires design document information corresponding to the development theme key specified on the screen for the list information of the development themes and the design document key corresponding to the item key of the selected item, and sends the design document information to the display control unit 15. The information in the screen format may be generated by the generation unit 16 or the display control unit 15.

[0059] <Processing flow> FIG. 8 is a diagram outlining an example of the flow of processing for outputting information that allows cross-sectional confirmation of development themes corresponding to each design item in response to a request from terminal 40 in this embodiment.

[0060] First, when the user 4 inputs a request to display a screen of list information of development themes (development theme list screen) from the terminal 40 (S01), the display control unit 15 of the design item management server 10 requests the generation unit 16 to generate list information of development themes. When the display control unit 15 acquires the list information of development themes from the generation unit 16, it outputs a screen of the acquired list information of development themes (development theme list screen) to the terminal 40 (S02). The terminal 40 displays the development theme list screen (S03).

[0061] When a development theme is selected by an input operation by the user 4, the terminal 40 requests transmission of list information of items corresponding to the designated development theme (S04). In response to this, the display control unit 15 requests the generation unit 16 to generate list information of items corresponding to the designated development theme.

[0062] The generation unit 16 generates the item information shown in Fig. 7 (information on items related to the selected development theme) (S05). The generation unit 16 also generates the conflict information shown in Fig. 7 (information on development themes other than the acquired item) (S06). The generation unit 16 generates information that associates the item information shown in Fig. 7 with the conflict information shown in Fig. 7, and sends this information (item list information) to the display control unit 15 (S07). The display control unit 15 outputs a screen (item list screen) based on the item list information to the terminal 40 (S08), and the terminal 40 displays the item list screen (S09).

[0063] In the above embodiment, the generation unit 16 acquires the second information, refers to the development theme DB 12, and acquires the development theme name and release date corresponding to the development theme key of the second information, but this is not limited to this. For example, the development theme name and release date corresponding to the development theme key may be included in the development theme item related information DB 13, and the generation unit 16 may acquire the development theme name and release date from the development theme item related information DB 13 when acquiring the second information.

[0064] Although the above description has been given with respect to a case where the item dictionary DB 11, the development theme DB 12, the development theme item related information DB 13, and the design document information DB 14 are included, the present invention is not limited to this. For example, any database having a data structure capable of generating the screen shown in FIG. 7 may be used.

[0065] Although not specifically mentioned in the above embodiment, the item list screen shown in Fig. 7 or a screen linked to the item list screen may display information (for example, the number of digits) for each item in the development theme displayed on the item list screen. This allows the user to recognize differences between development themes for the same item.

[0066] As described above, when a request for transmission of list information of items corresponding to a specified development theme is made by the terminal 40, the display control unit 15 requests the generation unit 16 to generate list information of items corresponding to the specified development theme. The generation unit 16 generates the item information (information of items related to the selected development theme) shown in Fig. 7 (information of items related to the selected development theme) and also generates the competitive information (information of development themes other than the acquired item) shown in Fig. 7 based on the development theme item related information DB 13 and the item dictionary DB 11. The generation unit 16 generates information that associates the item information shown in Fig. 7 with the competitive information shown in Fig. 7, and sends the information (item list information) to the display control unit 15.

[0067] As a result, the design item management server 10 outputs a list of items corresponding to a certain development theme (item information shown in FIG. 7), and also outputs information on other development themes corresponding to the items (competitive information shown in FIG. 7), making it possible to output information that allows items related to multiple development themes to be checked across the board.

[0068] Furthermore, the development theme item related information DB 13 has a status indicating the editing status of the design item, and the generation unit 16 generates information including the status information as the conflict information in Fig. 7. This enables the design item management server 10 to output information that allows cross-sectional confirmation of the status of items in each development theme.

[0069] Furthermore, the development theme DB 12 stores release dates, and the generation unit 16 generates information including the release dates of the development themes as the conflict information in Fig. 7. This allows the design item management server 10 to output information that allows the priority between development themes to be recognized, since the closer the release date is, the higher the priority is generally.

[0070] The invention made by the inventor has been specifically described above based on the embodiments, but it goes without saying that the present invention is not limited to the above embodiments and can be modified in various ways without departing from the spirit of the invention. For example, the above embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those having all of the described configurations. Furthermore, it is possible to add, delete, or replace part of the configuration of the above embodiments with other configurations.

[0071] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a storage medium such as an IC card, SD card, or DVD.

[0072] In addition, in the above figures, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily show all the control lines and information lines that are actually implemented. In reality, it can be assumed that almost all components are interconnected.

[0073] In the above embodiment, the development theme list displays the target development themes as a list, as shown in Figure 6, but there may be relationships between the development themes. For example, if a large development theme has multiple smaller development themes, the smaller development themes are related to each other through the large development theme (same large theme related). Also, a related development theme that continues development after a certain development theme is related to the target development theme (continuation related). A development theme that utilizes the results of a certain development theme is related to the target development theme (utilization related). By adding this related information to the development theme list and making it selectable, related development themes can also be selected, and a list of items for multiple related development themes can be generated. Here, in the case of multiple related development themes, items (e.g., item IDs) may overlap, but the configuration may be such that overlapping items are displayed without overlapping, or the overlapping items are clearly displayed.

[0074] Furthermore, even if an item in one development theme and another development theme are substantially identical, there may be variations in notation. However, when it is received from the user that an item in one development theme and an item in another development theme are identical, a display indicating the identity may be displayed, or an extraction process may be performed assuming the items to be identical. [Industrial Applicability]

[0075] The present invention can be used in a design item management system that outputs a list of design items using an information processing system. [Explanation of symbols]

[0076] 1...design item management system, 10...design item management server, 11...item dictionary DB, 12...development theme DB, 13...development theme item related information DB, 14...design document information DB, 15...display control unit, 16...generation unit, 30...network, 40...terminal

Claims

1. A design item management system for managing design items, a design item information storage unit that stores design item information that is information about the design items; a development theme item information storage unit that stores development theme item information, which is information that associates the design items with information related to development themes, which are themes related to functions of the development target; a generation unit that generates information on design items corresponding to a selected development theme and information on other development themes corresponding to the selected design items based on the design item information stored in the design item information storage unit and the development theme item information stored in the development theme item information storage unit; an output unit that outputs the information generated by the generation unit; Equipped with the information on the development themes includes information on a first development theme and information on a second development theme that is related to the development theme of the first development theme and is smaller than the development theme of the first development theme; the information relating to the first development theme includes information relating to a plurality of the second development themes, when the information generated by the generation unit is output and information related to the second development theme is duplicated, the output unit selectably outputs information related to the other development theme so that the information related to the second development theme is not duplicated or so that the overlapping information related to the second development theme is made apparent. Design item management system.

2. 2. The design item management system according to claim 1, the development theme item information storage unit includes, as information related to the development theme, information indicating an editing status of design items corresponding to the development theme in the development theme, the generating unit generates information including information indicating an editing status of the design items corresponding to the other development themes as information related to the other development themes corresponding to the design items. Design item management system.

3. 3. The design item management system according to claim 1, further storing information indicating a release date for the development theme; the generating unit generates information including information indicating a release date of the other development theme as information related to the other development theme corresponding to the design item. Design item management system.

Images