Patent application number | Description | Published |
20090319981 | SYSTEM AND METHOD FOR GENERATING IMPLEMENTATION ARTIFACTS FOR CONTEXTUALLY-AWARE BUSINESS APPLICATIONS - A method for generating implementation artifacts for contextually-aware business applications includes utilizing a platform independent model (PIM) of a business application; generating a platform specific model (PSM) from the PIM, wherein the generating of a PSM includes one or more transformations between one or more meta-models of the PIM and one or more meta-models of the generated PSM; generating implementation artifacts; and binding the generated implementation artifacts with any existing services of the business application. | 12-24-2009 |
20100077386 | SYSTEM AND A METHOD FOR CROSS-PLATFORM PORTING OF BUSINESS APPLICATIONS AND MAKING THEM CONTEXUALLY-AWARE ON TARGET PLATFORMS - A method for cross-platform porting of applications includes extracting one or more platform independent models from an existing one or more composite applications running on a given source platform. These platform independent models are then transformed into implementation artifacts on another, target platform, thereby effectively porting the composite application from one platform to another. The generated implementation artifacts on the target platform leverage existing assets in the target environment, which makes these generated artifacts “contextually-aware”. | 03-25-2010 |
20100333069 | STATIC CODE ANALYSIS - Techniques for static code analysis are provided. The techniques include routing a code analysis request to a set of one or more static code analysis tools based on a context of the request, merging one or more tool-specific outputs of the code analysis, wherein merging the one or more tool-specific outputs comprises using one or more tool-specific mappings to one or more static code analysis abstractions and one or more source linkages of one or more static code analysis defects, performing a deep analysis on a set of one or more defect categories, and combining results of the merging with the deep analysis to filter out one or more false-positives and to add one or more new true positives to create an optimal set of defects. | 12-30-2010 |
20110131080 | Performance-Aware Enterprise Components - Techniques for generating and executing a performance-aware enterprise component (PAEC) are provided. The techniques include creating a performance-aware enterprise component definition, wherein an enterprise component is a component with defined behavior and data models that represent an enterprise capability and provide a service to a client through a defined interface, and wherein the definition comprises an extensible markup language file comprising process component lifecycle information, one or more data items to be used in the component lifecycle, and one or more performance metrics, and executing the performance-aware enterprise component, wherein executing the performance-aware enterprise component comprises reading the performance-aware enterprise component definition and one or more relationships with the one or more data items, and operating the component lifecycle, wherein operating the component lifecycle comprises using the one or more performance metrics within the component lifecycle to enable one or more localized changes to be made within the enterprise component. | 06-02-2011 |
20110313932 | MODEL-BASED PROJECT NETWORK - One or more project profiles, one or more people profiles, one or more work product profiles are created and connections are made among the one or more project profiles, one or more people profiles, and one or more work product profiles that form a network of projects, people, work products and others. A profile database stores the network of the one or more project profiles, the one or more people profiles, the one or more work product profiles. Data stored in the profile database is analyzed and one or more people, work products and projects that are related to current project are recommended for use in the current project. | 12-22-2011 |
20110314337 | Method and Apparatus for Locating Input-Model Faults Using Dynamic Tainting - Approaches based on dynamic tainting to assist transform users in debugging input models. The approach instruments the transform code to associate taint marks with the input-model elements, and propagate the marks to the output text. The taint marks identify the input-model elements that either contribute to an output string, or cause potentially incorrect paths to be executed through the transform, which results in an incorrect or a missing string in the output. This approach can significantly reduce the fault search space and, in many cases, precisely identify the input-model faults. By way of a significant advantage, the approach automates, with a high degree of accuracy, a debugging task that can be tedious to perform manually. | 12-22-2011 |
20120047391 | SYSTEMS AND METHODS FOR AUTOMATED SUPPORT FOR REPAIRING INPUT MODEL ERRORS - Systems and associated methods for automated repair support for input model faults are described. Embodiments automate generation of fault repair support by producing one or more repair action suggestions for a given input model containing faults. Responsive to an indication of one or more faults within the model, embodiments utilize a fault index to ascertain the nature of faults within the model and to compile one or more repair action suggestions. Users can review the repair action suggestions, and preview the impact each of these suggestions will have on the model if implemented, and select an appropriate repair action for repairing a model containing faults. | 02-23-2012 |
20120066662 | SYSTEM AND METHOD TO VALIDATE AND REPAIR PROCESS FLOW DRAWINGS - Disclosed is a system and method for validating and repairing flow diagrams using a process modeling validation method in conjunction with a process modeling repair method. The process modeling validation method points out structural ambiguities in a flow diagram that can make its automatic interpretation difficult. It also proposes fix to resolve such ambiguities. The method discloses a process semantic annotation scheme that can interpret process semantics in a flow graph implicit in a flow diagram. Further, the validation process compares one or more components of one or more drawings to a set of rules determined by a business process modeling standards and provides a set of semantic errors describing faulty parts of the drawing that do not comply with the business process modeling standards. The process modeling repair method corrects the drawing to ease and enable its automatic interpretation of the flow diagram and make the faulty parts of the drawing comply with the business process modeling standards. | 03-15-2012 |
20120084224 | AUTOMATICALLY CREATED REPORT GENERATOR FOR MANAGING INFORMATION TECHNOLOGY SERVICE PROJECTS - Reports to manage service projects may be generated by an automatically generated project report generator software tool. The project report generator software tool is automatically created from an object-based model of work products in a project, wherein the object-based model is executable by a machine and comprises a plurality of work product object and a recording of at least some relationships between the object, wherein each work product object represents a document that contains information about the service project. One or more reports can be generated by the project report generator software tool during the lifetime of the service project, wherein the report is generated using the object-based model and at least some of the information in documents represented in the object-based model. | 04-05-2012 |
20120179825 | PROCESS MANAGEMENT USING REPRESENTATION STATE TRANSFER ARCHITECTURE - Process management techniques using a representation state transfer architecture that manages a given process in a data-centric manner are disclosed. By way of one example, a method of managing a given process in a data-centric manner in a client/server environment, comprising at least one client and at least one server, comprises the following steps. The server obtains from the client at least one request associated with the given process. In response to the request obtained from the client, the server generates an entity, wherein the generated entity is represented in terms of a data model and a lifecycle model associated therewith, wherein the lifecycle model comprises states and state transitions with each transition caused by one or more activities in the given process, and wherein the given process is represented as a collection of communicating entities. The server sends a response to the at least one request to the client, wherein the response is based at least in part on the generated entity. | 07-12-2012 |
20130080837 | FAULT LOCALIZATION FOR DATA-CENTRIC PROGRAMS - Methods and arrangements for localizing faults in programs. A program is assimilated, the program comprising statements. Output behavior of the statements is modeled, and statement occurrences are annotated. Passing and failing spectra are differenced to yield a difference, and a fault is located via employing the difference. | 03-28-2013 |
20140358820 | COMPUTER ASSISTED CLASSIFICATION OF PACKAGED APPLICATION OBJECTS AND ASSOCIATED CUSTOMIZATIONS INTO A BUSINESS PROCESS HIERARCHY - Methods and arrangements for providing classification for a business process hierarchy. Packaged application objects are received, comprising at least one of the standard application objects and custom objects. At least one of the standard application objects is mapped to at least one node of a business process hierarchy, thereby forming at least one mapping template. At least one of the standard application objects is mapped to at least one of the custom objects to create a first mapping, and at least one of the custom objects is mapped to at least one of the standard application objects to create a second mapping. The at least one mapping template, the first mapping and the second mapping are combined, to create a mapping of at least one of the custom objects to the business process hierarchy. Other variants and embodiments are broadly contemplated herein. | 12-04-2014 |