Virtual RAS repository

• US 8,141,038 B2
• Filed: 12/29/2005
• Issued: 03/20/2012
• Est. Priority Date: 12/29/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: O'Connell, Margaret M., Russo, Hanna, Balderas, Manuel A., Pinkus, Jennifer L.
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Aguilera, Todd
• Application Number:
  US11/321,857
• Publication Number:
  US 20070156764A1
• Time in Patent Office: 2,273 Days
• Field of Search: 707/100, 717100-103, 717106-108, 719/328
• US Class Current: 717/120
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

The present invention provides a virtual Reusable Asset Specification (RAS) repository. A method in accordance with an embodiment of the present invention includes: providing RAS assets for each different lifecycle phase of a software asset; and linking the RAS assets together using RAS related-assets.

Claims

1. A method for providing a virtual Reusable Asset Specification (RAS) repository, comprising:

providing, using a computing device, separate RAS assets for different lifecycle phases of a software asset in a plurality of different RAS repositories, the plurality of different RAS repositories together forming the virtual RAS repository at runtime through use of RAS related-assets, the plurality of different RAS repositories comprising;

an archives RAS repository for storing an installable RAS asset, the installable RAS asset including at least one artifact for implementing a solution, meta information for defining and describing the at least one artifact, and an archive RAS related-asset;

a deployed archives RAS repository for storing a deployed RAS asset corresponding to a deployment of the installable RAS asset stored in the archives RAS repository, the deployed RAS asset including a deployed RAS related-asset and a reference back to the installable RAS asset stored in the archives RAS repository, wherein the installable RAS asset stored in the archives RAS repository can have multiple related deployed RAS assets; and

an instances RAS repository for storing an instance RAS asset corresponding to an instantiation of the deployed RAS asset stored in the deployed archives RAS repository, the instance RAS asset including a reference back to the deployed RAS asset stored in the deployed RAS repository, wherein the deployed RAS asset stored in the deployed archives RAS repository can have multiple related instance RAS assets;

linking, using the computing device, the installable RAS asset stored in the archives RAS repository with the deployed RAS asset stored in the deployed archives RAS repository using the archive RAS related-asset, wherein the archive RAS related-asset comprises a uniform resource locator (URL), and wherein the URL of the archive RAS related asset includes information regarding a server on which the installable RAS asset was deployed and a path within the server; and

linking, using the computing device, the deployed RAS asset stored in the deployed archives RAS repository with the instance RAS asset stored in the instances RAS repository using the deployed RAS related-asset, wherein the deployed RAS related-asset comprises an URL, and wherein the URL of the deployed RAS related-asset includes information regarding an instantiation of the deployed RAS asset.

2. The method of claim 1, wherein the deployed archives RAS repository stores a plurality of deployed RAS assets corresponding to a plurality of deployments of the installable RAS asset stored in the archives RAS repository, each of the plurality of deployed RAS assets including a respective deployed RAS related-asset and a respective reference back to the installable RAS asset stored in the archives RAS repository.

3. The method of claim 1, wherein the different RAS repositories are located in different physical locations.

4. The method of claim 1, wherein the instances RAS repository stores a plurality of instance RAS assets corresponding to a plurality of instantiations of the deployed RAS asset stored in the deployed archives RAS repository, each of the plurality of instance RAS assets including a respective reference back to the deployed RAS asset stored in the deployed archive RAS repository.

5. The method of claim 1, further comprising:

wrapping existing artifacts in RAS to create RAS assets for the existing artifacts.

6. A system for providing a virtual Reusable Asset Specification (RAS) repository, comprising:

a computer device, including;

a system for providing separate RAS assets for different lifecycle phases of a software asset in a plurality of different RAS repositories, the plurality of different RAS repositories together forming the virtual RAS repository at runtime through use of RAS related-assets, the plurality of different RAS repositories comprising;

an archives RAS repository for storing an installable RAS asset, the installable RAS asset including at least one artifact for implementing a solution, meta information for defining and describing the at least one artifact, and an archive RAS related-asset;

a deployed archives RAS repository for storing a deployed RAS asset corresponding to a deployment of the installable RAS asset stored in the archives RAS repository, the deployed RAS asset including a deployed RAS related-asset and a reference back to the installable RAS asset stored in the archives RAS repository, wherein the installable RAS asset stored in the archives RAS repository can have multiple related deployed RAS assets; and

an instances RAS repository for storing an instance RAS asset corresponding to an instantiation of the deployed RAS asset stored in the deployed archives RAS repository, the instance RAS asset including a reference back to the deployed RAS asset stored in the deployed RAS repository, wherein the deployed RAS asset stored in the deployed archives RAS repository can have multiple related instance RAS assets; and

a system for linking the installable RAS asset stored in the archives RAS repository with the deployed RAS asset stored in the deployed archives RAS repository using the archive RAS related-asset, wherein the archive RAS related-asset comprises a uniform resource locator (URL), and wherein the URL of the archive RAS related asset includes information regarding a server on which the installable RAS asset was deployed and a path within the server and for linking the deployed RAS asset stored in the deployed archives RAS repository with the instance RAS asset stored in the instances RAS repository using the deployed RAS related-asset, wherein the deployed RAS related-asset comprises an URL, and wherein the URL of the deployed RAS related-asset includes information regarding an instantiation of the deployed RAS asset.

7. The system of claim 6, wherein the deployed archives RAS repository stores a plurality of deployed RAS assets corresponding to a plurality of deployments of the installable RAS asset stored in the archives RAS repository, each of the plurality of deployed RAS assets including a respective deployed RAS related-asset and a respective reference back to the installable RAS asset stored in the archives RAS repository.

8. The system of claim 6, wherein the different RAS repositories are located in different physical locations.

9. The system of claim 6, wherein the instances RAS repository stores a plurality of instance RAS assets corresponding to a plurality of instantiations of the deployed RAS asset stored in the deployed archives RAS repository, each of the plurality of instance RAS assets including a respective reference back to the deployed RAS asset stored in the deployed archive RAS repository.

10. The system of claim 6, further comprising:

a system for wrapping existing artifacts in RAS to create RAS assets for the existing artifacts.

11. A program product stored on a non-transitory computer readable medium for providing a virtual Reusable Asset Specification (RAS) repository when executed by a computer system, the computer readable medium comprising program code for:

providing separate RAS assets for different lifecycle phases of a software asset in a plurality of different RAS repositories, the plurality of different RAS repositories together forming the virtual RAS repository at runtime through use of RAS related-assets, the plurality of different RAS repositories comprising;

an archives RAS repository for storing an installable RAS asset, the installable RAS asset including at least one artifact for implementing a solution, meta information for defining and describing the at least one artifact, and an archive RAS related-asset;

a deployed archives RAS repository for storing a deployed RAS asset corresponding to a deployment of the installable RAS asset stored in the archives RAS repository, the deployed RAS asset including a deployed RAS related-asset and a reference back to the installable RAS asset stored in the archives RAS repository, wherein the installable RAS asset stored in the archives RAS repository can have multiple related deployed RAS assets; and

an instances RAS repository for storing an instance RAS asset corresponding to an instantiation of the deployed RAS asset stored in the deployed archives RAS repository, the instance RAS asset including a reference back to the deployed RAS asset stored in the deployed RAS repository, wherein the deployed RAS asset stored in the deployed archives RAS repository can have multiple related instance RAS assets;

linking the installable RAS asset stored in the archives RAS repository with the deployed RAS asset stored in the deployed archives RAS repository using the archive RAS related-asset, wherein the archive RAS related-asset comprises a uniform resource locator (URL), and wherein the URL of the archive RAS related asset includes information regarding a server on which the installable RAS asset was deployed and a path within the server; and

linking the deployed RAS asset stored in the deployed archives RAS repository with the instance RAS asset stored in the instances RAS repository using the deployed RAS related-asset, wherein the deployed RAS related-asset comprises an URL, and wherein the URL of the deployed RAS related-asset includes information regarding an instantiation of the deployed RAS asset.

12. The program product of claim 11, wherein the deployed archives RAS repository stores a plurality of deployed RAS assets corresponding to a plurality of deployments of the installable RAS asset stored in the archives RAS repository, each of the plurality of deployed RAS assets including a respective deployed RAS related-asset and a respective reference back to the installable RAS asset stored in the archives RAS repository.

13. The program product of claim 11, wherein the different RAS repositories are located in different physical locations.

14. The program product of claim 11, wherein the instances RAS repository stores a plurality of instance RAS assets corresponding to a plurality of instantiations of the deployed RAS asset stored in the deployed archives RAS repository, each of the plurality of instance RAS assets including a respective reference back to the deployed RAS asset stored in the deployed archive RAS repository.

15. The program product of claim 11, further comprising program code for:

providing RAS assets by wrapping existing artifacts in RAS to create RAS assets for the existing artifacts.