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

Design product management system and design product management method Download PDF

Info

Publication number
WO2022158021A1
WO2022158021A1 PCT/JP2021/031528 JP2021031528W WO2022158021A1 WO 2022158021 A1 WO2022158021 A1 WO 2022158021A1 JP 2021031528 W JP2021031528 W JP 2021031528W WO 2022158021 A1 WO2022158021 A1 WO 2022158021A1
Authority
WO
WIPO (PCT)
Prior art keywords
design
elements
completed
group
information
Prior art date
Application number
PCT/JP2021/031528
Other languages
French (fr)
Japanese (ja)
Inventor
啓 河原
正裕 松原
Original Assignee
日立Astemo株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日立Astemo株式会社 filed Critical 日立Astemo株式会社
Priority to JP2022576958A priority Critical patent/JP7406012B2/en
Priority to DE112021005618.2T priority patent/DE112021005618T5/en
Publication of WO2022158021A1 publication Critical patent/WO2022158021A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/10—Geometric CAD
    • G06F30/12—Geometric CAD characterised by design entry means specially adapted for CAD, e.g. graphical user interfaces [GUI] specially adapted for CAD
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2111/00—Details relating to CAD techniques
    • G06F2111/02—CAD in a network environment, e.g. collaborative CAD or distributed simulation

Definitions

  • the present invention relates to a design deliverable management system and a design deliverable management method for managing design information deliverables.
  • the MBSE Model-Based Systems Engineering
  • system design may be implemented multiple times to reflect changes in requirements and feedback from hardware design and software design, so even a system model that has been designed once will be changed again. Sometimes.
  • ALM Application Lifecycle Management
  • Patent Document 1 With the technology described in Patent Document 1, the above matters were not considered, and it was difficult to improve the reliability of design content management.
  • the present invention is configured as follows.
  • a design deliverable management system for managing deliverables 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 stored as design information.
  • a modeling tool that performs design work for each of the plurality of groups in accordance with a design command; the elements of the group among the plurality of groups for which design work has been completed by the modeling tool; a first control unit that gives information indicating design completion to the elements necessary for the group that has completed the design work;
  • a second storage unit that stores the elements required for the completed group, and a second control unit that stores the group to which information indicating the design completion is added in the second storage unit.
  • the design work for each of the plurality of groups is performed, and the element of the group for which the design work has been completed and the element for which the design work has been completed among the plurality of groups
  • Information indicating design completion is given to the elements necessary for a group, and the elements of the group to which the information indicating the design completion has been given and the elements necessary to the group for which the design work has been completed are transferred to a second group.
  • a design deliverables management system and a design deliverables management method are realized that can identify elements for which design has been completed from design information, store them separately, and improve the reliability of design content management. be able to.
  • FIG. 1 is a schematic configuration diagram of a design product management system according to Example 1 of the present invention
  • FIG. It is a figure which shows an example of the design information stored in design information DB.
  • FIG. 4 is a diagram showing an example of a data structure for managing drawings as part of design information
  • FIG. 4 is a functional configuration diagram showing a design completion element state change program and a design completion element synchronization program
  • 10 is a flow chart showing the flow of processing of a design completion element state change program and a design completion element synchronization program
  • FIG. 10 is a flow chart showing the flow of detailed processing of a design-completed element state changing unit
  • FIG. 9 is a diagram showing an example of design information data after the state is changed by the process of FIG. 8; 9 is a flow chart showing the flow of detailed processing of a state change detection unit
  • FIG. 4 is a diagram showing an example of the data structure of deliverable information for managing elements stored in a deliverable management DB
  • FIG. 10 is a functional configuration diagram of a design completion element state change program and a design completion element synchronization program in Embodiment 2
  • 10 is a flow chart showing the flow of processing of a design completion element state change program and a design completion element synchronization program of Example 2.
  • FIG. FIG. 5 is a diagram showing an example of product information data created by a product management design information generating unit;
  • FIG. 1 is a schematic configuration diagram of a design product management system 100 according to Embodiment 1 of the present invention.
  • the design deliverable 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 for designing by a plurality of people.
  • 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 unit), a server ROM 113, and a product management DB 114 (second storage unit).
  • 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 defined 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 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 temporarily copies the design information to the hard disk 122 using the input device 124 and the display device 125 of the design computer 102, and the modeling tool 127 to carry out the design work.
  • the modeling tool 127 performs design work for each of a plurality of groups, which will be described later, according to a user's design command.
  • the user can use the input device 124 to instruct the 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 portion 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 .
  • the design completion element synchronization program 115 is executed, and of the design information stored in the design information DB 112, only the part to which the information indicating "design completed" is 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.
  • FIG. 2 In system design using models, functional parts, physical parts, etc. are defined as elements, and relationships between elements are defined. Elements are grouped by folders and packages, such as by design unit.
  • a 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.
  • a package “Function B” 201 stores a functional component 220 (DC current detection) defined to implement the function B.
  • FIG. Package “physical architecture” 202 stores physical components 230 (AC current sensors) to which functional components are assigned.
  • FIG. 3 shows an example of a data structure for managing the design information shown in FIG. It is shown in FIG.
  • FIG. 3 is a diagram showing an example of a data structure for managing elements as part of design information.
  • the table 300 registers an ID, a name, a package in which the element is stored, a design state, and an update date and time for each element.
  • supplementary explanations of the elements may be included.
  • 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.
  • a connection ID, a connection source element ID, a connection destination element ID, and an update date/time are registered for each connection information.
  • the package including the connection information, the design state, the type of connection, etc. may be included.
  • information of connection information 240 and 241 is recorded.
  • FIG. 5 is a diagram showing an example of a data structure for managing diagram information as part of design information.
  • the table 500 registers, for each drawing, an ID, a name, a package in which the drawing is stored, an ID list of elements displayed in the drawing, and an update date and time.
  • an ID list of connection information displayed in the diagram a display method of size and color, and the like may be included.
  • the information of 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, the state change detection unit 605, and the model registration unit 606 correspond to each other. , corresponds to the design completion element synchronization program 115 .
  • the design completion target specifying unit 601 receives as input the design completion target 602 specified by the user of the design deliverable management system 100 .
  • Examples of design completion targets 602 include one or more of the packages of FIG.
  • the design completion element status 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 status of the tracked elements to "design completed".
  • the design completion element state change unit 603 identifies the elements required for the design completion target 602 using the connection information 240 and 241 between the elements in the diagram "function A architecture" 210 shown in FIG.
  • the design state of is “design completed”.
  • the design-completed element state changing unit 603 stores the information of the elements marked as “design-completed” in the hard disk 122 .
  • 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 status change detection unit 605 detects elements whose status is specified, for example, "design completed", 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 and detect the 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 .
  • FIG. 7 is a flow chart 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
  • steps S72 and S73 are processes of the design completion element synchronization program 115.
  • the design completion target designation unit 601 receives input of the design completion target 602 from the user (reception of design completion target designation).
  • the design completion target specifying unit 601 converts it into design completion target information.
  • An example is a list of package names whose design has been completed.
  • the design completion element state change unit 603 receives the design information 600 and the design completion target information as inputs, and changes the design state of the element related to the design completion target information in the design information 600 to " "Design completed” (state change of elements included in the completion target from design information).
  • step S72 the first model transfer unit 604 transfers the design information 600 updated by the design completion element state change unit 603 to the design information DB 112 (transfers the design information to the design information DB 112).
  • step S73 the state change detection unit 605 extracts elements of the design information 600 stored in the design information DB 112 whose state is "design completed". It is also possible to detect differences between the extracted elements and the product information stored in the product management DB 114 and input a list of elements for which differences are detected to the model registration unit 606 .
  • the model registration unit 606 registers the completed design information from the design information DB 112 to the product management DB 114 according to the input list (registers only design completion elements and changes to the product management DB 114). The process ends here.
  • FIG. 8 is a flowchart showing the detailed processing flow of step S71, which is the processing of the design-completed element state changing unit 603.
  • step S80 the table 500 for managing diagram information shown in FIG. 5 is searched for the package "function A" 200 specified by the user, and the diagram ID "D1" is extracted. The processing after step S81 is executed for each drawing ID.
  • step S81 for the diagram ID "D1” the 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.
  • step S82 for the element ID "E1” the design state of the element ID "E1" in the table 300 for managing the elements shown in FIG. 3 is changed to "design completed”. Similar processing is performed for the element IDs "E2" and "E4".
  • the state of the elements used in the design completion target 602 entered 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 processing shown in FIG.
  • the design status of the elements 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 status change is changed to the design information table 900 after the status change. Updated.
  • 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 section 604 .
  • FIG. 10 is a flowchart showing the detailed processing flow of step S73, which is the processing of the state change detection unit 605.
  • 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 processing after step S101 is executed for each element ID.
  • step S101 it is determined whether or not 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 S ⁇ b>103 , the selected element ID is added to the element ID list registered in the design product DB 114 . After that, the process moves to the next element ID.
  • step S101 If the selected element ID is already stored in the product management DB 114 in step S101, the process proceeds to step S102.
  • step S102 the update date and time of the element stored in the design information DB 112 and the update date and time of the element stored in the product management DB 114 are compared to determine whether the design information has been updated. In addition to the date and time of update, a change in name or content may be detected to determine update.
  • step S102 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 of step S103. In step S102, if the design information is updated, the process proceeds to step S103 to execute "add to element ID list to be registered". After that, the process moves to the next element ID.
  • FIG. 11 is a diagram showing an example of the data structure of deliverable information for managing the elements stored in the deliverable management DB 114.
  • FIG. Element IDs ⁇ “E1”, “E2” ⁇ are registered in the product information table 1100 before the design completion element synchronization program 115 is executed.
  • the element ID list for which design has been completed is ⁇ “E1”, “E2”, “E4” ⁇
  • the element IDs ⁇ “E1”, “E2” ⁇ already exist in the product information table 1100. Therefore, step S102 shown in FIG. 10 is executed. If the design information for the element ID "E1" has been updated, step S103 shown in FIG. 10 is executed.
  • step S103 shown in FIG. 10 is not executed, so the information 1112 for the element ID "E2" in the deliverable information table 1101 is not updated either.
  • step S103 shown in FIG. 10 is executed, and the information 1113 of the element ID "E4" is newly registered.
  • the diagram information and connection information may also be managed by the product management DB 114 .
  • a design deliverables management system and design deliverables management capable of identifying elements for which design has been completed from design information, separately storing them, and improving the reliability of design content management.
  • a method can be implemented.
  • Example 2 Next, Example 2 of the present invention will be described.
  • Example 1 The configuration of the design deliverable management system 100 in Example 1 is the same as in Example 2, so illustration and detailed description are 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.
  • FIG. The functional block diagram shown in FIG. 12 corresponds to the functional block diagram shown in FIG. 6 in the first 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 only with the product management design information generation unit 1201 .
  • the deliverable management information generation unit 1201 extracts the "design completed” element from the design information output by the design completion element state change unit 603, and generates deliverable information to be transferred to the deliverable management DB 114.
  • FIG. 13 is a flow chart 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 the same as steps S70, S71 and S72 shown in FIG. 7 in the first embodiment.
  • Step S131 is the process of the product management information generation unit 1201, and step S132 is the process of the second model transfer unit 604A.
  • the product management design information generation unit 1201 selects the elements of the design information 600 changed by the design completion element change unit 603 that have a specific state, for example, "design completed”. By detecting and copying the existing element, new product information to be registered in the product management DB 114 is created.
  • the newly created product information may include elements that have changed by comparing the product information and the design information stored in the product management DB 114 .
  • the product management information generation unit 1201 inputs the created product information to the second model transfer unit 604A.
  • the model transfer unit 604A transfers the input product information to the product management DB 114 . The process ends here.
  • FIG. 14 is a diagram showing an example of the product information data created by the product management design information generation unit 1201.
  • FIG. When the design information table 900 is input to the product management design information generation unit 1201, only the elements whose design status is “design completed” are copied and transferred to the product management DB 114 to generate the product information table 1400. be. That is, the information of the element IDs E1, E2, and E4 whose design status in the design information table 900 is design completed is copied, and the deliverable information table 1400 is generated.

Abstract

Provided is a design product management system capable of identifying and separately storing an element for which design has been completed from design information, and improving design content management reliability. A design product management system 100 equipped with a first storage unit 112 for storing, as design information, a plurality of elements required in order to design a design system, and a modeling tool 127 for performing a design operation for each of a plurality of groups according to a design command. In addition, the design product management system 100 is equipped with: a first control unit 126 for imparting information expressing design completion to an element of a group for which a design operation has been completed by the modeling tool 127 and to an element required by the group for which the design operation has been completed; a second storage unit 114 for storing elements of groups to which information expressing design completion has been imparted and elements required by groups for which the design operation has been completed; and a second control unit 115 for causing said second storage unit 114 to store groups to which information expressing design completion has been imparted.

Description

設計成果物管理システムおよび設計成果物管理方法Design deliverable management system and design deliverable management method
　本発明は、設計情報の成果物を管理する設計成果物管理システムおよび設計成果物管理方法に関する。 The present invention relates to a design deliverable management system and a design deliverable management method for managing design information deliverables.
　モデリング言語を用いてシステムを設計するＭＢＳＥ（Ｍｏｄｅｌ－Ｂａｓｅｄ　Ｓｙｓｔｅｍｓ　Ｅｎｇｉｎｅｅｒｉｎｇ）手法が提唱されている。要件分析やアーキテクチャ設計における検討をモデルで表現することで、従来のドキュメントベースの成果物と比較し、内容や成果物間の関係性を視覚的に理解しやすくなる。これによって、関係者間での情報共有が容易になるメリットがあると言われている。 The MBSE (Model-Based Systems Engineering) method of designing a system using a modeling language has been proposed. Representing requirements analysis and architectural design considerations in a model makes it easier to visually understand the content and relationships between deliverables compared to conventional document-based deliverables. This is said to have the advantage of facilitating information sharing among related parties.
　モデルを用いたシステム設計では、要件や機能部品、物理部品等を要素として定義し、要素間の関係情報も合わせて定義することで設計を進める。よって、１つのシステムモデル内に設計中の要素と設計が完了した要素が混在することがある。 In system design using models, requirements, functional parts, physical parts, etc. are defined as elements, and the design proceeds by defining the relationship information between the elements as well. Therefore, elements under design and elements whose design has been completed may coexist in one system model.
　また、システム設計は要求の変更や、ハードウェア設計、ソフトウェア設計からのフィードバックを反映するために複数回実施されることもあり、一度設計が完了したシステムモデルであっても、再度変更が加えられることがある。 In addition, system design may be implemented multiple times to reflect changes in requirements and feedback from hardware design and software design, so even a system model that has been designed once will be changed again. Sometimes.
　一方で、システム設計において、ソフトウェア詳細設計やソースコード、ハードウェアの回路設計図などの後工程に反映される情報、またはされた情報を把握することが開発プロジェクトの管理上で重要である。 On the other hand, in system design, it is important for the management of the development project to understand the information that will be reflected in the post-process such as software detailed design, source code, and hardware circuit design drawing.
　このため、システムモデルのうち設計が完了した情報だけを抽出し、バージョン管理も行い、確実に管理する必要がある。 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 that manages design information is ALM (Application Lifecycle Management), which is suitable for managing only information for which the above design has been completed.
　特許文献１に記載された技術においては、２人の設計者が同時平行で設計する場合を想定し、両者の設計が完了したと判断できた段階で、両者の設計情報ファイルをメインのサーバに送信し記憶させることを実現している。 In the technique described in Patent Document 1, it is assumed that two designers are simultaneously designing, and when it is determined that both designers have completed their designs, both design information files are transferred to the main server. It is realized to transmit and store.
特開平０５－１７４０７９号公報JP-A-05-174079
　しかし、１つの設計情報のうち設計が完了した部分のみを別途管理するためには、設計情報から設計が完了した要素を特定する必要がある。また、システムモデルでは設計単位に対応したパッケージ等を作成し、要素をグループ化することがあるが、複数の設計単位で使用される要素も存在するため、設計単位と要素のグループが異なることがある。 However, in order to separately manage only the completed design part of one piece of design information, it is necessary to identify the elements for which the design has been completed from the design information. In addition, in the system model, a package, etc. corresponding to the design unit is created and the elements are sometimes grouped, but since there are elements used in multiple design units, the design unit and the element group may differ. be.
　よって、設計が完了したパッケージに格納される要素のみを別途記憶させるだけでは、設計情報の一部が欠落する恐れがある。 Therefore, if only the elements stored in the package whose design has been completed are stored separately, there is a risk that part of the design information will be lost.
　特許文献１に記載の技術では、上記事項が考慮されておらず、設計内容の管理の信頼性を向上することが困難であった。 With the technology described in Patent Document 1, the above matters were not considered, and it was difficult to improve the reliability of design content management.
　本発明の目的は、設計情報から設計が完了した要素を特定し、別途記憶させ、設計内容の管理の信頼性を向上することが可能な設計成果物管理システムおよび設計成果物管理方法を実現することである。 It is an object of the present invention to provide a design deliverable management system and a design deliverable management method that can identify elements for which design has been completed from design information, store them separately, and improve the reliability of design content management. That is.
　上記課題を解決するために、本発明は以下のように構成される。 In order to solve the above problems, the present invention is configured as follows.
　複数の要素が組み合わされて複数のグループに分けられて設計される設計システムの成果物を管理する設計成果物管理システムであって、前記設計システムの設計に必要な前記複数の前記要素を設計情報として記憶する第１記憶部と、設計指令に従って、前記複数のグループのそれぞれの設計作業を行うモデリングツールと、前記複数のグループのうちの前記モデリングツールにより設計作業が完了した前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素に対して設計完了を示す情報を付与する第１制御部と、前記設計完了を示す情報が付与された前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素を記憶する第２記憶部と、前記設計完了を示す情報が付与された前記グループを前記第２記憶部に記憶させる第２制御部と、を備える。 A design deliverable management system for managing deliverables 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 stored as design information. a modeling tool that performs design work for each of the plurality of groups in accordance with a design command; the elements of the group among the plurality of groups for which design work has been completed by the modeling tool; a first control unit that gives information indicating design completion to the elements necessary for the group that has completed the design work; A second storage unit that stores the elements required for the completed group, and a second control unit that stores the group to which information indicating the design completion is added in the second storage unit.
　複数の要素が組み合わされて複数のグループに分けられて設計される設計システムの成果物を管理する設計成果物管理方法であって、前記設計システムの設計に必要な前記複数の前記要素を設計情報として第１記憶部に記憶し、設計指令に従って、前記複数のグループのそれぞれの設計作業を行い、前記複数のグループのうちの設計作業が完了した前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素に対して設計完了を示す情報を付与し、前記設計完了を示す情報が付与された前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素を第２記憶部に記憶する。 A design deliverable management method for managing deliverables 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 stored as design information. , and according to the design command, the design work for each of the plurality of groups is performed, and the element of the group for which the design work has been completed and the element for which the design work has been completed among the plurality of groups Information indicating design completion is given to the elements necessary for a group, and the elements of the group to which the information indicating the design completion has been given and the elements necessary to the group for which the design work has been completed are transferred to a second group. Store in the storage unit.
　本発明によれば、設計情報から設計が完了した要素を特定し、別途記憶させ、設計内容の管理の信頼性を向上することが可能な設計成果物管理システムおよび設計成果物管理方法を実現することができる。 According to the present invention, a design deliverables management system and a design deliverables management method are realized that can identify elements for which design has been completed from design information, store them separately, and improve the reliability of design content management. be able to.
本発明の実施例１による設計成果物管理システムの概略構成図である。1 is a schematic configuration diagram of a design product management system according to Example 1 of the present invention; FIG. 設計情報ＤＢに格納される設計情報の一例を示す図である。It is a figure which shows an example of the design information stored in design information DB. 設計情報の一部として要素を管理するためのデータ構造の一例を示す図である。It is a figure which shows an example of the data structure for managing an element as a part of design information. 設計情報の一部として接続情報を管理するためのデータ構造の一例を示す図である。It is a figure which shows an example of the data structure for managing connection information as a part of design information. 設計情報の一部として図を管理するためのデータ構造の一例を示す図である。FIG. 4 is a diagram showing an example of a data structure for managing drawings as part of design information; 設計完了要素状態変更プログラムと、設計完了要素同期プログラムと、を示す機能構成図である。FIG. 4 is a functional configuration diagram showing a design completion element state change program and a design completion element synchronization program; 設計完了要素状態変更プログラムと設計完了要素同期プログラムの処理の流れを示すフローチャートである。10 is a flow chart showing the flow of processing of a design completion element state change program and a design completion element synchronization program; 設計完了要素状態変更部の詳細処理の流れを示すフローチャートである。FIG. 10 is a flow chart showing the flow of detailed processing of a design-completed element state changing unit; FIG. 図８の処理による状態変更後の設計情報データの一例を示す図である。FIG. 9 is a diagram showing an example of design information data after the state is changed by the process of FIG. 8; 状態変更検出部の詳細処理の流れを示すフローチャートである。9 is a flow chart showing the flow of detailed processing of a state change detection unit; 成果物管理ＤＢに格納される要素を管理するための成果物情報のデータ構造の一例を示す図である。FIG. 4 is a diagram showing an example of the data structure of deliverable information for managing elements stored in a deliverable management DB; 実施例２における設計完了要素状態変更プログラムと、設計完了要素同期プログラムの機能構成図である。FIG. 10 is a functional configuration diagram of a design completion element state change program and a design completion element synchronization program in Embodiment 2; 実施例２の設計完了要素状態変更プログラムと、設計完了要素同期プログラムの処理の流れを示すフローチャートである。10 is a flow chart showing the flow of processing of a design completion element state change program and a design completion element synchronization program of Example 2. FIG. 成果物管理用設計情報生成部で作成される成果物情報データの一例を示す図である。FIG. 5 is a diagram showing an example of product information data created by a product management design information generating unit;
　以下、添付図面を参照して本発明の実施例について説明する。なお、添付図面は本発明の原理に則った具体的な実施例を示しているが、これらは本発明の理解のためのものであり、決して本発明を限定的に解釈するために用いられるものではない。また、各図において共通の構成については同一の参照番号が付されている。 Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that although the accompanying drawings show specific embodiments in accordance with the principles of the present invention, they are for the purpose of understanding the present invention and are by no means used for limiting interpretation of the present invention. is not. In addition, the same reference numerals are given to common configurations in each figure.
　（実施例１）
　図１は、本発明の実施例１による設計成果物管理システム１００の概略構成図である。 (Example 1)
FIG. 1 is a schematic configuration diagram of a design product management system 100 according to Embodiment 1 of the present invention.
　図１において、設計成果物管理システム１００は、サーバ１０１と、設計用コンピュータ１０２とを備え、これらはネットワーク１０３を介して接続されている。複数人で設計を実施するために設計用コンピュータ１０２を複数備えていてもよい。図１に示した例は、設計用コンピュータ１０２を複数備えている例である。 In FIG. 1, the design deliverable 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 for designing by a plurality of people. 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 unit), a server ROM 113, and a product management DB 114 (second storage unit). 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 defined 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 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 temporarily copies the design information to the hard disk 122 using the input device 124 and the display device 125 of the design computer 102, and the modeling tool 127 to carry out the design work. The modeling tool 127 performs design work for each of a plurality of groups, which will be described later, according to a user's design command.
　設計作業により設計情報が更新され、設計が完了した段階で、ユーザーは入力装置１２４を用いて、設計完了要素状態変更プログラム１２６の実行を指示し、設計情報の設計完了範囲を指定できる。 When the design information is updated by the design work and the design is completed, the user can use the input device 124 to instruct the 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 portion 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 . 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 part to which the information indicating "design completed" is 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. FIG. In system design using models, functional parts, physical parts, etc. are defined as elements, and relationships between elements are defined. Elements are grouped by folders and packages, such as by design unit.
　パッケージ「機能Ａ」２００には、図「機能Ａアーキテクチャ」２１０と、機能Ａを実現するために定義された機能部品２１１（ＡＣ電流検出）、２１２（電流制御）が格納されている。パッケージ「機能Ｂ」２０１には、機能Ｂを実現するために定義された機能部品２２０（ＤＣ電流検出）が格納されている。パッケージ「物理アーキテクチャ」２０２には、機能部品を割り当てる物理部品２３０（ＡＣ電流センサ）が格納されている。 A 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. A package "Function B" 201 stores a functional component 220 (DC current detection) defined to implement the function B. FIG. Package "physical architecture" 202 stores physical components 230 (AC current sensors) to which functional components are assigned.
　図「機能Ａアーキテクチャ」２１０には、機能部品２１１、２１２と、機能部品を実現する物理部品２３０と、要素間の接続情報２４０、２４１が表示されている。物理部品２３０のように、要素は他のパッケージの図で利用されうる特徴がある。この特徴によって、機能Ａが設計完了となった際にパッケージ「機能Ａ」２００に含まれる要素を成果物管理ＤＢ１１４に登録するだけでは、パッケージ「機能Ａ」２００に含まれていない要素２３０を登録することができない。 In the diagram "Function A Architecture" 210, functional components 211 and 212, physical components 230 that implement the functional components, and connection information 240 and 241 between elements are displayed. Like physical part 230, elements have characteristics that can be utilized in other package diagrams. Due to this feature, when the design of the function A is completed, the elements 230 not included in the package "function A" 200 can be registered only by registering the elements included in the package "function A" 200 in the product management DB 114. Can not do it.
　そこで、本発明の実施例１では、パッケージ「機能Ａ」２００に関連する、図「機能Ａアーキテクチャ」２１０で利用される要素２３０も含めて成果物管理ＤＢ１１４へ登録することを実現する。 Therefore, in the first embodiment of the present invention, it is realized to register in the product management DB 114 including the element 230 used in the diagram "function A architecture" 210 related to the package "function A" 200.
　本発明の実施例１における処理を説明するために、サーバ１０１の設計情報ＤＢ１１２、もしくは設計用コンピュータ１０２のハードディスク１２２において、図２に示す設計情報を管理するためのデータ構造の一例を図３から図５に示す。 In order to explain the processing in the first embodiment of the present invention, FIG. 3 shows an example of a data structure for managing the design information shown in FIG. It is shown in FIG.
　図３は、設計情報の一部として要素を管理するためのデータ構造の一例を示す図である。テーブル３００には、要素ごとに、ＩＤと、名称と、要素が格納されているパッケージと、設計状態と、更新日時と、が登録される。上記以外にも、要素の補足説明等を含めてもよい。図３に示す例では、機能部品２１１、２１２、２２０、物理部品２３０の情報が記録されている。 FIG. 3 is a diagram showing an example of a data structure for managing elements as part of design information. The table 300 registers an ID, a name, a package in which the element is stored, a design state, and an update date and time for each element. In addition to the above, supplementary explanations of the elements may 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, a connection ID, a connection source element ID, a connection destination element ID, and an update date/time are registered for each connection information. In addition to the above, the package including the connection information, the design state, the type of connection, etc. may be included. In the example shown in FIG. 4, information of connection information 240 and 241 is recorded.
　図５は、設計情報の一部として図の情報を管理するためのデータ構造の一例を示す図である。テーブル５００には、図ごとに、ＩＤと、名称と、図が格納されているパッケージと、図で表示する要素のＩＤリストと、更新日時と、が登録される。上記以外にも、図の補足説明、図で表示する接続情報のＩＤリスト、大きさや色などの表示方法、等を含めても良い。図５では、図「機能Ａアーキテクチャ」２１０の情報が記録されている。 FIG. 5 is a diagram showing an example of a data structure for managing diagram information as part of design information. The table 500 registers, for each drawing, an ID, a name, a package in which the drawing is stored, an ID list of elements displayed in the drawing, and an update date and time. In addition to the above, supplementary explanation of the diagram, an ID list of connection information displayed in the diagram, a display method of size and color, and the like may be included. In FIG. 5, the information of 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. FIG. 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, the state change detection unit 605, and the model registration unit 606 correspond to each other. , corresponds to the design completion element synchronization program 115 .
　設計完了対象指定部６０１は、設計成果物管理システム１００のユーザーが指定した設計完了対象６０２を入力として受け取る。設計完了対象６０２の例としては、図２のパッケージの１つ以上が挙げられる。設計完了要素状態変更部６０３は、ユーザーが設計した設計情報６００から、設計完了対象６０２に関連する要素を追跡し、追跡した要素の設計状態を「設計完了」に変更する。 The design completion target specifying unit 601 receives as input the design completion target 602 specified by the user of the design deliverable management system 100 . Examples of design completion targets 602 include one or more of the packages of FIG. The design completion element status 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 status of the tracked elements to "design completed".
　つまり、設計完了要素状態変更部６０３は、設計完了対象６０２に必要な要素を図２に示す図「機能Ａアーキテクチャ」２１０内の要素間の接続情報２４０、２４１を用いて特定し、特定した要素の設計状態を「設計完了」とする。　
　そして、設計完了要素状態変更部６０３は、「設計完了」となっている要素の情報をハードディスク１２２に格納する。そして、設計完了要素状態変更部６０３から設計情報が第１モデル転送部６０４に送られる。 In other words, the design completion element state change unit 603 identifies the elements required for the design completion target 602 using the connection information 240 and 241 between the elements in the diagram "function A architecture" 210 shown in FIG. The design state of is “design completed”.
Then, the design-completed element state changing unit 603 stores the information of the elements marked as “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 status change detection unit 605 detects elements whose status is specified, for example, "design completed", 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 and detect the 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 .
　上記動作により、設計が完了した設計情報のみを成果物管理ＤＢ１１４で管理することができる。 Through the above operation, only the design information for which the design has been completed can be managed in the product management DB 114.
　図７は、設計完了要素状態変更プログラム１２６と、設計完了要素同期プログラム１１５の処理の流れを示すフローチャートである。ステップＳ７０、Ｓ７１は設計完了要素状態変更プログラム１２６の処理であり、ステップＳ７２、Ｓ７３は設計完了要素同期プログラム１１５の処理である。 FIG. 7 is a flow chart showing the processing flow of the design completion element state change program 126 and the design completion element synchronization program 115. FIG. 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. FIG.
　処理を開始後、ステップＳ７０にて、設計完了対象指定部６０１はユーザーからの設計完了対象６０２の入力を受け付ける（設計完了対象の指定受付）。設計完了対象指定部６０１は設計完了対象６０２が入力されると、設計完了対象情報に変換する。例としては、設計完了となったパッケージ名のリスト等が挙げられる。 After starting the process, in step S70, the design completion target designation unit 601 receives input of the design completion target 602 from the user (reception of design completion target designation). When the design completion target 602 is input, the design completion target specifying unit 601 converts it into design completion target information. An example is a list of package names whose design has 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 inputs, and changes the design state of the element related to the design completion target information in the design information 600 to " "Design completed" (state change of elements included in the completion target from design information).
　次に、ステップＳ７２にて、第１モデル転送部６０４は、設計完了要素状態変更部６０３によって更新された設計情報６００を設計情報ＤＢ１１２に転送する（設計情報を設計情報ＤＢ１１２へ転送）。 Next, in step S72, the first model transfer unit 604 transfers the design information 600 updated by the design completion 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 state change detection unit 605 extracts elements of the design information 600 stored in the design information DB 112 whose state is "design completed". It is also possible to detect differences between the extracted elements and the product information stored in the product management DB 114 and input a list of elements for which differences are detected to the model registration unit 606 . The model registration unit 606 registers the completed design information from the design information DB 112 to the product management DB 114 according to the input list (registers only design completion elements and changes to the product management DB 114). The process ends here.
　ユーザーが設計完了対象６０２としてパッケージ「機能Ａ」２００を指定した場合を例に、設計完了要素状態変更プログラム１２６と、設計完了要素同期プログラム１１５の処理について詳細に説明する。 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 the case where the user designates the package "function A" 200 as the design completion target 602.
　図８は、設計完了要素状態変更部６０３の処理であるステップＳ７１の詳細処理の流れを示すフローチャートである。ステップＳ８０では、図５に示した図の情報を管理するためのテーブル５００より、ユーザーが指定したパッケージ「機能Ａ」２００を探索し、図ＩＤ“Ｄ１”を抽出する。ステップＳ８１以降の処理は各図ＩＤに対して実行する。 FIG. 8 is a flowchart showing the detailed processing flow of step S71, which is the processing of the design-completed element state changing unit 603. FIG. In step S80, the table 500 for managing diagram information shown in FIG. 5 is searched for the package "function A" 200 specified by the user, and the diagram ID "D1" is extracted. The processing after step S81 is executed for each drawing ID.
　図ＩＤ”Ｄ１”に対するステップＳ８１では、テーブル５００から図ＩＤ“Ｄ１”で表示する要素リスト｛Ｅ１，　Ｅ２，　Ｅ４｝を抽出する。ステップＳ８２の処理は各要素ＩＤに対して実行する。要素ＩＤ”Ｅ１”に対するステップＳ８２では、図３に示した要素を管理するためのテーブル３００の、要素ＩＤ”Ｅ１”の設計状態を「設計完了」へ変更する。要素ＩＤ”Ｅ２”、 ”Ｅ４”についても同様の処理を行う。 At step S81 for the diagram ID "D1", the 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 the elements shown in FIG. 3 is changed to "design completed". Similar processing is performed for the element IDs "E2" and "E4".
　以上の処理によって、ユーザーが入力した設計完了対象６０２で使用される要素の状態を変更することができる。 By the above processing, the state of the elements used in the design completion target 602 entered 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 processing shown in FIG. The design status of the elements 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 status change is changed to the design information table 900 after the status change. Updated. After that, 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 section 604 .
　図１０は、状態変更検出部６０５の処理であるステップＳ７３の詳細処理の流れを示すフローチャートである。ステップＳ１００では、図９に示した設計情報テーブル９００の状態が「設計完了」となっている要素ＩＤを抽出し、｛Ｅ１，Ｅ２，Ｅ４｝のような要素ＩＤリストを生成する。ステップＳ１０１以降の処理は各要素ＩＤについて実行される。 FIG. 10 is a flowchart showing the detailed processing flow of step S73, which is the processing of the state change detection unit 605. FIG. 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 processing after step S101 is executed for each element ID.
　ステップＳ１０１では、成果物管理ＤＢ１１４に格納されている成果物情報に、選択した要素ＩＤが既に記憶されているか否かを判断する。選択した要素ＩＤが成果物情報に存在しない場合、ステップＳ１０３を実行する。ステップＳ１０３では、選択した要素ＩＤを設計成果物ＤＢ１１４に登録する要素ＩＤリストに追加する。その後、次の要素ＩＤに対する処理へ移行する。 In step S101, it is determined whether or not 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 S<b>103 , the selected element ID is added to the element ID list registered in the design product DB 114 . After that, the process moves to the next element ID.
　ステップＳ１０１において、成果物管理ＤＢ１１４に選択した要素ＩＤが既に記憶されている場合、ステップＳ１０２に進む。ステップＳ１０２では、設計情報ＤＢ１１２に格納された要素の更新日時と、成果物管理ＤＢ１１４に格納された要素の更新日時を比較し、設計情報が更新されているかを判断する。更新日時以外に、名称や内容の変更を検出し、更新を判断してもよい。 If the selected element ID is already stored in the product management DB 114 in step S101, the process proceeds to step S102. In step S102, the update date and time of the element stored in the design information DB 112 and the update date and time of the element stored in the product management DB 114 are compared to determine whether the design information has been updated. In addition to the date and time of update, a change in name or content may be detected to determine update.
　ステップＳ１０２において、設計情報が更新されていないと判断した場合、ステップＳ１０３の処理は実行せずに、次の要素ＩＤに対する処理へ移行する。ステプＳ１０２において、設計情報に更新があった場合、ステップＳ１０３に進み、「登録する要素ＩＤリストに追加」を実行する。その後、次の要素ＩＤに対する処理へ移行する。 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 of step S103. In step S102, if the design information is updated, the process proceeds to step S103 to execute "add to element ID list to be registered". After that, the process moves to the next element ID.
　以上の処理を、設計完了状態となった要素ＩＤすべてに対して実行することで、状態が「設計完了」の要素のみを別途記録することが可能となる。 By executing the above processing for all element IDs in the design completed state, it is possible to separately record only the elements whose status is "design completed".
　図１１は、成果物管理ＤＢ１１４に格納される要素を管理するための成果物情報のデータ構造の一例を示す図である。設計完了要素同期プログラム１１５の実行前の成果物情報テーブル１１００には要素ＩＤ｛”Ｅ１”，”Ｅ２”｝が登録されている状態である。ここで、設計完了となった要素ＩＤリストが｛”Ｅ１”，”Ｅ２”，”Ｅ４”｝であった場合、要素ＩＤ｛“Ｅ１”，”Ｅ２”｝は成果物情報テーブル１１００に既に存在するため、図１０に示したステップＳ１０２が実行される。要素ＩＤ“Ｅ１”の設計情報が更新されていた場合、図１０に示したステップＳ１０３が実行される。 FIG. 11 is a diagram showing an example of the data structure of deliverable information for managing the elements stored in the deliverable management DB 114. FIG. 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 product information table 1100. Therefore, step S102 shown in FIG. 10 is executed. If the design information for the element ID "E1" has been updated, step S103 shown in FIG. 10 is executed.
　よって、更新された成果物情報テーブル１１０１の要素ＩＤ”Ｅ１”の情報１１１１のように上書きされる。 Therefore, it is overwritten like the information 1111 of the element ID "E1" in the updated product information table 1101.
　要素ＩＤ”Ｅ２”の設計情報が更新されていない場合、図１０に示したステップＳ１０３が実行されないため、成果物情報テーブル１１０１の要素ＩＤ”Ｅ２”の情報１１１２も更新されない。 If the design information for the element ID "E2" has not been updated, step S103 shown in FIG. 10 is not executed, so the information 1112 for the element ID "E2" in the deliverable information table 1101 is not updated either.
　要素ＩＤ”Ｅ４”は成果物情報テーブル１１００に存在しないため、図１０に示したステップＳ１０３が実行され、要素ＩＤ”Ｅ４”の情報１１１３が新たに登録される。同様に、図の情報、接続情報も成果物管理ＤＢ１１４で管理しても良い。 Since the element ID "E4" does not exist in the product information table 1100, step S103 shown in FIG. 10 is executed, and the information 1113 of the element ID "E4" is newly registered. Similarly, the diagram information and connection information may also be managed by the product management DB 114 .
　以上により、モデリングツールでの設計情報のうち、設計が完了した情報のみを抽出し、成果物管理ＤＢ１１４で管理することができる。 As described above, out of the design information in the modeling tool, only the information for which the design has been completed can be extracted and managed in the product management DB 114.
　本発明の実施例１によれば、設計情報から設計が完了した要素を特定し、別途記憶させ、設計内容の管理の信頼性を向上することが可能な設計成果物管理システム及び設計成果物管理方法を実現することができる。 According to the first embodiment of the present invention, a design deliverables management system and design deliverables management capable of identifying elements for which design has been completed from design information, separately storing them, and improving the reliability of design content management. A method can be implemented.
　また、ソフトウェア設計工程、ハードウェア設計工程、テスト工程等の他プロセスにおける成果物と、設計が完了したシステム設計情報のトレースを確保でき、さらに成果物のバージョンも管理できる。よって、設計の内容を高信頼に管理することができる。なお、本実施例１ではシステム設計を例としたが、モデルを用いたソフトウェア設計、ハードウェア設計においても本発明を適用することができる。 In addition, it is possible to secure traces of the deliverables in other processes such as the software design process, hardware design process, and test process, as well as the system design information for which the design has been completed, and also manage the versions of the deliverables. Therefore, the contents of the design can be managed with high reliability. Although system design is taken as an example in the first embodiment, 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 deliverable management system 100 in Example 1 is the same as in Example 2, so illustration and detailed description are 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. FIG. The functional block diagram shown in FIG. 12 corresponds to the functional block 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 only with the product management design information generation unit 1201 .
　成果物管理情報生成部１２０１は、設計完了要素状態変更部６０３が出力した設計情報から、「設計完了」要素を抽出し成果物管理ＤＢ１１４へ転送する成果物情報を生成する。 The deliverable management information generation unit 1201 extracts the "design completed" element from the design information output by the design completion element state change unit 603, and generates deliverable information to be transferred to the deliverable management DB 114.
　図１３は、実施例２の設計完了要素状態変更プログラム１２６と、設計完了要素同期プログラム１１５の処理の流れを示すフローチャートである。ステップＳ７０、Ｓ７１及びＳ７２は、実施例１における図７に示したステップＳ７０、Ｓ７１及びＳ７２と同様である。 FIG. 13 is a flow chart 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 the same as steps S70, S71 and S72 shown in FIG. 7 in the first embodiment.
　ステップＳ１３１は、成果物管理情報生成部１２０１の処理であり、ステップＳ１３２は、第２モデル転送部６０４Ａの処理である。ステップ１３１にて、成果物管理用設計情報生成部１２０１は、設計完了要素変更部６０３が変更した設計情報６００の要素のうち、状態が特定のもの、ここでは例として「設計完了」となっている要素を検出しコピーすることで、成果物管理ＤＢ１１４に登録する成果物情報を新たに作成する。 Step S131 is the process of the product management information generation unit 1201, and step S132 is the process of the second model transfer unit 604A. At step 131, the product management design information generation unit 1201 selects the elements of the design information 600 changed by the design completion element change unit 603 that have a specific state, for example, "design completed". By detecting and copying the existing element, new product information to be registered in the product management DB 114 is created.
　また、特定の状態に加えて、成果物管理ＤＢ１１４に格納される成果物情報と設計情報とを比較し変更点がある要素も、新たに作成する成果物情報に含めてもよい。成果物管理情報生成部１２０１は、作成した成果物情報を第２モデル転送部６０４Ａへ入力する。次にステップ１３２にて、モデル転送部６０４Ａは入力された成果物情報を成果物管理ＤＢ１１４へ転送する。以上で処理を終了する。 Also, in addition to the specific state, the newly created product information may include elements that have changed by comparing the product information and the design information stored in the product management DB 114 . The product management information generation unit 1201 inputs the created product information to the second model transfer unit 604A. Next, at step 132 , the model transfer unit 604A transfers the input product information to the product management DB 114 . The process ends here.
　図１４は、成果物管理用設計情報生成部１２０１で作成される成果物情報データの一例を示す図である。成果物管理用設計情報生成部１２０１に設計情報テーブル９００が入力された場合、設計状態が「設計完了」である要素のみをコピーし、成果物管理ＤＢ１１４へ転送する成果物情報テーブル１４００が生成される。つまり、設計情報テーブル９００の設計状態が設計完了となっている要素ＩＤがＥ１、Ｅ２及びＥ４の情報がコピーされ、成果物情報テーブル１４００が生成される。 FIG. 14 is a diagram showing an example of the product information data created by the product management design information generation unit 1201. FIG. When the design information table 900 is input to the product management design information generation unit 1201, only the elements whose design status is “design completed” are copied and transferred to the product management DB 114 to generate the product information table 1400. be. That is, the information of the element IDs E1, E2, and E4 whose design status in the design information table 900 is design completed is copied, and the deliverable information table 1400 is generated.
　以上により、設計情報から設計が完了した情報のみを抽出し成果物管理ＤＢ１１４で管理することができる。 As described above, it is possible to extract only the information for which the design has been completed from the design information and manage it in the product management DB 114 .
　本発明の実施例２においても、実施例１と同様な効果を得ることができる。 Also in the second embodiment of the present invention, the same effect as in the first embodiment can be obtained.
　１００・・・設計成果物管理システム、１０１・・・サーバ、１０２・・・設計用コンピュータ、１０３・・・ネットワーク、１１０・・・サーバ用ＣＰＵ、１１１・・・サーバ用ＲＡＭ、１１２・・・設計情報ＤＢ（第１記憶部）、１１３・・・サーバ用ＲＯＭ、１１４・・・成果物管理ＤＢ（第２記憶部）、１１５・・・設計完了要素同期プログラム（第２制御部）、１２０・・・ＣＰＵ、１２１・・・ＲＡＭ、１２２・・・ハードディスク、１２３・・・ＲＯＭ、１２４・・・入力装置、１２５・・・表示装置、１２６・・・設計完了要素状態変更プログラム（第１制御部）、１２７・・・モデリングツール、２００・・・パッケージ「機能Ａ」、２０１・・・パッケージ「機能Ｂ」、２０２・・・パッケージ「物理アーキテクチャ」、２１０・・・図「機能Ａアーキテクチャ」、２１１、２１２、２２０・・・機能部品、２３０・・・物理部品、２４０、２４１・・・接続情報、３００、４００、５００・・・テーブル、６００・・・設計情報、６０１・・・設計完了対象指定部、６０２・・・設計完了対象、６０３・・・設計完了要素状態変更部、６０４・・・第１モデル転送部、６０４Ａ・・・第２モデル転送部、６０５・・・状態変更検出部、６０６・・・モデル登録部、９００・・・設計情報テーブル、１１００、１１０１、１４００・・・成果物情報テーブル、１２０１・・・成果物管理用設計情報生成部 DESCRIPTION OF SYMBOLS 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 Product 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 parts, 230... physical parts, 240, 241... connection information, 300, 400, 500... tables, 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 State Change detection unit 606 Model registration unit 900 Design information table 1100, 1101, 1400 Product information table 1201 Product management design information generation unit

Claims (9)

  1. 　複数の要素が組み合わされて複数のグループに分けられて設計される設計システムの成果物を管理する設計成果物管理システムであって、
    　前記設計システムの設計に必要な前記複数の前記要素を設計情報として記憶する第１記憶部と、
    　設計指令に従って、前記複数のグループのそれぞれの設計作業を行うモデリングツールと、
    　前記複数のグループのうちの前記モデリングツールにより設計作業が完了した前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素に対して設計完了を示す情報を付与する第１制御部と、
    　前記設計完了を示す情報が付与された前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素を記憶する第２記憶部と、
    　前記設計完了を示す情報が付与された前記グループを前記第２記憶部に記憶させる第２制御部と、
    　を備えることを特徴とする設計成果物管理システム。     A design deliverable management system for managing deliverables of a design system designed by combining a plurality of elements and dividing them into a plurality of groups,
    a first storage unit that stores the plurality of elements necessary for designing the design system as design information;
    a modeling tool for performing design work for each of the plurality of groups according to design directives;
    A first control unit that provides information indicating design completion to the elements of the group for which design work has been completed by the modeling tool among the plurality of groups and to the elements necessary for the group for which the design work has been completed. When,
    a second storage unit that stores the elements of the group to which the information indicating the completion of the design has been added and the elements necessary for the group to which the design work has been completed;
    a second control unit for storing the group to which the information indicating the design completion is added in the second storage unit;
    A design deliverable management system comprising:
  2. 　請求項１に記載の設計成果物管理システムにおいて、
    　前記複数のグループは、前記要素間の接続情報を有するグループを有し、前記第１制御部は、前記接続情報を用いて、前記設計作業が完了した前記グループに必要な前記要素を特定することを特徴とする設計成果物管理システム。     In the design deliverable management system according to claim 1,
    The plurality of groups includes a group 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 deliverable management system characterized by
  3. 　請求項１に記載の設計成果物管理システムにおいて、
    　前記第２制御部は、前記設計完了を示す情報が付与された前記要素が、前記第２記憶部に記憶されていた場合、前記設計完了を示す情報が付与された前記要素が更新されているか否かを判断し、更新されているときは、前記第２記憶部に記憶されている前記要素を、前記設計完了を示す情報が付与された前記要素に更新することを特徴とする設計成果物管理システム。     In the design deliverable management system according to claim 1,
    When the element to which the information indicating the design completion is stored in the second storage unit, the second control unit determines whether the element to which the information indicating the design completion has been updated. A design deliverable characterized by determining whether or not the element has been updated, and updating the element stored in the second storage unit to the element to which the information indicating the completion of the design has been added if the element has been updated. management system.
  4. 　請求項１に記載の設計成果物管理システムにおいて、
    　前記第２制御部は、第１モデル転送部と、モデル登録部と、状態変更検出部と、を有し、
    　前記第１モデル転送部は、前記第１記憶部に記憶されていた前記設計情報と、前記設計作業が完了した前記グループの前記要素と、前記設計作業が完了した前記グループに必要な前記要素と、を前記第１記憶部に記憶させ、
    　前記状態変更検出部は、前記第１記憶部に記憶された前記設計作業が完了した前記グループの前記要素と、前記設計作業が完了した前記グループに必要な前記要素と、を検出し、
    　前記モデル登録部は、前記状態変更検出部が検出した前記設計作業が完了した前記グループの前記要素と、前記設計作業が完了した前記グループに必要な前記要素と、を前記第２記憶部に記憶させることを特徴とする設計成果物管理システム。     In the design deliverable management system according to claim 1,
    the second control unit has 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. , is stored in the first storage unit,
    The state change detection unit detects the elements of the group for which the design work is completed and the elements required for the group for which the design work is completed, stored in the first storage unit;
    The model registration unit stores, in the second storage unit, the elements of the group that has completed the design work detected by the state change detection unit and the elements that are necessary for the group that has completed the design work. A design deliverable management system characterized by:
  5. 　請求項１に記載の設計成果物管理システムにおいて、
    　前記第２制御部は、成果物管理用設計情報生成部と、第２モデル転送部と、を有し、
    　前記成果物管理用設計情報生成部は、前記第１制御部により前記設計完了を示す情報が付与された前記設計作業が完了した前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素を、前記第２モデル転送部に転送し、
    　前記第２モデル転送部は、前記成果物管理用設計情報生成部から転送された前記設計完了を示す情報が付与された前記設計作業が完了した前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素を前記第２記憶部に記憶させることを特徴とする設計成果物管理システム。     In the design deliverable management system according to claim 1,
    The second control unit has a product management design information generation unit and a second model transfer unit,
    The design information generation unit for managing a product manages the element of the group to which the design work is completed to which the information indicating the design completion is given by the first control unit, and the element necessary for the group to which the design work is completed. transferring the element to the second model transfer unit;
    The second model transfer unit transfers the element of the group to which the design work is completed to which the information indicating the design completion transferred from the product management design information generation unit and the element to which the design work is completed. A design deliverable management system, wherein the elements necessary for the group are stored in the second storage unit.
  6. 　複数の要素が組み合わされて複数のグループに分けられて設計される設計システムの成果物を管理する設計成果物管理方法であって、
    　前記設計システムの設計に必要な前記複数の前記要素を設計情報として第１記憶部に記憶し、
    　設計指令に従って、前記複数のグループのそれぞれの設計作業を行い、
    　前記複数のグループのうちの設計作業が完了した前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素に対して設計完了を示す情報を付与し、
    　前記設計完了を示す情報が付与された前記グループの前記要素及び前記設計作業が完了した前記グループに必要な前記要素を第２記憶部に記憶することを特徴とする設計成果物管理方法。     A design deliverable management method for managing deliverables of a design system designed by combining a plurality of elements and dividing them into a plurality of groups,
    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 according to a design directive;
    providing information indicating design completion to the elements of the group for which design work has been completed and the elements necessary for the group for which design work has been completed, among the plurality of groups;
    A design deliverable management method, wherein the elements of the group to which the information indicating the completion of the design is given and the elements necessary for the group to which the design work is completed are stored in a second storage unit.
  7. 　請求項６に記載の設計成果物管理方法において、
    　前記複数のグループは、前記要素間の接続情報を有するグループを有し、前記接続情報を用いて、前記設計作業が完了した前記グループに必要な前記要素を特定することを特徴とする設計成果物管理方法。     In the design deliverable management method according to claim 6,
    The design deliverable, wherein the plurality of groups includes a group having connection information between the elements, and the connection information is used to specify the elements necessary for the group for which the design work has been completed. Management method.
  8. 　請求項６に記載の設計成果物管理方法において、
    　前記設計完了を示す情報が付与された前記要素が、既に記憶されていた場合、前記設計完了を示す情報が付与された前記要素が更新されているか否かを判断し、更新されているときは、前記既に記憶されている前記要素を、前記設計完了を示す情報が付与された前記要素に更新することを特徴とする設計成果物管理方法。     In the design deliverable management method according to claim 6,
    If the element to which the information indicating the design completion is already stored, it is determined whether or not the element to which the information indicating the design completion has been updated, and if it has been updated, 7. A design deliverable management method, wherein said already stored elements are updated to said elements to which information indicating completion of said design has been added.
  9. 　請求項６に記載の設計成果物管理方法において、
    　前記第１記憶部に記憶されていた前記設計情報と、前記設計作業が完了した前記グループの前記要素と、前記設計作業が完了した前記グループに必要な前記要素と、を前記第１記憶部に記憶させ、
    　前記第１記憶部に記憶された前記設計作業が完了した前記グループの前記要素と、前記設計作業が完了した前記グループに必要な前記要素と、を検出し、
    　検出した前記設計作業が完了した前記グループの前記要素と、前記設計作業が完了した前記グループに必要な前記要素と、を前記第２記憶部に記憶させることを特徴とする設計成果物管理方法。     In the design deliverable 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. remember,
    detecting the elements of the group for which the design work is completed and the elements required for the group for which the design work is completed, stored in the first storage unit;
    A design deliverable management method, wherein 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.
PCT/JP2021/031528 2021-01-22 2021-08-27 Design product management system and design product management method WO2022158021A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022576958A JP7406012B2 (en) 2021-01-22 2021-08-27 Design product management system and design product management method
DE112021005618.2T DE112021005618T5 (en) 2021-01-22 2021-08-27 DRAFT PRODUCT MANAGEMENT SYSTEM AND DRAFT PRODUCT MANAGEMENT PROCESS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021009163 2021-01-22
JP2021-009163 2021-01-22

Publications (1)

Publication Number Publication Date
WO2022158021A1 true WO2022158021A1 (en) 2022-07-28

Family

ID=82549661

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/031528 WO2022158021A1 (en) 2021-01-22 2021-08-27 Design product management system and design product management method

Country Status (3)

Country Link
JP (1) JP7406012B2 (en)
DE (1) DE112021005618T5 (en)
WO (1) WO2022158021A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001084020A (en) * 1999-09-09 2001-03-30 Fujitsu Ten Ltd Design process management device
JP2003006239A (en) * 2001-06-26 2003-01-10 Fujitsu Ltd Design program and designing apparatus
JP2008117114A (en) * 2006-11-02 2008-05-22 Incs Inc Design support system and program
JP2019191798A (en) * 2018-04-23 2019-10-31 富士ゼロックス株式会社 Information processing apparatus and program

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS5174079A (en) 1974-12-25 1976-06-26 Nippon Oils & Fats Co Ltd AKURIRONITORIRUNOKENDAKUJUGOHOHO

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001084020A (en) * 1999-09-09 2001-03-30 Fujitsu Ten Ltd Design process management device
JP2003006239A (en) * 2001-06-26 2003-01-10 Fujitsu Ltd Design program and designing apparatus
JP2008117114A (en) * 2006-11-02 2008-05-22 Incs Inc Design support system and program
JP2019191798A (en) * 2018-04-23 2019-10-31 富士ゼロックス株式会社 Information processing apparatus and program

Also Published As

Publication number Publication date
JPWO2022158021A1 (en) 2022-07-28
JP7406012B2 (en) 2023-12-26
DE112021005618T5 (en) 2023-08-24

Similar Documents

Publication Publication Date Title
TWI479341B (en) High throughput, reliable replication of transformed data in information systems
CN103608779B (en) Improvement that is pasting data or being related to pasting data
JP4100156B2 (en) Data conversion system
US20130159365A1 (en) Using Distributed Source Control in a Centralized Source Control Environment
Kano et al. U-Compare: A modular NLP workflow construction and evaluation system
WO2017033441A1 (en) System construction assistance system and method, and storage medium
TWI493368B (en) Automatic generation of a query lineage
EP4022452A1 (en) Document tracking through version hash linked graphs
JPH10254689A (en) Application constitution design supporting system for client/server system
JP2001306372A (en) Method for managing document and storage medium storing program for executing the method
CN100485687C (en) Method and device for set-up disconnection data programmed model and its application
WO2022158021A1 (en) Design product management system and design product management method
JP2006268121A (en) Web application system and program for the same
JP2011248852A (en) System cooperation apparatus
JP2003030016A (en) Method and system for converting data, and processing program therefor
Marjudi et al. A Review and Comparison of IGES and STEP
AU2016100156A4 (en) Data Structure, Model for Populating a Data Structure and Method of Programming a Processing Device Utilising a Data Structure
JP2010061200A (en) Document management system and operation history display method
JP3660390B2 (en) Term dictionary management device
JP2001056809A (en) Document managing system
JP5189880B2 (en) Class structure generation method, class structure generation program, and class structure generation apparatus
JP4957043B2 (en) Information processing apparatus, program, and business application introduction method
JP2702986B2 (en) How to replace data in a program
JPH11232089A (en) System and method for managing terms and recording medium
US20040172392A1 (en) Data conversion method and computer system therefor

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21921126

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022576958

Country of ref document: JP

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 21921126

Country of ref document: EP

Kind code of ref document: A1