Community
Participate
Working Groups
BPMN2.0 models are considered as target models in many model to model transformations. At the end of every transformation there is a need to open and visualize the new created models. The problem with the BPMN2.0 modeler is the following: in order to open a BPMN2.0 model it must be composed of basic BPMNDI and DC elements and from these elements is the <dc:Bounds> element with the attributes x and y to position the element in the diagram. As no auto layout function is availabale within the modeler, it is obligatory to assign these values either manually or create a certain algorithim to position graphical elements which sounds a heavy task. a scenario to the above problem is the following: -User X wants to transform an 'A' model to a BPMN2.0 model -X applies the ATL transformation rules to the 'A' model -The result of the transformation is a BPMN2.0 model with only BPMN elements -X needs to open his model in the BPMN2.0 modeler -X develops an XSLT sheet to create the BPMNDI elements -X finds himself obliged to create an algorithim to position the graphical objects (assign x and y attributes) -As X is not familiar with such rules and algorithims, X is blocked How auto layout of graphical objects is helpful in such scenarios? x and y attributes are not mandatory, and if thier value is null the modeler will assign proper values depending on relations and connections between objects
Possibly following publication provides guidance for layouting: Ingo Kitzmann, Christoph König, Daniel Lübke, Leif Singer, "A Simple Algorithm for Automatic Layout of BPMN Processes," cec, pp.391-398, 2009 IEEE Conference on Commerce and Enterprise Computing, 2009 An MIT-licensed implementation is available at https://code.google.com/p/oryx-editor/source/browse/#svn%2Fbranches%2FBPMNLayouterInformatiCup%2Feditor%2Fserver%2Fsrc%2Fde%2Funihannover%2Fse%2Finfocup2008%2Fbpmn%2Flayouter
It sounds like you have an interest in this technology. Would you like to take this on as a pet project? ;)
*** Bug 417567 has been marked as a duplicate of this bug. ***
Improved layout for branching flows, for example: +--- Task | Gateway ---+ | +--- Task