Hi Frank,
First of all thank you for the important points brought out. Deriving
predecessor/successor relationships will be done for each chevron of a
diagram, as well as for the entire process that includes those chevrons in
a single diagram.
This is under the understanding that processes visualized by a set of
chevrons, belong to a generalized main process which can have
predecessors/successors of its own.
This is hoped to be implemented as follows.
1. When a chevron is clicked, display the relationships for that specific
chevron.
2. When the canvas/container of the diagram is clicked, display the
relationships of the main process.
Meeting with stakeholders was mainly focused on the xml format
representation ,as you have mentioned to separate the raw layout
information from the logic.
Therefore the position on the canvas of each chevron will be declared
separately from the logic of the business process model. Also BPMN 2.0 will
be taken into account to get a better understanding on this.
Current requirements did not include the import functionality of the xml
document,will discuss with the stakeholders regarding it so that we can add
it in the future.
As to considering the xml document when exporting the process model, the
idea expressed is to have a backup of the representation other than the xml
document? Please correct me if otherwise.
Hope things are clear now.Appreciate all the tips regarding the design
please let me know if there is anything more that needs to be added.
Thanks & Regards,
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
On Sat, Nov 1, 2014 at 10:46 PM, Frank Leymann wrote:
> Hi Himasha,
>
> I don't understand what you mean by "deriving predecessor/successor
> relationships for the entire diagram": does that mean that you derive the
> relationships for all chevrons of a diagram at once, i.e. that you apply
> your second bullet iteratively?
>
> Will the position on the canvas of each modeling element be part of the
> XML document you create? You want to take a look at BPMN 2.0: they
> separate the raw layouting information about a process model from the logic
> of the business process model: this allows different layouts for different
> tools, for different devices etc..
>
> I also suggest to consider the XML document you create as a step when
> exporting the process model. I.e. we should not assume that the XML is the
> only representation of the model in the database - correct?
>
> Finally: will you also support to import such an XML file that you create?
>
>
>
> Best regards,
> Frank
>
> 2014-10-30 9:19 GMT+01:00 Himasha Guruge :
>
>> Hi All,
>>
>> As per requirement in visualizing process associations of Process
>> Store, I have taken up the training project in creating a chevron diagram
>> editor/view for the Process Store. Similar to pre built textual based
>> process extension, this editor will also be build as an extension of
>> Enterprise Store, which will be moved to Process Store in the future.
>>
>> After discussion with the stakeholders, following functionalities are to
>> be supported.
>>
>>- Create chevron diagrams in drag and drop manner : JSPlumb will be
>>used for editor based manipulations.
>>- Derive predecessor/successor relationships from the positioning of
>>elements.
>>- Derive predecessor/successor relationships for the entire diagram
>>process.
>>- Navigate to associated process models/chevron diagrams from
>>elements in the current chevron diagram.
>>- Serialize canvas elements and convert into a specified xml format.
>>
>> Taking feedback of the stakeholder meeting into account, the core
>> elements and their formatting properties will be specified separately when
>> saving in xml format.
>>
>>
>> Thanks & Regards,
>>
>> Himasha Guruge
>> *Software Engineer*
>> WS*O2* *Inc.*
>> Mobile: +94 777459299
>> himas...@wso2.com
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
