GENERATING REUSABLE SOFTWARE ASSETS FROM DISTRIBUTED ARTIFACTS

• US 20080133558A1
• Filed: 01/18/2008
• Published: 06/05/2008
• Est. Priority Date: 03/18/2002
• Status: Active Grant

• Current Assignee: Akana, Inc. (Perforce Software Incorporated)
• Original Assignee: LogicLibrary, Inc. (Perforce Software Incorporated)
• Inventors: Graser, Timothy J., Tamminga, Paul W., Carlson, Brent A., Palof, John J., Gross, Dave H., Mariner, Debra L.
• Granted Patent: US 9,235,386 B2
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Claims

1. A computer-implemented system comprising:

a repository to store artifacts, wherein at least a portion of the artifacts comprise software instructions that are reusable in different development environments;

an asset source executing on a computer to monitor the repository and generate a software asset based on the artifacts upon detecting a new or updated artifact within the repository; and

an asset management system executing on one or more computers to receive the software asset from the asset source and to store the software asset within an asset library.

2. The system of claim 1, wherein the asset source generates the software asset to include references to the artifacts within the repository.

3. The system of claim 1, wherein the asset source generates the software asset upon detecting a new or updated artifact within the repository.

4. The system of claim 1, wherein the asset source generates the software asset in a format that complies with a data description language.

5. The system of claim 4, wherein the data description language comprises the extensible markup language (XML).

6. The system of claim 1, wherein the asset source comprises a staging area to store the software asset prior to storage within the asset library by the asset management system.

7. The system of claim 1, further wherein the asset source generates the software asset in a normalized format in accordance with an asset template.

8. The system of claim 7, wherein the asset template defines a schema for the software asset in accordance with a data description language.

9. The system of claim 1, wherein the asset source comprises a writable interface for editing the software asset.

10. The system of claim 1, wherein the asset source comprises an artifact storage to cache artifacts extracted from the repository.

11. The system of claim 1, further comprising an asset capture tool to update the software asset based on additional artifacts.

12. The system of claim 11, wherein the asset capture tool includes a user interface to receive the additional artifacts from a user.

13. The system of claim 11, wherein the asset capture tool includes scripts to generate the additional artifacts.

14. The system of claim 1, further comprising:

an asset template that defines a schema for a software asset in accordance with a data description language; and

an asset capture tool to update the software asset in accordance with the asset template, wherein the asset capture tool identifies missing artifacts from the software asset based on the asset template.

15. The system of claim 1, further comprising a rules engine to generate metadata that maps the software asset to elements of one or more models that graphically represent a set of software components having instructions.

16. The system of claim 15, further comprising an asset retrieval module to selectively retrieve the software asset from the asset library based on the metadata.

17. The system of claim 15, wherein the models comprises at least one of a process model, a structural model, a resource model, and an implementation model.

18. The system of claim 1, further comprising an asset retrieval module to receive input from a user selecting an element of a model, and to selectively retrieve the software asset from the asset library based on the input.

19. The system of claim 18, wherein the asset retrieval module generates a search specification based on the user input.

20. The system of claim 19, further comprising a scoring engine to score the software asset within the asset library against the search specification.

21. The system of claim 1, wherein the artifact comprises one of source code, binary code, a requirements specification, a design document, a model, a use case, and a collaboration diagram.

22. A computer-implemented system comprising:

a plurality of repositories to store artifacts;

asset templates that define schemas for reusable software assets in accordance with a data description language;

a plurality of asset sources executing on one or more computers to monitor the repositories and generate software assets to include metadata that reference the artifacts in accordance with schemas of the asset templates; and

an asset management system executing on one or more computers to receive the software assets from the asset sources and store the software assets within an asset library.

23. The system of claim 22, wherein the asset sources generates the software assets upon detecting a new or updated artifact within the repository.

24. The system of claim 22, wherein the metadata comprises the extensible markup language (XML).

25. The system of claim 22, wherein the asset sources comprises staging areas to store the software assets prior to storage within the asset management system.

26. The system of claim 25, further comprising an asset capture tool to update the software assets within the staging area.

27. The system of claim 22, wherein the asset sources comprise a multi-level hierarchy of asset sources, wherein higher-level asset sources of the hierarchy receive software assets from low-level asset sources of the hierarchy and form aggregate software assets.

28. A computer-implemented system comprising:

a plurality of repositories to store artifacts;

a multi-level hierarchy of asset sources to generate software assets having metadata that reference the artifacts, wherein higher-level asset sources of the hierarchy receive software assets from low-level asset sources of the hierarchy and combine the received software assets to form aggregate software assets; and

an asset management system executing on one or more computers to receive the aggregate software assets from the hierarchy of asset sources and store the aggregate software assets within an asset library.

29. The system of claim 28, wherein the asset sources generate the software assets in accordance with asset templates that define schemas for the software assets in accordance with a data description language.

30. The system of claim 28, further comprising at least two asset capture tools communicatively coupled to different asset sources of different levels of the hierarchy.

31. The system of claim 28, further comprising a publishing module to retrieve the software assets from the asset sources and to insert the software assets into the asset library.

32. The system of claim 28, further comprising an asset capture tool that updates the software assets to include metadata that maps the aggregate software assets to elements of a model.

33. The system of claim 32, further comprising an asset retrieval module to selectively retrieve the software assets from the asset library based on the metadata.

34. The system of claim 28, further comprising a rules engine to generate metadata that maps the software asset to elements of one or more models.

35. The system of claim 34, wherein the models comprises at least one of a process model, a structural model, a resource model, and an implementation model.

36. A computer-implemented system comprising:

a model having one or more elements;

a database to store reusable software assets; and

an asset retrieval module executing on a computer to receive input from a user selecting an element of the model that graphically represent a set of software components having instructions, and to selectively retrieve a subset of the software assets from the database based on the input.

37. The system of claim 36, further comprising a rules engine to generate metadata that maps the software assets to the elements the model.

38. The system of claim 36, wherein the model comprises one of a process model, a structural model, a resource model, and an implementation model.

39. The system of claim 36, wherein the asset retrieval module generates a search specification based on the user input.

40. The system of claim 39, further comprising a scoring engine to score the software assets within database against the search specification.

41. A method comprising:

executing asset sources on one or more computers to monitor repositories and retrieve artifacts from the repositories upon detecting a new or updated artifact within the repository, wherein at least a portion of the artifacts comprise software instructions;

executing asset sources on one or more computers to generate software assets based on the artifacts in a form that conforms to a data description language that identifies the artifacts within the repositories; and

publishing the software assets for storage within an asset library.

42. The method of claim 41, wherein generating software assets comprises generating the software assets based on new and updated artifacts within the repositories.

43. The method of claim 41, wherein generating software assets comprises generating the software assets to include references to related artifacts within the repository.

44. The method of claim 41, wherein the data description language comprises the extensible markup language (XML).

45. The method of claim 41, further comprising storing the software assets within a staging area prior to publication to the asset management system.

46. The method of claim 41, wherein generating the software assets comprises generating the software assets in accordance with an asset template that defines a schema for the software assets.

47. The method of claim 45, wherein generating the software assets comprises:

identifying additional artifacts required for the software assets; and

invoking an asset capture module to update the software assets to include the additional artifacts.

48. The method of claim 47, wherein invoking the asset capture module comprises invoking scripts to automatically update the software assets.

49. The method of claim 47, wherein invoking the asset capture module comprises invoking a user interface to receive the additional artifacts.

50. The method of claim 47, further comprising publishing the updated software assets to the asset library.

51. The method of claim 41, wherein retrieving artifacts from repositories comprises:

receiving the artifacts via distributed asset sources; and

communicating the artifacts from the asset sources to a publishing module for insertion into the asset library.

52. The method of claim 41, wherein generating the software assets comprises generating metadata that maps the software assets to elements of one or more models that graphically represent a set of software components having instructions.

53. The method of claim 52, further comprising selectively retrieving the software assets from the asset library based on the metadata.

54. The method of claim 52, further comprising:

receiving input from a user selecting one or more elements of the models; and

retrieving software assets from the asset library based on the selected elements of the model.

55. The method of claim 54, further comprising ranking the software assets of the asset library according to the selected elements of the models.

56. The method of claim 41, wherein the artifact comprises one of source code, binary code, a requirements specification, a design document, a model, a use case, and a collaboration diagram.

57. A computer-readable medium comprising instructions to cause a processor to:

executing asset sources on one or more computers to monitor repositories and retrieve one or more artifacts from the repositories upon detecting a new or updated artifact within the repository, wherein at least a portion of the artifacts comprise software instructions;

automatically generate software assets that include a data description language that describes one or more of the artifacts; and

publish the software assets to an asset library.

58. A method comprising:

receiving input from a user selecting one or more elements of a model that graphically depicts a set of software components having instructions that are reusable on different software programs; and

retrieving software assets from an asset library based on the selected elements.

59. The method of claim 58, further comprising:

generating software assets based on artifacts, wherein the software assets conform to a data description language and include metadata that maps the software assets to elements of the models; and

storing the software assets within an asset library.

60. A computer-readable medium comprising instructions to cause a processor to:

receive input from a user selecting one or more elements of a model that graphically depicts a software program; and

retrieve software assets from an asset library based on the selected elements, wherein the software asset identifies one or more software elements having instructions that are reusable on different software programs.

61. The computer-readable medium of claim 60, further comprising instructions to cause the processor to:

generate software assets based on artifacts, wherein the software assets conform to a data description language and include metadata that maps the software assets to elements of the models; and

store the software assets within an asset library

62. A computer-readable medium comprising data structures that store:

software models having elements; and

software assets having metadata that maps the software asset to the elements of the software models.