JP7406012B2 - Design product management system and design product management method - Google Patents

Description

The present invention relates to a design product management system and a design product management method for managing design information products.

An MBSE (Model-Based Systems Engineering) method for designing a system using a modeling language has been proposed. By expressing considerations during requirements analysis and architecture design in a model, it becomes easier to visually understand the content and relationships between deliverables compared to traditional document-based deliverables. This is said to have the advantage of making it easier to share information among related parties.

In system design using models, design proceeds by defining requirements, functional components, physical components, etc. as elements, and also defining relationship information between the elements. Therefore, elements that are currently being designed and elements that have been designed may coexist within one system model.

Additionally, system design may be performed multiple times to reflect changes in requirements and feedback from hardware and software design, and even a system model that has been designed once may be subject to changes. Sometimes.

On the other hand, in system design, it is important to understand information that is reflected in subsequent processes such as detailed software design, source code, and hardware circuit design drawings, and information that has been reflected in subsequent processes in order to manage a development project.

For this reason, it is necessary to extract only the information for which the design has been completed from the system model, perform version control, and manage it reliably.

An example of a system for managing design information is ALM (Application Lifecycle Management), which is suitable for managing only the information for which the above design has been completed.

In the technology described in Patent Document 1, it is assumed that two designers are designing in parallel, and when it is determined that both designers have completed their designs, the design information files of both designers are transferred to the main server. It has been realized that it can be transmitted and stored.

Japanese Patent Application Publication No. 05-174079

However, in order to separately manage only the portion of one piece of design information for which the design has been completed, it is necessary to specify the elements for which the design has been completed from the design information. In addition, in system models, packages may be created that correspond to design units and elements may be grouped together, but since there are elements that are used in multiple design units, the design units and element groups may differ. be.

Therefore, if only the elements to be stored in the designed package are separately stored, there is a risk that part of the design information will be missing.

The technique described in Patent Document 1 does not take the above matters into consideration, and it is difficult to improve the reliability of management of design contents.

An object of the present invention is to realize a design product management system and a design product management method that can identify elements whose design has been completed from design information, store them separately, and improve the reliability of management of design contents. That's true.

In order to solve the above problems, the present invention is configured as follows.

A design product management system that manages products of a design system that is designed by combining a plurality of elements and dividing them into a plurality of groups, wherein the plurality of elements necessary for designing the design system are stored in design information. a first storage unit that stores design information in each of the plurality of groups, a modeling tool that performs design work for each of the plurality of groups according to a design instruction, and the elements of the group whose design work has been completed by the modeling tool among the plurality of groups; a first control unit that adds information indicating design completion to the elements necessary for the group to which the design work has been completed; The present invention includes a second storage section that stores the elements necessary for the completed group, and a second control section that causes the second storage section to store the group to which information indicating the completion of the design has been added.

A design product management method for managing products of a design system designed by combining a plurality of elements and dividing them into a plurality of groups, wherein the plurality of elements necessary for designing the design system are managed as design information. and perform design work for each of the plurality of groups in accordance with design instructions, and store the elements of the group of the plurality of groups for which the design work has been completed and the elements for which the design work has been completed. Information indicating design completion is added to the elements necessary for the group, and the elements of the group to which the information indicating design completion is attached and the elements necessary for the group for which the design work has been completed are added to the second element. Store in the storage unit.

According to the present invention, it is possible to realize a design product management system and a design product management method that can identify elements whose design has been completed from design information, store them separately, and improve the reliability of management of design contents. be able to.

1 is a schematic configuration diagram of a design product management system according to a first embodiment of the present invention. It is a diagram showing an example of design information stored in a design information DB. FIG. 3 is a diagram showing an example of a data structure for managing elements as part of design information. FIG. 3 is a diagram showing an example of a data structure for managing connection information as part of design information. FIG. 3 is a diagram showing an example of a data structure for managing diagrams as part of design information. FIG. 2 is a functional configuration diagram showing a design completion element state change program and a design completion element synchronization program. 12 is a flowchart showing the processing flow of a design completion element state change program and a design completion element synchronization program. 12 is a flowchart showing a detailed process flow of a design completed element state change unit. 9 is a diagram illustrating an example of design information data after the state is changed by the process of FIG. 8. FIG. 7 is a flowchart showing a detailed process flow of a state change detection unit. FIG. 3 is a diagram illustrating an example of a data structure of product information for managing elements stored in a product management DB. FIG. 7 is a functional configuration diagram of a design completion element state change program and a design completion element synchronization program in Example 2. FIG. 12 is a flowchart showing the processing flow of a design completion element state change program and a design completion element synchronization program according to the second embodiment. FIG. 3 is a diagram illustrating an example of product information data created by a product management design information generation unit.

Embodiments of the present invention will be described below with reference to the accompanying drawings. Note that although the attached drawings show specific embodiments in accordance with the principles of the present invention, they are for the purpose of understanding the present invention, and should not be used to limit the interpretation of the present invention in any way. isn't it. Further, common components in each figure are given the same reference numerals.

(Example 1)
FIG. 1 is a schematic configuration diagram of a design product management system 100 according to a first embodiment of the present invention.

In FIG. 1, a design product management system 100 includes a server 101 and a design computer 102, which are connected via a network 103. A plurality of design computers 102 may be provided in order for a plurality of people to carry out the design. The example shown in FIG. 1 is an example in which a plurality of design computers 102 are provided.

The server 101 includes a server CPU 110, a server RAM 111, a design information DB 112 (first storage), a server ROM 113, and a product management DB 114 (second storage). The design information DB 112 and the product management DB 114 may be constructed in one auxiliary storage device. A design completion element synchronization program 115 (second control unit) is stored in the server ROM 113, and the server 101 executes the processing specified by the design completion element synchronization program 115 while using the server RAM 111 as a temporary storage device. , is executed using the server CPU 110.

The design computer 102 includes a CPU 120, a RAM 121, a hard disk 122, a ROM 123, an input device 124, and a display device 125. A design completion element state change program 126 (first control unit) and a modeling tool 127 are stored in the ROM 123, and these are executed using the CPU 120 and RAM 121 of the design computer 102.

The design information is stored in the design information DB 112 of the server 101, and the user uses the input device 124 and display device 125 of the design computer 102 to temporarily copy the design information to the hard disk 122, and uses the modeling tool 127. carry out design work. The modeling tool 127 performs design work for each of a plurality of groups, which will be described later, according to design instructions from the user.

When the design information is updated through the design work and the design is completed, the user can use the input device 124 to instruct execution of the design completion element state change program 126 and specify the design completion range of the design information.

The design completion element state change program 126 adds information indicating "design completion" to the part of the design information related to the above design completion range, and transfers the design information to the design information DB 112 of the server 101. At the timing when the transfer is completed, the design completion element synchronization program 115 is executed, and of the design information stored in the design information DB 112, only the portion to which information indicating "design completion" has been added is registered in the deliverable management DB 114. .

FIG. 2 is a diagram showing an example of design information stored in the design information DB 112. In system design using models, functional components, physical components, etc. are defined as elements, and relationships between the elements are defined. Elements are grouped by folders or packages, such as design units.

The package "Function A" 200 stores a diagram "Function A architecture" 210 and functional components 211 (AC current detection) and 212 (current control) defined to realize the function A. The package "Function B" 201 stores a functional component 220 (DC current detection) defined to realize Function B. The package "physical architecture" 202 stores a physical component 230 (AC current sensor) to which functional components are assigned.

The diagram "Function A architecture" 210 displays functional components 211 and 212, a physical component 230 that realizes the functional components, and connection information 240 and 241 between the elements. Like physical component 230, the element has features that can be utilized in other package diagrams. Due to this feature, when the design of function A is completed, it is not possible to simply register the elements included in the package "function A" 200 in the deliverable management DB 114. Can not do it.

Therefore, in the first embodiment of the present invention, the element 230 related to the package "Function A" 200 and used in the diagram "Function A architecture" 210 is also registered in the artifact management DB 114.

In order to explain the processing in the first embodiment of the present invention, an example of a data structure for managing the design information shown in FIG. 2 in the design information DB 112 of the server 101 or the hard disk 122 of the design computer 102 is shown in FIG. Shown in Figure 5.

FIG. 3 is a diagram showing an example of a data structure for managing elements as part of design information. In the table 300, for each element, an ID, a name, a package in which the element is stored, a design state, and an update date and time are registered. In addition to the above, supplementary explanations of the elements may also be included. In the example shown in FIG. 3, information on functional components 211, 212, 220, and physical component 230 is recorded.

FIG. 4 is a diagram showing an example of a data structure for managing connection information as part of design information. In the table 400, for each connection information, a connection ID, an ID of an element that is a connection source, an ID of an element that is a connection destination, and an update date and time are registered. In addition to the above, the package containing the connection information, the design state, the type of connection, etc. may also be included. In the example shown in FIG. 4, connection information 240 and 241 are recorded.

FIG. 5 is a diagram showing an example of a data structure for managing diagram information as part of design information. In the table 500, for each diagram, an ID, a name, a package in which the diagram is stored, an ID list of elements to be displayed in the diagram, and an update date and time are registered. In addition to the above, supplementary explanations for figures, ID lists of connection information to be displayed in figures, display methods such as size and color, etc. may also be included. In FIG. 5, information in the diagram "Function A Architecture" 210 is recorded.

FIG. 6 is a functional configuration diagram showing the design completion element state change program 126 and the design completion element synchronization program 115. The design completion target designation unit 601 and the design completion element state change unit 603 correspond to the design completion element state change program 126, and the first model transfer unit 604, state change detection unit 605, and model registration unit 606 correspond to the design completion element state change program 126. , corresponds to the design completion element synchronization program 115.

The design completion target designation unit 601 receives as input a design completion target 602 designated by the user of the design product management system 100. Examples of design completion targets 602 include one or more of the packages of FIG. 2 . The design completion element state change unit 603 tracks elements related to the design completion target 602 from the design information 600 designed by the user, and changes the design state of the tracked elements to "design completion".

In other words, the design completion element state change unit 603 specifies the elements necessary for the design completion target 602 using the connection information 240 and 241 between the elements in the "Function A architecture" 210 shown in FIG. The design status of is set to "Design Completed".
Then, the design completed element state change unit 603 stores information on the elements that are “design completed” in the hard disk 122. Then, the design information is sent from the design completion element state change unit 603 to the first model transfer unit 604.

The first model transfer unit 604 transfers all the design information stored in the hard disk 122 to the design information DB 112. The state change detection unit 605 detects elements in a specific state, for example, "design completed" from among the design information stored in the design information DB 112. In addition to the specific state, it is also possible to compare the product information stored in the product management DB 114 and the elements detected from the design information DB 112 to detect elements with changes.

The model registration unit 606 extracts the elements detected by the state change detection unit 605 from the design information DB 112 and registers them in the product management DB 114.

The above operation allows the product management DB 114 to manage only the design information for which the design has been completed.

FIG. 7 is a flowchart showing the processing flow of the design completion element state change program 126 and the design completion element synchronization program 115. Steps S70 and S71 are processes of the design completion element state change program 126, and steps S72 and S73 are processes of the design completion element synchronization program 115.

After starting the process, in step S70, the design completion target designation unit 601 receives an input of the design completion target 602 from the user (design completion target designation reception). When a design completion target 602 is input, the design completion target designation unit 601 converts it into design completion target information. An example is a list of names of packages whose designs have been completed.

Next, in step S71, the design completion element state change unit 603 receives the design information 600 and the design completion target information as input, and changes the design state of the element related to the design completion target information in the design information 600 to " Update to "Design Completed" (change status of elements included in completion target from design information).

Next, in step S72, the first model transfer unit 604 transfers the design information 600 updated by the design completed element state change unit 603 to the design information DB 112 (transfers the design information to the design information DB 112).

Next, in step S73, the status change detection unit 605 extracts elements whose status is "design completed" from among the elements of the design information 600 stored in the design information DB 112. It is also possible to detect a difference between the extracted element and the product information stored in the product management DB 114, and input a list of the elements in which the difference has been detected to the model registration unit 606. The model registration unit 606 registers design information whose design has been completed from the design information DB 112 to the product management DB 114 according to the input list (registers only design completed elements and changes to the product management DB 114). This completes the process.

The processing of the design completion element state change program 126 and the design completion element synchronization program 115 will be described in detail, taking as an example a case where the user specifies the package "Function A" 200 as the design completion target 602.

FIG. 8 is a flowchart showing the detailed process flow of step S71, which is the process of the design completed element state changing unit 603. In step S80, the package "Function A" 200 specified by the user is searched from the table 500 for managing diagram information shown in FIG. 5, and the diagram ID "D1" is extracted. The processing from step S81 onwards is executed for each diagram ID.

In step S81 for the diagram ID "D1", an element list {E1, E2, E4} to be displayed with the diagram ID "D1" is extracted from the table 500. The process of step S82 is executed for each element ID. In step S82 for the element ID "E1", the design state of the element ID "E1" in the table 300 for managing elements shown in FIG. 3 is changed to "design completed". Similar processing is performed for element IDs “E2” and “E4”.

Through the above processing, the state of the element used in the design completion target 602 input by the user can be changed.

FIG. 9 is a diagram showing an example of design information data after the state is changed by the process shown in FIG. 8. The design state of the element used in the diagram "Function A architecture" 210 included in the design completion target 602 is changed to "design complete", and the design information table 300 before the state change is changed to the design information table 900 after the state change. Updated. Thereafter, the design information table 900 stored as temporary data in the hard disk 122 of the design computer 102 is transferred to the design information DB 112 by the model transfer unit 604.

FIG. 10 is a flowchart showing the detailed process flow of step S73, which is the process of the state change detection unit 605. In step S100, element IDs whose status is "design completed" in the design information table 900 shown in FIG. 9 are extracted, and an element ID list such as {E1, E2, E4} is generated. The processes after step S101 are executed for each element ID.

In step S101, it is determined whether the selected element ID is already stored in the product information stored in the product management DB 114. If the selected element ID does not exist in the product information, step S103 is executed. In step S103, the selected element ID is added to the element ID list to be registered in the design product DB 114. Thereafter, the process moves to the next element ID.

In step S101, if the selected element ID is already stored in the product management DB 114, the process advances to step S102. In step S102, the update date and time of the elements stored in the design information DB 112 and the update date and time of the elements stored in the deliverable management DB 114 are compared to determine whether the design information has been updated. In addition to the update date and time, updates may be determined by detecting changes in name or content.

If it is determined in step S102 that the design information has not been updated, the process proceeds to the next element ID without executing the process in step S103. In step S102, if the design information has been updated, the process advances to step S103 and "add to element ID list to be registered" is executed. Thereafter, the process moves to the next element ID.

By performing the above process for all element IDs in the design completed state, it becomes possible to separately record only the elements whose state is "design completed".

FIG. 11 is a diagram showing an example of the data structure of product information for managing elements stored in the product management DB 114. Element IDs {“E1”, “E2”} are registered in the product information table 1100 before the design completion element synchronization program 115 is executed. Here, if the element ID list for which design has been completed is {"E1", "E2", "E4"}, the element IDs {"E1", "E2"} already exist in the deliverable information table 1100. Therefore, step S102 shown in FIG. 10 is executed. If the design information of element ID "E1" has been updated, step S103 shown in FIG. 10 is executed.

Therefore, the information 1111 of the element ID "E1" in the updated product information table 1101 is overwritten.

If the design information for the element ID "E2" has not been updated, step S103 shown in FIG. 10 is not executed, and therefore the information 1112 for the element ID "E2" in the product information table 1101 is also not updated.

Since the element ID "E4" does not exist in the product information table 1100, step S103 shown in FIG. 10 is executed, and information 1113 of the element ID "E4" is newly registered. Similarly, diagram information and connection information may also be managed by the product management DB 114.

As described above, only the information on which the design has been completed can be extracted from among the design information in the modeling tool and managed in the product management DB 114.

According to Embodiment 1 of the present invention, a design product management system and design product management are capable of identifying elements whose design has been completed from design information, storing them separately, and improving the reliability of management of design contents. method can be realized.

Furthermore, it is possible to secure traces of deliverables from other processes such as the software design process, hardware design process, and test process, as well as system design information for which the design has been completed, and also manage versions of the deliverables. Therefore, the contents of the design can be managed with high reliability. Although the first embodiment takes system design as an example, the present invention can also be applied to software design and hardware design using models.

(Example 2)
Next, Example 2 of the present invention will be described.

The configuration of the design product management system 100 in the first embodiment is the same as that in the second embodiment, so illustration and detailed description will be omitted.

FIG. 12 is a functional configuration diagram of the design completion element state change program 126 and the design completion element synchronization program 115 in the second embodiment. The product management design information generation unit 1201 and the second model transfer unit 604A correspond to the design completion element synchronization program 115. The functional configuration diagram shown in FIG. 12 corresponds to the functional configuration diagram shown in FIG. 6 in the first embodiment. In the second embodiment, the state change detection unit 605 in the first embodiment is omitted, and a product management design information generation unit 1201 is added. The design completion element synchronization program 115 can handle both design information and product management information using only the product management design information generation unit 1201.

The product management information generation unit 1201 extracts the “design complete” element from the design information output by the design completion element state change unit 603 and generates product information to be transferred to the product management DB 114.

FIG. 13 is a flowchart showing the processing flow of the design completion element state change program 126 and the design completion element synchronization program 115 of the second embodiment. Steps S70, S71, and S72 are similar to steps S70, S71, and S72 shown in FIG. 7 in the first embodiment.

Step S131 is a process of the artifact management information generation unit 1201, and step S132 is a process of the second model transfer unit 604A. In step 131, the deliverable management design information generation unit 1201 selects elements of the design information 600 changed by the design completion element change unit 603 that have a specific state, for example, “design completion”. By detecting and copying existing elements, new product information to be registered in the product management DB 114 is created.

Furthermore, in addition to the specific state, elements that have been changed by comparing the product information stored in the product management DB 114 with the design information may also be included in the newly created product information. The product management information generation unit 1201 inputs the created product information to the second model transfer unit 604A. Next, in step 132, the model transfer unit 604A transfers the input product information to the product management DB 114. This completes the process.

FIG. 14 is a diagram showing an example of product information data created by the product management design information generation unit 1201. When the design information table 900 is input to the design information generation unit 1201 for product management, a product information table 1400 is generated that copies only the elements whose design status is "design completed" and transfers them to the product management DB 114. Ru. That is, the information of the element IDs E1, E2, and E4 whose design status is design completed in the design information table 900 is copied, and the product information table 1400 is generated.

As described above, only information on completed designs can be extracted from the design information and managed in the product management DB 114.

In the second embodiment of the present invention, the same effects as in the first embodiment can be obtained.

100... Design product management system, 101... Server, 102... Design computer, 103... Network, 110... Server CPU, 111... Server RAM, 112... Design information DB (first storage unit), 113... Server ROM, 114... Deliverable management DB (second storage unit), 115... Design completion element synchronization program (second control unit), 120 ... CPU, 121 ... RAM, 122 ... Hard disk, 123 ... ROM, 124 ... Input device, 125 ... Display device, 126 ... Design completion element state change program (first control unit), 127... Modeling tool, 200... Package "Function A", 201... Package "Function B", 202... Package "Physical Architecture", 210... Diagram "Function A Architecture" ", 211, 212, 220... Functional component, 230... Physical component, 240, 241... Connection information, 300, 400, 500... Table, 600... Design information, 601... Design completion target designation unit, 602... Design completion target, 603... Design completion element state change unit, 604... First model transfer unit, 604A... Second model transfer unit, 605... Status Change detection unit, 606...Model registration unit, 900...Design information table, 1100, 1101, 1400...Delivery information table, 1201...Design information generation unit for product management

Claims (9)

A design product management system that manages products of a design system designed by combining multiple elements and dividing them into multiple groups,
a first storage unit that stores the plurality of elements necessary for designing the design system as design information;
a modeling tool that performs design work for each of the plurality of groups according to design instructions;
A first control unit that provides information indicating design completion to the elements of the group for which the design work has been completed by the modeling tool among the plurality of groups and the elements necessary for the group for which the design work has been completed. and,
a second storage unit that stores the elements of the group to which information indicating the design completion has been added and the elements necessary for the group for which the design work has been completed;
a second control unit that causes the second storage unit to store the group to which information indicating the completion of the design has been added;
A design artifact management system comprising: The design product management system according to claim 1,
The plurality of groups have groups having connection information between the elements, and the first control unit uses the connection information to identify the elements necessary for the group for which the design work has been completed. A design product management system featuring: The design product management system according to claim 1,
If the element to which the information indicating the design completion is attached is stored in the second storage unit, the second control unit determines whether the element to which the information indicating the design completion is attached has been updated. A design product characterized in that it is determined whether or not the design has been completed, and if the element has been updated, the element stored in the second storage unit is updated to the element to which information indicating the completion of the design has been added. management system. The design product management system according to claim 1,
The second control unit includes a first model transfer unit, a model registration unit, and a state change detection unit,
The first model transfer unit transfers the design information stored in the first storage unit, the elements of the group for which the design work has been completed, and the elements necessary for the group for which the design work has been completed. , stored in the first storage unit,
The state change detection unit detects the element of the group for which the design work has been completed and the element necessary for the group for which the design work has been completed, which is stored in the first storage unit,
The model registration unit stores, in the second storage unit, the elements of the group for which the design work has been completed, detected by the state change detection unit, and the elements necessary for the group for which the design work has been completed. A design product management system characterized by: The design product management system according to claim 1,
The second control unit includes a product management design information generation unit and a second model transfer unit,
The design information generation unit for product management generates the elements of the group for which the design work has been completed, to which information indicating the design completion has been assigned by the first control unit, and the elements necessary for the group for which the design work has been completed. transferring the element to the second model transfer unit;
The second model transfer unit transmits the elements of the group to which the design work has been completed and the elements of the group to which the design work has been completed to which the information indicating the design completion transferred from the product management design information generation unit has been attached. A design product management system characterized in that the elements necessary for a group are stored in the second storage unit. A design product management method for managing products of a design system designed by combining multiple elements and dividing them into multiple groups, the method comprising:
storing the plurality of elements necessary for designing the design system as design information in a first storage unit;
performing design work for each of the plurality of groups in accordance with design instructions;
Adding information indicating design completion to the elements of the group for which the design work has been completed and the elements necessary for the group for which the design work has been completed among the plurality of groups;
A design product management method comprising: storing in a second storage unit the elements of the group to which information indicating the design completion has been added and the elements necessary for the group for which the design work has been completed. In the design product management method according to claim 6,
The plurality of groups include a group having connection information between the elements, and the connection information is used to identify the elements necessary for the group for which the design work has been completed. Management method. In the design product management method according to claim 6,
If the element to which the information indicating the design completion is attached has already been stored, it is determined whether the element to which the information indicating the design completion is attached has been updated, and if it has been updated, . A design product management method, characterized in that the already stored element is updated to the element to which information indicating the design completion has been added. In the design product management method according to claim 6,
The design information stored in the first storage unit, the elements of the group for which the design work has been completed, and the elements necessary for the group for which the design work has been completed are stored in the first storage unit. Let me remember,
detecting the elements of the group for which the design work has been completed and the elements necessary for the group for which the design work has been completed, which are stored in the first storage unit;
A design product management method, characterized in that the detected elements of the group for which the design work has been completed and the elements necessary for the group for which the design work has been completed are stored in the second storage unit.

Images