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 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: 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: Computer-implemented methods and computer program products implement techniques for rating ideas in an idea management system. The techniques include circulating an idea to one or more users in an organization, receiving from one or more of the users in the organization an opinion of the idea, weighting each of the grades based on a first weight, and determining a grade of the idea based on the weighted grades. The first weight represents a characteristic of the corresponding user. The opinion includes a rating of the idea and the rating of the idea comprises a grade based on a first pre-determined scale.

Abstract: Systems and methods consistent with the present invention enable the use of computer-aided software engineering (CASE) tools to analyze and verify a configuration of a business application. By transforming business application structures into object-oriented structures, object-oriented CASE tools may be used to verify the underlying business application configuration. CASE tools may be used to analyze and test the effects of potential configuration changes in a business application. CASE tools could be applied to assist a consultant in configuring a business application or verifying an existing business application configuration.

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 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.

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: 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: In accordance with embodiments of the present invention, methods and systems redesign a business application composed in a first programming format by receiving a model representing the business application in a second programming format and processing the model using a code refactoring tool in the second programming format. A modification to the model made by the code refactoring tool is analyzed and applied, in the first programming format, to the business application.

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: Using methods and systems consistent with the present invention, deprecated logic entities of a business application may be identified using an object-oriented model of the business application. By transforming business application structures into object-oriented structures, deprecated logic entities in the business application may be exposed using object-oriented referential integrity checking.

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. The OOP model may be created by selecting the minimum set of attributes of the business application's data structures that uniquely define those data structures. 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.

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: 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 may transform business application objects and relationships into object-oriented programming elements, making it possible to display and manipulate representations of the business objects and their relationships in an easily comprehensible and manageable manner using standard object-oriented programming language tools. With this capability a user may easily see all the business objects that depend upon or are somehow related to the selected business object and gain awareness of the scope of objects in the business application that may be affected by a change to the selected business object. By using an object-oriented model of a complex, table-based business application, relationships not previously understandable may now be easily determined, displayed, and modified.

Abstract: Embodiments of methods and systems consistent with the invention transform business application operations, rules, and schemas into OOP constructs that represent the operation, rule, or schema, emulate its operation in terms of sequence with other operations, and represent its relationship(s) to the data it operates with and upon in the business application. An automated system determines each operation that makes up a schema or rule in the business application by analyzing the database table(s) that hold the schema or rule. The system may transform the business operation into part of an OOP model by declaring or creating an empty OOP language construct to represent the operation, such as a Java™ function or method. The transformation process may be controlled by a set of transformation rules.