In this third and last posting, I will show how the (platform independent) analysis model can be transformed into a (platform specific) design that leverages BPEL.
Design
The design involves mapping the analysis to artifacts that actually are implemented. Assuming that the Technical Architecture dictates a Service Oriented Architecture that uses BPEL to implement services and service orchestration, the design would at least include the following:
- WSDL’s
- A diagram design of the BPEL processes to implement
- A database design (that supports retrieval of resident information and storage and retrieval of parking permits and their applications)
To show how the implementation might look like the following two BPEL process diagrams are included.
A part of the ParkingPermitProcess looks as follows:
The same holds true for the user goal level Validate Parking Permit use case that looks as in the following picture (that actually zooms in on the ValidateParkingPermitApplication step of the previous picture):
In practice, you can imagine a human workflow step to be included that supports manual intervention of the outcome by Parking Services.
This ends a short history about the road you could walk from business process modeling to a BPEL implementation, and that with use cases as well. Now was that impressive or what?!
3 comments:
牙醫,植牙,矯正,矯正牙齒,皮膚科,痘痘,中醫,飛梭雷射,毛孔粗大,醫學美容,痘痘,seo,關鍵字行銷,自然排序,網路行銷,自然排序,關鍵字行銷、seo,部落格行銷,網路行銷,seo,關鍵字行銷,自然排序,部落格行銷,網路行銷,牛舌餅,婚紗,台中婚紗,腳臭,腳臭,腳臭,腳臭,腳臭,腳臭,腳臭,腳臭。
高雄婚紗,街舞,小產,雞精,性感,辣妹,雷射溶脂,雙下巴,抽脂,瘦小腹,微晶瓷,電波拉皮,淨膚雷射,清潔公司,居家清潔,牙周病,牙齒矯正,植牙,牙周病,矯正,植牙。
Really effective material, thanks so much for the post.
Post a Comment