Abstract: A method and computer program product for integrating risk management concepts into a standard business process metamodel by defining a set of metamodel extensions to standard process modeling languages that incorporate risk information directly in the process model. The method includes collecting risk-relevant information for addition to a business process model, and enabling visualizing of a risk-extended business process model. using a notation to express notions as failure modes of resources, root cause events, and sources of execution failure and low job output quality directly in the context of process models. Additionally, the method enables the computation of risk-related impacts on the distribution of process performance measures using a Bayesian network model or a discrete-event simulation model.

Abstract: Methods, systems and computer program products for improvement of vertical process merging by reconstruction of equivalent models and hierarchical process merging. Embodiments of the invention include a method for identifying and resolving differences between business process models, the method including receiving a first business process model project, identifying a second business process model project, performing changes to the second business process model project, merging the first and second business process model projects, creating a delta model configured to analyze the differences between the business process model projects, wherein an analysis of the differences between the first and second business process model projects are in the form of low-level changes and auto-applying the low-level changes of the first business process model project to generate a new business process model project.

Abstract: Changing a business process model involves several aspects: (1) given a set of change operations, dependencies and conflicts are encoded in dependency and conflict matrices; (2) given a change sequence for a process model M, the change sequence is broken up into subsequences such that operations from different subsequences are independent; (3) given a change sequence for a process model V1 and another change sequence for a process model V2, conflicts between operations in the different change sequences are determined; (4) the process structure tree can be used to localize dependency computations, yielding a more efficient approach to determining dependencies; and (5) the process structure tree can be used to localize conflict computations, yielding a more efficient approach to determining conflicts.

Abstract: A method for modeling business transformation includes steps of: constructing a first analysis model based on at least one legacy-business-process-model; and analyzing the first analysis model in conjunction with at least one business-process-reference-model. The method further includes deriving a second analysis model in response to analyzing the first analysis model in conjunction with the at least one business-process-reference-model and refining the second analysis model to obtain a design model.

Abstract: A method of automatic pattern based editing of business models on a canvas of business model editing application includes receiving a request to automatically edit a business model, constructing an initial current set C of elements from the business model, constructing an initial next set N of elements from the business model, and connecting elements between the initial current set C and the initial next set N until all elements in both the initial current set C and the initial next set N have been connected. The connecting is based on at least connecting elements sequentially if the elements exist from left to right on the canvas, and connecting elements in parallel or using a decision and merge combination if the elements exist from top to bottom on the canvas.

Abstract: A method and system for guided resolution of inter-model inconsistencies are provided. A method includes grouping inconsistencies, detected as a result of a model-driven software development process, into model partitions within a list by analyzing relationships between the underlying models and identifying model partitions that are capable of being processed independently from one another during a resolution process. The method also includes assigning priorities to models that contribute to the detected inconsistencies and inconsistency types. The method further includes reordering the list of inconsistencies to minimize the number of context switches during the resolution process and presenting, via a user interface screen, a listing of the inconsistencies and associated resolutions resulting from the reordering to the user at a client system. The user applies a selected resolution for each of the inconsistencies.

Abstract: Methods and apparatus are provided for production of a difference log in a data processing system The difference log defines differences between process models defined in system memory. For each of the process models, model structure data provided in memory defines a hierarchy of SESE regions representing the structure of that model. Also provided in memory are model comparison data defining correspondences between elements of the models, and region comparison data defining correspondences between regions of the SESE region hierarchies for the models. The model comparison and region comparison data are analyzed to identify differences between the SESE region hierarchies, and a difference log defining said differences is produced. In preferred systems, the model structure data and the region comparison data is computed for the models, and the difference log has a hierarchical structure corresponding to the structure of the process models.

Abstract: A method and system for inconsistency resolution in a model-driven software development environment are provided. A method includes performing a safety analysis for resolutions in response to detected inconsistencies to determine whether the resolution, if implemented, will lead to a resolution cycle when applied to a given inconsistency. The determination includes processing a resolution tree for the inconsistency and, using a resolution strategy tree, for each resolution that resolves an inconsistency, analyzing whether beginning with the resolution, it is possible to resolve all the inconsistencies subsequently introduced as side effects without a resolution cycle occurring. The analysis includes traversing the resolution strategy tree, whereby all resolution strategies derived by traversing the resolution strategy tree lead to a resolution cycle if the resolution strategy tree is infinite.

Abstract: A method of organizing received decision instances based on reference architecture, including determining a respective particular project phase attribute for each of the decision instances, classifying the decision instances, determining a respective scope attribute for each of the decision instances, categorizing the decision instances in accordance with each of the respective scope attributes thereof, for all decision instances with the same categorization and with the same classification, ordering the corresponding decision instances by model elements, modeling directed links between apparently dependent decision instances, analyzing the dependent decision instances to confirm that the decision instances satisfy the apparent dependencies represented by the directed links and producing an error message if a result of the analysis is negative, and generating a real-time updateable and/or modifiable to-do list interface.

Abstract: A method of actively managing software design decisions including identifying design model elements from a given requirements model, computing a design model element type for each of the design model elements, accessing reference architecture to locate one or more decision templates, confirming that a scope of the decision template is applicable to the design model element type, and if the scope of the decision template is applicable to the design model element type, generating decision instances based on the decision template to be applied to the design model element.

Abstract: A system for combining quality assurance and model transformations in a business-driven development environment includes a host system executing a business modeling application, a transformation framework including a transformation programming interface (TPI) and a quality assurance framework executing on top of the business modeling application, and a plurality of transformation plug-in tools in communication with the TPI. The TPI includes options for model access and traversal, model element creation/removal, model element property editing and analysis. The options are applied to the transformations, via the selected transformation plug-in tools, to a business model resulting in a modified business model that conforms to an information technology (IT)-based executable code.

Abstract: Methods and systems are provided for automatic identification of an insertion point. Comparison defining the correspondence between elements of models is done. The sequence order of elements in the second model is analyzed to identify predecessor and successor elements of the element t. The comparison is used to identify a set of transferred predecessors (Ptrans), comprising elements of the first model which correspond to predecessor elements (PS) in the second model, and a set of transferred successors (Strans) comprising elements of the first model which correspond to successor elements (SS) in the second model. Then, positions of the elements x, y in the sequence order of the first model are compared with the positions of elements in the sets of transferred predecessors and successors (Ptrans, Strans). An edge between the elements x and y is identified as an insertion point.

Abstract: Techniques for composition of model transformations from a predetermined set of model transformations. A state machine is provided in memory. The states are defined in the state machine in terms of predetermined model attributes. In response to specification of a target state for an input model to be transformed, an execution sequence in the state machine, between a start state corresponding to the input model and an end state corresponding to the specified target state, is selected. Each transformation in the selected sequence is then successively executed on the input model. After executing each transformation in the selected sequence, the transformed input model state is compared to the model state defined in the state machine to determine if the selected sequence is inoperable for the input model. If so, an alternative execution sequence in the state machine, between the input model state and the specified target state, is selected.