International Business Machines Corporation

Boris Melamed

Benjamin Halberstadt

Marc N Haber

Gidi Weber

Hayden Marchant

Guy Yitzhaki

Gideon Sireling

Ilan D Prager

Joshua Fox

Efrat Hexter

Zvi Schreiber

Eliezer Israel

Yehuda Kossowsky

Rannen Meir

Ziv Zalman Hellman

Ruth M Amaru

Yifat Yulevich

Alexander Pyasik

Shlomo Steinhart

Joseph Edelstein

Erel Sharf

Benny Halberstadt

Shlomit Becker

Ben Berger

David Cavenor

Shani Turgeman

Ahuva Hazan-Fuchs

A principal model is configured within a memory to facilitate automatic generation of at least one resource for use by a computer-executable application. At least one model item required for a task that is absent from the principal model is identified. The absent model item is instantiated in a decoration model that operates with the principal model to augment operational functionality of the principal model.

Model augmentation in a model-driven application development environment

Aspects include detecting that an extract transform load (ETL) job in an ETL system has been submitted for execution. The ETL job can include an input data storage location and an output data storage location. The ETL job is analyzed to predict whether execution of the ETL job will result in sensitive information being made accessible to an unauthorized user. The analyzing can be based on a sensitivity status of contents of the input data storage location and a data lineage of contents of the output data storage location. The ETL job is prevented from executing based on predicting that execution of the ETL job will result in sensitive information being made accessible to an unauthorized user. Execution of the ETL job is initiated based on predicting that execution of the ETL job will not result in sensitive information being made accessible to an unauthorized user.

Real-time data leakage prevention and reporting

A computer system may generate a lineage graph for a data processing system. The lineage graph may contain one or more nodes, and it may identify the flow of data through the data processing system. The computer system may determine that a first node in the lineage graph defunct. The computer system may then generate a report for the data processing system and provide the report to a user. The report may include an explanation of why the first node is defunct. The computer system may insert an indication that the first node is defunct into metadata for the first node. The indication may also include the explanation of why the first node is defunct.

Identifying defunct nodes in data processing systems

A principal model is configured to facilitate automatic generation of at least one resource for use by a computer-executable application. The principal model includes a group of classes, references, attributes, and associations between any of the classes. At least one model item required for a task that is absent from the principal model is identified. The absent model item is instantiated in a decoration model that operates with the principal model to augment operational functionality of the principal model. The decoration model includes a class, a reference, and an attribute for any corresponding one of the group of classes, references, and attributes of the principal model.

Using metamodels during context-sensitive analyzes of reusable components of computer software applications, including identifying entry and exit paths into and from a reusable component within a metamodel of a computer application development environment, determining during a static analysis of a computer software application that navigation will proceeds along a path corresponding in the metamodel to such an entry or exit path, retaining, if an entry path, an identifier of an invoking node along the path within the computer software application, and, if an exit path, for each terminal node along each of a plurality of paths from the reusable component within the computer software application, comparing an identifier of an invoking node preceding the terminal node with the retained invoking node identifier, and determining, if the invoking node identifiers match, that the path among the plurality of paths is a correct path for a current context of the static analysis.

Metamodeling contextual navigation of computer software applications

Using metamodels during context-sensitive analyses of reusable components of computer software applications, including identifying entry and exit paths into and from a reusable component within a metamodel of a computer application development environment, determining during a static analysis of a computer software application that navigation will proceeds along a path corresponding in the metamodel to such an entry or exit path, retaining, if an entry path, an identifier of an invoking node along the path within the computer software application, and, if an exit path, for each terminal node along each of a plurality of paths from the reusable component within the computer software application, comparing an identifier of an invoking node preceding the terminal node with the retained invoking node identifier, and determining, if the invoking node identifiers match, that the path among the plurality of paths is a correct path for a current context of the static analysis.

Augmenting a model in a model-driven application development architecture, including defining a task to be performed on at least one model item of a principal model, where the principal model is configured to facilitate the automatic generation of at least one resource for use by a computer-executable application, identifying at least one model item required for use the task that is absent from the principal model, defining the absent model item in a decoration model, mapping the decoration model to the principal model, and storing both of the models on a computer-readable medium.

A computer-executable application is provided with access to resources generated using a principal model. A decoration model associated with the principal model is instantiated for use by the application. The application is provided with access to an object of the decoration model responsive to a request by the application to access an object of the principal model. The decoration model object corresponds to the principal model object.

Decorated model architecture for efficient model-driven application development

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.

Business rules for configurable metamodels and enterprise impact analysis

Creating data tables by identifying paths in a tree of data entities and relationships, the tree including data entities and relationships between the entities, where each of the paths originates from the same data entity, includes a terminal data entity that is at the to-many end of a one-to-many or many-to-many relationship with another data entity along the path, and includes no other of the data entities that lie along any path descending from the terminal data entity and that is at the to-many end of a one-to-many or many-to-many relationship with another of the data entities that lie along the path descending from the terminal data entity, and creating on a computer-readable medium a separate table for each of the paths, where each of the tables includes a column per each of the data entities of the path for which the table was created.

Disambiguation of tabular date

Managing metadata in a metadata repository that includes parsing metadata to determine an identity of the metadata and individual items associated with the metadata. Converting the identity of the metadata and the individual items associated with the metadata into corresponding object structures. Storing the object structure representing the identity of the metadata into a first table of the metadata repository and storing the object structures that represent the individual items associated with the metadata into a second table of the metadata repository. Responsive to receiving a request to modify a row in the first table or a row in the second table, logically deleting the row being modified without actually deleting or modifying the row, and creating a new row within the first table or the second table having the modified row, in which the new row further includes a link to the logically deleted row.

Safe multi-stream versioning in a metadata repository

A computer-executable application is provided with access to resources generated using a principal model. A decoration model associated with said principal model is instantiated for use by the application. The application is provided with access to an object of the decoration model responsive to a request by the application to access an object of the principal model. The decoration model object corresponds to the principal model object.

Growing community of inventors

Jerusalem, Israel

Boris Melamed