Software component library management system

• US 7,676,792 B2
• Filed: 10/21/2005
• Issued: 03/09/2010
• Est. Priority Date: 03/15/2001
• Status: Expired due to Fees

• Current Assignee: Kabushiki Kaisha Toshiba (Toshiba Corporation)
• Original Assignee: Kabushiki Kaisha Toshiba (Toshiba Corporation)
• Inventors: Irie, Yutaka, Tanaka, Seiichiro
• Primary Examiner(s): RUTTEN, JAMES D
• Application Number:
  US11/254,669
• Publication Number:
  US 20060037001A1
• Time in Patent Office: 1,600 Days
• Field of Search: 717121-123
• US Class Current: 717/121
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A software component library management system is provided, which can effectively support both a component utilization user and a component management user in carrying out their business tasks. The component management tool 6 includes a component retrieve/pickup function unit 10 and a component administration/registration function unit 20. The component administration/registration function unit 20 is adapted to make registrations of attribute information on software components stored in the component database 5, such as relation information items representing relations between the software component and other software components. The component retrieve/pickup function unit 10 can retrieve and pickup a batch of software components related to a specific software component, based on the relation information items. The relation information item includes a slave link used to identify a slave component which a certain software component uses (slave information item), and a master link used to identify a master component by which a certain software component is used (master information item).

Claims

1. A software component library management system that manages a software component library having a plurality of software components stored therein, the system comprising:

a component management unit that registers a plurality of relation information items respectively representing a relation of a certain software component to another software component, as attribute information of the software components stored in the software component library, the relation information items including a slave information item specifying a slave component which a certain software component uses, and a master information item specifying a master component by which a certain software component is used;

a component providing unit that provides a batch of software components related to a specific software component, based upon the relation information items registered in the component management unit; and

wherein when an updated version of a software component is stored in the software library, the component management unit newly registers the updated version of the software component while creating and registering a renewed relation information item including sub-information that an operation among software components has not been confirmed yet, based upon a relation information item for a previous version of the software component.

2. The software component library management system according to claim 1, wherein the component management unit registers a slave information item for a software component stored in the software component library, while automatically creating and registering a master information item corresponding to the slave information item.

3. The software component library management system according to claim 1, wherein the component management unit manages a cluster of versions which is comprised of a group of different versions of a software component stored in the software component library;

and the component management unit newly registers an updated version of a software component stored in the software component library, while creating and registering a renewed relation information item that represents a relation of the software component to a cluster of versions of a related software component serving as either a slave component or a master component, based upon a relation information item for a previous version of the software component.

4. The software component library management system according to claim 1, wherein the component management unit manages a relation information item for a software component stored in the software component library, along with an operation confirmation information item;

and the component management unit newly registers an updated version of a software component stored in the software component library, while registering an operation confirmation information item that an operation among software components has not been confirmed yet, along with a relation information item for a previous version of the software component.

5. The software component library management system according to claim 1, wherein the component management unit lists and displays a combination of software components of which mutual operation has not been confirmed yet, based upon the relation information items for the software components stored in the software component library.

6. The software component library management system according to claim 1, wherein the component management unit deletes a specific software component stored in the software component library, while searching for a presence of a master component which uses the specific software component, and giving an alert, if present.

7. A method of managing a software component library having a plurality of software components stored therein, the method comprising the steps of:

registering, by a processor configured to register relation information, a plurality of relation information items that respectively represent a relation of a certain software component to another software component, as attribute information of the software components stored in the software component library, the relation information items including a slave information item specifying a slave component which a certain software component uses, and a master information item specifying a master component by which a certain software component is used;

providing a batch of software components related to a specific software component, based upon the registered relation information items; and

when an updated version of a software component is stored in the software component library, newly registering by said processor, the updated version of the software component while creating and registering a renewed relation information item including sub-information that an operation among software components has not been confirmed yet, based upon a relation information item for a previous version of the software component.

8. The method according to claim 7, further comprising the step of registering a slave information item for a software component stored in the software component library, while automatically creating and registering a master information item corresponding to the slave information item.

9. The method according to claim 7, further comprising the step of listing and displaying a combination of software components of which mutual operation has not been confirmed yet, based upon the relation information items for the software components stored in the software component library.

10. The method according to claim 7, further comprising the step of deleting a specific software component stored in the software component library, while searching for a presence of a master component which uses the specific software component, and giving an alert, if present.

11. A tangible computer-readable storage medium having embedded therein instructions, which when executed by a processor, cause the processor to perform a method comprising:

registering a plurality of relation information items that respectively represent a relation of a certain software component to another software component, as attribute information of the software components stored in the software component library, the relation information items including a slave information item specifying a slave component which a certain software component uses, and a master information item specifying a master component by which a certain software component is used;

providing a batch of software components related to a specific software component, based upon the registered relation information items; and

when an updated version of a software component is stored in the software component library, newly registering the updated version of the software component, while creating and registering a renewed relation information item including sub-information that an operation among software components has not been confirmed yet, based upon a relation information item for a previous version of the software component.

12. The tangible computer-readable storage medium according to claim 11, wherein the instructions further cause the processor to execute the procedure of registering a slave information item for a software component stored in the software component library, while automatically creating and registering a master information item corresponding to the slave information item.

13. The tangible computer-readable storage medium according to claim 11, wherein the instructions further cause the processor to execute the procedure of listing and displaying a combination of software components of which mutual operation has not been confirmed yet, based upon the relation information items for the software components stored in the software component library.

14. The tangible computer-readable storage medium according to claim 11, wherein the instructions further cause the processor to execute the procedure of deleting a specific software component stored in the software component library, while searching for a presence of a master component which uses the specific is software component, and giving an alert, if present.