Targeted asset capture, identification, and management

• US 20030009455A1
• Filed: 07/06/2001
• Published: 01/09/2003
• Est. Priority Date: 07/06/2001
• Status: Active Grant

• Current Assignee: Akana, Inc. (Perforce Software Incorporated)
• Original Assignee: LogicLibrary, Inc. (Perforce Software Incorporated)
• Inventors: Palof, John, Mariner, Debra, Carlson, Brent, Tamminga, Paul, Graser, Tim
• Granted Patent: US 7,080,355 B2
• Time in Patent Office: Days
• US Class Current: 707/6
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A targeted asset capture system that maps software resources to a domain model, and search and management tools for retrieving asset information and controlling asset acquisition. The domain model may include a process-centered organization and/or a structural organization of model tasks, functions, and data types. Capture includes mapping to the model functions and data types, and preferably also includes capturing other information about the asset and about the quality of mapping. The domain model may be used to build a search specification for searching for available assets that meet some or all of a set of functional (and/or nonfunctional) requirements. The search specification may also be published in part or in whole as a development specification.

Claims

1. A software utility for interacting with a user to classify a resource according to a predetermined domain model, the utility comprising:

data type mapping means that allow the user to map data types to the domain model;

function mapping means that allow the user to map resource functions to the domain model;

identification means that allow the user to specify the location of the resource; and

a database comprising data type maps, resource function maps, and location information specified by the user.

2. The software utility of claim 1, wherein the domain model comprises:

a process model comprising processes and use cases;

a structural model comprising reference components, reference interfaces, and reference functions.

3. The software utility of claim 2, wherein portions of the process model are linked to reference components, reference interfaces, or reference functions of the structural model.

4. The software utility of claim 3, wherein the domain model comprises a plurality of process models, portions of each process model linked to reference components, reference interfaces, or reference functions of the structural model.

5. The software utility of claim 2, wherein the data type mapping means allow the user to map data types to the structural model.

6. The software utility of claim 2, wherein the function mapping means allow the user to map functions to the structural model.

7. The software utility of claim 1 wherein the data type mapping means or the function mapping means use synonyms to suggest mapping candidates.

8. The software utility of claim 1, wherein the data type mapping means or the function mapping means comprise means for the user to provide comments, the comments being stored in the database.

9. The software utility of claim 8, wherein the comments are associated with a particular data type or resource function and include information relating to quality of the mapping.

10. The software utility of claim 8, wherein the comments are associated with a particular data type or resource function and include information relating to the purposes or usage of individual functions or data types.

11. The software utility of claim 1, further comprising search means for searching the database.

13. The software utility of claim 12, further comprising a search engine for searching the database to locate resources meeting functional or nonfunctional requirements.

14. The software utility of claim 13, wherein the search engine comprises a scoring engine that ranks resources according to how closely they match the functional or nonfunctional requirements.

15. The software utility of claim 13, wherein the search engine comprises means for creating a persistent search specification that can be shared between multiple users.

16. The software utility of claim 15, wherein resources located by the search engine may be selectively attached to the persistent search specification.

17. The software utility of claim 16, wherein portions of the persistent search specification not met by attached assets may be published as requirements for development of additional resources.

18. The software utility of claim 15, further comprising means for notifying at least one of the multiple users when resources matching the persistent search specification are added to the database.

19. The software utility of claim 15, further comprising means for publishing the persistent search specification as requirements for development of additional resources.

20. The software utility of claim 19, further comprising means for notifying at least one of the multiple users when resources matching the persistent search specification are added to the database.

21. The software utility of claim 12, wherein the functionality information is mapped to a plurality of domain models.

22. The software utility of claim 12, further comprising means for viewing the domain model in order to specify requirements for searching the database.

23. The software utility of claim 22, wherein the viewing means comprise a graphical user interface.

24. The software utility of claim 23, wherein the domain model comprises a process model and a structural model, and wherein the graphical user interface comprises means for navigating between the process model and the structural model.

25. The software utility of claim 23, wherein elements of the domain model may be directly accessed by keyword search.

26. The software utility of claim 12, wherein the database further comprises a usage record for the resource.

27. The software utility of claim 26, wherein the usage record is associated with a development project.

28. The software utility of claim 26, wherein the usage record comprises one or more items selected from the group consisting of payment records, license keys, request histories, and usage histories.

29. The software utility of claim 26, further comprising means for generating usage reports for the resource.

30. The software utility of claim 26, further comprising means for one or managers to approve requests for resource acquisition.

12. A software utility for managing resources within an enterprise, comprising:

a database comprising resource information including location information and functionality information, the functionality information being mapped to a domain model.

31. A method of classifying a resource comprising functions and data types, the method comprising:

providing a domain model comprising model functions and model data types;

mapping resource data types to model data types to produce data type maps;

mapping resource functions to model functions to produce function maps; and

storing the data type maps and function maps in a searchable database.

32. The method of claim 31, wherein the domain model comprises:

a process model comprising processes and use cases; and

a structural model comprising reference components, reference interfaces, and reference functions.

33. The method of claim 32, wherein portions of the process model are linked to reference components, reference interfaces, or reference functions of the structural model.

34. The method of claim 33, wherein the domain model comprises a plurality of process models, portions of each process model linked to reference components, reference interfaces, or reference functions of the structural model.

35. The method of claim 31, further comprising providing suggestions of possible model functions or model data types for mapping to resource functions or resource data types.

36. The method of claim 35, wherein providing suggestions includes using synonyms to search model function descriptions and model data type descriptions.

37. The method of claim 31, further comprising storing comments relating to the resource in the database.

38. The method of claim 37, wherein the comments relate to the quality of mapping of the function maps or the data type maps.

39. The method of claim 37, wherein the comments include information relating to the purposes or usage of individual resource functions or resource data types.

40. A method of managing resources within an enterprise, comprising:

maintaining a searchable database of resource information including location information and functionality information, the functionality information being mapped to a domain model.

41. The method of claim 40, further comprising searching the database using a search engine that ranks resources according to how closely they match functional or nonfunctional requirements.

42. The method of claim 40, further comprising creating a persistent search specification for the database that can be shared between multiple users.

43. The method of claim 42, further comprising attaching at least one resource to the persistent search specification.

44. The method of claim 43, further comprising publishing the portions of the search specification not met by any attached resource as requirements for development of additional resources.

45. The method of claim 42, further comprising notifying a user when a resource is added to the database that matches the persistent search specification.

46. The method of claim 42, further comprising publishing the persistent search specification as requirements for development of additional resources.

47. The method of claim 40, further comprising accepting requests for acquisition of resources and forwarding the requests to an acquirer.

48. The method of claim 47, further comprising storing acquisition information provided by the acquirer.

49. The method of claim 48, further comprising generating a report of resource acquisition or resource usage.

50. The method of claim 47, further comprising generating a report of requests for the resource.

51. A method of mapping a software resource to a domain resource model comprising model functions and model data types, the method comprising:

determining resource functions and resource data types to be mapped;

determining an order for mapping resource functions and resource data types, wherein more complex functions and data types are mapped later than simpler functions and data types;

presenting the resource functions and data types in the determined order to a user for mapping; and

presenting suggested mappings for each function and data type to the user for determination of a mapping, wherein determined mappings for earlier resource functions or data types are used to suggest mappings for later types.

52. The method of claim 51, wherein all data types are ordered before functions.

53. The method of claim 51, wherein the user may elect to map functions and data types in an order other than the presented order.