Your SlideShare is downloading. ×
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
19_Turning Software.ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

19_Turning Software.ppt

178

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
178
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Turning Software into a Service 2004. 2. Yonsei Univ. Supercomputing Lab. Koh, Kwang-Won
  • 2. Introduction  Software as a Service (SaaS)  Assembled and provided service  Separate the possession and ownership of software from its use  Key know-how  Not who provides service  What service a transaction requires at any particular point
  • 3. SaaS and Other Service Forms  Software should deliver a service  Functionality that results from combining the facilities that the service integration layer provides with those from the component services that make up an application
  • 4. Service Integration Layer  Incorporation of four key service-oriented functions  Service description  Service discovery  Service delivery  Service composition
  • 5. Service Integration Layer  Service description (cont.)  Matches client needs to appropriate services  Provides the means of mapping  Accommodated descriptions  Functionality, interfaces, and nonfunctional characteristics  Constrained descriptions  QoS and cost
  • 6. Service Integration Layer  Service delivery (cont.)  Three steps  Invocation step  Calling-for step  Provision step  Validate the invocation  Suspension step  The client no longer needs the provider to supply the service
  • 7. Service Integration Layer  Service composition (cont.)  Need a suitable mechanism for creating new forms of service on demand  Nothing in SaaS prevents it
  • 8. Current Service-related Protocols  Requires further developments  XML-based protocols  SOAP, WSDL, and UDDI  IBM’s web services conceptual stack
  • 9. Current Service-related Protocols  W3C web services architecture stack
  • 10. Current Service-related Protocols  Proposed Web services stack framework
  • 11. Current Service-related Protocols  Network  XML-based messaging  Service description  Functional description of a web service  Interface and implementation  Nonfunctional description  QoS, cost, geographic location, number of retries, and legal factors
  • 12. Current Service-related Protocols  Conversations  External view of the messages  Correct data types and sequence of messages  Choreography  Coordinate Web services  Operation flow  Transactions  Monitoring transactions between Web services
  • 13. Current Service-related Protocols  Business process and workflow  Compose a higher-level service from several other Web services  Contracts  Outlines the format of the machine-readable contracts necessary to automate service-based electronic business  Discovery  Publish details of Web services  Search and discover any that meet the needs
  • 14. Realizing the Service Integration Layer  Service description  WSDL: not semantically  ebXML: Collaboration Protocol Profile (CPP) focuses largely on the transaction's technical aspects and Web Services Endpoint Language (WSEL) is designed to the nonfunctional, negotiable elements  DAML-S: the only available description method designed for describing the functional and nonfunctional aspects of services  Not yet final release
  • 15. Realizing the Service Integration Layer  Service discovery  UDDI: inability to allow semantic descriptions  DAML-S service profile  Ontology-based language
  • 16. Realizing the Service Integration Layer  Service negotiation  Collaboration Protocol Agreement (CPA)  Defines the common protocols and capabilities of only two parties  Intersection of the two parties’ CPP documents  Defined properties such as the contract’s duration and the transactions’ agreed security features
  • 17. Realizing the Service Integration Layer  Service delivery  ebXML’s CPA document  Monitor the transactions & terminate the process  Web Services Choreography Interface (WSCI): reacts in exceptional circumstances  WSCI and WSEL: detail time-out period
  • 18. Realizing the Service Integration Layer  Service composition  Several protocol combinations are available  Business Process Modeling Language (BPML) or Business Process Execution Language for Web Services (BPEL4WS): model the actual control and data flows within composition
  • 19. Conclusion  Service will be dynamically composable when needed in the SaaS model  Related to Handling Semantic information

×