International Business Machines Corporation

Anthony Hayden Lindsey

Mila Keren

Gary Martin Johnston

Yael Shaham-Gafni

Timothy W Wilson

Beth Bridgers Lindsey

Gregory Thomas Melahn

Samuel Anthony Ruby

Edward Kurt Borchardt

Tuyet Diem Huynh

Frank Sydnor Haynes

John Henry Koch, Iii

Mark Edward Lorenz

George A McKenna

Steven Michael Milinkovich

John T Mason

Scott G Carley

Pamela B Owens

Bruce G Whitenack, Jr

Alex Abraham Akilov

Peter Paul Dimitrios

A system for generating target language source code utilizing an object oriented code generator is disclosed. A desired computer programming function is specified using a fourth generation language. An object oriented converter converts the fourth generation language specification into an object oriented model which retains the function and inter-relationships defined in the specification. The object oriented model is applied against a set of source code templates for a desired target language, which will typically be a third generation language. An object oriented generator engine parses the resulting collection of templates to form source code files having the desired programming function in the desired target language.

System and method for generating target language code utilizing an object oriented code generator

The present invention provides a method, system, and computer program product for programmatically manipulating a user interface process to maintain synchronization of object-oriented programming language methods during a rollback operation in a procedural logic debugger. This technique is designed for use in integrated execution environments that provide seamless execution of, and transfer of control between, objects written in an object-oriented programming language and business logic written in a procedural programming language, and which span multiple programming models based on different technologies. The disclosed technique enables developers to have greater control over the debugging process by manipulating the next statement to be executed. The procedural debugger automatically positions to the selected statement, and a corresponding user interface process is then programmatically adjusted to bring the user interface into synchronization with the selected statement. (Or, the debugger itself may initiate the repositioning operation, in which case the technique operates in the same manner to provide a synchronized result.)

Manipulation of an object-oriented user interface process to provide rollback of object-oriented scripts from a procedural business logic debugger

The present invention provides a method, system, and computer program product for blending object-oriented (OO) programming languages with traditional (non-OO) programming languages such that they can execute and share data in a coordinated and integrated manner. Occurrence of a special keyword construct within a non-OO function triggers invocation of an OO method or script, the name of which is preferably specified as a parameter. The OO script executes synchronously, returning control to the non-OO function upon completion. The disclosed technique enables OO scripts to provide a more natural, logical interface to users wherein results of the non-OO function may be provided when most appropriate to the logic being executed, rather than requiring the non-OO function to be artificially designed as in prior art systems which must account for the limitations of their non-integrated execution environment.

Blending object-oriented objects with traditional programming languages

A technique, system, and computer program for presenting test coverage metrics in a visual programming environment. The information is presented in the same general visual manner in which a visual programmer creates a visual program. A number of alternative presentation styles are defined whereby the visual program is augmented to indicate test coverage status. For example, when displaying connections, one color may be used when displaying a connection to indicate that it has been covered, while a different color is used for connections that were not covered. Or, different line styles (such as solid versus dashed, or different degrees of line thickness) may be used to represent the same information. Alternatively, the test coverage status may be indicated by annotating the graphical representation of the visual program with text (such as &ldquo;covered&rdquo; or &ldquo;not covered&rdquo;).

Presentation of visual program test coverage information

A method, system, and computer program for presenting runtime performance data for analysis in a visual programming environment. The performance data is presented in substantially the same manner in which a visual programmer creates a visual program. A number of alternative presentation styles are defined whereby the visual program is augmented to indicate performance data. For example, when displaying connections, one color may be used when displaying a connection to indicate it has been executed a relatively high number of times, while a different color (or a different hue of the first color) is used for connections that were executed a relatively low number of times. Or, different line styles may be used (such as different degrees of line thickness, or solid lines compared to lines comprised of dashes of varying length) may be used to represent the same information. Alternatively, the performance data may be indicated by annotating the graphical representation of the visual program with text (indicating the number of times the connection was executed, for example). Total and local elapsed time will also be presented, using the same presentation techniques. Both the execution counts and the elapsed time may be indicated in actual numbers, or as a percentage of the corresponding totals.

Presentation of visual program performance data

A method, system, and computer program for providing test coverage metrics in a visual programming environment. A test coverage model for visual programming is defined, which accounts for the specialized nature of visual programming, and the metrics are based on this model. The metrics are expressed in terms of elements familiar to the visual programmer, as opposed to using source code metrics. In a preferred embodiment, these elements comprise events, actions, connections, and attributes. The code implementing a visual program is instrumented according to this model, and test coverage information is gathered as the instrumented program executes.

Technique for test coverage of visual programs

A method, system, and computer program for providing runtime performance analysis in a visual programming environment. A performance data collection technique for visual programming is defined, which accounts for the specialized nature of visual programming, and the analysis is based on this collected data. The performance data is expressed in terms of elements familiar to the visual programmer, as opposed to using a source code approach. In a preferred embodiment, these elements comprise events, actions, connections, and attributes. The code implementing a visual program is instrumented according to this performance data collection technique, and performance information is gathered as the instrumented program executes. Preferably, the information gathered comprises execution counts and elapsed time per element.

Visual program runtime performance analysis

A bridge for exporting and importing Envy components to and from a TeamConnection object oriented programming environment includes an Envy side and a TeamConnection side. The Envy side of the bridge creates and transfers an Envy library file that contains the contents of a selected Envy component and a Bill of Materials that describes the contents of the Envy Library file. The TeamConnection side of the bridge searches the transferred Bill of Materials for keywords associated with objects. The TeamConnection side of the bridge then creates a TeamConnection part for each object identified by a respective keyword. To import an Envy component stored within a TeamConnection object oriented programming environment, the TeamConnection side of the bridge creates and transfers an Envy library file containing the contents of the Envy component and a Bill of Materials describing the contents of the Envy library file. The Envy side of the bridge searches the Bill of Materials for keywords. Each identified object is then transferred into the Envy Manager of the Envy object oriented programming environment.

Bridge for exporting and importing objects between object oriented

A technique for permitting tracepoints to be set relative to data components of object oriented programs for debugging purposes is disclosed. A new method is created or an existing method is modified in an object which contains data relative to which tracing is desired. The new or modified method intercepts a message intended to access the designated data, and depending on the type of access being attempted and/or other conditions set by the developer, tracing may be initiated, modified, or terminated. Tracing is controlled by forwarding an appropriate message to a trace manager. The read or write operation is preserved by the newly created access method, which performs the desired access of the data component.

Data triggered trace support for debugging object oriented programs

System and method for generating target language code utilizing an

A technique for permitting tracepoints to be set relative to data elements for the debugging of a procedural program is disclosed. A proxy object is provided for each data element relative to which tracing is desired. The proxy object intercepts messages sent from the program to the data element caused by the execution of logic statements. In accordance with a developer's specified parameters, tracing functions relative to the data element are invoked in response to the receipt of each message dependent upon the nature of the message. The proxy object then forwards the message to the intended data element. Subsequent return of control from the data element to the program may also invoke the proxy object and affect tracing in accordance with parameters supplied by the developer to the debugger.

Data triggered trace technique for debugging software programs

A system for generating target language source code utilizing an object oriented technology is disclosed. A desired computer programming function is specified using an object oriented user interface. The result is an object oriented model of the desired target language program. The object oriented model is processed by a generator engine, which recursively generates each object in the model, if necessary, to surface all primitive objects relative to the target language contained in the model. Each primitive object is mapped to its corresponding template from a set of source code templates which corresponds to the desired target language, which is typically a third generation language. An object oriented generator engine parses the resulting collection of templates to form source code files having the desired programming function in the desired target language.

Object oriented system and method for generating target language code

A method for automatically translating computer application program modeling data expressed in entity/relationship terminology into computer application program model data expressed in object oriented terminology. A conversion process extracts unique entity names from the E/R model database and converts the entity names so found into object oriented class names. Next, based on the type of entity/relationships found in the E/R data model, target and source entities are identified for each 'is a' type of relationship and the converted object oriented class names are arranged in a hierarchical inheritance grouping in which each unique class name whose matching entity name is the source of a 'is a' relationship is subordinate to the unique object class name in the hierarchy which matches the target entity name is said 'is a' relationship and in which grouping any unique object class name that has no matching entity with an 'is a' relationship is placed subordinate to an arbitrarily selected unique object class name.

Entity/relationship to object oriented logical model conversion method

A system and method for enabling re-filtering of trace history data in a debugger without re-executing the program. Trace history data is stored together with its category information when the program is initially executed and trace history text is output to a user. If re-filtering is necessary, the new filtering criteria is applied to the stored trace history data and new text is output to the user.

Growing community of inventors

Fuquay Varina, NC, United States of America

Anthony Hayden Lindsey