WO2023276212A1 - ソフトウェア部品更新システム及びソフトウェア部品更新方法 - Google Patents
ソフトウェア部品更新システム及びソフトウェア部品更新方法 Download PDFInfo
- Publication number
- WO2023276212A1 WO2023276212A1 PCT/JP2022/002693 JP2022002693W WO2023276212A1 WO 2023276212 A1 WO2023276212 A1 WO 2023276212A1 JP 2022002693 W JP2022002693 W JP 2022002693W WO 2023276212 A1 WO2023276212 A1 WO 2023276212A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- software component
- software
- information
- tree
- database
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 18
- 238000000605 extraction Methods 0.000 claims abstract description 8
- 238000013461 design Methods 0.000 claims description 5
- 238000011161 development Methods 0.000 description 22
- 238000012545 processing Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 5
- 239000000284 extract Substances 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 238000007792 addition Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
Definitions
- the present invention relates to a software component database that stores software components that make up software and configuration management of product groups.
- the software component tree has multiple nodes representing variations of the software component.
- Patent Document 1 Japanese Unexamined Patent Application Publication No. 2010-33373
- the software configuration management system has a component-product correspondence table, component-file correspondence information, a synchronization section for mutually reflecting changes in the software component database and changes in the software product, update information, and a correspondence table update section.
- a software configuration management system is described (see abstract). The technique described in Patent Literature 1 can efficiently reflect update information of software components managed in a software component database to a product group.
- Patent Document 1 proposes a method for managing software component groups, which are core assets, it is also necessary to perform configuration management using a software component tree and work to reflect update information for project-specific component groups.
- a group of project-specific parts includes parts that cannot be shared with other projects due to reasons such as security requirements and ownership of rights.
- project development the group of software components reused from core assets and the group of project-specific components are updated or newly added.
- project assets the software component groups managed in the project are called project assets.
- project assets When the project assets are updated due to project development, it was a challenge to appropriately reflect the update information in the database of the core assets and the product group of the project according to the sharing range of the software components.
- Patent Document 1 does not describe a method for reflecting updates of software components stored in databases of multiple projects in databases of other projects or products according to the sharing range.
- a software component tree of core assets is required to extract software component groups necessary for a project from core assets.
- a software component tree of the project assets is required.
- Patent Literature 1 does not disclose a method of managing multiple software component trees and mutually reflecting update information.
- the present invention has been made in view of the above problems.
- the purpose is to update the tree and reflect the update information of software components in databases of other projects and product groups.
- the software component update system is composed of a computer having a processor and a memory, and includes software component tree information representing a plurality of software components in a tree format, tag information representing attributes of each of the software components, and the software components. connected to a first database and a second database for storing software component files including design information and source codes constituting components, based on the tag information and the software component tree information of the first database; a parts tree reconstruction unit for reconstructing the software parts tree of the second database; and identifying the software parts of the second database that need to be updated based on the reconstructed software parts tree. and a file updater for updating the software component file of the specified software component.
- the update information of the software components can be reflected in databases of other projects or product groups according to the sharing range of the software components.
- FIG. 1 is a diagram illustrating a configuration example of a software component update system of Example 1;
- FIG. 2 is a block diagram showing a hardware configuration example of the software component update system of Embodiment 1;
- FIG. 4 is a diagram showing a configuration example of a software component tree according to the first embodiment;
- FIG. 4 is a diagram showing a configuration example of tag selection information in Example 1.
- FIG. FIG. 12 is a diagram showing an example of a screen displaying difference information when updating the software component tree of the second embodiment; 4 is a flowchart of processing executed by the software component update system of the first embodiment;
- FIG. 1 is a diagram showing a configuration example of a software component update system 100 according to the first embodiment.
- the software component update system 100 of the present invention updates the asset A software component tree 111 and the asset Based on the tag selection information 123 of B, the asset B software parts tree 121 is rebuilt, and based on the rebuilt software parts tree, the software parts group that needs to be updated is identified, and the asset A database 110 is created. It is possible to reflect the update information of the software components included in the asset B software component database 122 included in the asset B database 120 .
- the software component update system 100 has an operation interface 101, a component tree reconstruction unit 102, a component extraction unit 103, and a file update unit 104. Details of the hardware configuration of the software component update system 100 will be described later with reference to FIG.
- the asset A database 110 and the asset B database 120 are asset databases that store information on arbitrary software component groups.
- Examples of software component groups stored in the asset databases 110 and 120 include core assets, which are software component groups that can be reused in multiple projects, and software components that can be reused in a specific project.
- core assets which are software component groups that can be reused in multiple projects, and software components that can be reused in a specific project.
- project assets that are groups, and software component groups that constitute a specific product.
- Each asset database 110 and 120 includes a software component tree 111 and 121 of each asset representing the configuration of the software component to be managed in a tree format, and a software component including design information and source code constituting the software component to be managed. It stores software component databases 112 and 122 for each asset storing files, and tag selection information 113 and 123 for each asset for specifying software components to be managed.
- the software component trees 111 and 121 have tag information 114a to 114d, 124a, and 124c representing attributes such as features of the software components included in each of the asset databases 110 and 120 as nodes constituting the tree.
- the code "114" or "124" with the subscript omitted is used when the individual is not specified. The same applies to the codes of other constituent elements.
- the tag information 114, 124 records, for example, software component function names, specific product names, security requirement information, functional safety support information, information on rights attribution, and other information representing versatility.
- the software component trees 111 and 121 of each asset hold dependency relationships and exclusive relationships of the tag information 114 and 124 as described later, and based on the combination of tags recorded in the asset A tag selection information 113 and 123, can derive all the tags necessary for the development of each asset. Details of the configuration of the software component trees 111 and 121 will be described later with reference to FIG.
- the tag selection information 113 and 123 is information recording a combination of tag information necessary for development of each asset among the tag information 114 and 124 included in the software component trees 111 and 121 of each asset. Furthermore, the tag selection information 113 and 123 of each asset also records tag information that is not shared with other assets, as will be described later. Details of information recorded in the tag selection information 113 and 123 will be described later with reference to FIG.
- the developer of asset B selects a plurality of tag information 114 of asset A representing the characteristics required for development of asset B from the asset A software parts tree 111, and the asset B software parts tree 121 is constructed.
- the combination of tag information selected by the developer of asset B at this time is recorded in the asset B tag selection information 123 .
- the tag information 114 a to 114 d are examples of the tag information 114 included in the asset A software component tree 111 .
- the tag information 114a and 114b indicate the tag information 114 of the asset A that existed when the development of the asset B was started, and the tag information 114c and 114d did not exist when the development of the asset B started and were updated later.
- the tag information 114 of the asset A newly added to the asset A software component tree 111 is shown.
- the tag information 114a is the tag T4 necessary for the development of the asset B, and indicates that it is reflected in the asset B software component tree 121 as the tag information 124a.
- the tag information 114b indicates that the tag T5 is unnecessary for the asset B and is not included in the asset B software component tree 121.
- the tag information 114c indicates a tag T6 that is newly added in the development of the asset A after the asset B software component tree 121 is constructed and that needs to be newly added to the asset B as the tag information 124c.
- the tag information 114d indicates the tag T7 that was newly added in the development of the asset A after the asset B software component tree 121 was built, but is not shared with the asset B.
- the update worker 130 uses the software component update system 100 to show the update information of the asset A to the user who performs the work to reflect it on the asset B.
- update operator 130 When reflecting the update information of asset A on asset B, update operator 130 updates asset A database 110 in software component update system 100 via operation interface 101 of software component update system 100, and update information. Address information for specifying the asset B database 120 to be reflected is input to the software component update system 100 .
- the parts tree reconstruction unit 102 identifies the asset A database 110 and the asset B database 120 based on the information input via the operation interface 101, and reconstructs the asset A software parts tree 111 and tag selection information from each asset database. 113, acquire the tag selection information 123 of asset B, and reconstruct the asset B software component tree 121 based on the information;
- the component extracting unit 103 Based on the software component tree reconstructed by the component tree reconstructing unit 102, the component extracting unit 103 identifies a software component group that needs to be updated, and stores the corresponding software component file in the asset A software component database 112. Extract from
- the file update unit 104 checks the difference between the software component file extracted by the component extraction unit 103 and the corresponding software component file stored in the asset B software component database 122, and reflects the update information.
- the update information is reflected in the software components that need to be reflected in the asset B database 120 among the software components updated in the asset A database 110 .
- FIG. 2 is a block diagram showing a hardware configuration example of the software component update system 100 of FIG.
- the software component update system 100 has a CPU 202, a memory 201, and a communication device 220, and each processing unit 101, 102, 103, and 104 shown in FIG. 1 is executed in each CPU.
- the memory 201 includes ROM, which is a non-volatile storage element, and RAM, which is a volatile storage element.
- the ROM stores immutable programs (eg, BIOS) and the like.
- RAM is a high-speed and volatile storage element such as DRAM (Dynamic Random Access Memory), and temporarily stores programs executed by CPU 202 and data used when the programs are executed.
- the CPU 202 is an arithmetic device that executes programs stored in the memory 201 . Note that part of the processing performed by the CPU 202 by executing the program may be performed by another arithmetic device (for example, hardware such as ASIC and FPGA).
- the CPU 202 operates as a functional unit that provides a predetermined function by executing the program of each functional unit.
- the software component update system 100 also has a storage device (not shown).
- the storage device is, for example, a large-capacity, non-volatile storage device such as a magnetic storage device (HDD) or flash memory (SSD).
- the storage device stores data used by the CPU 202 when executing programs and programs executed by the CPU 202 . That is, each functional unit of the operation interface 101 , the parts tree reconstruction unit 102 , the parts extraction unit 103 , and the file update unit 104 is loaded into the memory 201 as a program and executed by the CPU 202 .
- the software component update system 100 also has an input/output device 221 .
- the input/output device 221 includes, for example, an input device such as a mouse, a keyboard, or a touch panel, and an output device such as a display. Note that another device connected to the software component update system 100 via a network may provide the input/output device 221 .
- the program executed by the processor 1 is provided to the software component update system 100 via removable media (CD-ROM, flash memory, etc.) or network, and stored in a non-volatile storage device, which is a non-temporary storage medium. Therefore, the renewable energy certification management system should have an interface for reading data from removable media.
- the software component update system 100 is a computer system configured on one physical computer or on a plurality of logically or physically configured computers, and is built on a plurality of physical computer resources. It may run on a virtual machine. For example, the programs that make up the software component update system 100 may each run on separate physical or logical computers, or may be combined to run on one physical or logical computer.
- FIG. 3 is a diagram showing a configuration example of the software component trees 111 and 121 in FIG.
- the software component trees 111 and 121 have tag information 300, 310, 320, 330, and 340 representing features of software components as nodes constituting the trees.
- Each piece of tag information is associated with a software component.
- tag information 300 is associated with software component 301 and tag information 310 is associated with software component 311 .
- Information relating to software components and software component files may be managed by including it in the software component tree as part of the tag information, or may be managed by separately creating a correspondence table.
- the software component trees 111 and 121 have constraint information 361 and 362 representing dependency relationships and exclusive relationships between multiple pieces of tag information.
- the software component 301 associated with the upper tag information 300 of the tag information 310 is selected as the dependent software component. extracted. Furthermore, according to the constraint information 361, the software components 331 associated with the tag information 330 having a dependency relationship with the tag information 310 are extracted, and according to the constraint information 362, the software components 341 associated with the tag information 340 having an exclusive relationship are excluded. be done.
- a developer who modifies the asset A database 110 of FIG. Register association and constraint information.
- the software component update system 100 of this embodiment reflects the update information of the asset A software component tree 111 in the asset B software component tree 121 by the processing described later with reference to FIG.
- FIG. 4 is a diagram showing a configuration example of the tag selection information 113 and 123 in FIG.
- the tag selection information 113 and 123 is information about the tag usage status in the asset databases 110 and 120 in which the tag selection information 113 and 123 are stored for the tag information of the software component trees 111 and 121 .
- the table in FIG. 4 shows the relationship between tag types, target assets, and tags recorded as tag selection information 113 and 123.
- the tag type designates a selection tag or a non-shared tag depending on how the tag to be recorded is used.
- Information indicating target assets that do not share a specific tag is recorded in the target asset only if the tag type is a non-shared tag.
- the tag type is a selection tag
- a combination of tag information selected by the developer at the start of asset development from among the tag information possessed by the software component trees 111 and 121 is recorded in the tag.
- the tag type is a non-shared tag
- a list of tag information that is not shared with the target asset is recorded in the tag.
- the tag may record a regular expression representing specific tag information.
- the software component update system 100 of this embodiment deletes the unnecessary tag information 114 from the asset A software component tree 111 based on the tag selection information 113 and 123, and updates the update destination asset B software. Rebuild the parts tree 121 . As a result, the software components that need to be updated in the asset B database 120 can be identified from the reconstructed software component tree.
- the software component update system 100 includes address information for specifying the updated asset A database 110 and an address for specifying the asset B database 120 to which the update is to be reflected by the operation interface 101 of the update worker 130. Accept input of information.
- the software component update system 100 starts the update process with the input of the update worker 130 as a trigger, and executes the process of step S600.
- step S600 the parts tree reconstruction unit 102 copies the information of the asset A software parts tree 111 based on the address information specifying the asset databases 110 and 120 input by the update worker 130, and reproduces the information.
- a software component tree 611 for construction work is created.
- step S601 after acquiring the asset A tag selection information 113 from the asset A database 110, the parts tree reconstruction unit 102 selects the tag type "non-shared tag" and the target asset "asset B ” as a search key to obtain a list of tags that are not shared with asset B. After that, the parts tree reconstruction unit 102 deletes the tag information that matches the tag described in the tag list that is not shared with the asset B from the tag information 114 included in the software parts tree 611 for reconstruction work. At this time, the child node associated with the tag information to be deleted is also deleted.
- step S602 after acquiring the asset B tag selection information 123 from the asset B database 120, the parts tree reconstruction unit 102 uses the tag type "selection tag" as a search key to retrieve the asset B A combination of tags selected by the developer when constructing the software component tree 121 is acquired. After that, the parts tree reconstruction unit 102 identifies tag information that can be derived from the combination of the acquired tags among the tag information 114 based on the constraint information 361 and 362 included in the software parts tree 611 for reconstruction work. Then, the other tag information is deleted, and a reconstructed software component tree 614 is created. At this time, as in step S601, the child node linked to the tag information to be deleted is also deleted. The parts tree reconstruction unit 102 then outputs the reconstructed software parts tree 614 to the parts extraction unit 103 .
- step S603 the component extracting unit 103 receives the reconstructed software component tree 614 from the component tree reconstructing unit 102, and extracts the software component list associated with the tag information included in the software component tree 614 from the software components to be updated. Output as 615.
- step S604 the component extraction unit 103 extracts the software component file 616 to be updated from the asset A software component database 112 based on the software component 615 to be updated, and extracts the reconstructed software component tree 614 and the software component file to be updated. 616 is output to the file update unit 104 .
- step S605 the file updating unit 104 receives the reconstructed software component tree 614 and the software component file 616 to be updated from the component extracting unit 103, and merges the reconstructed software component tree 614 with the asset B software component tree 121.
- the file update unit 104 also merges the software component file 616 to be updated with the software component file included in the asset B software component database 122 . This will reflect the update.
- update conflicts are taken into consideration, and if conflicts occur, they are not merged, and the update operator 130 is notified of the conflicts via the operation interface 101.
- the update processing by the software component update system 100 is now complete, and the update information of the software components that need to be reflected in the asset B database 120 among the software components updated in the asset A database 110 are reflected.
- the software component tree 111 included in the asset A database 110 and the software components included in the asset A database 110 are updated by the software component update system 100, among the software components updated in the asset A,
- the update information of the software component can be reflected in the asset B software component database 122 included in the asset B database 120 . Therefore, even when software component groups with different shared ranges are managed, the configuration management of software components and the work of updating and reflecting updates to multiple projects and product groups can be made more efficient.
- Example 2 A second embodiment will be described with reference to FIG.
- the file update unit 104 of the software component update system 100 performs processing different from that in the first embodiment when reflecting the update of the software component tree and software components in step S605 of FIG. Since other configurations and processes are the same as those of the first embodiment, description thereof is omitted.
- the update operator 130 when the software component update system 100 reflects the update information on the asset B database 120, the update operator 130 receives the difference information of the asset B software component tree 121 before and after the update and the asset B software component. By visually presenting the difference information of the database 122, the update operator 130 can efficiently grasp the update contents of the software components and select the update information to be reflected as necessary for development.
- FIG. 5 is a diagram showing an example of a screen displaying difference information when the file update unit 104 of this embodiment updates the software component tree.
- the file update unit 104 of this embodiment merges the software component tree 614 reconstructed in step S605 of FIG. indicate.
- the file update unit 104 displays, for example, the name of the asset A whose software component has been updated, the name of the asset B to which the update is reflected, the software component tree difference information 510 and the software component file difference information 520 on the difference information display screen 500 . Generate data for display in .
- the software component tree difference information 510 is an example of visualizing the difference information between the reconstructed software component tree 614 and the tag information 124 of the asset B software component tree 121 .
- the tag difference information 511 represents tag information that is not updated among the tag information 124 of the asset B.
- the tag update display 512 shows that the software component associated with the corresponding tag information of the tag information 124 included in both asset A and asset B is changed due to the development of asset A, and the update is reflected in the asset B database 120. indicates that A tag update display 513 indicates tag information newly added to the asset B database 120 among tag information newly added to the asset A software component tree 111 .
- the software component file difference information 520 displays the difference information between the software component file 616 to be updated and the software component file contained in the asset B software component database 122 in tabular form. At this time, a combination of the name of the software component file to be updated (Filename) and the update status (Status) is displayed. The update status (Status) displays addition (Add), change (Modified), deletion (Delete), etc. according to the update status of the file.
- the update operator 130 can refer to the information displayed on the difference information display screen 500 and edit the changes to the asset B software parts tree 121 and software parts files using a file explorer or the like.
- the update operator 130 when the software component update system 100 reflects update information on the asset B database 120, the update operator 130 is asked to update the asset B software component tree 121 and the asset B software component database 122 before and after the update. By visually presenting the difference information, the update operator 130 can efficiently grasp the update contents of the software component.
- the software component update system 100 includes software component tree information 111 and 121 representing a plurality of software components in a tree format, tag information representing attributes of each software component, Connect to a first database (assets A database 110) and a second database (assets B database 120) that store software parts files (software parts databases 112, 122) containing design information and source codes that constitute software parts.
- a parts tree reconstruction unit 102 for reconstructing the software parts tree of the second database 120 based on the tag information and the software parts tree information 111 of the first database 110; and the reconstructed software parts tree and a file update unit 104 for updating the software component files of the specified software component files.
- update information of the software components can be reflected in databases of other projects or product groups according to the sharing range of the software components. Furthermore, update information can also be reflected in the software component tree of each asset, making configuration management of software components and work to reflect updates to multiple projects and product groups more efficient.
- the first database 110 and the second database 120 store tag selection information 113 and 123 that record combinations of tag information for identifying software components to be managed, and the component tree reconstruction unit 102 Since the software parts tree of the second database 120 is reconstructed based on the tag selection information 113, the tag information, and the software parts tree information 111 of the first database 110, it is reflected in the software parts tree of the second database 120. It is possible to delete those that are not required, to identify necessary updates in the software component tree of the second database 120, and to accurately select those that should be reflected in the software component tree of the second database 120.
- the file update unit 104 generates display data for displaying software component tree information and software component difference information before and after updating on the screen, so that system operation can be presented to the user and updated files can be displayed in an easy-to-understand manner. can.
- the present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the scope of the attached claims.
- the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the described configurations.
- part of the configuration of one embodiment may be replaced with the configuration of another embodiment.
- the configuration of another embodiment may be added to the configuration of one embodiment.
- additions, deletions, and replacements of other configurations may be made to a part of the configuration of each embodiment.
- each configuration, function, processing unit, processing means, etc. described above may be realized by hardware, for example, by designing a part or all of them with an integrated circuit, and the processor realizes each function. It may be realized by software by interpreting and executing a program to execute.
- Information such as programs, tables, and files that implement each function can be stored in storage devices such as memory, hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.
- storage devices such as memory, hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.
- control lines and information lines indicate those that are considered necessary for explanation, and do not necessarily indicate all the control lines and information lines necessary for implementation. In practice, it can be considered that almost all configurations are interconnected.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
Description
図1は、実施例1のソフトウェア部品更新システム100の構成例を示す図である。
実施例2について図5を参照して説明する。実施例2では、ソフトウェア部品更新システム100のファイル更新部104が図6のステップS605において、ソフトウェア部品ツリー及びソフトウェア部品の更新を反映する際に、実施例1とは異なる処理を行う。その他の構成や処理については、実施例1と同じであるため説明を省略する。
Claims (6)
- ソフトウェア部品更新システムであって、
プロセッサ及びメモリを有する計算機によって構成され、
複数のソフトウェア部品をツリー形式で表すソフトウェア部品ツリー情報と、前記ソフトウェア部品のそれぞれの属性を表すタグ情報と、前記ソフトウェア部品を構成する設計情報及びソースコードを含むソフトウェア部品ファイルとを記憶する第1のデータベース及び第2のデータベースに接続されており、
前記タグ情報及び前記第1のデータベースのソフトウェア部品ツリー情報に基づいて、前記第2のデータベースのソフトウェア部品ツリーを再構築する部品ツリー再構築部と、
前記再構築されたソフトウェア部品ツリーに基づいて、更新の反映が必要な前記第2のデータベースの前記ソフトウェア部品を特定する部品抽出部と、
前記特定されたソフトウェア部品のソフトウェア部品ファイルを更新するファイル更新部と、を有することを特徴とするソフトウェア部品更新システム。 - 請求項1に記載のソフトウェア部品更新システムであって、
前記第1のデータベース及び前記第2のデータベースは、管理対象のソフトウェア部品を特定するための前記タグ情報の組合せを記録したタグ選択情報を記憶し、
前記部品ツリー再構築部は、前記タグ選択情報、前記タグ情報、及び前記第1のデータベースのソフトウェア部品ツリー情報に基づいて、前記第2のデータベースのソフトウェア部品ツリーを再構築することを特徴とするソフトウェア部品更新システム。 - 請求項1に記載のソフトウェア部品更新システムであって、
前記ファイル更新部は、前記ソフトウェア部品ツリー情報及び前記ソフトウェア部品の更新前後の差分情報を画面に表示するための表示データを生成することを特徴とするソフトウェア部品更新システム。 - プロセッサ及びメモリを有する計算機が実行するソフトウェア部品更新方法であって、
前記計算機は、複数のソフトウェア部品をツリー形式で表すソフトウェア部品ツリー情報と、前記ソフトウェア部品のそれぞれの属性を表すタグ情報と、前記ソフトウェア部品を構成する設計情報及びソースコードを含むソフトウェア部品ファイルとを記憶する第1のデータベース及び第2のデータベースに接続されており、
前記ソフトウェア部品更新方法は、
前記プロセッサが、前記タグ情報及び前記第1のデータベースのソフトウェア部品ツリー情報に基づいて、前記第2のデータベースのソフトウェア部品ツリーを再構築する部品ツリー再構築ステップと、
前記プロセッサが、前記再構築されたソフトウェア部品ツリーに基づいて、更新の反映が必要な前記第2のデータベースの前記ソフトウェア部品を特定する部品抽出ステップと、
前記プロセッサが、前記特定されたソフトウェア部品のソフトウェア部品ファイルを更新するファイル更新ステップと、を有することを特徴とするソフトウェア部品更新方法。 - 請求項4に記載のソフトウェア部品更新方法であって、
前記第1のデータベース及び前記第2のデータベースは、管理対象のソフトウェア部品を特定するための前記タグ情報の組合せを記録したタグ選択情報を記憶し、
前記部品ツリー再構築ステップでは、前記プロセッサが、前記タグ選択情報、前記タグ情報、及び前記第1のデータベースのソフトウェア部品ツリー情報に基づいて、前記第2のデータベースのソフトウェア部品ツリーを再構築することを特徴とするソフトウェア部品更新方法。 - 請求項4に記載のソフトウェア部品更新方法であって、
前記ファイル更新ステップでは、前記プロセッサが、前記ソフトウェア部品ツリー情報及び前記ソフトウェア部品の更新前後の差分情報を画面に表示するための表示データを生成することを特徴とするソフトウェア部品更新方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/550,882 US20240086179A1 (en) | 2021-06-28 | 2022-01-25 | Software component update system, and software component update method |
JP2023531354A JPWO2023276212A1 (ja) | 2021-06-28 | 2022-01-25 | |
EP22832380.4A EP4365730A1 (en) | 2021-06-28 | 2022-01-25 | Software component update system, and software component update method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021-106330 | 2021-06-28 | ||
JP2021106330 | 2021-06-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023276212A1 true WO2023276212A1 (ja) | 2023-01-05 |
Family
ID=84692232
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/002693 WO2023276212A1 (ja) | 2021-06-28 | 2022-01-25 | ソフトウェア部品更新システム及びソフトウェア部品更新方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240086179A1 (ja) |
EP (1) | EP4365730A1 (ja) |
JP (1) | JPWO2023276212A1 (ja) |
WO (1) | WO2023276212A1 (ja) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009205190A (ja) * | 2008-02-26 | 2009-09-10 | Hitachi Ltd | ソフトウェア自動構成装置 |
WO2010013538A1 (ja) * | 2008-07-29 | 2010-02-04 | 株式会社日立製作所 | ソフトウェア構成管理方法およびシステム |
JP2021106330A (ja) | 2019-12-26 | 2021-07-26 | キヤノン株式会社 | 情報処理装置、情報処理方法、及びプログラム |
-
2022
- 2022-01-25 WO PCT/JP2022/002693 patent/WO2023276212A1/ja active Application Filing
- 2022-01-25 EP EP22832380.4A patent/EP4365730A1/en active Pending
- 2022-01-25 US US18/550,882 patent/US20240086179A1/en active Pending
- 2022-01-25 JP JP2023531354A patent/JPWO2023276212A1/ja active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009205190A (ja) * | 2008-02-26 | 2009-09-10 | Hitachi Ltd | ソフトウェア自動構成装置 |
WO2010013538A1 (ja) * | 2008-07-29 | 2010-02-04 | 株式会社日立製作所 | ソフトウェア構成管理方法およびシステム |
JP2010033373A (ja) | 2008-07-29 | 2010-02-12 | Hitachi Ltd | ソフトウェア構成管理方法およびシステム |
JP2021106330A (ja) | 2019-12-26 | 2021-07-26 | キヤノン株式会社 | 情報処理装置、情報処理方法、及びプログラム |
Non-Patent Citations (1)
Title |
---|
"Lecture Notes/Software Studies 19 - Foundations of Software Engineering IV", 1 January 1997, MODERN SCIENCE SOCIETY, JP, ISBN: 4-7649-0264-8, article KUMOKIRI, KEITA; ODA, TAKESHI: "Distributed software repositories with disclosure range control", pages: 131 - 134, XP009543290 * |
Also Published As
Publication number | Publication date |
---|---|
US20240086179A1 (en) | 2024-03-14 |
EP4365730A1 (en) | 2024-05-08 |
JPWO2023276212A1 (ja) | 2023-01-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11971945B2 (en) | System for synchronization of changes in edited websites and interactive applications | |
US8606752B1 (en) | Method and system of restoring items to a database while maintaining referential integrity | |
JP6024559B2 (ja) | プログラムおよびバージョン管理方法 | |
Barmpis et al. | Hawk: Towards a scalable model indexing architecture | |
CN109952564A (zh) | 数据库系统中测试数据的形成与操纵 | |
US20110295794A1 (en) | System and method for supporting data warehouse metadata extension using an extender | |
US10540371B2 (en) | Systems and methods for synchronizing database schema | |
US20040015486A1 (en) | System and method for storing and retrieving data | |
JP6598996B2 (ja) | データ準備のためのシグニチャベースのキャッシュ最適化 | |
US8027997B2 (en) | System and article of manufacture for defining and generating a viewtype for a base model | |
US20110208700A1 (en) | Method for carrying out database version control | |
JP2006172446A (ja) | 複合データアクセス | |
US20110153562A1 (en) | Error prevention for data replication | |
US11409505B1 (en) | Automated authoring of software solutions from a data model with related patterns | |
JP6598997B2 (ja) | データ準備のためのキャッシュ最適化 | |
De Jong et al. | Zero-downtime SQL database schema evolution for continuous deployment | |
JP2001306372A (ja) | 文書管理方法およびその方法を実施するためのプログラムを記憶した記憶媒体 | |
JPH0550774B2 (ja) | ||
JP7279524B2 (ja) | データ管理プログラム、データ管理方法およびデータ管理システム | |
WO2023276212A1 (ja) | ソフトウェア部品更新システム及びソフトウェア部品更新方法 | |
JP2018109898A (ja) | データマイグレーションシステム | |
CN113886505A (zh) | 一种基于搜索引擎和关系型数据库实现动态建模的管理系统 | |
WO2023223424A1 (ja) | ドキュメント生成装置、プログラム及びドキュメント生成方法 | |
Schneller et al. | MySQL admin cookbook | |
JP2003208346A (ja) | データベース更新情報の反映システムおよびそのためのプログラム |
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: 22832380 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023531354 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18550882 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022832380 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022832380 Country of ref document: EP Effective date: 20240129 |