Extended web services framework to meet non-functional requirements

ABSTRACT

Non-functional requirements/characteristics are important for providing effectively every kind of services including web services. A realistic web service must meet both functional and non-functional requirements of its consumers. Therefore, it is important that a web services framework is augmented so that non-functional characteristics of a web service can be determined at run-time and consumers are bound to a service that best meet their functional as well as non-functional requirements. In this paper, we propose an extension of the existing web services framework that enables a collection of functional and non-functional service characteristics at run-time, and usage of the collected data in discovery, binding, and execution of web services. Descriptions of new and enhanced components of the proposed framework are also presented. Typical publishing and usage scenarios in the proposed framework are also described.

REFERENCES

• 1: BEA Systems Inc., http://www.bea.com/webservices
• 2: Better Business Bureau, http://www.bbb.org
• 3: Department of Consumer Affairs, http://www.dca.ca.gov/, http://www.ci.nyc.ny.us/html/dca/home.html
• 4: HTTP -- Hypertext Transfer Protocol, http://www.w3.org/Protocols/
• 5: IBM Web Services, http://www-106.ibm.com/developerworks/webservices/
• 6: Microsoft Web Services, http://msdn.microsoft.com/webservices/
• 7: OASIS, 2002. Universal Description, Delivery, and Integration of Web Services (UDDI), Version 2.0, http://www.uddi.org
• 8: Singhera, Z., Dynamic Monitoring and Binding of Web Services, The 2004 International Symposium on Collaborative Technologies and Systems (CTS'04), San Diego, CA, January 18--23, 2004.
• 9: Sun Web Services, http://java.sun.com/webservices/
• 10: Shuping Ran, A model for web services discovery with QoS, ACM SIGecom Exchanges, v.4 n.1, p.1-10, Spring, 2003 [doi>10.1145/844357.844360]
• 11: Web Services, http://www.w3c.org/2002/ws
• 12: Web Services Coordination (WS-Coordination), http://www.ibm.com/developerworks/webservices/library/ws-coor
• 13: Web Services Description Language (WSDL), http://www.w3.org/TR/wsdl/
• 14: Web Services Security (WS-Security) Version 1.0, http://www.ibm.com/developerworks/webservices/library/ws-secure
• 15: Web Services Transaction (WS-Transaction), http://www.ibm.com/developerworks/webservices/library/ws-transpec/?dwzone= webservices
• 16: World Wide Web Consortium. Extensible Markup Language (XML), http://www.w3.org/XML
• 17: World Wide Web Consortium. Simple Object Access Protocol (SOAP), http://www.w3.org/2000/xp/Group/

INDEX TERMS

Primary Classification:
  H. Information Systems
  H.3 INFORMATION STORAGE AND RETRIEVAL
      H.3.5 On-line Information Services
          Subjects: Web-based services

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
        D.2.12 Interoperability

General Terms:
Design, Management

Keywords:
Web services, framework, non-functional requirements