Thank you all. I like the idea of an "(Enterprise)Store for Everything" a lot.
For process assets ... some brainstorming: 1) The artifact "text based process" is a "non executable process model". This process model can be "instantiated" by creating a "text based process instance" -> this feature would like a predefined document-type/-structure/-flow in DMS/ECM (like alfresco). 2) The artifact "BPMN process" is a "non executable process model" (i. e. for documentation purposes) or a "executable process model". For create/edit/viewing the "BPMN model" a BPMN 2.0 graphical editor and/or viewer is required. The "executable process model" requires a "runtime environment" like the WSO2 BPS for "running the instances". Amal Gunatilake is working on WSO2 BPMN Explorer jaggery app <https://github.com/wso2-dev/carbon-business-process/tree/e424fe3ad681ecebfee1e73cc008fbd9dda460fc> and BPMN humantask jaggery app <https://github.com/amalhub/bpmn-humantask> 3) The artifact "BPEL process" ... like "BPMN process" How would the architecture for an integrated WSO2 Process Landscape look like? 2014-09-04 10:28 GMT+02:00 Shiva Balachandran <[email protected]>: > > > > On Wed, Sep 3, 2014 at 5:53 PM, Manfred Herrmann < > [email protected]> wrote: > >> Hi Shiva, >> >> a "process store" sounds like a store for "business process >> definition/documentation". I am wrong? >> > No, you are correct, we are looking to build a store to hold business > process definitions/ documentations along with organisational charts, IT > activities and many more models. > >> >> If it is a "store for business process documentation", some questions >> about: >> >> Is the main requirement of the stakeholder based on "easy access to >> process definitions/documentation" for all employees? >> > Yes, also to associate and view similar processes and the variants. > >> >> What is a "text based process", "process model" and a "instance of a >> process"? >> > Text based process is the same as business process definition, where the > content is purely textual. > > A process model is the structure of the process, the name, description, > values, associations and much more informative values related to the > process. > > >> How would you compare the "BPM process definition" (like bpmn and bpel) >> with "text based process"? >> > > Both are the same as mentioned above. The reason we used the wording "Text > based process" was to imply that the content was purely textual. > >> >> >> Thank you very much >> >> >> 2014-09-03 12:43 GMT+02:00 Shiva Balachandran <[email protected]>: >> >> Hi Sameera, >>> >>> We are currently looking at a single process model, which is text based >>> processes therefore there will be one single asset type, Processes. People >>> can create processes of this type and perform functions such as creating, >>> viewing, associating and other functionality. >>> >>> Thank you. >>> >>> >>> >>> On Wed, Sep 3, 2014 at 3:22 PM, Sameera Medagammaddegedara < >>> [email protected]> wrote: >>> >>>> Hi Chathura, >>>> >>>> Will there be two asset types managed by the ES? (Process Models and >>>> Processes) >>>> >>>> *Process Models* >>>> - Created and managed by Process Model designers >>>> - Visible in the store >>>> - Can be extended by users by specifying a parent process model >>>> - Will this extended process model be stored as a new process model? >>>> - Can original process model be modified by users? >>>> >>>> *Processes* >>>> - Created from process models in the Store >>>> - Created and managed by process consumers? >>>> - Visible in the Store >>>> >>>> *Types of users* >>>> - Process Model Designers >>>> - Process Model Consumers? >>>> - Process Consumers (Who is anyone that visits the Store front) >>>> >>>> Thank You, >>>> Sameera >>>> >>>> >>>> On Wed, Sep 3, 2014 at 2:52 PM, Chathura Ekanayake <[email protected]> >>>> wrote: >>>> >>>>> >>>>> On Wed, Sep 3, 2014 at 2:23 PM, Sameera Medagammaddegedara < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Shiva and Chathura, >>>>>> >>>>>> >>>>>> The processes will be built as an asset type of the Enterprise Store >>>>>>> as discussed and the utility functions of the store such as adding, >>>>>>> editing, viewing, searching and visualizing will be done in the store >>>>>>> front >>>>>>> rather than navigating to the publisher. >>>>>>> >>>>>> Currently there are no utility methods in the Store app code base >>>>>> that will allow you to provide adding and editing >>>>>> capabilities.However,this >>>>>> can be done by using the carbon module which is provided with the ES. >>>>>> >>>>>> >>>>>> As Shiva has mentioned, we want to do both adding and displaying >>>>>>> process models in the same UI, diverting from the current model of ES to >>>>>>> have a separate publisher and a store >>>>>>> >>>>>> Who will maintain and control the original version of the process? >>>>>> Will processes have a defined lifecycle? >>>>>> >>>>> >>>>> Processes can be viewed, edited and deleted by any user with relevant >>>>> permissions. Yes, processes have a lifecycle. >>>>> >>>>> >>>>>> An example requirement would be: a user browsing a process model may >>>>>>> want to add some details to certain sections of the model, so that he >>>>>>> should be able to do it from the same UI. Similarly, a user may want to >>>>>>> add >>>>>>> a specialized version of a currently displaying model >>>>>>> >>>>>> Would it be possible to model this as a user selecting a process then >>>>>> creating an instance of it with his own customizations? Where will these >>>>>> customizations be stored? >>>>>> >>>>> >>>>> This will not create a process instance. This scenario is creating a >>>>> new process model by adding details to an existing model. The new model >>>>> will also be stored in the store and the user has the option to add an >>>>> association stating that this is a specialization of the previous model. >>>>> >>>>> >>>>>> >>>>>> Will there be two classes of users? >>>>>> - Process designers who create and publish the process >>>>>> - Process consumers that take a process ,create an instance of it >>>>>> ,configure or customize it and then combine it with other processes? >>>>>> >>>>> >>>>> There are process consumers (i.e. process participants) who most of >>>>> the time just view the processes. However, other stakeholders (i.e. >>>>> process >>>>> designers, management staff, business analysts, etc.) may want to perform >>>>> actions like view, navigate, visualize, analyze, edit and add process >>>>> models. >>>>> >>>>> >>>>> >>>>>> >>>>>> Thank You, >>>>>> Sameera >>>>>> >>>>>> >>>>>> On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> As Shiva has mentioned, we want to do both adding and displaying >>>>>>> process models in the same UI, diverting from the current model of ES to >>>>>>> have a separate publisher and a store. An example requirement would be: >>>>>>> a >>>>>>> user browsing a process model may want to add some details to certain >>>>>>> sections of the model, so that he should be able to do it from the same >>>>>>> UI. >>>>>>> Similarly, a user may want to add a specialized version of a currently >>>>>>> displaying model. Therefore, I think the adding/editing functionality >>>>>>> has >>>>>>> to be provided in the same UI, controlled by user's authorizations. >>>>>>> >>>>>>> Regards, >>>>>>> Chathura >>>>>>> >>>>>>> >>>>>>> On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> The Enterprise Store currently satisfies necessity to host >>>>>>>> applications, gadgets and eBooks. Users are able to add new assets of >>>>>>>> the >>>>>>>> given type or create their own asset type and work with the store. A >>>>>>>> requirement has arose to develop a Process Store to host processes of >>>>>>>> all >>>>>>>> types and visualize associations with processes whilst providing other >>>>>>>> utility functions. I am currently working on building a Process Store >>>>>>>> to >>>>>>>> address the requirement. >>>>>>>> >>>>>>>> After discussion with the stakeholder we have agreed to initially >>>>>>>> build the store as an extension of the enterprise store and move the >>>>>>>> process store out as an product in the future. The extension to be >>>>>>>> built >>>>>>>> will be for textual based processes and in future will be able to >>>>>>>> support >>>>>>>> other type of processes too. >>>>>>>> >>>>>>>> The extension to be built will have the following functionality:- >>>>>>>> >>>>>>>> >>>>>>>> - Adding a text based process >>>>>>>> - Editing a text based process >>>>>>>> - View a text based process >>>>>>>> - Search for a text based process >>>>>>>> >>>>>>>> >>>>>>>> - Associate existing text based process to a new variant - The >>>>>>>> user when adding a new process can associate the new process to a >>>>>>>> existing >>>>>>>> one if the new process is a variant or similar to the existing >>>>>>>> process but >>>>>>>> a variant. >>>>>>>> >>>>>>>> >>>>>>>> - Navigating processes through associations - The user can >>>>>>>> navigate through the associations to find similar processes or their >>>>>>>> variants. >>>>>>>> >>>>>>>> >>>>>>>> - Visualizing associations in graph views - The associations >>>>>>>> between the processes will be sketched or depicted. This will be >>>>>>>> developed >>>>>>>> using JSPlumb. >>>>>>>> >>>>>>>> The processes will be built as an asset type of the Enterprise >>>>>>>> Store as discussed and the utility functions of the store such as >>>>>>>> adding, >>>>>>>> editing, viewing, searching and visualizing will be done in the store >>>>>>>> front >>>>>>>> rather than navigating to the publisher. >>>>>>>> >>>>>>>> Thank you >>>>>>>> >>>>>>>> -- >>>>>>>> Shiva Balachandran >>>>>>>> Software Engineer >>>>>>>> WSO2 Inc. >>>>>>>> >>>>>>>> Mobile - +94 774445788 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sameera Medagammaddegedara >>>>>> Software Engineer >>>>>> >>>>>> Contact: >>>>>> Email: [email protected] >>>>>> Mobile: + 94 077 255 3005 >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sameera Medagammaddegedara >>>> Software Engineer >>>> >>>> Contact: >>>> Email: [email protected] >>>> Mobile: + 94 077 255 3005 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Shiva Balachandran >>> Software Engineer >>> WSO2 Inc. >>> >>> Mobile - +94 774445788 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Shiva Balachandran > Software Engineer > WSO2 Inc. > > Mobile - +94 774445788 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
