Software component update system and software component update method

The software component update system addresses the challenge of reflecting updates across projects with different sharing scopes by using a computer system to manage and update software component trees, enhancing efficiency and accuracy in software component database management.

JP7579451B2Active Publication Date: 2024-11-07ASTEMO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023531354
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-06-28
Filing Date
2022-01-25
Publication Date
2024-11-07
Estimated Expiration
2042-01-25

AI Technical Summary

Technical Problem

Existing software component management systems struggle to efficiently reflect update information across multiple projects and product groups, particularly for components with different sharing scopes, requiring significant manual effort to manage and update software component trees.

Method used

A software component update system that includes a computer system with a processor and memory, utilizing software component tree information, tag information, and a parts tree reconstruction unit to identify and update software components across databases based on sharing scopes, efficiently reflecting updates in databases of other projects or product groups.

Benefits of technology

The system enables efficient management and reflection of update information across projects and product groups with different sharing scopes, reducing manual effort and ensuring accurate and timely updates in software component databases.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579451000001
    Figure 0007579451000001
  • Figure 0007579451000002
    Figure 0007579451000002
  • Figure 0007579451000003
    Figure 0007579451000003
Patent Text Reader

Abstract

Provided is a software component update system connected to a first database and a second database, the software component update system having: a component tree reconstruction unit for reconstructing a software component tree in the second database on the basis of tag information and software component tree information in the first database; a component extraction unit for identifying, on the basis of the reconstructed software component tree, the software component in the second database for which the update needs to be reflected; and a file update unit for updating a software component file of the identified software component.
Need to check novelty before this filing date? Find Prior Art

Description

Incorporation by Reference

[0001] This application claims priority to Japanese Patent Application No. 2021-106330, filed on June 28, 2021, the contents of which are incorporated herein by reference. [Technical field]

[0002] The present invention relates to a software component database that stores software components that constitute software, and to configuration management of a product group. [Background technology]

[0003] In recent years, development techniques that reuse existing software components by combining them as needed have become widely used as a method for efficiently developing new software products.

[0004] One method for managing software components is to build a tree model that associates software variability with software components. In this specification, this model is called a software component tree. A software component tree has multiple nodes that represent the variations of software components.

[0005] When developing a new product, developers can select a node that matches the new product from the software component tree, and efficiently select and extract software components that can be reused in the product.When developing software components in parallel in multiple projects with this management method, it is necessary to reflect update information of the files that make up the software components in other projects and software products, but this task requires a lot of man-hours, which is an issue.

[0006] The following prior art exists as background technology in this technical field. Patent Document 1 (JP 2010-33373 A) describes a software configuration management system that includes a software component database and a software product management unit, and receives data transmission and reception from a software component database management client and a software product operation client. The software configuration management system includes a component-product correspondence table, component-file correspondence information, a synchronization unit that reflects changes in the software component database and changes in the software product, update information, and a correspondence table update unit (see Abstract). The technology described in Patent Document 1 makes it possible to efficiently reflect update information of software components managed in the software component database in a group of products. Summary of the Invention [Problem to be solved by the invention]

[0007] In large-scale development projects, in addition to software components that can be reused in multiple projects, there are also software components that can be reused only in the products of a specific project. Hereinafter, in this application, the software components that can be reused in multiple projects are referred to as core assets, and the software components that can be reused only in the products of a specific project are referred to as project-specific components.

[0008] Patent Document 1 proposes a method for managing software components that are core assets, but project-specific components also require configuration management using a software component tree and updating information. Project-specific components include those that cannot be shared with other projects due to security requirements, rights attribution, and other reasons.

[0009] In project development, software components reused from core assets and project-specific components are updated or newly added. In a project, it is necessary to collectively manage these software components used in project development, and the software components managed by a project are called project assets. When project assets are updated in project development, the challenge is to appropriately reflect the update information in the databases of core assets and project products according to the scope of sharing of software components.

[0010] However, Patent Document 1 does not disclose a method for reflecting updates to software components stored in databases of multiple projects in the databases of other projects or products according to the scope of sharing.

[0011] Furthermore, in order to maintain the relationships between the software components contained in each asset, it is necessary to manage the configuration of software components using a software component tree for each asset. For example, a software component tree for core assets is required to extract the software components required for a project from the core assets. Also, a software component tree for project assets is required to extract the software components required for a product from the project assets.

[0012] When new software components are added through the development of each asset, the differences between each software component tree must be checked and, depending on the need for reuse, the update information must be reflected in other software component trees, and this reflection work requires an enormous amount of man-hours, which is a problem. However, Patent Document 1 does not disclose a method for managing multiple software component trees and mutually reflecting update information.

[0013] The present invention has been made in consideration of the above problems, and has an object to update the software component trees of other projects or product groups in accordance with the shared range of the software components, even when multiple projects develop software components with different shared ranges, and to reflect the update information of the software components in the databases of the other projects or product groups. [Means for solving the problem]

[0014] A representative example of the invention disclosed in the present application is as follows: That is, a software component updating system is configured by a computer having a processor and a memory, is connected to a first database and a second database storing 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 software component files including design information and source code constituting the software components, and is characterized by having: a part tree reconstruction unit that reconstructs the software component tree of the second database based on the tag information and the software component tree information of the first database, a part extraction unit that identifies the software components of the second database that require updates based on the reconstructed software component tree, and a file updating unit that updates the software component files of the identified software components. Effect of the Invention

[0015] According to one aspect of the present invention, even if there are software components with different sharing ranges, update information of the software components can be reflected in the databases of other projects or product groups according to the sharing range of the software components. Problems, configurations, and effects other than those described above will become apparent from the description of the embodiments below. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 illustrates an example of a configuration of a software component update system according to a first embodiment. [Diagram 2] 1 is a block diagram illustrating an example of a hardware configuration of a software component updating system according to a first embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of the configuration of a software component tree according to the first embodiment. [Figure 4] FIG. 11 is a diagram illustrating a configuration example of tag selection information according to the first embodiment. [Diagram 5] FIG. 11 is a diagram illustrating an example of a screen that displays difference information when updating a software component tree according to the second embodiment. [Figure 6] 4 is a flowchart of a process executed by the software component update system according to the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Hereinafter, the embodiments will be described in detail with reference to the drawings.

[0018] <Example 1> FIG. 1 is a diagram illustrating an example of the configuration of a software component updating system 100 according to the first embodiment.

[0019] In this embodiment, when the software component tree 111 contained in the asset A database 110 and the software components contained in the asset A database 110 are updated, the software component update system 100 of the present invention reconstructs the asset B software component tree 121 based on the asset A software component tree 111 and the tag selection information 123 of asset B, and identifies a group of software components for which updates need to be reflected based on the reconstructed software component tree, making it possible to reflect the update information of the software components contained in the asset A database 110 in the asset B software component database 122 contained in the asset B database 120.

[0020] The software component updating system 100 includes an operation interface 101, a component tree reconstructing unit 102, a component extracting unit 103, and a file updating unit 104. The details of the hardware configuration of the software component updating system 100 will be described later with reference to FIG.

[0021] The asset A database 110 and the asset B database 120 are asset databases that store information on any group of software components. Examples of the software components stored in the asset databases 110 and 120 include core assets, which are software components that can be reused in multiple projects, as described in the above-mentioned problem, project assets, which are software components that can be reused in a specific project, and software components that constitute a specific product.

[0022] Each asset database 110 and 120 stores, respectively, a software component tree 111 and 121 for each asset that represents the configuration of the software components to be managed in tree format, a software component database 112 and 122 for each asset that stores software component files including design information and source code that configure the software components to be managed, and tag selection information 113 and 123 for each asset for identifying the software components to be managed.

[0023] The software component trees 111 and 121 have, as nodes constituting the tree, tag information 114a to 114d, 124a, and 124c that indicate attributes such as features of the software components contained in the asset databases 110 and 120, respectively.

[0024] In addition, when the tag information of each asset does not need to be identified, the subscript is omitted and the code "114" or "124" is used. The same applies to the codes of the other components.

[0025] The tag information 114, 124 records, for example, the functional name of the software component, a specific product name, security requirement information, functional safety compliance information, information regarding ownership of rights, and other information indicating versatility.

[0026] Furthermore, as will be described later, the software component trees 111 and 121 for each asset hold the dependency and exclusive relationships of the tag information 114, 124, and can derive all tags necessary for the development of each asset based on the combinations of tags recorded in the asset A tag selection information 113 and 123. The details of the configuration of the software component trees 111 and 121 will be described later with reference to FIG.

[0027] The tag selection information 113 and 123 is information that records a combination of tag information necessary for the development of each asset from among the tag information 114 and 124 contained 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 the information recorded in the tag selection information 113 and 123 will be described later with reference to FIG.

[0028] When starting development of asset B, the developer of asset B selects multiple pieces of asset A tag information 114 that indicate features required for the development of asset B from the asset A software component tree 111, and an asset B software component tree 121 is constructed. The combination of tag information selected by the developer of asset B at this time is recorded in asset B tag selection information 123.

[0029] Tag information 114a to 114d are examples of tag information 114 included in the asset A software component tree 111. Of these, tag information 114a and 114b indicate tag information 114 of asset A that existed when development of asset B began, while tag information 114c and 114d indicate tag information 114 of asset A that did not exist when development of asset B began and was newly added to the asset A software component tree 111 through a later update.

[0030] Tag information 114a indicates that tag T4 is necessary for the development of asset B, and is reflected as tag information 124a in asset B software component tree 121. On the other hand, tag information 114b indicates that tag T5 is unnecessary for asset B, and is not included in asset B software component tree 121.

[0031] Tag information 114c indicates tag T6 that was newly added in the development of asset A after the asset B software component tree 121 was constructed, and that needs to be newly added as tag information 124c to asset B as well. Tag information 114d indicates tag T7 that was newly added in the development of asset A after the asset B software component tree 121 was constructed, but is not shared with asset B.

[0032] The update operator 130 uses the software component update system 100 to show the update information of asset A to the user who will carry out the work of reflecting the information in asset B.

[0033] An overview of the processing performed in the software component updating system 100 will be described below with reference to Fig. 1. The details of the processing performed in the software component updating system 100 will be described later with reference to Fig. 6.

[0034] When reflecting the update information of asset A in asset B, an update operator 130 inputs, via the operation interface 101 of the software component update system 100, the asset A database 110 updated in the software component update system 100 and address information for identifying the asset B database 120 to which the update will be reflected, into the software component update system 100.

[0035] The component 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, obtains the asset A software component tree 111, tag selection information 113, and asset B tag selection information 123 from each asset database, and reconstructs the asset B software component tree 121 based on that information.

[0036] The component extraction unit 103 identifies a group of software components that need to be updated based on the software component tree reconstructed by the component tree reconstruction unit 102 , and extracts the corresponding software component files from the asset A software component database 112 .

[0037] 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.

[0038] Through the above processing, the update information is reflected in those software components that need to be reflected in the asset B database 120, among the software components updated in the asset A database 110.

[0039] FIG. 2 is a block diagram showing an example of a hardware configuration of the software component updating system 100 of FIG.

[0040] The software component updating system 100 includes a CPU 202, a memory 201, and a communication device 220, and each of the CPUs executes the processing units 101, 102, 103, and 104 shown in FIG.

[0041] The memory 201 includes a ROM, which is a non-volatile storage element, and a RAM, which is a volatile storage element. The ROM stores unchanging programs (e.g., BIOS) and the like. The RAM is a high-speed, volatile storage element such as a DRAM (Dynamic Random Access Memory), and temporarily stores programs executed by the CPU 202 and data used when the programs are executed.

[0042] The CPU 202 is a calculation device that executes the programs stored in the memory 201. Note that some of the processes performed by the CPU 202 executing the programs may be executed by other calculation devices (e.g., hardware such as ASIC and FPGA). The CPU 202 operates as a functional unit that provides a predetermined function by executing the programs of each functional unit.

[0043] The software component updating 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 a flash memory (SSD). The storage device stores data used by the CPU 202 when executing a program, and the program executed by the CPU 202. That is, each of the functional units, the operation interface 101, the component tree reconstruction unit 102, the component extraction unit 103, and the file update unit 104, is loaded into the memory 201 as a program and executed by the CPU 202.

[0044] The software component update system 100 also has an input / output device 221. The input / output device 221 is composed of an input device such as a mouse, a keyboard, or a touch panel, and an output device such as a display. Note that the input / output device 221 may be provided by another device connected to the software component update system 100 via a network.

[0045] The programs executed by the processor 1 are provided to the software component update system 100 via a removable medium (such as a CD-ROM or a flash memory) or a network, and are stored in a non-volatile storage device, which is a non-transitory storage medium. For this reason, the renewable energy authentication management system may have an interface for reading data from the removable medium.

[0046] The software component update system 100 is a computer system configured on one physical computer, or on multiple logically or physically configured computers, and may operate on a virtual computer constructed on multiple physical computer resources. For example, the programs that configure the software component update system 100 may each operate on separate physical or logical computers, or multiple programs may be combined to operate on a single physical or logical computer.

[0047] FIG. 3 is a diagram showing an example of the configuration of the software component trees 111 and 121 in FIG.

[0048] The software component trees 111 and 121 have, as nodes constituting the tree, tag information 300, 310, 320, 330, and 340 that indicate the characteristics of the software components.

[0049] Each piece of tag information is associated with a software component. For example, tag information 300 is associated with software component 301, and tag information 310 is associated with software component 311. Association information between software components and software component files may be managed by being included in a software component tree as part of the tag information, or may be managed by creating a separate correspondence table.

[0050] Furthermore, the software component trees 111 and 121 have constraint information 361, 362 that represents the dependency and exclusive relationships between multiple pieces of tag information. When starting development of a new asset such as a new project or product, by specifying tag information that matches the characteristics of the development target from the base software component tree, it is possible to identify software components required for development based on the hierarchical structure of the tag information and constraint information, and to construct a software component tree for the new asset.

[0051] For example, if only the tag information 300 is selected, only the associated software component 301 can be reused.

[0052] Also, for example, when tag information 310 is selected, in addition to software component 311 associated with tag information 310, software component 301 associated with higher-level tag information 300 of tag information 310 is extracted as software components in a dependent relationship. Furthermore, software component 331 associated with tag information 330 in a dependent relationship with tag information 310 is extracted in accordance with constraint information 361, and software component 341 associated with tag information 340 in an exclusive relationship in accordance with constraint information 362 is excluded.

[0053] When a developer who modifies the asset A database 110 in Figure 1 adds a new software component during the development process, the developer adds tag information for the newly developed software component to the asset A software component tree 111, associates it with the software component, and registers constraint information.

[0054] The software component updating 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 a process that will be described later with reference to FIG.

[0055] FIG. 4 is a diagram showing an example of the configuration of the tag selection information 113 and 123 in FIG.

[0056] The tag selection information 113 and 123 is information about the tag information held by the software component trees 111 and 121, and is information about the usage status of tags in the asset databases 110 and 120 in which the tag selection information 113 and 123 is stored.

[0057] The table in FIG. 4 shows the relationship between the tag type, the target asset, and the tag, which are recorded as the tag selection information 113 and 123.

[0058] In the tag selection information 113 and 123, the tag type is specified as a selected tag or a non-shared tag depending on the usage method of the tag to be recorded. Only when the tag type is a non-shared tag, information indicating a target asset that does not share a specific tag is recorded in the target asset.

[0059] When the tag type is a selection tag, a combination of tag information selected by a developer at the start of development of an asset from among the tag information held by the software component trees 111 and 121 is recorded in the tag.

[0060] Furthermore, if 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.

[0061] In addition to recording tag information as it is, a regular expression expressing specific tag information may be recorded in the tag.

[0062] As will be described later, the software component updating system 100 of this embodiment deletes unnecessary tag information 114 from the asset A software component tree 111 based on the tag selection information 113 and 123, and reconstructs the updated asset B software component tree 121. This makes it possible to identify software components that need to have their updates reflected in the asset B database 120 from the reconstructed software component tree.

[0063] An example of a processing flow of the first embodiment will be described with reference to FIG.

[0064] The software component update system 100 accepts input, via the operation interface 101 of the update worker 130, of address information for identifying the updated asset A database 110 and address information for identifying the asset B database 120 to which the update will be reflected.

[0065] The software component update system 100 starts the update process triggered by an input from the update operator 130, and executes the process of step S600.

[0066] In step S600, the part tree reconstruction unit 102 copies the information of the asset A software part tree 111 based on the address information identifying each asset database 110 and 120 entered by the update worker 130, and creates a software part tree 611 for the reconstruction work.

[0067] In step S601, the part tree reconstruction unit 102 acquires asset A tag selection information 113 from the asset A database 110, and then acquires a list of tags not shared with asset B from the asset A tag selection information 113, using the tag type "non-shared tag" and the target asset "asset B" as search keys. The part tree reconstruction unit 102 then deletes tag information that matches tags listed in the list of tags not shared with asset B from among the tag information 114 included in the software component tree 611 for reconstruction work. At this time, it also deletes child nodes associated with the tag information to be deleted.

[0068] In step S602, the component tree reconstruction unit 102 acquires asset B tag selection information 123 from the asset B database 120, and then acquires from the asset B tag selection information 123 the tag combination selected by the developer when constructing the asset B software component tree 121, using the tag type "selected tag" as a search key. The component tree reconstruction unit 102 then identifies tag information from tag information 114 that can be derived from the acquired tag combination, based on constraint information 361, 362 included in the software component tree 611 for reconstruction work, deletes other tag information, and creates a reconstructed software component tree 614. At this time, as in step S601, it also deletes child nodes linked to the tag information to be deleted. The component tree reconstruction unit 102 then outputs the reconstructed software component tree 614 to the component extraction unit 103.

[0069] In step S603, the component extraction unit 103 receives the reconstructed software component tree 614 from the component tree reconstruction unit 102, and outputs a list of software components associated with tag information included in the software component tree 614 as software components 615 to be updated.

[0070] In step S604, the part extraction unit 103 extracts a software part file 616 to be updated from the asset A software part database 112 based on the software part 615 to be updated, and outputs the reconstructed software part tree 614 and the software part file 616 to be updated to the file update unit 104.

[0071] In step S605, the file update unit 104 receives the reconstructed software part tree 614 and the software part file 616 to be updated from the part extraction unit 103, and merges the reconstructed software part tree 614 into the asset B software part tree 121. The file update unit 104 also merges the software part file 616 to be updated into the software part file included in the asset B software part database 122, thereby reflecting the update.

[0072] When merging, update conflicts are taken into consideration, and if a conflict occurs, the merge is not performed and the update operator 130 is notified of the conflict via the operation interface 101.

[0073] This completes the update process by the software component update system 100, and update information for software components that need to be reflected in the asset B database 120, among the software components updated in the asset A database 110, is reflected.

[0074] According to this embodiment, when the software component tree 111 contained in the asset A database 110 and the software components contained in the asset A database 110 are updated, the software component update system 100 can identify a group of software components that need to have the updates reflected in asset B, from among the software components updated in asset A, and can reflect the update information of the software components in the asset B software component database 122 contained in the asset B database 120. Therefore, even when managing software component groups with different sharing scopes, it is possible to efficiently manage the configuration of software components and to efficiently reflect updates to multiple projects and product groups.

[0075] <Example 2> A second embodiment will be described with reference to Fig. 5. In the second embodiment, when the file update unit 104 of the software component update system 100 reflects updates to the software component tree and software components in step S605 of Fig. 6, the file update unit 104 performs processing different from that of the first embodiment. Other configurations and processing are the same as those of the first embodiment, and therefore description thereof will be omitted.

[0076] In this embodiment, when the software component update system 100 reflects update information in the asset B database 120, the update operator 130 is visually presented with difference information in the asset B software component tree 121 before and after the update and difference information in the asset B software component database 122, thereby enabling the update operator 130 to efficiently grasp the update contents of the software components and select the update information to be reflected as required by development.

[0077] FIG. 5 is a diagram showing an example of a screen on which the file update unit 104 of this embodiment displays difference information when updating a software component tree.

[0078] The file update unit 104 of this embodiment merges the software component tree 614 reconstructed in step S605 of FIG. 6, and displays the difference information display screen 500 before merging the software component file 616 to be updated into the asset B database 120.

[0079] The file update unit 104 generates data for displaying, for example, the name of asset A whose software component has been updated, the name of asset B into which the update is to be reflected, software component tree difference information 510, and software component file difference information 520 on the difference information display screen 500.

[0080] Software component tree difference information 510 is an example of a visualized difference information between the reconstructed software component tree 614 and the tag information 124 of the asset B software component tree 121. Tag difference information 511 indicates tag information that will not be updated out of the tag information 124 of asset B. Tag update display 512 indicates that, out of the tag information 124 included in both asset A and asset B, a software component associated with corresponding tag information has been changed due to the development of asset A, and that the update will be reflected in the asset B database 120. Tag update display 513 indicates tag information that will be newly added to the asset B database 120 out of the tag information that has been newly added to the asset A software component tree 111.

[0081] The software component file difference information 520 displays in tabular form the difference information between the software component file 616 to be updated and the software component files included in the asset B software component database 122. At this time, a combination of the name (Filename) of the software component file to be updated and the update status (Status) is displayed. The update status (Status) displays addition, modification, deletion, etc. according to the update status of the file.

[0082] 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 component tree 121 and the software component files using a file explorer or the like.

[0083] According to this embodiment, when the software component update system 100 reflects update information in the asset B database 120, the update operator 130 is visually presented with difference information between the asset B software component tree 121 and the asset B software component database 122 before and after the update, thereby enabling the update operator 130 to efficiently grasp the update contents of the software components.

[0084] The software component update system 100 of this embodiment allows development work to proceed while grasping the effect of update work on software components. Also, software components to be updated can be selected according to the needs of the project.

[0085] As described above, software component updating system 100 according to an embodiment of the present invention is connected to a first database (asset A database 110) and a second database (asset B database 120) that store software component tree information 111, 121 that represents a plurality of software components in a tree format, tag information that represents the attributes of each of the software components, and software component files (software component databases 112, 122) that include design information and source code that constitute the software components. Software component updating system 100 has a component tree reconstruction unit 102 that reconstructs the software component tree of second database 120 based on the tag information and software component tree information 111 of first database 110, a component extraction unit 103 that identifies software components in second database 120 that require updates to be reflected based on the reconstructed software component tree, and a file updating unit 104 that updates the software component files of the identified software component files. Therefore, even if there are software components with different sharing scopes, update information of software components can be reflected in databases for other projects or products according to the sharing scope of the software components. In addition, update information can also be reflected in the software component tree of each asset, making it possible to efficiently manage the configuration of software components and reflect updates to multiple projects and product groups.

[0086] Furthermore, the first database 110 and the second database 120 store tag selection information 113 and 123, which record combinations of tag information for identifying software components to be managed, and the component tree reconstruction unit 102 reconstructs the software component tree of the second database 120 based on the tag selection information 113, the tag information, and the software component tree information 111 of the first database 110. This makes it possible to delete items that are not to be reflected in the software component tree of the second database 120, to identify updates that are required in the software component tree of the second database 120, and to accurately select items that should be reflected in the software component tree of the second database 120.

[0087] The file update unit 104 generates display data for displaying on the screen the software component tree information and the difference information before and after the update of the software components, so that the operation of the system can be presented to the user and the updated files can be displayed in an easy-to-understand manner.

[0088] The present invention is not limited to the above-described embodiments, and includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. Furthermore, a part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, a part of the configuration of each embodiment may be added, deleted, or replaced with another configuration.

[0089] Furthermore, each of the aforementioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0090] Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC card, an SD card, or a DVD.

[0091] In addition, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, it can be considered that almost all components are connected to each other.

Claims

1. A software component update system, The present invention is configured by a computer having a processor and a memory, the 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 a software component file including design information and source code constituting the software components are connected to a first database and a second database; a component tree reconstruction unit that reconstructs a software component tree of the second database based on the tag information and the software component tree information of the first database; a component extraction unit that identifies the software components in the second database that require updating based on the reconstructed software component tree; a file updating unit that updates a software component file of the specified software component.

2. 2. The software component update system according to claim 1, the first database and the second database store tag selection information that records a combination of the tag information for identifying a software component to be managed; a component tree reconstruction unit that reconstructs the software component tree of the second database based on the tag selection information, the tag information, and the software component tree information of the first database;

3. 2. The software component update system according to claim 1, The software component updating system is characterized in that the file updating section generates display data for displaying on a screen the software component tree information and difference information before and after the update of the software components.

4. A software component update method executed by a computer having a processor and a memory, comprising: the computer is connected to a first database and a second database, each storing 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 a software component file including design information and source code constituting the software components; The software component update method includes: a part tree reconstruction step in which the processor reconstructs a software part tree of the second database based on the tag information and the software part tree information of the first database; a part extraction step of identifying the software parts of the second database that require updating based on the reconstructed software part tree by the processor; a file updating step in which the processor updates a software component file of the identified software component.

5. 5. A software component update method according to claim 4, further comprising the steps of: the first database and the second database store tag selection information that records a combination of the tag information for identifying a software component to be managed; A software component update method, characterized in that in the component tree reconstruction step, the processor reconstructs the software component tree of the second database based on the tag selection information, the tag information, and the software component tree information of the first database.

6. 5. A software component update method according to claim 4, further comprising the steps of: A software component updating method, wherein in the file updating step, the processor generates display data for displaying on a screen the software component tree information and difference information before and after the update of the software components.

Citation Information

Patent Citations

  • Automatic software configuration device

    JP2009205190A

  • Application generator for data transformation applications

    US20150193210A1

  • Software configuration management method and system

    WO2010013538A1