Abstract: The embodiments provide for automatic incremental learning of programming language grammar. A corpus (i.e., a text file of software code written in a particular programming language) is parsed based on a set of grammar rules. An unparsed statement from the corpus is identified along with a section thereof, which did not match any of the grammar rules in the set. A subset of the set of grammar rules at fault for the parsing failure is identified. Groups of new grammar rules are developed such that each group comprises at least one new grammar rule, such that each group can parse the unparsed statement, and such that each new grammar rule is a modification of grammar rule(s) in the subset. One specific group can then be selected for possible incorporation into the set of grammar rules. Optionally, before a specific group is selected, the groups can be heuristically pruned and/or ranked.

Abstract: Systems and methods execute a computer program to produce a trace of the computer program and divide the trace into independent threads of execution. Each of the independent threads of execution comprises an execution sequence of the lines of programming code that ends with an identified write line of programming code that outputs an incorrect result. These systems and methods also identify key field within each of the independent threads of execution. In programming, which is processing records in a table one by one, key-fields are a subset of the fields of the table. The key fields impact the computations sequence leading up to the identified write line of the programming code. These systems and methods identify key-based dynamic slices from the independent threads of execution. Each of the key-based dynamic slices includes lines of programming code that are used in computations, processing the table records corresponding to the key fields.

Abstract: Harvesting assets for packaged application practices, in one aspect, may include obtaining one or more work products associated with deployment of packaged software applications, extracting content and style, enhancing content and style with models of work products, and storing assets in asset repository.

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

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

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

Abstract: An example embodiment disclosed is a system for automated model extraction of documents containing flow diagrams. An extractor is configured to extract from the flow diagrams flow graphs. The extractor further extracts nodes and edges, and relational, geometric and textual features for the extracted nodes and edges. A classifier is configured to recognize process semantics based on the extracted nodes and edges, and the relational, geometric and textual features of the extracted nodes and edges. A process modeling language code is generated based on the recognized process semantics. Rules to recognize patterns in process diagrams may be determined using supervised learning and/or unsupervised learning. During supervised learning, an expert labels example flow diagrams so that a classifier can derive the classification rules. During unsupervised learning flow diagrams are clustered based on relational, geometric and textual features of nodes and edges.

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

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

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

Abstract: Reusing assets for packaged software application configurations may include defining one or more query criteria based on information associated with a project, querying an asset repository stored in a storage device using the one or more query criteria, receiving a list of one or more assets from the asset repository in response to the querying, and using the one or more assets on the list to compose a document defining deployment procedures associated with deploying a packaged software application.

Abstract: Techniques for generating and executing a performance-aware enterprise component (PAEC) are provided.

Abstract: Non-functional concerns are addressed within an abstract model corresponding to a real-world system. One or more annotations profiles are constructed. Each annotations profile describes one or more annotations, where each annotation corresponds to and represents one of the non-functional concerns. Each of a number of modeling elements of the abstract model is associated with an annotation corresponding to a non-functional concern pertaining to the modeling element. One or more transformation templates are constructed. Each transformation template transforms the abstract model to a specific implementation platform to which the transformation template corresponds. For each transformation template, the abstract model as has been transformed to the specification implementation platform to which the transformation template corresponds is executed. Such execution results in consumption of the non-functional concerns represented by the annotations associated with the modeling elements.

Abstract: Harvesting assets for packaged application practices, in one aspect, may include obtaining one or more work products associated with deployment of packaged software applications, extracting content and style, enhancing content and style with models of work products, and storing assets in asset repository.

Abstract: One or more document templates defining deployment procedures associated with deploying a packaged software application are obtained. One or more objects are created representing the one or more document templates and one or more elements of the one or more documents, and one or more links between the one or more objects are created. The one or more links represent one or more relationships between the created one or more objects. The one or more objects and the one or more links may be stored and/or output in a selected format.

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

Abstract: Techniques for modeling a composite application are provided. The techniques include identifying one or more entities that are processed in a user enterprise, identifying one or more actions to be performed during a lifecycle of the one or more entities, and modeling a composite application based on the one or more actions to be performed during a lifecycle of the one or more entities.

Abstract: 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”.

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

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