JP2023028672A - Design item management system - Google Patents

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

The present invention relates to technology for managing design items, and more particularly to technology effective when applied to a system for managing design items.

Generally, in system development, a design document is created for each development unit such as a function unit. The created design document (for example, information including design items such as codes used in the function) is saved as a database. As a technique for managing design documents in a database in this way, there is a technique described in Patent Document 1.

Patent Literature 1 describes that a virtual folder associated with a design document is provided, and the version of the virtual folder is also changed and managed according to the version change of each design document.

Japanese Patent Application Laid-Open No. 2004-252719

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

By the way, development of a plurality of development themes (themes related to functions to be developed) often progresses in parallel when, for example, enhancing a system. A common design item may be used in multiple development themes, and it is desirable to be able to cross-check the development theme corresponding to a certain design item in order to develop appropriately.

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to provide a system capable of outputting information that enables cross-sectional confirmation of design items related to a plurality of development themes.

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

A brief outline of typical inventions disclosed in the present application is as follows.

A design item management system according to a representative embodiment of the present invention is a design item management system for managing design items, comprising: a design item information storage unit for storing design item information, which is information relating to design items; a development theme item information storage unit for storing development theme item information, which is information in which information relating to a development theme, which is a theme relating to a function to be developed, is associated with development theme item information; and 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, generating information on design items corresponding to the selected development theme and information on other development themes corresponding to the design items. and an output unit for outputting the information generated by the generating unit.

Among the inventions disclosed in the present application, the effects obtained by representative ones are briefly described below.

That is, according to the representative embodiment of the present invention, it is possible to output information that allows cross-checking of design items related to a plurality of development themes.

1 is a diagram showing an overview of a configuration example of a design item management system that is an embodiment of the present invention; FIG. 4 is a diagram showing an overview of the data structure of data stored in an item dictionary DB 11; FIG. 4 is a diagram showing an overview of the data structure of data stored in a development theme DB 12; FIG. 4 is a diagram showing an overview of the data structure of data stored in a development theme item related information DB 13; FIG. 4 is a diagram showing an overview of the data structure of data stored in a design document information DB 14; FIG. FIG. 10 is a diagram showing an example screen of list information of development themes; It is an example of a screen of list information of items corresponding to a designated development theme. FIG. 10 is a diagram showing an overview of an example of the flow of processing for outputting information that allows cross-sectional confirmation of development themes corresponding to each design item;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In principle, the same parts are denoted by the same reference numerals throughout the drawings for describing the embodiments, and repeated descriptions thereof will be omitted. On the other hand, parts that have been described with reference numerals in one drawing may be referred to with the same reference numerals, although they are not shown again in the description of other drawings.

A design item management system, which is an embodiment of the present invention, is a system for managing system design items (for example, design items such as code information). This design item management system associates and stores development themes (themes related to functions to be developed) for enhancement, etc., and design items used in the development themes, thereby creating development themes corresponding to each design item. Output information that can be cross-checked.

As described above, a development theme is a theme related to a function to be developed, and indicates, for example, a theme related to system enhancement (change, modification, or extension of the system).

When enhancing, the development of multiple development themes may progress in parallel. Each development theme has items that are commonly used, and each development theme may modify the items. As described above, when the development of multiple development themes progresses in parallel, there is a possibility that other development themes have already been corrected. In addition, if a certain design item is corrected in a certain development theme, other development themes may also be affected.

The design item management system provides information that allows easy identification of development themes affected by predetermined design items.

<System configuration (outline)>
FIG. 1 is a diagram showing an overview of a configuration example 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 held by a user 4 who is in charge of design and connectable to the design item management server 10 via a network 30 such as the Internet. and

The design item management server 10 is a server system including, for example, a server device and a virtual server constructed on a cloud computing service, and stores design item information of the system.

The terminal 40 requests the design item management server 10 to display information on development themes and design items according to an input operation by the user 4 . Also, the terminal 40 requests correction of design items related to the development theme.

<Description of the functions of the design item management server>
Next, the functions of the design item management server 10 will be explained. The design item management server 10 uses a CPU (Central Processing Unit) (not shown) to store an OS (Operating System) and a DBMS (DataBase Management System) developed on a memory, middleware such as a Web server program, and software running thereon. By executing, the function of each part described later is realized. In this embodiment, the design item management server 10 includes an item dictionary DB 11 (design item information storage unit), a development theme DB 12, and a development theme item related information DB 13 recorded in a storage device such as a HDD (Hard Disk Drive) (not shown). (development theme item information storage unit), and design document information DB 14 and other data stores. Further, the design item management server 10, as shown in the figure, has respective units such as a display control unit 15 (output unit) implemented as software, and a generation unit 16, for example.

The item dictionary DB 11 is a database that stores design item information, which is information about design items, and is a known item dictionary. The structure of information stored in the item dictionary DB 11 will be described with reference to FIG. FIG. 2 is a diagram showing an overview of the data structure of data stored in the item dictionary DB 11. As shown in FIG. As shown in FIG. 2, the item dictionary DB 11 stores information including item keys, item IDs, item names, item descriptions, and the number of digits.

The item key is information for identifying each design item. The item key is information that is set each time each 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 according to the input operation of the user 4 or the like. The item name is input from the terminal 40 according to the user's 4 input operation or the like. The item description is input from the terminal 40 according to the user's 4 input operation or the like. In the item explanation, information for explaining the item such as the definition of the values that the item can take and the information indicated by the code of the item is entered. The number of digits is the number of digits of the item, and is input from the terminal 40 according to the input operation of the user 4 or the like. The item dictionary DB 11 may further have information on items. For example, information on code conditions (range of values allowed in the code, restrictions on values in the first digit, etc.) may be included.

Returning to FIG. 1, the development theme DB 12 is a database that stores attribute information of development themes. The structure of information stored in the development theme DB 12 will be described with reference to FIG. FIG. 3 is a diagram showing an overview of the data structure of data stored in the development theme DB 12. As shown in FIG. As shown in FIG. 3, the development theme DB 12 stores information including development theme keys, development theme numbers, development theme names, teams in charge of development themes, and release dates. A development theme key is information for identifying a development theme. The development theme key is automatically given by the design item management server 10 .

The development theme number is information for identifying the development theme from the user's point of view. The development theme number is input from the terminal 40 according to the user's 4 input operation or the like. The development theme name is a name that indicates the development theme, and is input from the terminal 40 according to the user's 4 input operation or the like, for example.

The team in charge indicates the team in charge of the development theme, and is input from the terminal 40 according to the input operation of the user 4 or the like.

The release date of the development theme indicates the release date of the development theme, and is input from the terminal 40 according to the input operation of the user 4 or the like.

Returning to FIG. 1, the development theme item related information DB 13 is a database that stores information that associates development themes with design items (development theme item information that is information that associates design items with information about development themes). is.

Here, the structure of information stored in the development theme item related information DB 13 will be described with reference to FIG. FIG. 4 is a diagram showing an overview of the data structure of data stored in the development theme item related information DB 13. As shown in FIG. As shown in FIG. 4, the development theme item related information DB 13 stores information including development theme keys, item keys, statuses, and edit contents.

The development theme key is information for identifying a development theme, similar to the development theme key shown in FIG. The item key is information for identifying each design item like the item key shown in FIG. The status indicates the editing status of the item corresponding to the item key. As the status, for example, contents indicating "editing (editable state)", "design completed (determined contents of items)", etc. are input.

The edited content is information indicating the changed content of the item corresponding to the item key. For example, when the number of digits of the code is changed, the number of digits before change and the number of digits after change are entered.

Returning to FIG. 1, the design document information DB 14 is a database that stores information on the design document. Here, the structure of information stored in the design document information DB 14 will be described with reference to FIG. FIG. 5 is a diagram showing an overview of the data structure of data stored in the design document information DB 14. As shown in FIG. As shown in FIG. 5, the design document information DB 14 stores information including development theme keys, item keys, and design document keys.

The development theme key is information for identifying a development theme, similar to the development theme key shown in FIG. The item key is information for identifying each design item like the item key shown in FIG. A design document key is information for identifying a design document. Further, the design document information DB 14 may include information on the content of the design document corresponding to the design document key (for example, information on the manager of the design document, the layout of the design document, etc.).

Returning to FIG. 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 the development theme list screen display request from the terminal 40, the display control unit 15 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 , the display control unit 15 outputs a screen of the acquired development theme list information (development theme list screen) to the terminal 40 . Here, an example of a screen of list information of development themes will be described with reference to FIG. FIG. 6 is a diagram showing a screen example of list information of development themes.

As shown in FIG. 6, the development theme list information screen includes data (development theme number, development theme name, team in charge, and release date) stored in the development theme DB 12 as shown in FIG. data).

Each development theme can be selected on the development theme list information screen. When a certain development theme is designated by the user's input operation of the terminal 40, the terminal 40 requests transmission of list information of items corresponding to the designated development theme.

When the display control unit 15 receives a transmission request for list information of items corresponding to the designated development theme from the terminal 40, the display control unit 15 requests the generation unit 16 to generate list information of items corresponding to the designated development theme. .

When the display control unit 15 acquires the list information of the items corresponding to the designated development theme from the generation unit 16 , the display control unit 15 outputs the screen of the list information of the items corresponding to the designated development theme to the terminal 40 . Here, an example of a screen of list information of items corresponding to the designated development theme will be described with reference to FIG.

FIG. 7 is an example of a screen of list information of items corresponding to the designated development theme. It is assumed to be list information of items corresponding to the development theme (the release date is 2017/12/01) whose development theme name is "○△ check supported".

As shown in FIG. 7, it includes check boxes 60 for selecting items, and item information including item keys, item IDs, item names, and statuses of 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 development theme item related information DB 13 . The item information status is based on data stored in the development theme item related information DB 13 .

In addition, in FIG. 7, the development theme name, status, and release date are included as information (competition information) on other development theme items corresponding to each item. The development theme name, status, and release date are based on data stored in the development theme DB 12 and development theme item related information DB 13 .

In the example of FIG. 7, data with an item key of "01002" has an item ID of "UKETK_NO", an item name of "Receipt NO", and a status of "Editing ”. In addition, as conflict information, it indicates that there is an item with the same item key even in the development theme name "Compatible with 〇〇 check" (release date is 2017/11/10), and the status of the item with "Compatible with 〇〇 check" indicates that the design is complete.

Here, "editing" in the status indicates that it is in the design stage, and "design completed" indicates that it is under coding or testing.

Although not displayed in the screen shown in FIG. 7, another screen (for example, the screen in FIG. 6) indicating that the release date of the development theme for "○△ check correspondence" is 2017/12/01 is displayed at the same time. may be displayed. Further, the screen of FIG. 7 may include information indicating that the release date of the development theme "supporting 〇△ check" is 2017/12/01.

FIG. 7 also includes a check box 60 for selecting each item and a search button 70 for requesting a search for the design information of the item selected by the check box 60 .

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

Thus, the display control unit 15 outputs the information generated by the generation unit 16. FIG.

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 result to the display control unit 15 .

Upon receiving a development theme list information generation request from the display control unit 15, the generation unit 16 refers to the development theme DB 12, generates development theme list information, and sends the generated development theme list information to the display control unit 16. 15. For example, the generation unit 16 generates the development theme key, development theme number, development theme name, team in charge, and release date list information of the development theme DB 12 as the development theme list information.

Further, upon receiving a request for generating list information of items corresponding to the designated development theme, the generating unit 16 refers to the development theme item related information DB 13 to obtain the development theme key corresponding to the designated development theme. 1 Acquire information (development theme key, item key, status, etc.). The generation unit 16 also refers to the item dictionary DB 11 to acquire an item key, an item ID, and an item name corresponding to the item key of the information (first information) acquired from the development theme item related information DB 13 . Thereby, the generation unit 16 can generate the item information shown in FIG.

The generating unit 16 also refers to the development theme item related information DB 13 to generate a development theme key that corresponds to the item key in the information corresponding to the development theme key of the above-mentioned designated development theme and that is different from the designated development theme. Acquire second information (development theme key, item key, status, etc.). The generation unit 16 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. Thereby, the generation unit 16 can generate the competition information shown in FIG.

As described above, the generation unit 16 refers to various databases and controls the display of the information in which the item information and the competition information shown in FIG. 7 are associated with each other as list information of items corresponding to the designated development theme. Send to section 15 .

In this way, the generation unit 16 generates information on design items corresponding to the selected development theme (item information in FIG. 7) and Information (conflict information in FIG. 7) on other corresponding development themes is generated.

Further, 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 status information as the competition information in FIG.

The development theme DB 12 stores the release date, and the generation unit 16 generates information including the release date of the development theme as the competition information in FIG.

Note that upon receiving a request for a list of information on the design document of the selected item, the generating unit 16 refers to the design document information DB 14, and generates the development theme key specified on the development theme list information screen and the selected item. acquires the design document information corresponding to the design document key corresponding to the item key of , and sends the design document information to the display control unit 15 . Note that the screen format information may be generated by the generation unit 16 or may be generated by the display control unit 15 .

<Process flow>
FIG. 8 is a diagram showing an overview of an example of the flow of processing for outputting information for cross-checking development themes corresponding to each design item in response to a request from terminal 40 in the present embodiment. .

First, when the user 4 makes an input operation to request display of a development theme list information screen (development theme list screen) from the terminal 40 (S01), the display control unit 15 of the design item management server 10 sends a request to the generation unit 16. Request to generate list information of development theme. When the display control unit 15 acquires the development theme list information from the generation unit 16, the display control unit 15 outputs a screen of the acquired development theme list information (development theme list screen) to the terminal 40 (S02). The terminal 40 displays a development theme list screen (S03).

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

The generation unit 16 generates item information (information on items related to the selected development theme) shown in FIG. 7 (S05). In addition, the generation unit 16 generates competition information (information on development themes other than the acquired items) shown in FIG. 7 (S06). The generation unit 16 generates information in which the item information shown in FIG. 7 and the competition information shown in FIG. 7 are associated with each other, and sends the 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 obtains the second information, refers to the development theme DB 12, and obtains the development theme name and release date corresponding to the development theme key of the second information. can't For example, the development theme name and release date corresponding to the development theme key are included in the development theme item related information DB 13, and when the generating unit 16 acquires the second information, the development theme name and release date are stored in the development theme item related information DB 13. You may make it acquire a day.

Also, the 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 provided has been described, but 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.

Although not particularly described in the above-described embodiment, information (for example, , number of digits) may be displayed. This makes it possible to recognize the difference for each development theme in the same item.

As described above, when the terminal 40 requests transmission of list information of items corresponding to the designated development theme, the display control unit 15 causes the generation unit 16 to display items corresponding to the designated development theme. Request to generate list information. The generation unit 16 generates the item information (information on items related to the selected development theme) shown in FIG. 7 based on the development theme item related information DB 13 and the item dictionary DB 11, Generate information (information on development themes other than the acquired item). The generation unit 16 generates information in which the item information shown in FIG. 7 and the competition information shown in FIG.

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 of other development themes corresponding to the item (item information shown in FIG. 7). competition information) is output, it is possible to output information that can cross-check items related to a plurality of development themes.

Further, 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 status information as the competition information in FIG. As a result, the design item management server 10 can output information with which the status of items in each development theme can be cross-checked.

Further, the development theme DB 12 stores the release date, and the generation unit 16 generates information including the release date of the development theme as the competition information in FIG. As a result, the design item management server 10 generally gives higher priority to the closer to the release date, so it is possible to output information with which the priority between development themes can be recognized.

Although the invention made by the present inventor has been specifically described above based on the embodiments, the present invention is not limited to the above embodiments, and can be variously modified without departing from the scope of the invention. Needless to say. For example, the above embodiments have been described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the described configurations. Moreover, it is possible to add, delete, or replace some of the configurations of the above-described embodiments with other configurations.

Further, each of the above configurations, functions, processing units, processing means, and the like may be realized by hardware, for example, by designing a part or all of them using an integrated circuit. Moreover, each of the above configurations, functions, etc. may be realized by software by a processor interpreting and executing a program for realizing each function. Information such as programs, tables, and files that implement each function can be stored in recording devices such as memories, hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.

Further, in each of the above drawings, control lines and information lines are those considered to be necessary for explanation, and not all control lines and information lines for implementation are necessarily shown. In fact, it may be considered that almost all configurations are interconnected.

Further, in the above-described embodiment, as shown in FIG. 6, the target development themes are displayed in the list of development themes. When there are multiple small development themes, the small development themes have a relationship (related to the same major theme) through the large development theme, and the related development continues after a certain development theme. A development theme and a target development theme have a relationship (continuation relationship), and a development theme that utilizes the deliverables of a development theme and a target development theme have a relationship (utilization relationship), By adding such related information to the development theme list and making it selectable, related development themes can also be selected together and an item list of multiple related development themes can be generated. Here, in the case of a plurality of related development themes, items (for example, item IDs) may overlap, but the configuration is such that the overlapping items are displayed without overlapping or the overlapping items are conspicuously displayed. may

In addition, even if the items of one development theme and another development theme are substantially the same, the notation may vary, but the item of one development theme and the item of another development theme must be the same. is received from the user, a conspicuous display indicating the same may be performed, or an extraction process may be performed as the same.

INDUSTRIAL APPLICABILITY 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 item;
a development theme item information storage unit that stores development theme item information that is information in which the design item and information about a development theme that is a theme about a function to be developed are associated;
design item information corresponding to the selected development theme 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; , a generator that generates information on other development themes corresponding to the design item;
an output unit that outputs information generated by the generation unit;
A design item management system comprising The design item management system according to claim 1,
The development theme item information storage unit includes, as information about the development theme, information indicating an editing status of design items corresponding to the development theme in the development theme,
The generation unit generates information including information indicating an editing status of the design item corresponding to the other development theme as information related to the other development theme corresponding to the design item.
Design item management system. The design item management system according to claim 1 or 2,
further storing information indicating the release date of the development theme;
The generation unit generates information including information indicating a release date of the other development theme as information on the other development theme corresponding to the design item.
Design item management system.

Images