Abstract: A computing system uses tree data structures summarizing map builds to identify differences between map builds. The tree data structures include nodes summarizing portions of geographic regions of map builds. Responsive to a request to compare a first and second map build, the computing system accesses the tree data structures for the first and second map builds and identifies differences by traversing the tree data structures in lockstep and comparing the hash values for corresponding nodes in the tree data structures. The computing system traverses the tree data structures by identifying nodes that are different between the tree data structures until one or more bottom-level nodes are identified as different. The computing system identifies map features corresponding to the identified bottom-level nodes as different and transmits the identified map features to a client device associated with the request.

Abstract: In accordance with embodiments of the present invention, methods and systems analyze potential logic errors or problems of a business application by receiving a model representing the business application and processing the model using an object-oriented tool. The errors or problems may be corrected in the model and the correction applied to the business application. In one exemplary embodiment, the logic errors or problems may be marked in the model for identification to a user.

Abstract: Embodiments of methods and systems consistent with the present invention enable data-focused analysis of an application by reorganizing execution information generated by an application into categories associated with the data objects used by the application, and displaying or otherwise using the reorganized information for analysis, debugging, execution tracing, etc. of the application. Thus, the application execution information is presented from the data standpoint instead of from the execution sequence standpoint.

Abstract: Embodiments consistent with the invention transform business application logic entities or structures into OOP structures that represent the data, relationships, and operations of the business application structures. The business application structures are transformed from the application level, including consideration of the business application logic and relationships. In one embodiment, transformation is done using a set of automated transformation rules. The resulting OOP structure model of the business application structure may be used with OOP tools to analyze, maintain, debug, modify, and revise the business application structure, and to create new structures for the business application.

Abstract: A system and method for object reference monitoring. In one embodiment of the invention, a method includes running a computer application, monitoring a configuration point of the computer application during runtime, determining that a program object is accessed by the computer application at the configuration point, and storing data regarding the program object.

Abstract: An interactive configuration environment consistent with the present invention integrates and displays a table-based business application using a single, interactive display. When business application structures are displayed using object-oriented code structures, the business meaning of the object-oriented code structures may also be displayed in the integrated environment. Users can write a new business rule using object-oriented code, and that code may be converted into logic entities to apply the new rule in the business application. When a user rolls a mouse over an item in the object-oriented code, documentation of the underlying business meaning may be displayed in a pop-up box.

Abstract: Systems and methods consistent with the invention may analyze a business application's data, operations, and relationships and create a corresponding object oriented programming (OOP) model corresponding to the business application entities. In one embodiment the OOP model may be realized in the Java programming language and may include OOP objects, functions, and operators. Each OOP model accurately represents the data, relationships, and rules associated with the corresponding business entity. Once converted to an OOP model, systems and methods consistent with the invention may use standard OOP tools to understand, manipulate, design, redesign, analyze, and modify the business application. This can be done independently of the native business application system, as the OOP model is separate and independent from the business application entities. Modifications made to the OOP model may then be converted back into business application entities and installed in the native system.

Abstract: Embodiments consistent with the invention transform business application logic entities or structures into OOP structures that represent the data, relationships, and operations of the business application structures. The business application structures are transformed from the application level, including consideration of the business application logic and relationships. In one embodiment, transformation is done using a set of automated transformation rules. The resulting OOP structure model of the business application structure may be used with OOP tools to analyze, maintain, debug, modify, and revise the business application structure, and to create new structures for the business application.

Abstract: Exemplary methods and systems consistent with the present invention allow a user to compare different versions of a business application using an object-oriented model of the business application. By transforming business application structures into object-oriented structures, such as object-oriented language constructs, structures, and other elements, individual differences between versions of the business applications may be identified and displayed to a user, for example, on a user interface. A user may display object-oriented models of the business application representing, for instance, the latest control version, the latest deployed version, and a test version including test modifications. Having all three versions represented in object-oriented models allows a user to perform a three-way comparison between the object-oriented models, increasing productivity and efficiency of maintaining, debugging, modifying, controlling and deploying the business application.

Abstract: A system and method for object reference monitoring. In one embodiment of the invention, a method includes running a computer application, monitoring a configuration point of the computer application during runtime, determining that a program object is accessed by the computer application at the configuration point, and storing data regarding the program object.

Abstract: Embodiments of methods and systems consistent with the present invention enable data-focused analysis of an application by reorganizing execution information generated by an application into categories associated with the data objects used by the application, and displaying or otherwise using the reorganized information for analysis, debugging, execution tracing, etc. of the application. Thus, the application execution information is presented from the data standpoint instead of from the execution sequence standpoint.

Abstract: Embodiments of methods and systems consistent with the present invention enable data-focused analysis and filtering of a business application data event log by reorganizing information generated by an application into categories associated with the objects used by the application, and filtering the reorganized information for analysis, debugging, execution tracing, etc. of the application. Thus, the application execution information may be filtered and analyzed from the data standpoint instead of from the execution sequence standpoint.

Abstract: Systems and methods consistent with the invention create a model of a configurable business application that is compatible with an integrated development environment. The tools available in the integrated development environment (IDE) may be used as an integrated business application configuration environment (ICE) to analyze and change the configuration of the business application model while providing scope visualization, context visualization, object-interrelation analysis, error detection, and other benefits and features that an integrated environment provides for program code development. The reconfigured business application model may then be transformed into structures for the business application, so that the implemented changes to the model are applied to the actual business application.

Abstract: Embodiments consistent with invention detect and display errors in a business application by analyzing a hierarchical model of the business application that enforces the hirarchical structure of configuration objects that are used by the business application. Detected errors are marked for the configuration object containing the error and propagated up through the hierarchical structure of the business application model. A display of the hierarchical structure of the business application model with error indicators is useful for efficiently finding and correcting the errors in the actual business application.

Abstract: Systems and methods for merging models of a business application compare configuration models of the business application and display the differences between the models. Selections are made among the different displayed configurations, and a new configuration model is made based on the selections, merging the models that were selected from. The new configuration model may be transformed to configuration data and the business application reconfigured so that it matches the new model.

Abstract: Embodiments of the invention may transform business application relationships or links into OOP constructs that represent the relationship, tying together different types of business objects, such as data and operations, in a manner that allows automated OOP tools to check the integrity of the relationships and thus the integrity of relationships in the modeled business application. In one embodiment, an automated system uses an object-oriented language construct, such as an assignment operator (e.g., “=” in Java), to link together OOP objects representing business data and business operations. The object-oriented language construct binds different OOP objects representing business application objects and enforces a relationship between them.

Abstract: In accordance with embodiments of the present invention, methods and systems analyze potential logic errors or problems of a business application by receiving a model representing the business application and processing the model using an object-oriented tool. The errors or problems may be corrected in the model and the correction applied to the business application. In one exemplary embodiment, the logic errors or problems may be marked in the model for identification to a user.

Abstract: Systems and methods consistent with the invention may analyze a business application's data, operations, and relationships and create a corresponding object oriented programming (OOP) model corresponding to the business application entities. In one embodiment the OOP model may be realized in the Java programming language and may include OOP objects, functions, and operators. Each OOP model accurately represents the data, relationships, and rules associated with the corresponding business entity. Once converted to an OOP model, systems and methods consistent with the invention may use standard OOP tools to understand, manipulate, design, redesign, analyze, and modify the business application. This can be done independently of the native business application system, as the OOP model is separate and independent from the business application entities. Modifications made to the OOP model may then be converted back into business application entities and installed in the native system.

Abstract: Embodiments consistent with the invention transform business application logic entities or structures into OOP structures that represent the data, relationships, and operations of the business application structures. The business application structures are transformed from the application level, including consideration of the business application logic and relationships. In one embodiment, transformation is done using a set of automated transformation rules. The resulting OOP structure model of the business application structure may be used with OOP tools to analyze, maintain, debug, modify, and revise the business application structure, and to create new structures for the business application.

Abstract: In accordance with embodiments of the present invention, methods and systems analyze referential integrity of a business application by receiving a model representing the business application and processing the model using a code compiler to identify a compiler exception. The compiler exception is correlated in the model to a referential integrity instance in the business application and a correction of the compiler exception is enabled in the model. The correction is then applied to the business application to correct the correlated referential instance.