Business Process -based Conceptual Design of Rich Internet Applications

1,345 views
1,266 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,345
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
24
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Business Process -based Conceptual Design of Rich Internet Applications

  1. 1. Business Process -based Conceptual Design of Rich Internet Applications<br />Marco Brambilla, J.Carlos Preciado, Marino Linaje, Fernando Sánchez-Figueroa<br />
  2. 2. Summary<br />Motivation and objetives<br />RIA modelingfoundations<br />RIA modeling foundations with BPMN<br />Data modeling<br />Business Logic modeling<br />Communication modeling<br />Transforming from BPMN to WebML and RUX models<br />BPMN to WebML transformations<br />From WebML to RUX-Method transformation (Presentation modeling)<br />Case Study<br />
  3. 3. Motivation and objetives<br />
  4. 4. Basic RIAs modeling foundations<br />
  5. 5. Representing RIA modeling foundations with BPMN<br />For specifying BP models BPMN and its companion metamodelBPDM. <br />the BPMN to generate later the design of data, business logic, communication, and presentation<br />interpretation of the BPMN models that fits the needs of RIAs<br />define a translation to the various aspects of the application. <br />An intermediate level of abstraction is required:<br />activities and events specified in the BP model should be the ones that trigger the behaviour of the business logics and of the presentation components. <br />
  6. 6. Representing RIA modeling foundations with BPMN<br />BPMN models for RIAs is to specify the distribution of the computation and data storage between client and server. <br />pools and lanes must be organized:<br />pool  actor/role of the Web application. <br />each pool is composed by a set of predefined lanes that must be marked as: CLIENT, SERVER, and (optionally) CLIENT-SERVER.<br />Client and server lanes will comprise aspects that will stand/occur just in one of the sides<br />client-server lane may be used to represent common issues.<br />
  7. 7. Data modeling<br />BPMN data objects can be exploited for inferring the basic information concepts in the data model of the application. <br />Data distribution (client or server) and persistence (persistent or volatile) can be described in the BPMN: <br />Data objects are represented inside the client or the server lanes<br />Persistence is described by the state attribute (‘P’ or ‘V’) within the data object<br />Special considerations:<br />When the same name is used by two data objects, these data objects are considered the same<br />
  8. 8. Business Logicmodeling<br />BPMN allows representing the business logic by using the control flow (arrows), connection objects, artifacts, and lanes. <br />Client and Server lanes indicate those elements that will stand/occur at one of the sides, while mixed business logic can be specified in the Client-server lane. <br />The client-server lane is useful for two different scenarios:<br />To perform the same operation twice (once at client and later at server side).<br />On BPMN collapsed sub-processes where their expansions involve processes both in the client and in the server lanes.<br />Special considerations:<br />relation between the activities and the data  associations.<br />Directionality (depicted by an arrow) added to an association shows whether the data object is an input or an output to the activity<br />
  9. 9. Communicationmodeling<br />we focus in the native communication mechanisms that these applications provide. <br />We must notice that in RIAs the servers are also able to begin a conversation, by means of PUSH communication paradigms (plus traditional client-server PULL communication). <br />BPMN controlflow arrows are used to describe communication between activities of the processes. <br />The kind of communication (push or pull) can be immediately derived from the direction of the arrow from the origin to the target. <br />Control flows can be refined by a text annotation specifying whether the transmission is synchronous (‘S’) or asynchronous (‘A’). <br />
  10. 10. Transforming from BPMN to WebML and RUX models<br />In our proposal, the information specified in the BP is used by the WebML model as a high level specification of the hypertext behaviour<br />The design steps can be summarized as follows: <br />
  11. 11. BPMN toWebMLTransformation<br />Process metadata model (RIA specific information is in bold red font).<br />
  12. 12. From WebML to RUX-Method transformation<br />
  13. 13. Case Study<br />a product list on which filters, searches and selections can be applied; on the right side<br />the details of the selected product; and at the bottom <br />the shopping cart<br />drag&drop<br />
  14. 14. Case Study<br />
  15. 15. Case Study<br />

×