JP7734529B2 - Design item management system - Google Patents

Description

The present invention relates to technology for managing design items, and in particular to technology that is effective when applied to systems for managing design items.

Typically, in system development, design documents are created for each development unit, such as a function. These created design documents (e.g., information including design items such as code used by that function) are stored as a database. Patent Document 1 describes a technology for managing design documents in a database in this way.

Patent Document 1 describes creating virtual folders associated with design documents, and changing and managing the versions of the virtual folders in accordance with changes to the version of each design document.

Japanese Patent Application Laid-Open No. 2004-252719

As mentioned above, version control can prevent inconsistencies between multiple files.

When enhancing a system, development of multiple development themes (themes related to the functions being developed) 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-check the development themes that correspond to a certain design item.

The object of this invention is to provide a system that can output information that allows cross-sectional checking of design items related to multiple development themes.

The above and other objects and novel features of the present invention will become apparent from the description and accompanying drawings of this specification.

A brief summary of the representative inventions disclosed in this application is as follows:

A design item management system according to a representative embodiment of the present invention is a design item management system that manages 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 the 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.

The effects achieved by representative inventions disclosed in this application can be briefly explained as follows:

In other words, according to a representative embodiment of the present invention, it is possible to output information that allows cross-sectional confirmation of design items related to multiple development themes.

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. 2 is a diagram showing an outline of the data structure of data stored in an item dictionary DB 11. [0023]FIG. FIG. 2 is a diagram showing an outline of the data structure of data stored in a development theme DB 12. 1 is a diagram showing an outline of the data structure of data stored in a development theme item related information DB 13. FIG. FIG. 2 is a diagram showing an outline of the data structure of data stored in a design document information DB 14. FIG. 10 is a diagram showing an example of a screen displaying a list of development themes; 10 is an example of a screen displaying a list of items corresponding to a specified development theme. 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.

Embodiments of the present invention will be described in detail below with reference to the drawings. In all drawings used to explain the embodiments, identical parts will generally be given the same reference numerals, and repeated explanations will be omitted. However, parts that have been described using reference numerals in one drawing may be referred to using the same reference numerals when explaining other drawings, although they will not be shown again.

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 and associates development themes (themes related to the functions being developed) at the time of enhancement, etc. with the design items used in those development themes, and outputs information that allows cross-sectional confirmation of the development themes corresponding to each design item.

As mentioned above, a development theme is a theme related to the functionality of the development target, and refers to, for example, a theme related to system enhancement (system modification, modification, and expansion).

When enhancing, development across multiple development themes may proceed in parallel. Each development theme has common items, and there is a possibility that those items will be modified in each development theme. As mentioned above, when development across 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.

The design item management system provides information that makes it easy to identify development themes that are affected by specific design items.

<System configuration (overview)>
1 is a diagram showing an overview of an example of the configuration of a design item management system according to an 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 can connect to the design item management server 10 via a network 30 such as the Internet.

The design item management server 10 is a server system consisting of, for example, server equipment and virtual servers built on cloud computing services, and stores design item information for the system.

In response to input operations by user 4, terminal 40 requests the design item management server 10 to display information related to the development theme and design items. Terminal 40 also requests modifications to design items related to the development theme.

<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). The design item management server 10 also 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.

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 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 item dictionary DB11. As shown in Figure 2, item dictionary DB11 stores information including item keys, item IDs, item names, item descriptions, and the number of digits.

The item key is information used to identify 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 input operations by the user 4, etc. The item name is input from the terminal 40 in response to input operations by the user 4, etc. The item description is input from the terminal 40 in response to input operations by the user 4, etc. The item description is information to describe 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 in the item, and is input from the terminal 40 in response to input operations by the user 4, etc. The item dictionary DB 11 may also 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.

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

The development theme number is information for identifying the development theme from the user's perspective. The development theme number is input from terminal 40 in response to an input operation by user 4, etc. The development theme name is a name indicating the development theme, and is input from terminal 40 in response to an input operation by user 4, for example.

The responsible team indicates the team responsible for the development theme, and is input from terminal 40 in response to input operations by user 4, etc.

The development theme release date indicates the release date of the development theme and is input from terminal 40 in response to input operations by user 4, etc.

Returning to Figure 1, the development theme item related information DB13 is a database that stores information that associates development themes with design items (development theme item information, which is information that associates design items with information related to development themes).

Here, the structure of the information stored in the development theme item related information DB13 will be explained using Figure 4. Figure 4 is a diagram showing an overview of the data structure of the data stored in the development theme item related information DB13. As shown in Figure 4, the development theme item related information DB13 stores information including development theme keys, item keys, status, and edit contents.

The development theme key is information that identifies the development theme, similar to the development theme key shown in Figure 3. The item key is information that identifies 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 may be entered as "Editing (editable)" or "Design completed (item content finalized)."

Edit content is information indicating the changes made to the item corresponding to the item key. For example, if the number of digits in the code is changed, the number of digits before the change and the number of digits after the change are entered.

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

The development theme key is information that identifies the development theme, similar to the development theme key shown in Figure 3. The item key is information that identifies each design item, similar to the item key shown in Figure 2. The design document key is information that identifies the design document. In addition, the design document information DB14 may include information related to the content of the design document corresponding to the design document key (for example, information about the person responsible for managing the design document and the layout of the design document).

Returning to Figure 1, the display control unit 15 is a unit that displays and outputs various screens in response to requests from the terminal 40. When the display control unit 15 receives a request from the terminal 40 to display a development theme list screen, it requests the generation unit 16 to generate list information for 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. Here, an example of the screen of the list information of development themes will be described using Figure 6. Figure 6 is a diagram showing an example of the screen of the list information of development themes.

As shown in Figure 6, the development theme list information screen 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.

In addition, each development theme can be selected on the development theme list information screen. When a development theme is specified by input operation by the user of terminal 40, terminal 40 requests the transmission of list information of items corresponding to the specified development theme.

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.

When the display control unit 15 obtains 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 using Figure 7.

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

As shown in FIG. 7, the item information includes check boxes 60 for selecting items, and each item's item key, item ID, item name, and status. The item information's item key, item ID, and item name are based on data stored in the item dictionary DB11 and development theme item related information DB13. The item information's status is based on data stored in the development theme item related information DB13.

In addition, in Figure 7, information (competitive information) regarding 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 DB12 and development theme item related information DB13.

In the example of Figure 7, the data with item key "01002" has an item ID of "UKETK_NO", an item name of "Reception NO", and a status of "Editing" in the development theme "XX Check Compatible". Furthermore, the conflict information indicates that there is 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".

Here, the status "Editing" indicates that it is in the design stage, and "Design Completed" indicates that it is in coding or testing.

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

In addition, Figure 7 includes check boxes 60 for selecting each item and a search button 70 for requesting a search for design information for the item selected in the check box 60.

When the search button 70 is pressed with one of the check boxes 60 selected, the display control unit 15 requests the generation unit 16 to provide a list of design document information for the selected item. The display control unit 15 then outputs a screen listing the design document information obtained from the generation unit 16 to the terminal 40.

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

Returning to Figure 1, the generation unit 16 is the part that searches various databases in response to requests from the display control unit 15 and sends the search results to the display control unit 15.

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, generates 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 number, development theme name, responsible team, and release date from the development theme DB 12 as the list information of development themes.

When the generation unit 16 receives a request to generate list information of items corresponding to a specified development theme, it references the development theme item related information DB13 to obtain first information (development theme key, item key, status, etc.) corresponding to the development theme key of the specified development theme. The generation unit 16 also references the item dictionary DB11 to obtain the item key, item ID, and item name corresponding to the item key of the information (first information) obtained from the development theme item related information DB13. This allows the generation unit 16 to generate the item information shown in FIG. 7.

The generation unit 16 also references the development theme item related information DB13 to obtain second information (development theme key, item key, status, etc.) that corresponds to an item key in information that corresponds to the development theme key of the specified development theme and has a development theme key that is different from the specified development theme. The generation unit 16 references the development theme DB12 to obtain the 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.

As described above, the generation unit 16 references various databases and sends the 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.

In this way, the generation unit 16 generates information on 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 DB 11 and the development theme item related information DB 13.

In addition, the development theme item related information DB13 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 Figure 7.

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 shown in Figure 7.

When the generation unit 16 receives a request for a list of design document information for a selected item, it references 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 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 screen format may be generated by the generation unit 16 or the display control unit 15.

<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.

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

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

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 competitive 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 competitive 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).

In the above-described embodiment, the generation unit 16 acquires the second information, references 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.

Furthermore, while the above description is based on the case where there is an item dictionary DB11, a development theme DB12, a development theme item related information DB13, and a design document information DB14, this is not limited to this. For example, any database with a data structure capable of generating the screen shown in Figure 7 may be used.

Furthermore, 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 (e.g., the number of digits) for each item in the development theme displayed on the item list screen. This makes it possible to recognize differences between development themes for the same item.

As explained above, when a request is made by terminal 40 to send list information of items corresponding to a specified development theme, display control unit 15 requests generation unit 16 to generate list information of items corresponding to the specified development theme. Based on development theme item related information DB 13 and item dictionary DB 11, generation unit 16 generates the item information shown in FIG. 7 (information on items related to the selected development theme) and also generates competitive information (information on other development themes for the acquired item) shown in FIG. 7. Generation unit 16 generates information that associates the item information shown in FIG. 7 with the competitive information shown in FIG. 7, and sends this information (item list information) to display control unit 15.

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

In addition, the development theme item related information DB13 has statuses that indicate the editing status of design items, and the generation unit 16 generates information including status information as the conflict information in Figure 7. This allows the design item management server 10 to output information that allows the status of items in each development theme to be checked across the board.

In addition, the development theme DB 12 stores release dates, and the generation unit 16 generates information including the release dates of development themes as the conflict information shown in Figure 7. This allows the design item management server 10 to output information that makes it possible to recognize the priority between development themes, since the closer the release date, the higher the priority.

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 invention, and the invention is not necessarily limited to those that include all of the described configurations. Furthermore, it is possible to add, delete, or replace some of the configurations of the above embodiments with other configurations.

Furthermore, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole in hardware, for example by designing them as integrated circuits. Furthermore, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing programs that realize the respective functions. Information such as programs, tables, and files that realize the respective functions can be stored in a storage device such as memory, a hard disk, or an SSD (Solid State Drive), or on a storage medium such as an IC card, SD card, or DVD.

In addition, in the above diagrams, the control lines and information lines shown are those considered necessary for explanation, and do not necessarily represent all control lines and information lines in the actual implementation. In reality, it is safe to assume that almost all components are interconnected.

In addition, in the above embodiment, the development theme list displays the target development themes as shown in Figure 6, but there may be relationships between 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). Furthermore, a related development theme that continues development after a certain development theme is related to the target development theme (continuation related). Furthermore, 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, generating a list of items for multiple related development themes. Here, in the case of multiple related development themes, items (e.g., item IDs) may overlap, but the system may be configured to display overlapping items separately, or to highlight overlapping items.

In addition, even if an item in one development theme and another development theme is essentially the same, there may be variations in notation. However, if it is received from the user that an item in one development theme and an item in another development theme are the same, a display indicating the sameness may be displayed, or an extraction process may be performed assuming that they are the same.

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

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 (3)

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. 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. 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.