| Business rules for configurable metamodels and enterprise impact analysis -> Monitor Keywords |
|
|
 
Business rules for configurable metamodels and enterprise impact analysisRelated Patent Categories: Data Processing: Software Development, Installation, And Management, Software Program Development Tool (e.g., Integrated Case Tool Or Stand-alone Development Tool)Business rules for configurable metamodels and enterprise impact analysis description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20060064666, Business rules for configurable metamodels and enterprise impact analysis. Brief Patent Description - Full Patent Description - Patent Application Claims
CROSS REFERENCES TO RELATED APPLICATIONS [0001] This application is a continuation-in-part of assignee's pending application U.S. Ser. No. 10/053,045, filed on Jan. 15, 2002, entitled "Method and System for Deriving a Transformation by Referring Schema to an Central Model," which is a continuation-in-part of assignee's pending application U.S. Ser. No. 09/866,101, filed on May 25, 2001, entitled "Method and System for Collaborative Ontology Modeling." FIELD OF THE INVENTION [0002] The present invention relates to management of enterprise metadata. BACKGROUND OF THE INVENTION [0003] Large enterprises rely on vast amounts and diverse types of data for their operation--personnel data, financial data, accounting data, inventory data, capital equipment data, document management data, and more. Today, data is generally stored according to data structures referred to as a data schemas, such as XML and relational database schemas, these being a form of metadata. The term "metadata" is used to denote data about the structure of the raw data itself, and about the structures of other Information Technology (IT) systems such as applications, processes, middleware and hardware configurations. The raw data, which includes actual data about specific personnel, for example, or specific pieces of inventory, is referred to as "instance data." Thus, for a data store having the structure of a relational database, the metadata describes the tables and their columns to be populated with data, and the raw data, referred to as instance data, is the actual data stored within the tables and columns. Similarly, for a data store of XML documents, the metadata describes the XML complexTypes and their XML elements, and the instance data is the actual data stored within the XML documents. Each data store is referred to generically as a "data asset." [0004] Types of metadata include inter alia data schemas such as relational and XML schemas, source code, architecture models such as information models and process models, operational metadata regarding usage of applications and up-time, hardware inventories and configurations, service level agreements, and IT budgets. [0005] It is common for large enterprises to have thousands of different data assets, each with a unique schema; i.e., thousands of different metadata descriptions, within their IT. For example, financial data may be spread out over several different relational databases, personnel data may be spread out over several different XML document stores, and inventory data may be spread out according to several different Cobol Copybook definitions. [0006] In order to describe all of the different types of enterprise IT assets, including inter alia data assets and applications, a metamodel is used to model the entire repertoire of IT asset types. Such asset types include inter alia relational database schemas, XML schemas, COBOL Copybook definitions, Java applications, Engage Transform and Load (ETL) middleware and the structures associated therewith. A "metamodel" is a model for metadata, and describes the types of assets within the enterprise IT, and their inter-dependencies. Actual metadata itself instantiates the metamodel. [0007] The three levels of data--instance data, metadata and metamodel, form a data hierarchy, wherein the structure of each level of data is described by the level above it. The three data levels within the data hierarchy are denoted by M0 (instance data), M1 (metadata) and M2 (metamodel). More generally, M0 includes instance data, messages and specific interactions; M1 defines actual IT structures, such as specific schemas, interfaces and inter-dependencies; and M2 describes types of structures and cross-references of IT. [0008] In order to enable efficient use of a rich and configurable metamodel, a system is needed that supports (i) metamodel editing; (ii) classes, properties, inheritance and multiple inheritance within a metamodel; and (iii) industry standards such as Meta-Object Facility (MOF.TM.) for structure of the metamodel, XML Interchange (XMI.TM.) for import and export of metadata, and standard metamodels such as the Common Warehouse Metamodel (CWM.TM.) and the DMTF Common Information Model (CIM.TM.). MOF.TM., XMI and CWM.TM. are standards developed by the Object Modeling Group (OMG.RTM.); and CIM is a standard developed by Distributed Management Task Force, Inc. (DMTF.TM.). [0009] While the prior art includes flexible metamodels such as MOF-compliant metamodels, which flexibly define the structure of metadata, metamodels have not been used to describe specific rules which metadata must obey. Therefore, metamodels have hitherto had limited use in the detailed governance of IT. [0010] Furthermore, although there are standard languages such as MOF for specifying metamodels, in reality sources of metadata currently have their own metamodels, making it difficult to accumulate metadata from different sources into one overall metadata model of enterprise IT. SUMMARY OF THE DESCRIPTION [0011] The present invention concerns a method and system for metadata management. The present invention supports (i) a rich and configurable metamodel with run-time metamodel editing; (ii) multiple inheritance and the addition of business rules within a metamodel; (iii) industry standards such as MOF.TM., XMI.TM., CWM.TM. and CIM.TM.. The metamodel of the present invention supports an endless number of types of metadata, including inter alia metadata for data assets, business applications, organization charts, process models, hardware configurations and network topographies; and (iv) mapping between incompatible metamodels to enable import, export, synchronization and federation of metadata. [0012] There is thus provided in accordance with a preferred embodiment of the present invention a metadata management system for importing, integrating and federating meta-data, including a configurable metamodel for modeling metadata that describes enterprise IT assets, 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 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. [0013] There is further provided in accordance with a preferred embodiment of the present invention a metadata management system for validating metadata, including a configurable metamodel for modeling metadata that describes enterprise IT assets, business rules on the metamodel, and a metadata validation module operating on said configurable metamodel for validating specific metadata against the metamodel business rules. [0014] There is yet further provided in accordance with a preferred embodiment of the present invention a metadata management system for generating metadata including a configurable metamodel for modeling metadata that describes enterprise IT assets, business rules on the metamodel, and a metadata generation module operating on said configurable metamodel for guiding the generation of specific metadata using the metamodel business rules. [0015] There is moreover provided in accordance with a preferred embodiment of the present invention a metadata management system for managing an IT organization, including a configurable metamodel for modeling metadata that describes enterprise IT assets, business rules on the metamodel, and a validation module operating on said configurable metamodel for validating rules for IT governance against the metamodel business rules. [0016] There is additionally provided in accordance with a preferred embodiment of the present invention a method for importing, integrating and federating metadata, including 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 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. [0017] There is further provided in accordance with a preferred embodiment of the present invention a method for validating metadata, including 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. [0018] There is yet further provided in accordance with a preferred embodiment of the present invention a method for generating metadata including 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. [0019] There is moreover provided in accordance with a preferred embodiment of the present invention a method for managing an IT organization, including 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. [0020] There is additionally provided in accordance with a preferred embodiment of the present invention a computer-readable storage medium storing program code for causing a computer to perform the steps 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 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. Continue reading about Business rules for configurable metamodels and enterprise impact analysis... Full patent description for Business rules for configurable metamodels and enterprise impact analysis Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Business rules for configurable metamodels and enterprise impact analysis patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Business rules for configurable metamodels and enterprise impact analysis or other areas of interest. ### Previous Patent Application: Standard cell library having globally scalable transistor channel length Next Patent Application: System and method of model-driven development using a transformation model Industry Class: Data processing: software development, installation, and management ### FreshPatents.com Support Thank you for viewing the Business rules for configurable metamodels and enterprise impact analysis patent info. IP-related news and info Results in 0.21099 seconds Other interesting Feshpatents.com categories: Qualcomm , Schering-Plough , Schlumberger , Seagate , Siemens , Texas Instruments , 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
