Business rules for configurable metamodels and enterprise impact analysis

• US 20060064666A1
• Filed: 09/01/2005
• Published: 03/23/2006
• Est. Priority Date: 05/25/2001
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schreiber, Zvi, Fox, Joshua, Melamed, Boris, Amaru, Ruth M., Halberstadt, Benjamin
• Application Number:
  US11/219,039
• Publication Number:
  US 20060064666A1
• Time in Patent Office: Days
• US Class Current: 717/100
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

A metadata management system for importing, integrating and federating metadata, including a configurable metamodel, a metadata repository for storing metadata whose structure reflects the metamodel, at least one external metadata source, which is able to persist metadata in accordance with the structure of a meta-schema, a mapping module for mapping the meta-schema to the metamodel, and a transformation module, operatively coupled to the metadata mapping module, for translating specific metadata from the at least one external metadata source to the metadata repository, for use in import, export or synchronization of metadata between the external metadata source and the metadata repository. A method and a computer-readable storage medium are also described.

Claims

1. A metadata management system for importing, integrating and federating metadata, comprising:

a configurable metamodel for modeling metadata that describes enterprise IT assets;

a metadata repository for storing metadata whose structure reflects said metamodel;

at least one external metadata source, which is able to persist metadata in accordance with the structure of a meta-schema;

a mapping module for mapping said meta-schema to the metamodel; and

a transformation module, operatively coupled to said metadata mapping module, for translating specific metadata from said at least one external metadata source to said metadata repository, for use in import, export or synchronization of metadata between said at least one external metadata source and said metadata repository.

2. The metadata management system of claim 1 wherein the mapping module is also used to map specific metadata to an information model.

3. The metadata management system of claim 2 wherein the information model is an ontology model.

4. The metadata management system of claim 1 wherein said metamodel complies with the OMG MOF standard.

5. The metadata management system of claim 1 wherein said metamodel is an ontology.

6. The metadata management system of claim 1 wherein said transformation module translates metadata from the external metadata source into an XMI document.

7. The metadata management system of claim 1 wherein said transformation module transforms metadata using an XSLT script.

8. The metadata management system of claim 1 wherein said mapping module maps data element groups, and then maps specific data elements within each group.

9. A metadata management system for validating metadata, comprising:

a configurable metamodel for modeling metadata that describes enterprise IT assets;

business rules on said metamodel; and

a metadata validation module operating on said configurable metamodel for validating specific metadata against said metamodel business rules.

10. The metadata management system of claim 9 wherein the business rules include an arithmetic conversion rule.

11. The metadata management system of claim 9 wherein the business rules include type restriction on an inherited property.

12. The metadata management system of claim 9 wherein the business rules include specifying a metadata value as being required.

13. The metadata management system of claim 9 wherein the business rules include specifying a valid range for a metadata value.

14. The metadata management system of claim 9 wherein the business rules include specifying a metadata value as being unique.

15. The metadata management system of claim 9 wherein the business rules include a lookup table.

16. The metadata management system of claim 9 wherein the business rules include a naming convention.

17. The metadata management system of claim 9 wherein the business rules are used to specify assignment of stewardship responsibility.

18. A metadata management system for generating metadata comprising:

a configurable metamodel for modeling metadata that describes enterprise IT assets;

business rules on said metamodel; and

a metadata generation module operating on said configurable metamodel for guiding the generation of specific metadata using said metamodel business rules.

19. The metadata management system of claim 18 wherein the business rules include an arithmetic conversion rule.

20. The metadata management system of claim 18 wherein the business rules include type restriction on an inherited property.

21. The metadata management system of claim 18 wherein the business rules include specifying a metadata value as being required.

22. The metadata management system of claim 18 wherein the business rules include specifying a valid range for a metadata value.

23. The metadata management system of claim 18 wherein the business rules include specifying a metadata value as being unique.

24. The metadata management system of claim 18 wherein the business rules include a lookup table.

25. The metadata management system of claim 18 wherein the business rules include a naming convention.

26. The metadata management system of claim 18 wherein the business rules are used to specify assignment of stewardship responsibility.

27. A metadata management system for managing an IT organization, comprising:

a configurable metamodel for modeling metadata that describes enterprise IT assets;

business rules on said metamodel; and

a validation module operating on said configurable metamodel for validating rules for IT governance against said metamodel business rules.

28. The metadata management system of claim 27 wherein the rules for IT governance include assignment of responsibility for assets.

29. A method for importing, integrating and federating metadata, comprising:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, (ii) a metadata repository for storing metadata whose structure reflects the metamodel, and (iii) at least one external metadata source, which is able to persist metadata in accordance with the structure of a meta-schema;

mapping the meta-schema to the metamodel; and

translating specific metadata from the external metadata source to the metadata repository for use in import, export or synchronization of metadata between the at least one external metadata source and the metadata repository.

30. The method of claim 29 wherein said mapping maps specific metadata to an information model.

31. The method of claim 30 wherein the information model is an ontology model.

32. The method of claim 29 wherein the metamodel complies with the OMG MOF standard.

33. The method of claim 29 wherein the metamodel is an ontology.

34. The method of claim 29 wherein said mapping translates metadata from the external metadata source into an XMI document.

35. The method of claim 29 wherein said translating uses an XSLT script.

36. The method of claim 29 wherein said mapping comprises:

mapping data element groups; and

mapping specific data elements within each group.

40. The method of claim 29 wherein the rules for IT governance include assignment of responsibility for assets.

37. A method for validating metadata, comprising:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, and (ii) business rules on the metamodel; and

validating specific metadata against the metamodel business rules.

38. A method for generating metadata comprising:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, and (ii) business rules on the metamodel; and

guiding the generation of specific metadata using the metamodel business rules.

39. A method for managing an IT organization, comprising:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, and (ii) business rules on the metamodel; and

validating rules for IT governance against the metamodel business rules.

41. A computer-readable storage medium storing program code for causing a computer to perform a method of:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, (ii) a metadata repository for storing metadata whose structure reflects the metamodel, and (iii) at least one external metadata source, which is able to persist metadata in accordance with the structure of a meta-schema;

mapping the meta-schema to the metamodel; and

translating specific metadata from the external metadata source to the metadata repository for use in import, export or synchronization of metadata between the at least one external metadata source and the metadata repository.

42. A computer-readable storage medium storing program code for causing a computer to perform a method of:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, and (ii) business rules on the metamodel; and

validating specific metadata against the metamodel business rules.

43. A computer-readable storage medium storing program code for causing a computer to perform a method of:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, and (ii) business rules on the metamodel; and

guiding the generation of specific metadata using the metamodel business rules.

46. The metadata management system of claim 43 whereby assets of the enterprise IT system include server computers.

47. The metadata management system of claim 43 whereby assets of the enterprise IT system include web sites.

48. The metadata management system of claim 43 whereby assets of the enterprise IT system include data sources.

49. The metadata management system of claim 43 whereby assets of the enterprise IT system include data transformations.

50. The metadata management system of claim 43 whereby assets of the enterprise IT system include software applications.

51. The metadata management system of claim 43 whereby the business rules dictate whether impact consequences are transitive and, if so, to what degree.

44. A computer-readable storage medium storing program code for causing a computer to perform a method of:

providing (i) a configurable metamodel for modeling metadata that describes enterprise IT assets, and (ii) business rules on the metamodel; and

validating responsibility assignments against the metamodel business rules.

45. A metadata management system for performing impact analysis on an IT system comprising:

a configurable metamodel for modeling metadata that describes assets of an enterprise IT system, the metamodel including meta-classes and meta-properties;

business rules on said metamodel for indicating that certain meta-properties have impact consequences; and

an impact analyzer operating on said configurable metamodel for determining which assets of the enterprise IT system are impacted by one or more specified assets.

52. A method for generating metadata comprising:

providing (i) a configurable metamodel for modeling metadata that describes assets of an enterprise IT system, the metamodel including meta-classes and meta-properties, and (ii) business rules on said metamodel for indicating that certain meta-properties have impact consequences; and

determining which assets of the enterprise IT system are impacted by one or more specified assets.

53. The method of claim 52 whereby assets of the enterprise IT system include server computers.

54. The method of claim 52 whereby assets of the enterprise IT system include web sites.

55. The method of claim 52 whereby assets of the enterprise IT system include data sources.

56. The method of claim 52 whereby assets of the enterprise IT system include data transformations.

57. The method of claim 52 whereby assets of the enterprise IT system include software applications.

58. The method of claim 52 whereby the business rules dictate whether impact consequences are transitive and, if so, to what degree.

59. A computer-readable storage medium storing program code for causing a computer to perform a method of:

providing (i) a configurable metamodel for modeling metadata that describes assets of an enterprise IT system, the metamodel including meta-classes and meta-properties, and (ii) business rules on said metamodel for indicating that certain meta-properties have impact consequences; and

determining which assets of the enterprise IT system are impacted by one or more specified assets.

60. A metadata management system for performing impact analysis on an IT system comprising:

a configurable metamodel for modeling metadata that describes assets of an enterprise IT system, the metamodel including meta-classes and meta-properties;

a meta-descriptor for meta-properties to designate that a meta-property has an impact consequence; and

an impact analyzer operating on said configurable metamodel for determining which assets of the enterprise IT system are impacted by one or more specified assets.

61. A method for generating metadata comprising:

providing (i) a configurable metamodel for modeling metadata that describes assets of an enterprise IT system, the metamodel including meta-classes and meta-properties, and (ii) a meta-descriptor for meta-properties to designate that a meta-property has an impact consequence; and

determining which assets of the enterprise IT system are impacted by one or more specified assets.

62. A computer-readable storage medium storing program code for causing a computer to perform a method of:

providing (i) a configurable metamodel for modeling metadata that describes assets of an enterprise IT system, the metamodel including meta-classes and meta-properties, and (ii) a meta-descriptor for meta-properties to designate that a meta-property has an impact consequence; and

determining which assets of the enterprise IT system are impacted by one or more specified assets.