JP2018049397A - Design information management device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a design information management device which allows a user to easily obtain a metrics concerning reuse of design information and easily capture a range of impact due to a change in the design information.SOLUTION: The design information management device includes a project information storage part, a design information storage part and an information operation part. The design information storage part stores design information containing a project identifier, a design information identifier for identifying each design information, master information for identifying a master when design information on the master is present and content information indicating the contents of each design. The information operation part invalidates current state information on design information before a change, create changed design information and performs setting so that master information in the changed design information means the design information before the change when updating the design information, while it creates design information of a duplication destination, duplicates content information of design information of a duplication origin to the design information of the duplication destination and performs setting so that master information in the design information of the duplication destination means the design information of the duplication origin when duplicating the information.SELECTED DRAWING: Figure 1

Description

  Embodiments described herein relate generally to a design information management apparatus and a program.

When developing information systems and computer software, a design process is executed as one of the processes. In the design process, the developer creates design information.
The design information has an identifier for identifying the design information and the content of the design information itself. Design information is created, updated, deleted, or retrieved throughout the development life cycle. For storing design information, a configuration management system or the like is used to manage the history of creation, update, and deletion of design information.

  In addition, the design information may be reused. This is because reusing at least a part of past design information may be less costly than creating new design information from scratch. When the design information is reused, the existing design information is copied, an identifier is newly given to the new design information, and stored in the configuration management system.

For example, Patent Document 1 describes a system that enables reuse of design data (design document). In this system, an identification ID for each design data is assigned and stored in a repository, design reasons related to individual design data are stored in another repository 16 and the design data is reused by searching based on the design reasons. Is possible.
Further, for example, Patent Document 2 describes a system in which software component design information is stored in a database and can be searched by a keyword.
Here, reusing design information means copying existing design information and using it for another purpose, or copying existing design information and making further changes. .

  However, the design information management method according to the prior art has two major problems. The first problem is to be able to acquire metrics related to reuse of design information. In addition, the second problem is to be able to acquire the influence range of the change when the design information is changed in a situation where the design information is reused. Next, each problem will be described in more detail.

Regarding the first problem, the configuration management system according to the related art can reuse design information, but may not be able to acquire metrics related to the reuse appropriately and simply.
As described above, the main purpose of reuse of design information is to reduce development costs. The reuse of design information has the following two types. The first is the reuse of design information within a project. Second, the design information is reused across projects, that is, the design information of other projects is reused and utilized as the design information of the own project. From the standpoint of reducing project costs by reusing design information, it is desirable to easily obtain various metrics. Here, metrics are specifically the rate at which design information is reused within a project, the rate at which one's own project reuses design information from another project, and the other project reuses design information from its own project. This is the percentage used. However, the configuration management system according to the prior art does not have information on which design information to be managed is reused, and therefore it is not possible to easily measure the above metrics. There was sex.

Regarding the second problem, the configuration management system according to the prior art can reuse design information, but does not have information on which design information is reused from which other design information. For this reason, when the design information is to be changed, the influence range of the change may not be easily detected.
When certain design information is reused, the design information can be a reuse source of a plurality of design information of a plurality of projects. If it is necessary to make some changes to the reused design information, the change may need to be reflected in the design information of the reuse source. In addition, if there is a need to change the design information of the reuse source, the change may need to be reflected in the design information of all reuse destinations that use the design information as the reuse source. . From the standpoint of reducing the cost of a project through reuse, when changing certain design information, the design information of the reuse source of the design information to be changed and all the reused from the reuse source It is necessary to know design information appropriately.

JP 2006-330998 A JP 2006-018448 A

  A problem to be solved by the present invention is to provide a design information management apparatus and program capable of easily acquiring metrics relating to reuse of design information and easily grasping the influence range of changes in design information. That is.

  The design information management apparatus according to the embodiment includes a project information storage unit, a design information storage unit, and an information operation unit. The project information storage unit stores project information including a project identifier for identifying a project. The design information storage unit specifies the parent when the project identifier, the design information identifier for identifying the design information in the project, and the design information of the parent that is the copy source or the change source exist. Design information including parent information, current state information indicating whether the design information is valid or invalid, and content information indicating the design content is stored. The information operation unit has a function of creating, updating, or deleting the project information and the design information. When the design information is updated, the current state information about the design information before the change is displayed. Invalidate and create the design information after the change and set the parent information in the design information after the change to point to the design information before the change. Design information is created and the content information of the design information of the copy source is copied to the design information of the copy destination, and the parent information in the design information of the copy destination is set to indicate the design information of the copy source.

1 is a block diagram showing a schematic functional configuration of a design information management apparatus 1 according to a first embodiment. Schematic which shows the menu screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the project creation screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the project selection screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the project duplication screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the project deletion screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information creation screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the project metrics display screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information selection screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information edit screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information replication screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information deletion screen of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information change influence range display screen (the 1) of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the design information change influence range display screen (the 2) of the design information management apparatus 1 of 1st Embodiment. Schematic which shows the specification of the project information storage part 21 of 1st Embodiment. It is the schematic which shows the specification of the design information storage part 22 of 1st Embodiment. Schematic which shows the specification of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the project creation method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the project identifier list acquisition method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the project duplication method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the project deletion method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the design information creation method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the design information identifier list acquisition method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the design information replication method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the design information deletion method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the design information update method of the information operation part 11 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the method "get unique ID" of the information operation part 11 of 1st Embodiment. Schematic diagram of change history for explaining a process in which a change influence detection unit 12 according to the first embodiment detects an influence range by tracing a change history of design information (part 1). Schematic diagram of change history for explaining a process in which the change influence detection unit 12 of the first embodiment detects the influence range by tracing the change history of the design information (part 2). Schematic diagram of change history for explaining a process in which the change influence detection unit 12 of the first embodiment detects the influence range by tracing the change history of design information (No. 3). Schematic which shows the specification of the change influence detection part 12 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the change influence range detection method of the change influence detection part 12 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the setting ancestor design information acquisition method of the change influence detection part 12 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the descendant acquisition method of the change influence detection part 12 of 1st Embodiment. Schematic which shows the specification of the metrics measurement part 13 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the metrics measurement method of the metrics measurement part 13 of 1st Embodiment. Schematic for demonstrating the detailed process sequence etc. of the reuse design information acquisition method which the metrics measurement part 13 of 1st Embodiment has. Schematic for demonstrating the detailed process sequence etc. of the reused design information acquisition method which the metrics measurement part 13 of 1st Embodiment has. Schematic for demonstrating the detailed process sequence etc. of the "get ancestor" method which the metrics measurement part 13 of 1st Embodiment has. Schematic for demonstrating the detailed process sequence etc. of the "is descendant" method which the metrics measurement part 13 of 1st Embodiment has.

  Hereinafter, a design information management device and a program according to an embodiment will be described with reference to the drawings.

FIG. 1 is a block diagram showing a schematic functional configuration of the design information management apparatus according to the present embodiment. As illustrated, the design information management apparatus 1 includes an interface unit 10, an information operation unit 11, a change impact detection unit 12, a metrics measurement unit 13, a project information storage unit 21, and a design information storage unit 22. Consists of including. Each of the above-described parts constituting the design information management apparatus 1 is realized using, for example, an electronic circuit. As an example, each unit may be realized in a form in which a CPU (Central Processing Unit) executes a computer program. In addition, each unit may include a storage unit such as a semiconductor memory or a magnetic hard disk device in order to store information.
The design information management device 1 is connected to the terminal device 30 and exchanges information with the terminal device 30.
The design information management apparatus 1 is realized using, for example, a server computer. Further, as the terminal device 30, for example, a personal computer, a tablet terminal, a smartphone, a wearable terminal, or the like is used.
The design information management device 1 and the terminal device 30 are connected using, for example, a communication network (WAN or LAN). For example, communication using the Internet protocol (IP) is performed between the design information management device 1 and the terminal device 30.
The function of each unit is as described below.

  The interface unit 10 has a function of connecting and mediating the terminal device 30 and each unit in the design information management device 1. Specifically, the interface unit 10 receives an instruction from the terminal device 30 and transmits it to each unit in the design information management device 1, or conversely transmits it to the terminal device 30 side to display information passed from each unit. To do.

  The information operation unit 11 operates project information and design information according to instructions received via the interface unit 10. Specifically, the information operation unit 11 creates, updates, deletes, searches for project information stored in the project information storage unit 21 and design information stored in the design information storage unit 22. To do.

  More specifically, the information operation unit 11 has a function of creating, updating, or deleting project information and design information. In addition, when updating the design information, the information operation unit 11 invalidates the current state information about the design information before the change, creates the design information after the change, and the parent information in the design information after the change is not changed. Set to point to the design information. In addition, when duplicating design information, the information operation unit 11 creates design information of a duplication destination, duplicates the content information of the design information of the duplication source into the design information of the duplication destination, and also displays Set the information to point to the design information of the copy source.

The change influence detection unit 12 detects the influence range of the change of the design information based on the instruction received via the interface unit 10.
More specifically, the change impact detection unit 12 sequentially follows the design information in the parent direction from the start point based on the parent information of the design information, starting from the designated design information, and the design information of the start point. Identify the oldest parent with content information. Then, the change influence detection unit 12 changes the content information of the design information of the starting point by sequentially tracing the design information of the child direction based on the parent information of the design information from the identified oldest parent. Detect a range that may be affected if

The metrics measurement unit 13 measures the metrics of the project based on the instruction received via the interface unit 10.
More specifically, the metric measurement unit 13 is a first statistical information that is a statistic regarding the number of designated projects reused design information of other projects for the designated designated project based on the parent information of the design information. And second statistical information that is the number of times that the designated project reuses the design information of the designated project, and third statistical information that is the number of statistics that the other project reuses the design information of the designated project. calculate. In addition, the metrics measurement unit 13 acquires a use / used relationship while tracing a history between design information using a method described later. In addition, the metrics measurement unit 13 calculates the above statistical information by performing statistical calculation regarding the number of design information and the like based on the obtained usage / use relationship.

The project information storage unit 21 stores information on identifiers of system development projects and software development projects.
Specifically, the project information storage unit 21 stores project information including a project identifier for identifying a project.
Each instance of the project information stored in the project information storage unit 21 has the following information (1) and (2).
(1) Variable id: String type (2) Variable current: Boulean (Boolean) type The above variable id stores a character string of a project identifier. The variable current represents whether the project information is valid (true) or invalid (false).
At a certain time, an effective project (current = true) can be uniquely identified by a project identifier (variable id).

The design information storage unit 22 stores design information including identifiers of design information (system and software specifications) defined in a system development project and software development project, and specific design contents.
The design information storage unit 22 stores design information. The design information includes a project identifier for identifying the project to which it belongs. The design information includes a design information identifier for identifying design information in the project. The design information includes parent information for specifying the parent when there is design information of the parent that is the copy source or the change source. In addition, the design information includes current state information indicating whether the design information is valid or invalid. Further, the design information includes content information representing design content.

Each instance of the design information stored in the design information storage unit 22 has the following information (3) to (8).
(3) Variable id: String type (4) Variable parentId: String type (parent information)
(5) Variable current: Boulean type (current state information)
(6) Variable projectId: String type (7) Variable specId: String type (8) Variable contents Map <String, String> type The variable id is identification information for uniquely identifying an instance of design information.
The variable parentId stores the id of the design information of the parent of the design information. The variable parentId is also called a parent identifier. For example, when certain design information is copied, the copy source design information is a parent and the copy destination design information is a child. For example, when certain design information is updated (content change), the design information before update is a parent, and the design information after update is a child.
The variable current represents whether the design information instance is valid (true) or invalid (false).
The variable projectId is information for identifying the project to which the design information instance belongs. The value of the variable projectId is associated with the project information variable projectId stored in the project information storage unit 21.
The variable specId is information for identifying the design information.
The variable contents holds the contents of design information. The contents of the design information are expressed as a list of attribute name (string type) and attribute value (string type) pairs.
The primary key of the design information is the variable id described above. The variable id uniquely identifies an instance of design information. At a certain point in time, valid design information (current = true) is uniquely specified by a combination of a project identifier (variable projectId) and a design information identifier (variable specId).

  The terminal device 30 exchanges data with the design information management device 1. The terminal device 30 is used by a user. The terminal device 30 transmits an instruction to the interface unit 10 of the design information management device 1 based on a user operation, or displays information sent from the interface unit 10 on its own screen. Specifically, the terminal device 30 transmits an instruction for creating, updating, deleting, and searching for project information and design information to the interface unit 10. In addition, the terminal device 30 transmits an instruction to the interface unit 10 to display the influence range of the design information change or to display the metrics related to the reuse of the design information.

  FIG. 2 is a schematic diagram showing a menu screen of the design information management apparatus 1. This menu screen is displayed on the screen of the terminal device 30 by the function of the interface unit 10. As shown, the menu screen includes a plurality of menu items that can be clicked. In the figure, underlined items are clickable menu items. The clickable menu item is associated with link destination information (such as a URI) that is changed by a user's click operation. Some menu items may or may not be displayed depending on the situation (context).

Specifically, the menu screen includes “project creation” and “project selection” as clickable menu items.
Further, when a project has been selected by the above “project selection”, the identifier of the selected project is displayed. In the illustrated example, the selected project is “Attendance system for company XX”.
If a project has already been selected, the menu items that can be clicked include "Project Duplication", "Delete Project", "Project Metrics Display", "Design Information Creation", and "Design Information Selection". . The functions of these menu items are for various processes for the selected project.

Further, when the design information has been selected by the “design information selection” described above (in this case, the project is also selected as a premise), the identifier of the selected design information is displayed. In the illustrated example, the selected design information is a “user management function”.
In addition, when design information has been selected, “design information editing”, “design information duplication”, “design information deletion”, and “design information change influence range display” are displayed as clickable menu items. . The functions of these menu items are for various processes for the selected design information of the selected project.

  3 to 14, functions of each unit will be described from the viewpoint of the user interface (screen or the like) of the design information management apparatus 1.

  FIG. 3 is a schematic diagram showing a project creation screen of the design information management apparatus 1. When “project creation” is selected on the menu screen described above, the interface unit 10 displays this project creation screen.

  As shown in the figure, the project creation screen includes an input field for inputting a project identifier, and a “project creation” button. A user (for example, a person in charge of system development) can perform an operation of operating a keyboard or the like to input a project identifier in an input field and pressing a “create project” button. When the operation is performed, the interface unit 10 calls a project creation method of the information operation unit 11. When this project creation method is called, the information operation unit 11 executes the project new creation method. When a new project is created, the interface unit 10 stores the project identifier of the newly created project as the selected project identifier. Accordingly, the interface unit 10 displays the selected project identifier on the menu screen described above.

  FIG. 4 is a schematic diagram showing a project selection screen of the design information management apparatus 1. When “project selection” is selected on the menu screen described above, the interface unit 10 displays this project selection screen.

  As shown in the figure, the project selection screen displays a list including a list of project identifiers. In the example shown in the drawing, a list of project identifiers such as “Attendance system for XX company” and “Order receiving system for XX company” is displayed. These project identifiers are stored in the project information storage unit 21. The interface unit 10 acquires a list of project identifiers to be displayed on the project selection screen by calling the project identifier list acquisition method of the information operation unit 11. The project selection screen is configured so that the user can select one from the displayed list of project identifiers. When the user performs an operation of selecting one project identifier from the displayed list, the interface unit 10 stores the project identifier as the selected project identifier. Accordingly, the interface unit 10 displays the selected project identifier on the menu screen described above.

  FIG. 5 is a schematic diagram showing a project duplication screen of the design information management apparatus 1. When “duplicate project” is selected on the menu screen described above, the interface unit 10 displays this duplicate project screen.

  As shown in the figure, the project duplication screen displays the currently selected project identifier. This selected project becomes the duplication source project in the duplication processing. The project duplication screen includes a project identifier input field (a field displayed as “project identifier to be duplicated and created”) and a project duplication button. The user can input a project identifier in the project identifier input field on the project duplication screen and press the project duplication button. When the project copy button is pressed by a user operation, the interface unit 10 calls a project copy method of the information operation unit 11. Then, the information operation unit 11 executes the project duplication method. As a result, the information operation unit 11 duplicates the duplication source project and generates a new project. New project information generated by duplication is also stored in the project information storage unit 21. When the project duplication process is completed, the interface unit 10 stores the generated project identifier as the selected project identifier. Accordingly, the interface unit 10 displays the selected project identifier on the menu screen described above.

  FIG. 6 is a schematic diagram showing a project deletion screen of the design information management apparatus 1. When “Delete Project” is selected on the menu screen described above, the interface unit 10 displays this project delete screen.

As shown in the figure, the project deletion screen displays the selected project identifier at that time. This selected project is the project to be deleted here. The project duplication screen also displays a project deletion button.
The user can press this project delete button. When the project deletion button is pressed by a user operation, the interface unit 10 calls a project deletion method of the information operation unit 11. Then, the information operation unit 11 executes a project deletion method. Since the project deletion process is to delete the currently selected project, the selected program disappears when the deletion process is completed. Accordingly, the interface unit 10 clears the stored selected project identifier. Accordingly, the interface unit 10 updates the above-described menu screen to a state where the selected project identifier does not exist.

  FIG. 7 is a schematic diagram showing a design information creation screen of the design information management apparatus 1. When “design information creation” is selected on the menu screen described above, the interface unit 10 displays this design information creation screen.

  As shown in the figure, the design information creation screen displays the selected project identifier at that time. This selected project is a project for which design information is created. The design information creation screen also includes a design information identifier input field, a design information input field, and a design information creation button. The user can input the design information identifier in the design information identifier input field and press the design information creation button. At this time, the user may be allowed to input design information in the design information input field. When the user presses the design information creation button, the interface unit 10 calls a design information creation method of the information operation unit 11. Then, the information operation unit 11 executes a design information creation method to create design information. The design information created by the information operation unit 11 is stored in the design information storage unit 22.

  FIG. 8 is a schematic diagram showing a project metrics display screen of the design information management apparatus 1. When “project metrics display” is selected on the menu screen described above, the interface unit 10 displays this project metrics display screen.

  As shown in the figure, the project metrics display screen displays the currently selected project identifier. Further, the project metrics display screen displays the number of design information possessed by the selected project. In the illustrated example, the number of design information is 1000. The project metrics display screen displays metrics for the selected project. In the example illustrated, the project metrics display screen includes, as metrics, statistical information about the reuse source project (left side in the figure) and statistical information about the reuse destination project (right side in the figure).

The information on the reuse source project includes a list of pairs of the name of the reuse source project (project identifier) and the number of reuses from the reuse source project (number of reuses). In the example shown in the figure, “Project X” (number of reuses 100) is listed first, and “Project Y” (number of reuses 500) is listed second.
The information on the reuse destination project includes a list of pairs of the name of the reuse destination project (project identifier) and the number reused by the reuse destination project (number of reused). In the example shown in the figure, “Project Z” (100 reused number) is listed first, and “Project W” (50 reused number) is listed second.

  Note that when “display project metrics” is selected on the menu screen, the interface unit 10 calls a project metrics measurement method of the metrics measurement unit 13. The metrics measuring unit 13 executes the called project metrics measuring method, and returns the project metrics information to the interface unit 10 as a result. The interface unit 10 that has received the result from the metric measurement unit 13 displays the project metrics display screen described above.

  FIGS. 9 to 14 show screens related to design information selection, editing, duplication, and deletion, and design information change influence range display.

  FIG. 9 is a schematic diagram showing a design information selection screen of the design information management apparatus 1. When “design information selection” is selected on the aforementioned menu screen, the interface unit 10 displays this design information selection screen.

  As shown in the figure, the design information selection screen displays the selected project identifier. The design information selection screen displays a list including a list of design information identifiers for the selected project. In the illustrated example, a list of design information identifiers such as “login function” and “login screen” is displayed. These design information identifiers are stored in the design information storage unit 22 in association with project identifiers. The interface unit 10 acquires a list of design information identifiers by calling a design information identifier list acquisition method of the information operation unit 11. The user can select one of the design information identifiers on the design information selection screen. When the user selects a design information identifier, the interface unit 10 stores the design information identifier as a selected design information identifier. At the same time, the interface unit 10 displays the identifier of the selected design information in the menu screen described above.

  FIG. 10 is a schematic diagram showing a design information editing screen of the design information management apparatus 1. When “design information editing” is selected on the aforementioned menu screen, the interface unit 10 displays this design information editing screen. The design information editing screen displays the selected project identifier and the selected design information identifier. The selected design information of the selected project is information to be edited on the design information editing screen.

The design information editing screen displays a list of attribute name / attribute value pairs included in the design information to be edited. In the example shown in the figure, the attribute value “user information management function” is displayed corresponding to the attribute name “description”, the attribute value “user information table” is displayed corresponding to the attribute name “data”, and The same applies to other attributes.
In addition, the design information editing screen has a design information update button. The user can edit the displayed design information (attribute value for the attribute name), and is stored in the design information storage unit 22 by the edited design information by pressing the design information update button. An instruction to update the design information can be given. When the user presses the design information rain true button, the interface unit 10 calls a design information update method of the information operation unit 11. The information operation unit 11 updates the design information stored in the design information storage unit 22 by executing a design information update method.

  FIG. 11 is a schematic diagram showing a design information duplication screen of the design information management apparatus 1. When “copy design information” is selected on the menu screen described above, the interface unit 10 displays this design information copy screen.

  The design information duplication screen displays the selected project identifier and the selected design information identifier. The selected design information of the selected project is design information to be a copy source. The design information duplication screen includes a duplication destination project identifier input field for designating a duplication destination project identifier, a design information identifier input field for designating the duplication destination design information identifier, and a design information duplication button. Have. The user can input the copy destination project identifier in the copy destination project identifier input field, input the design information identifier in the design information identifier input field, and press the design information copy button. When the user performs an operation of pressing the design information copy button, the interface unit 10 calls a design information copy method of the information operation unit 11. Then, the information operation unit 11 executes the design information duplication method to duplicate the design information.

  FIG. 12 is a schematic diagram showing a design information deletion screen of the design information management apparatus 1. When “deletion of design information” is selected on the menu screen described above, the interface unit 10 displays this design information deletion screen.

  The design information deletion screen displays the selected project identifier and the selected design information identifier. The selected design information of the selected project is design information to be deleted. The design information deletion screen has a design information deletion button. The user can press a design information deletion button on the design information deletion screen. When the user presses the design information deletion button, the interface unit 10 calls a design information deletion method of the information operation unit 11. Then, the information operation unit 11 executes a design information deletion method and deletes the selected design information. When the selected design information is deleted, the interface unit 10 clears the stored information on the selected design information identifier. Accordingly, the interface unit 10 updates the above-described menu screen to a state where the selected design information does not exist.

  FIG. 13 is a schematic diagram showing a design information change influence range display screen (No. 1) of the design information management apparatus 1. When the “design information change influence range display screen” is selected on the aforementioned menu screen, the interface unit 10 displays the design information change influence range display screen.

  The design information change influence range display screen displays information on the selected project identifier and information on the selected design information identifier. In the illustrated example, the selected project identifier is “Attendance system for company XX”. The selected design information identifier is “user management function”. The design information change influence range display screen displays a list of attribute name / attribute value pairs in the selected design information.

  The user can select one of the attribute names included in this list. When the user performs an operation of selecting an attribute name from the list, the interface unit 10 calls the design information change influence range detection method of the change influence detection unit 12. Then, the change influence detection unit 12 executes the design information change influence range detection method, and acquires information on the design information change influence range as a result. Then, the change influence detection unit 12 returns information on the design information change influence range to the interface unit 10. Then, the interface unit 10 displays the design information change influence range display screen on the design information change influence range information acquired from the change influence detection unit 12.

  FIG. 14 is a schematic diagram showing a design information change influence range display screen (No. 2) of the design information management apparatus 1. FIG. 14 shows a screen on which the interface unit 10 displays the design information change influence range information acquired from the change influence detection unit 12 after the user selects an attribute name while the screen shown in FIG. 13 is displayed. This is the screen. In the illustrated example, the change influence range when the selected attribute name is “description” is displayed. This design information change influence range display screen (No. 2) displays a list of design information included in the design information change influence range when the design information of the selected attribute name “description” is changed. The change influence range is a range that may be affected when the design information of the selected attribute name is changed. As shown in the figure, the change influence range is displayed as a list of pairs of project identifiers and design information identifiers. In the example shown in the figure, a pair of a project identifier “project X” and a design information identifier “user management function” or a project identifier “project Z” and a design information identifier “person in charge” is associated with the selected attribute name “description”. A pair with “Management Function” is displayed as a change influence range.

  In the above, it demonstrated based on the example of a screen structure which the interface part 10 displays. When the design information management apparatus 1 performs various processes for managing the design information, the user interface may be different from that described above.

  Next, with reference to FIGS. 15 to 40, more specific processing of the information operation unit 11, the project information storage unit 21, and the design information storage unit 22 among the units configuring the design information management apparatus 1. The contents will be described.

FIG. 15 is a schematic diagram showing specifications of the project information storage unit 21. In the drawing, row numbers are shown for convenience.
In the following, a string is a character string.
The first to third lines indicate the definition of the schema (data) related to the project information storage unit 21. The schema includes a Boolean type variable current and a string type variable id. These variables are variables that hold independent values for each project instance stored in the project information storage unit 21. The variable current represents whether the project is valid or invalid at that time. The variable value true represents “valid”, and the variable value false represents “invalid”. A variable id is a variable that holds a project identifier.

The fourth to eighth lines represent the definition of the method specifications that the project information storage unit 21 has. In the following description, the project information that is a parameter of the method insert and update is an object having a valid / invalid state (current) and a project identifier (id) as variables.
The project information storage unit 21 has insert, update, select, and find as methods. The parameter of the method insert is project information. The parameters of method update are search conditions and project information. The parameter of the method select is a search condition. The method select returns a cursor as a search result. A cursor is an object for sequentially accessing a plurality of entities (object-oriented instances or rows in a relational data model) included in search results. The parameter of the method find is a search condition.
The method “insert” is for inserting new project information into the project information storage unit 21. The method update is for updating the contents of the project information already stored in the project information storage unit 21. The methods “select” and “find” return the projects stored in the project information storage unit 21 that match the search condition specified as an argument. The method select returns a plurality of entities that match the search conditions, whereas the method find returns a single entity that matches the search conditions.

  The ninth to eleventh lines represent the definition of the cursor method specification. The cursor has hasNext and next as methods. Neither hasNext nor next has parameters. The method hasNext returns a Boolean value indicating whether the next entity still exists. When the value of hasNext is true, it means that there is still the next entity. When the value of hasNext is false, it means that there is no more next entity. The method next returns the next entity when the value of hasNext is true. When the method next is executed, the position indicated by the cursor moves to the next entity.

FIG. 16 is a schematic diagram showing specifications of the design information storage unit 22. In the drawing, row numbers are shown for convenience.
The first line through the eighth line show the definition of the schema related to the design information storage unit 22. The schema here is a string type variable id, a string type variable parentId, a Boolean type variable current, a string type variable projectId, a string type variable specId, and a set of pairs of strings and strings. Contains the content variable. The variable id stores an identifier. The variable parentId stores a parent identifier (parent information) of design information. The variable current represents whether the design information is valid or invalid. The value true corresponds to “valid”, and the value false corresponds to “invalid”. The variable projectId stores the project identifier of the design information. The variable specId stores a design information identifier of the design information. The variable contents stores the contents of design information. The content of this design information is a set of pairs (correspondences) of attribute names (strings) and attribute values (strings).

  The ninth to thirteenth lines represent the definition of the method specifications that the design information storage unit 22 has. The design information storage unit 22 has insert, update, select, and find as methods. Note that these methods have the same functions as the methods having the same names described with reference to FIG. 15 except that the project information storage unit 21 or the design information storage unit 22 is targeted. . Therefore, detailed description is omitted here.

  The 14th to 16th lines represent the definition of the cursor method specification. The cursor has hasNext and next as methods. Note that these methods have the same functions as the methods having the same names described with reference to FIG. 15 except that the project information storage unit 21 or the design information storage unit 22 is targeted. . Therefore, detailed description is omitted here.

FIG. 17 is a schematic diagram illustrating specifications of the information operation unit 11. In the drawing, row numbers are shown for convenience.
The figure (from the 1st line to the 12th line) shows the definition of the specification of the method which the information operation part 11 has. The information operation unit 11 includes, as methods, project creation, project identifier list acquisition, project duplication, project deletion, design information creation, design information identifier list acquisition, design information duplication, design information deletion, design information update, and get unique Id. Have.
Detailed contents and processing procedures of these methods will be described with reference to FIGS.

FIG. 18 is a schematic diagram for explaining a detailed processing procedure of the project creation method of the information operation unit 11. This figure shows the function of the project creation method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the project creation method has a project identifier as a parameter. The project identifier is a string type.
The contents of the processing procedure are described in the second to fifth lines.
In the second line, the object project (project information) is initialized.
In the third line, the value of the project identifier which is a parameter is substituted for the variable id of the object project.
On the fourth line, true is assigned to the variable current of the object project. This true is a value indicating that the project is valid.
Then, on the fourth line, the method “insert” in the project information storage unit 21 is called by specifying the object “project” as an argument.
With the above procedure, the project creation method of the information operation unit 11 creates information on a new project in the project information storage unit 21.

FIG. 19 is a schematic diagram for explaining a detailed processing procedure and the like of the project identifier list acquisition method of the information operation unit 11. This figure shows the function of the project identifier list acquisition method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the project identifier list acquisition method has no parameters.
The contents of the processing procedure are described from the second line to the eighth line.
In the second line, the method select of the project information storage unit 21 is called. At this time, “current = true” is specified as a search condition as an argument. That is, the information of all currently valid projects stored in the project information storage unit 21 is extracted. Then, the return value that is the result of the method select is assigned to the object cursor (cursor).
In the third line, a variable (object) result is initialized. That is, it is assumed that an empty list is stored in the variable result.

The fourth to seventh lines are a loop process repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, the process for each piece of project information extracted by the method select on the second line is performed.
On the fifth line, next, which is an element of the object cursor, is assigned to the object project. That is, one piece of unprocessed project information is assigned to the object project.
In the sixth line, the method add of the object result is called. At this time, id (project identifier) which is a variable of the object project is specified as an argument of the method add. By executing this method add, the id (project identifier) of the current project is added as an element to the list of the object result.
The seventh line indicates the end of the loop (while statement) from the fourth line.
On the eighth line, the project identifier list acquisition method returns an object result as a return value to the caller.
Through the above procedure, the project identifier list acquisition method of the information operation unit 11 acquires a list of project identifiers of all valid projects stored in the project information storage unit 21.

FIG. 20 is a schematic diagram for explaining a detailed processing procedure of the project duplication method of the information operation unit 11. The figure shows the function of the project duplication method using pseudo code. In the drawing, row numbers are shown for convenience.
As described from the first line to the second line, the project duplication method has a duplication source project identifier and a duplication destination project identifier as parameters. Each of the duplication source project identifier and the duplication destination project identifier is a string type.
The comments in the third to fourth lines indicate that the project duplication method duplicates all design information belonging to the duplication source project to the duplication destination project.
Lines 5 to 13 describe the contents of the processing procedure.
In the fifth to sixth lines, the method select of the design information storage unit 22 is called. At this time, “project id = replication source project identifier” and “current = true” are specified as search conditions that are arguments. That is, by calling this method select, all valid design information of the project corresponding to the duplication source project identifier that is a parameter of the project duplication method is extracted. Then, the return value that is the result of the method select is assigned to the object cursor (cursor).

The while statement from the seventh line to the thirteenth line describes a loop process that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. In other words, in this loop, processing is performed for each of all design information in the copy source project extracted by the method select on the fifth line.
On the 8th line, next, which is an element of the object cursor, is assigned to the object spec (design information). That is, one piece of unprocessed design information is assigned to the object spec.
From the ninth line to the twelfth line, the design information duplication method of the information operation unit 11 itself is called. At this time, the argument to be specified is as follows. That is, the project identifier of the copy source is projectId (project identifier) which is a variable of the above spec (design information). The design information identifier of the copy source is specId (design information identifier) that is also a variable of spec. The copy destination project identifier is the copy destination project identifier specified by the parameter. The design information identifier of the copy destination is specId which is a variable of spec, that is, the same design information identifier as that of the copy source. One of the design information is duplicated by calling the design information duplication method.
The 13th line indicates the end of the while statement starting from the 7th line.
Through the above procedure, the project duplication method of the information operation unit 11 duplicates all design information of a specific project stored in the design information storage unit 22 as design information of another project.

FIG. 21 is a schematic diagram for explaining a detailed processing procedure and the like of the project deletion method of the information operation unit 11. This figure shows the function of the project deletion method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the project deletion method has a project identifier as a parameter.
The comments from the second line to the third line indicate that the project deletion method deletes all design information belonging to the specified project and invalidates the information of the project.
The contents of the processing procedure are described from the 4th line to the 12th line.
In the fourth to fifth lines, the method select of the design information storage unit 22 is called. At this time, “project id = project identifier” and “current = true” are specified as search conditions that are arguments. That is, by calling this method select, all valid design information belonging to the project to be deleted is extracted. Then, the return value that is the result of the method select is assigned to the object cursor (cursor).

The while statement from the sixth line to the ninth line describes the processing of a loop that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, processing is performed for each piece of design information extracted by the method select in the fourth row.
On the seventh line, next, which is an element of the object cursor, is assigned to the object spec (design information). In other words, one unprocessed design information is assigned to the object spec in the while statement.
In the eighth line, the design information deletion method of the information operation unit 11 itself is called. At this time, the projectId (project identifier) and specId (design information identifier) stored in the object spec at that time are specified as arguments. By calling this design information deletion method, the design information specified by the object spec is deleted.
The ninth line indicates the end of the while statement starting from the sixth line.

In line 10, the method find of the project information storage unit 21 is called. At this time, “id = project identifier” is designated as a search condition. That is, the project information stored in the project information storage unit 21 and the information of the project that is currently being deleted is searched for. Then, project information which is a return value from the method find is substituted into the object project.
In the 11th line, false is assigned to the variable current of the object project. That is, the project information that is currently the deletion target is invalidated.
In line 12, the method update in the project information storage unit 21 is called. At this time, “id = project identifier” is designated as a search condition. That is, the project that is currently the deletion target is the update target. Also, an object project is specified as data to be updated. As described in the 11th line, false is stored in the variable current of the object project. That is, by calling this method update, the project to be deleted is invalidated in the project information stored in the project information storage unit 21.
With the above procedure, the project deletion method of the information operation unit 11 deletes all design information of a specific project stored in the design information storage unit 22. The project information stored in the project information storage unit 21 is invalidated.

FIG. 22 is a schematic diagram for explaining a detailed processing procedure and the like of the design information creation method of the information operation unit 11. This figure shows the function of the design information creation method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the design information creation method has a project identifier, a design information identifier, and contents as parameters.
The contents of the processing procedure are described from the second line to the ninth line.
In the second line, an object spec (design information) is initialized.
In the third line, a uniquely identifiable identifier is generated by calling the get unique ID method. The generated identifier is stored in the variable id of the object spec.
On the fourth line, the variable parentId (parent ID) of the object spec is set to null.
On the fifth line, the variable current of the object spec is set to true. That is, a value that this design information is valid is set.
In the sixth line, the value of the project identifier that is a parameter is substituted into the variable projectId (project identifier) of the object spec.
On the seventh line, the value of the design information identifier that is a parameter is substituted into the variable specId (design information identifier) of the object spec.
On the 8th line, the value of the content that is a parameter is assigned to the variable contents of the object spec.
The necessary values are stored in the object spec in the procedure described in the second to eighth lines.
Then, on the ninth line, the method insert of the design information storage unit 22 is called. At this time, the above object spec is specified as an argument. As a result, the design information set in the procedure from the second line to the eighth line is stored (inserted) in the design information storage unit 22 in the design information storage unit 22.
Through the above procedure, the design information creation method of the information operation unit 11 creates new design information in the design information storage unit 22.

FIG. 23 is a schematic diagram for explaining a detailed processing procedure and the like of the design information identifier list acquisition method of the information operation unit 11. This figure shows the function of the design information identifier list acquisition method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the design information identifier list acquisition method has a search condition as a parameter.
The contents of the processing procedure are described from the second line to the eighth line.
In the second line, the method select of the design information storage unit 22 is called. At this time, the search condition that is a parameter of the design information identifier list acquisition method is directly specified as an argument of the method select. Then, the return value from the method select is assigned to the object cursor (cursor).
In the third line, a variable (object) result is initialized. That is, it is assumed that an empty list is stored in the variable result. This result is a list (array) for sequentially adding design information identifiers in the loop processing from the fourth line to the seventh line below.

The while statement from the fourth line to the seventh line describes a loop process that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, processing is performed for each piece of design information extracted by the method select in the second row.
On the fifth line, next, which is an element of the object cursor, is assigned to the object spec (design information). That is, one piece of unprocessed design information is assigned to the object spec.
In the sixth line, the method add of the object result is called. At this time, specId (design information identifier) that is a variable of the object spec is specified as an argument of the method add. By executing this method add, the specId (design information identifier) of the current spec is added as an element to the list of the object result.
The seventh line indicates the end of the while statement starting from the fourth line.
On the eighth line, the design information identifier list acquisition method returns the object result as a return value to the caller.
Through the above procedure, the design information identifier list acquisition method of the information operation unit 11 acquires a list of design information identifiers of design information corresponding to the search conditions stored in the design information storage unit 22.

FIG. 24 is a schematic diagram for explaining a detailed processing procedure and the like of the design information duplication method of the information operation unit 11. This figure shows the function of the design information duplication method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first to second lines, the design information duplication method uses the duplication source project identifier, the duplication source design information identifier, the duplication destination project identifier, and the duplication destination design information identifier as parameters. Have.
The contents of the processing procedure are described from the third line to the twelfth line.
In the description from the third line to the fourth line, the method find of the design information storage unit 22 is called. The search conditions specified as arguments at this time are “projectId = replication source project identifier”, “specId = replication source design information identifier”, and “current = true”. The logical product of these three conditions is the search condition. That is, by executing this method find, design information which is design information specified by parameters (replication source project identifier and replication source design information identifier) and which is currently valid is found. The design information that is the result of the method find is substituted into the object spec (first design information).

In the fifth line, an object spec2 (second design information, an object for design information of a copy destination) is initialized.
In the sixth line, the uniquely identifiable identification information generated by the method get unique ID described above is assigned to the variable id of the object spec2.
In the seventh line, the value of the variable id of the object spec is assigned to the variable parentId of the object spec2. That is, the ID of the design information of the copy source is set as the parent ID in the design information of the copy destination. As described above, the variable parentId is used to represent a parent-child relationship between design information in replication or the like.
On the 8th line, true is assigned to the variable current of the object spec2. In other words, a value for validating spec2 is substituted.
On the ninth line, a copy destination project identifier that is a parameter of the design information copy method is substituted for the variable projectId of the object spec2.
In the 10th line, a replication destination design information identifier that is a parameter of the design information replication method is substituted into the variable specId of the object spec2.
In the 11th line, the value of the variable contents of the object spec (design information of the duplication source) is substituted into the variable contents of the object spec2. That is, the content of the design information of the object spec2 is made identical (duplicated) with the content of the design information of the object spec2.

As described above, in the processing from the fifth line to the eleventh line, a value is set in the object spec2 holding the design information of the duplication destination.
Then, on the 12th line, the method insert of the design information storage unit 22 is called. The argument specified at this time is the object spec2. That is, an object spec2 having values set in the fifth to eleventh lines is newly stored (inserted) in the design information storage unit 22.
Through the above procedure, the design information duplication method of the information operation unit 11 duplicates a piece of design information stored in the design information storage unit 22 and generates new design information in the design information storage unit 22. . At this time, parent-child relationship information is set between the design information of the copy source and the design information of the copy destination. Specifically, the ID of the design information of the copy source is stored in the variable parentId included in the design information of the copy destination.

FIG. 25 is a schematic diagram for explaining a detailed processing procedure and the like of the design information deletion method of the information operation unit 11. This figure shows the function of the design information deletion method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the design information deletion method has a project identifier and a design information identifier as parameters.
The contents of the processing procedure are described in the second to fifth lines.
In the description from the second line to the third line, the method find of the design information storage unit 22 is called. At this time, the search conditions specified as arguments are “projectId = project identifier”, “specId = design information identifier”, and “current = true”. The logical product of these three conditions is the search condition. That is, by executing this method find, design information that is design information specified by parameters (project identifier and design information identifier) and is currently valid is found. The design information that is the result of the method find is substituted into the object spec (design information).

In the fourth line, false is assigned to the variable current of the object spec. That is, a value indicating that the design information is invalid is set.
On the fifth line, the method update in the design information storage unit 22 is called. At this time, the search condition specified as an argument is “id = spec.id”. In other words, the design information found by the method find on the second line is an object to be updated by the method update. Further, the design information is updated by the value set in the object spec in the processing from the second line to the fourth line. That is, the value of the variable current of the design information is set to false. That is, the design information is invalidated. In this way, the designated design information is deleted (invalidated) in the design information storage unit 22.
With the above procedure, the design information deletion method of the information operation unit 11 deletes (invalidates) one piece of design information stored in the design information storage unit 22.

FIG. 26 is a schematic diagram for explaining a detailed processing procedure and the like of the design information update method of the information operation unit 11. This figure shows the function of the design information update method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the design information update method has a project identifier, a design information identifier, and contents as parameters.
The contents of the processing procedure are described from the second line to the thirteenth line.
In the description from the second line to the third line, the method find of the design information storage unit 22 is called. At this time, the search conditions specified as arguments are “projectId = project identifier”, “specId = design information identifier”, and “current = true”. The logical product of these three conditions is the search condition. That is, by executing this method find, design information that is design information specified by parameters (project identifier and design information identifier) and is currently valid is found. The design information that is the result of the method find is substituted into the object spec (first design information).
On the fourth line, false is assigned to the variable current of the object spec. That is, a value indicating that the content of the object spec is invalid is set.
In the fifth line, the update method of the design information storage unit 22 is called. At this time, “id = spec.id” is designated as the search condition. That is, the search condition read in the second row is set as an update target. The value of the object spec is used as the value to be updated. That is, the design information is invalidated. As a result, the design information before the update remains in the design information storage unit 22 in an invalid state (current = false).

In the processes from the sixth line to the thirteenth line, the updated design information is inserted into the design information storage unit 22.
In line 6, object spec2 (second design information) is initialized.
In the seventh line, the unique identification information generated by the get unique ID method is assigned to the variable id of the object spec2.
In the eighth line, the value of the variable id of the object spec (first design information) is substituted into the variable parentId of the object spec2. That is, when the design information is updated, the value of the variable parentId is set so that the design information before the update can be managed as a parent and the updated design information as a child.
In the ninth line, true is assigned to the variable current of the object spec2. That is, a value indicating that the object spec2 is valid is set.
In the 10th line, the value of the variable projectId of the object spec (first design information) is substituted into the variable projectId (project identifier) of the object spec2.
In the 11th line, the value of the variable specId of the object spec (first design information) is substituted into the variable specId (design information identifier) of the object spec2.
That is, the project identifier and design information identifier do not change before and after the update.
On the 12th line, the value of the content that is the parameter of the design information update method is substituted into the variable contents of the object spec2. That is, the contents of design information can be changed by this update.
As described above, in the processing from the sixth line to the twelfth line, a value is set in the object spec2.
Then, on the 13th line, the method insert of the design information storage unit 22 is called. At this time, the object spec2 is specified as an argument. That is, design information having the value of the object spec2 is newly inserted into the design information storage unit 22.
Through the above procedure, the design information update method of the information operation unit 11 updates the contents of a piece of design information stored in the design information storage unit 22. However, the design information before the update remains in the design information storage unit 22 in an invalid state (current = false). In addition, the ID of the design information before the update is stored in the parentId of the design information after the update. Thereby, the design information (parent) before update and the design information (child) after update are related as a parent-child relationship.

FIG. 27 is a schematic diagram for explaining a detailed processing procedure and the like of the method “get unique ID” of the information operation unit 11. This figure shows the function of the method “get unique ID” using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the method get unique ID has no parameters.
The second line defines the static variable id of the method. The value of the static variable is maintained even after the method processing ends. That is, when the method get unique ID is called, the value of the static variable id is updated by the process on the fifth line. The value of the updated static variable is maintained as it is, and when the method get unique ID is called next time, the value after the update in the previous process is held at the time of entry to the method. Note that the initial value of the static variable id is 0. That is, the value of the static variable id when the method get unique ID is first called is zero.
The comments from the third line to the fourth line indicate that the method get unique ID is a method that returns a different value each time. That is, since the method get unique ID returns a different value every time, this means that the value can be used as identification information for uniquely identifying design information, for example.
Lines 5 to 6 describe the contents of the processing procedure.
In the fifth line, the value of the static variable id is incremented (+1).
In the sixth line, the value of the static variable id at that time is returned as a return value from the method get unique ID.
Through the above procedure, the method “get unique ID” acquires a unique ID that can be used as identification information.

Next, a specific operation of the change influence detection unit 12 will be described.
28, 29, and 30 are schematic diagrams of change histories for explaining the process in which the change influence detection unit 12 detects the influence range by tracing the change history of the design information.

First, a history of design information in the illustrated example will be described with reference to FIG. In the figure, S1 to S15 correspond to each process in the design information history chain.
In S1 of FIG. 28, some design information is newly created.
And S1 was changed to S2. That is, S1 is a parent of S2, and S2 is a child of S1.
Next, S3 was generated by copying (duplicating) S2. That is, S2 is a parent of S3, and S3 is a child of S2.
Next, S3 was copied to project Z3, and S4 was generated. That is, S3 is a parent of S4, and S4 is a child of S3.
Next, S4 was changed within project Z3 to S5. That is, S4 is a parent of S5, and S5 is a child of S4.
On the other hand, S3 was branched. That is, S3 was changed within project Y to S6. That is, S3 is a parent of S6, and S6 is a child of S3.
Also, when project Y was copied and “project Y_copy” was generated, S6 was copied to S7. That is, S6 is a parent of S7, and S7 is a child of S6.
In “Project Y_Copy”, S7 is changed to S8. That is, S7 is a parent of S8, and S8 is a child of S7.
Further, in “Project Y_Copy”, S8 is further changed to S9. That is, S8 is a parent of S9, and S9 is a child of S8.
On the other hand, S8 is branched, copied to project Z1, and further modified twice, resulting in S10, S11, and S12 in these processes. Again, the parent-child relationship is maintained.
In addition, S10 was further branched, copied to project Z2, and further changed twice, resulting in S13, S14, and S15 in these processes. Again, the parent-child relationship is maintained.

  As described above, the history has a tree structure. That is, the design information of a child of certain design information can be zero, one, or a plurality. On the other hand, the design information of the parent of certain design information is zero or one. The design information of the parent of some design information is zero when the design information is newly created. In other words, the design information of the parent of certain design information is zero when the design information corresponds to the root node in the tree structure.

In the process of copying and changing, for the first time in S6, that is, when S6 is generated by changing S3, a specific description “XX” is generated in the design information. That is, there is a possibility that the children and grandchildren of S6 have inherited the description “XX”.
In S9, the person in charge of the project examined the correction of the description “XX”. The person in charge wanted to know the range of influence when "XX" was corrected.
In such a situation, the change influence detection unit 12 performs a process for detecting the influence range.

  FIG. 29 is a schematic diagram illustrating a progress situation in the middle of the process in which the change influence detection unit 12 detects the change influence while tracing the history. That is, in order to detect the influence range when the description “XX” in S9 is corrected, the change influence detection unit 12 performs a search in the parent direction from S9. Then, the change impact detection unit 12 detects that the design information in which the description “XX” first appears was S6, that is, the change impact detection unit 12 traces the history starting from S9, and S8, S7. , S6 detects that the description “XX” exists, but S3 that is the parent of S6 does not have the description “XX”, that is, the change impact detection unit 12 first detects the description “XX”. It is detected that the design information is S6.

  FIG. 30 is a schematic diagram illustrating a progress status of processing in which the change impact detection unit 12 further detects a change impact following the status of FIG. That is, since S6 is the first design information in which the description “XX” appears, the change impact detection unit 12 next searches for a history in the child direction starting from S6. Then, all the design information in which the description “XX” is not corrected or deleted is extracted in the search in the direction of the child. That is, in the illustrated history, the design information S6, S7, S8, S9, S10, S11, S12, S13, S14, and S15 are ranges in which there is a possibility of change.

The processing procedure of the change influence detection unit 12 is summarized as follows.
step 1: The change influence detection unit 12 first finds a specific attribute (a pair of attribute name and attribute value) of specific design information to be changed (S9 in the example of FIG. 30).
Step 2: Next, the change impact detection unit 12 follows the ancestor of the design information (that is, the direction of the parent, in other words, the copy source and the change source), and the attribute value of the specific attribute is the design information to be changed. The oldest design information that matches the attribute value is found (S6 in the example of FIG. 30).
Step 3: Collect all design information of descendants (duplication destination and change destination) of the oldest design information found in step 2.
step 4: The result collected in step 3 is set as the change influence range.

Next, more specific processing contents of the change influence detection unit 12 will be described with reference to FIGS. 31 to 34.
FIG. 31 is a schematic diagram illustrating the specification of the change influence detection unit 12. In the drawing, row numbers are shown for convenience.
The figure (from the 1st line to the 4th line) shows the definition of the specification of the method which the change influence detection part 12 has. The change influence detection unit 12 has change influence range detection, setting ancestor design information acquisition, and descendant acquisition as methods.
Detailed contents and processing procedures of each method will be described with reference to FIGS.

FIG. 32 is a schematic diagram for explaining a detailed processing procedure and the like of the change influence range detection method of the change influence detection unit 12. This figure shows the function of the change influence range detection method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the change influence range detection method has a design information identifier and an attribute name as parameters.
The contents of the processing procedure are described from the second line to the seventh line.
In the second line, the method find in the design information storage unit 22 is called. At this time, the search condition specified as an argument is “specId = design information identifier”. That is, it searches for design information having specId equal to the design information identifier that is a parameter of the change influence range detection method. The result returned from the method find is assigned to the object spec.
In the third line, a change ancestor design information acquisition method of the change influence detection unit 12 itself is called. At this time, the object spec and the attribute name that is a parameter of the change influence range detection method are specified as arguments. The setting ancestor design information acquisition method returns the design information of the oldest ancestor for the specified attribute name. Then, the design information returned from the set ancestor design information acquisition method is assigned to the object “ancestor”.
The comment on the fourth line indicates that the process on the third line is a process for searching for an ancestor with a target attribute value set.
In the fifth line, the change effect detection unit 12 itself calls a descendant acquisition method. At this time, the object “ancestor” acquired in the third process is designated as an argument. The list of descendant design information returned from the descendant acquisition method is assigned to the object “descendant list”.
The comment on the sixth line indicates that the process on the fifth line acquires a list of design information that is a descendant of the specified object “ancestor”.
On the second line, the descendant list obtained by the process on the fifth line is returned as a return value from the change influence range detection method.
By the above procedure, the change influence range detection method of the change influence detection unit 12 can acquire the influence range when the design information is changed as a list of design information.

FIG. 33 is a schematic diagram for explaining a detailed processing procedure and the like of the setting ancestor design information acquisition method of the change impact detection unit 12. This figure shows the function of the setting ancestor design information acquisition method using pseudo code. In the drawing, row numbers are shown for convenience.
This setting ancestor design information acquisition method is called from the change influence range detection method described above. The setting ancestor design information acquisition method recursively calls the setting ancestor design information acquisition method itself. The setting ancestor design information acquisition method searches for and acquires the oldest ancestor in which the contents of design information in a specific attribute are set.
As described in the first line, the setting ancestor design information acquisition method has design information and an attribute name as parameters.
The comments from the second line to the third line follow the design information history in the parent direction (the direction of the ancestor) as the processing outline of the setting ancestor design information acquisition method. It shows that different design information is returned. However, when there is no parent, the design information itself is returned.

The contents of the processing procedure are described from the 4th line to the 10th line.
The “if” statement on the fourth line is for determining whether or not a value other than null is stored in the variable parentId of the design information that is a parameter.
If the condition described in the fourth line is true, the processes from the fifth line to the ninth line are executed. If the condition described in the fourth line is false, the processes from the fifth line to the ninth line are not executed.
On the fifth line, the method find of the design information storage unit 22 is used to find the parent design information, and the obtained design information (parent design information) is substituted into the object parent.
The if statement on the sixth line is for determining whether or not the attribute value in the current design information is the same as the attribute value in the parent design information. When this condition is true (that is, when the attribute values are the same), the setting ancestor design information acquisition method is recursively called in order to search for an upper parent. The arguments specified at this time are the parent and the attribute name as a parameter. Then, a return value from the setting ancestor design information acquisition method that is recursively called is returned as a return value.
If the condition of the “if” statement on the sixth line is false, the process on the seventh line is not executed.
The ninth line is a right curly brace corresponding to the left curly brace of the fourth line, and indicates the end of the “if” sentence of the fourth line.
As the process on the 10th line, design information (design information as a parameter is returned as a return value. Note that the process on the 10th line is performed because the condition of the if statement on the 4th line is false. If there is, or if the condition of the “if” sentence on the sixth line is false.
Through the above procedure, the setting ancestor design information acquisition method of the change impact detection unit 12 acquires design information that is the oldest ancestor with a specific attribute value set.

FIG. 34 is a schematic diagram for explaining a detailed processing procedure and the like of the descendant acquisition method of the change influence detection unit 12. This figure shows the function of the descendant acquisition method using pseudo code. In the drawing, row numbers are shown for convenience.
This descendant acquisition method is called from the change influence range detection method described above. In addition, this descendant acquisition method recursively calls the descendant acquisition method itself. The descendant acquisition method adds design information to the descendant list while searching for descendants in the history.
As described in the first line, the descendant acquisition method has design information as a parameter.
The contents of the processing procedure are described from the second line to the ninth line.
In the second line, a variable (object) result is initialized. That is, it is assumed that an empty list is stored in the variable result.

In the third line, the method select of the design information storage unit 22 is called. At this time, the search condition specified as an argument is “parentId = design information.id”. That is, the design information is extracted by the method select so that the design information that is the parameter of the descendant acquisition method is the parent. That is, the design information of the child one generation lower than the design information specified as the parameter is extracted. Then, the return value from the method select is assigned to the object cursor.
The while statement from the fourth line to the eighth line describes a loop process that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, processing is performed for each of the child design information extracted by the method select in the third row.
On the fifth line, next, which is an element of the object cursor, is assigned to the object child. That is, one piece of unprocessed design information among the child design information extracted by the method select is assigned to the object child.
In the sixth line, the method add of the object result is called. At this time, the object child is specified as an argument. By executing this method add, the content of the object child is added as one element to the result, which is an object for storing the list of design information.
In line 7, the descendant acquisition method is called recursively. At this time, the object child is specified as an argument. The process on the seventh line is to search for design information of further descendants of the design information represented by the object child. Then, a return value (a list of design information of descendants below child) returned from the descendant acquisition method is added to the object result by the method add.
The eighth line indicates the end of the while statement from the fourth line.
In line 9, the object result is returned as the return value of the method.
Through the above procedure, the descendant acquisition method of the change impact detection unit 12 collects design information that is a descendant of the design information specified as a parameter, and returns a list of the design information. By calling this descendant acquisition method from the above-described change influence range detection method (FIG. 32), all design information corresponding to the descendants of a specific ancestor can be extracted.

Next, more specific processing contents of the metrics measurement unit 13 will be described with reference to FIGS.
FIG. 35 is a schematic diagram showing specifications of the metrics measuring unit 13. In the drawing, row numbers are shown for convenience.
The figure (from the 1st line to the 6th line) shows the definition of the specification of the method which the metrics measurement part 13 has. The metrics measurement unit 13 has metrics measurement, reuse design information acquisition, reused design information acquisition, get ancestor, and is descendant as methods.
Detailed contents and processing procedures of these methods will be described with reference to FIGS.

FIG. 36 is a schematic diagram for explaining a detailed processing procedure and the like of the metrics measurement method of the metrics measurement unit 13. This figure shows the function of the metrics measurement method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the metrics measurement method has a project identifier as a parameter.
The contents of the processing procedure are described from the second line to the twelfth line.
In the second line, the reuse design information list is initialized.
In the third line, the reuse design information list is initialized.

On the fourth line, the method select of the project information storage unit 21 is called. At this time, “current = true” is specified as an argument search condition. That is, the project information of a valid project is extracted by the method select. Then, the return value from the method select is assigned to the object cursor.
The while statement from the fifth line to the eleventh line describes a loop process that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, the process for each piece of project information extracted by the method select on the fourth line is performed.
On the sixth line, “next project” as an element of the object cursor is substituted for “other project” which is a variable (object). That is, one piece of unprocessed project information among the project information extracted by the method “select” is assigned to the object “other project”.
In the seventh to eighth lines, a reuse design information acquisition method that is a method of the metrics measurement unit 13 itself is called. At this time, a project identifier that is a parameter of the metrics measurement method and id (project information identifier) that is an element of the object “other project” are specified as arguments. The processing contents of the reuse design information acquisition method will be described later. Then, the return value returned from the reuse design information acquisition method is stored in the reuse design information list so as to be associated with the id of “other project”.
From the ninth line to the tenth line, a reusable design information acquisition method that is a method of the metrics measurement unit 13 itself is called. At this time, a project identifier that is a parameter of the metrics measurement method and id (project information identifier) that is an element of the object “other project” are specified as arguments. The processing contents of the reused design information acquisition method will be described later. Then, the return value returned from the reused design information acquisition method is stored in the reused design information list so as to be associated with the id of “other project”.
The eleventh line indicates the end of the while statement in the fifth line.

In the 12th line, the reuse design information list and the reuse design information list obtained by the processing of the above while statement are returned as return values of the metrics analysis method.
With the above procedure, for the specified project, design information reused from other projects (reuse design information list) and design information reused by other projects (reused design information list) ) And can be acquired.

FIG. 37 is a schematic diagram for explaining the detailed processing procedure of the reuse design information acquisition method possessed by the metrics measurement unit 13. This figure shows the function of the reuse design information acquisition method using pseudo code. In the drawing, row numbers are shown for convenience.
As described from the first line to the second line, the reuse design information acquisition method has its own project identifier and another project identifier as parameters. Both these parameters are of string type.
The contents of the processing procedure are described from the third line to the tenth line.

In the third line, a variable (object) result is initialized. That is, it is assumed that an empty list is stored in the variable result.
In the fourth to fifth lines, the method select of the design information storage unit 22 is called. At this time, the search conditions specified as arguments are “projectId = own project identifier” and “current = true”. The logical product of these two conditions is a search condition. That is, by this method select, only the design information which is the design information stored in the design information storage unit 22 and is valid for the own project is extracted. Then, the return value from the method select is assigned to the object cursor.

The while statement from the sixth line to the ninth line describes a loop process that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, processing is performed for each piece of design information extracted by the method select in the fourth row.
In the seventh line, next, which is an element of the object cursor, is assigned to the object spec. That is, one piece of unprocessed design information is assigned to the object spec.
In line 8, call the “is descendant” method. Details of the “is descendant” method will be described later. At this time, the other project identifier, which is a parameter of the reuse design information acquisition method, and the object spec are specified as arguments. Then, the if statement on the eighth line determines whether the return value returned from this is descendant method is true or false. If true, that is, if the design information represented by the object spec (design information in the own project) is reuse from the project specified by the other project identifier, the add method of the object result is called. That is, the design information (spec) is added to the result list. If the return value from the is descendant method is false, this result is not added to the list.
The ninth line indicates the end of the while statement from the sixth line.

On line 10, the object result is returned as a return value from this method.
Through the above procedure, the reuse design information acquisition method acquires a list of design information (design information in the own project) by reuse from a project specified by other project design information. Based on this, it is also possible to calculate statistics on design information reused from other projects.

FIG. 38 is a schematic diagram for explaining the detailed processing procedure of the reuse design information acquisition method possessed by the metrics measurement unit 13. This figure shows the function of the reuse design information acquisition method using pseudo code. In the drawing, row numbers are shown for convenience.
As described from the first line to the second line, the reusable design information acquisition method has its own project identifier and another project identifier as parameters. Both these parameters are of string type.
The contents of the processing procedure are described from the third line to the 111th line.

In the third line, a variable (object) result is initialized. That is, it is assumed that an empty list is stored in the variable result.
In the fourth to fifth lines, the method select of the design information storage unit 22 is called. At this time, the search conditions specified as arguments are “projectId = other project identifier” and “current = true”. The logical product of these two conditions is a search condition. That is, by this method select, only the design information that is the design information stored in the design information storage unit 22 and is valid for other projects is extracted. Then, the return value from the method select is assigned to the object cursor.

The while statement from the sixth line to the ninth line describes a loop process that is repeated while the next element remains in the object cursor. The variable hasNext of the object cursor has already been described. That is, in this loop, processing is performed for each piece of design information extracted by the method select in the fourth row.
In the seventh line, next, which is an element of the object cursor, is assigned to the object spec. That is, one piece of unprocessed design information is assigned to the object spec.
In line 8, call the “get ancestor” method. Details of the “get ancestor” method will be described later. At this time, the other project identifier, which is a parameter of the reuse design information acquisition method, and the object spec are specified as arguments. The if statement on the eighth line determines whether the return value returned from this get ancestor method is true or false. If true, that is, if the design information represented by the object spec is reused from the project specified by the local project identifier, the add method of the object result is called and the design information (spec) is returned to the result Add to the list of If the return value from the get ancestor method is false, this result is not added to the list.
The ninth line indicates the end of the while statement from the sixth line.

In line 10, the uniq method of object result is called. At this time, no argument is specified. As described in the comment on the 10th line, the uniq method performs a process of removing duplicate elements in the list (array) of the object result. In other words, as a result of executing the uniq method, each element of the object result list is unique.
On line 11, the object result is returned as a return value from this method.
Through the above procedure, the reused design information acquisition method acquires a list of design information in another project in which the design information included in the project specified by the project identifier is reused. In this list, as described above, duplicates are deleted. Based on this, it is also possible to calculate statistics on design information reused in other projects.

FIG. 39 is a schematic diagram for explaining a detailed processing procedure and the like of the “get ancestor” method possessed by the metrics measurement unit 13. The figure shows the function of the “get ancestor” method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the get ancestor method has a project identifier and design information as parameters.
As indicated by comments in the second to third lines, this get ancestor method returns design information of ancestors belonging to the project indicated by the project identifier as a parameter. If the project has no ancestor, the method returns null.
The contents of the processing procedure are described from the third line to the eleventh line.

The if statement on the fourth line determines whether or not the projectId (project identifier), which is an element of the design information specified by the parameter, is equal to the project specified by the parameter. If this is true (equal), the design information is returned as a return value, and the processing of this method is terminated. If this is false (if different), the process proceeds to the next fifth line.
The if statement on the fifth line determines whether or not parentId (ID of the parent design information), which is an element of the design information specified by the parameter, is null. When this is true (when the parent is null, that is, when there is no parent), false is returned as a return value, and the processing of this method is terminated. When this is false (when a parent ID other than null is stored, that is, when there is a parent), the process proceeds to the next sixth line.
In the sixth line, the method find of the design information storage unit 22 is called. At this time, “id = design information.parentId” specified as an argument. That is, the design information of the parent of the design information specified by the parameter is searched. Then, design information that is a return value from the method find is assigned to the object parent.
In line 7, call the get ancestor method recursively. At this time, the project identifier specified as a parameter and the above parent are specified as arguments. Then, the return value returned from the called get ancestor method is returned as a return value.
Through the above procedure, the get ancestor method acquires the ancestor belonging to the specified project of the specified design information.

FIG. 40 is a schematic diagram for explaining a detailed processing procedure and the like of the “is descendant” method that the metrics measurement unit 13 has. The figure shows the function of the “is descendant” method using pseudo code. In the drawing, row numbers are shown for convenience.
As described in the first line, the is descendant method has a project identifier and design information as parameters.
As the comments from the 2nd to 3rd lines indicate, this is descendant method is true if the ancestor of the design information specified by the parameter belongs to the project specified by the parameter. return. Otherwise, it returns false.
The third to eighth lines describe the contents of the processing procedure.

The if statement on the fourth line calls the get ancestor method. At that time, the project identifier and design information specified by the parameters are specified as arguments. When the return value returned from the get ancestor method is null, that is, when the ancestor of this design information does not exist in the project of the specified project identifier, the processing of the fifth line is false (false). Is returned as the return value of the is descendant method.
Control is passed to the else clause part of the sixth line when the result of the determination made in the fourth line is false. At this time, as the process on the sixth line, true is returned as the return value of the is descendant method.
With the above procedure, the is descendant method determines whether or not the designated design information is a descendant of the designated project, and returns a true / false value.

As described above, according to this embodiment, regarding design information duplication (reuse) and design information change, previous and subsequent design information is regarded as a parent-child relationship, and history information is retained. Therefore, design information can be managed based on the history of duplication and change.
In addition, when a certain design information is changed, by tracing the history information, it is possible to efficiently detect the range of influence of the change on other design information (in the own project and other projects).
In addition, various metrics can be measured regarding the reuse of design information and the like. This makes it possible to quantitatively evaluate the improvement in productivity due to the reuse of design information.

  In the above embodiment, the design information management apparatus 1 has the change influence detection unit 12, but the design information management apparatus 1 may not have the change influence detection unit 12. Even in this case, the design information management apparatus 1 can hold and analyze design information duplication history and change history information. In addition, the metrics related to the reuse of design information can be measured by the metrics measuring unit 13.

  In the above embodiment, the design information management apparatus 1 has the metrics measurement unit 13. However, the design information management apparatus 1 may not have the metrics measurement unit 13. Even in this case, the design information management apparatus 1 can hold and analyze design information duplication history and change history information. Further, when the change influence detection unit 12 exists, by following the parent-child relationship, it is possible to detect a range affected by the change when the contents of certain design information are changed.

  In the above embodiment, in order to express the parent-child relationship between the design information as data, the identification information of the parent design information is held in the design information on the child side. It is. For example, conversely, identification information of child design information may be held on the parent side. Further, the parent-child relationship between the design information may be held by other data expressions.

  In the above embodiment, the metrics include the amount of reuse of design information from other projects (number of cases, etc.), the amount of reuse of design information from own projects (number of cases, etc.), and the own project by other projects. The amount of design information reused (number of cases, etc.) was measured. In addition, for example, a ratio of the number of reused design elements to the total number of design elements (design information) may be calculated as metrics. Further, as a metric, for example, a ratio of the number of attributes that does not change at the time of reuse to the total number of attributes among the reused design elements may be calculated. Further, as a metric, a difference between the date and time when the reused design element was originally created and the date and time when the reused design element was reused (the length of the date and time difference) may be calculated. Further, the number of projects that reuse design information of a certain project may be calculated as metrics. Further, as a metric, the maximum value of the lifetime of reuse for all design elements may be calculated. By these, development productivity can be evaluated.

  According to at least one embodiment described above, when the information operation unit updates the design information, the design information before and after the change is stored in the design information storage unit, and the design information before and after the change is stored. The parent information is set with the parent-child relationship. Thereby, the change history of design information can be traced. When the information operation unit replicates design information, the design information of the replication source and the replication destination is stored in the design information storage unit, and the design information of the replication source and the replication destination is set as a parent-child relationship, and the parent information is set. . Thereby, the history of reuse of design information can be traced.

  Note that at least some of the functions of the design information management apparatus in the above-described embodiment may be realized by a computer. In that case, the program for realizing the function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer-readable recording medium” refers to a storage device such as a flexible disk, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, a “computer-readable recording medium” dynamically holds a program for a short time, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory inside a computer system that serves as a server or a client in that case may be included and a program held for a certain period of time. The program may be a program for realizing a part of the above-described functions, or may be a program that can realize the above-described functions in combination with a program already recorded in a computer system.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 1 ... Design information management apparatus, 10 ... Interface part, 11 ... Information operation part, 12 ... Change influence detection part, 13 ... Metric measurement part, 21 ... Project information storage part, 22 ... Design information storage part, 30 ... Terminal device

Claims (4)

A project information storage unit for storing project information including a project identifier for identifying a project;
The project identifier, a design information identifier for identifying design information in the project, parent information for specifying the parent when there is design information of a parent that is a copy source or a change source, and design information A design information storage unit that stores design information including current state information that indicates whether is valid or invalid, and content information that represents design content;
A function to create, update, or delete the project information and the design information. When the design information is updated, the current state information about the design information before the change is invalidated and changed. Create the design information after, set the parent information in the design information after the change to point to the design information before the change, and if the design information is copied, create the design information of the copy destination An information operation unit configured to copy the content information of the design information of the copy source to the design information of the copy destination and set the parent information in the design information of the copy destination to indicate the design information of the copy source;
Design information management device comprising: Starting from the designated design information, the design information in the direction from the origin to the parent is sequentially traced based on the parent information of the design information, and the oldest parent in which the content information of the design information of the origin exists is specified. If the content information of the design information of the starting point is changed by sequentially following the design information of the direction of the child based on the parent information of the design information from the identified oldest parent, there is a possibility of being affected Change impact detection unit for detecting a certain range,
The design information management apparatus according to claim 1, further comprising: Based on the parent information possessed by the design information, for the designated designated project, the first statistical information which is statistics regarding the number of times the designated project has reused design information of other projects, and the designated project is the designated A metric measuring unit that calculates second statistical information that is the number of reuses of design information of the project itself and third statistical information that is statistics of the number of reuses of design information of the designated project by other projects ,
The design information management device according to claim 1, further comprising: Computer
A project information storage unit for storing project information including a project identifier for identifying the project;
The project identifier, a design information identifier for identifying design information in the project, parent information for specifying the parent when there is design information of a parent that is a copy source or a change source, and design information A design information storage unit that stores design information including current state information that indicates whether or not is valid and content information that represents design content;
A function to create, update, or delete the project information and the design information. When the design information is updated, the current state information about the design information before the change is invalidated and changed. Create the design information after, set the parent information in the design information after the change to point to the design information before the change, and if the design information is copied, create the design information of the copy destination An information operation unit configured to copy the content information of the design information of the copy source to the design information of the copy destination and set the parent information in the design information of the copy destination to indicate the design information of the copy source;
Program to function as.

Images