Skip to main content
Article thumbnail
Location of Repository

Management concerns in service-driven applications

By Ahmed M. Alghamdi

Abstract

With the abundance of functionality-similar Web-Services, the offered or agreed on qualities are becoming decisive factors in attracting private as well as corporate customers to a given service, among all others. Nevertheless, the state-of-art in handling qualities, in this emerging service paradigm, remains largely bound to the aspects of technology and their standards (e. g. time-response, availability, throughputs). However, current approaches still ignore capital domain-based business qualities and management concerns (e. g. customer profiles, business deadlines).\ud The main objective of this thesis is to leverage the handling of quality and management issues in service-driven business applications toward the intuitive business level supported by a precise and flexible conceptualisation. Thus, instead of addressing qualities using just rigid IT-SLA (service-level agreements) as followed by Web Services technology and standards, we propose to cope with more abstract and domain-dependent and adaptive qualities in an intuitive, yet conceptual, manner. The approach is centred on evolving business rules and policies for management, with a clean separation of functionalities as specific rules. At the conceptual level, we propose specialised architectural connectors called management laws that we also separate from coordination laws for functionality issues. We further propose a smooth and compliant mapping of the conceptualisation toward service technology, using existing rule-based standards

Publisher: University of Leicester
Year: 2008
OAI identifier: oai:lra.le.ac.uk:2381/4748

Suggested articles

Citations

  1. (2002). (Editor): Service Level Agreement in the Data Center,
  2. 0: The Semantic Web. doi
  3. (2001). 1.2 Working Draft, World Wide Web Consortium
  4. A Comparison of XML interchange formats for business process modelling. In: Fischer L (ed) Workflow handbook. Future strategies,
  5. (2008). A CP-nets-based Design and Verification Framework for Web Services Composition. doi
  6. A Formal Basis for Architectural Connection. doi
  7. A Framework for Business Rule Driven Service Composition, doi
  8. (2007). A Homogenous Reaction Rules Language for Complex Event Processing.
  9. (2005). A Logic Based SLA Management Framework.
  10. A Methodology and Tool Support for Managing Business Rules in Organisations. doi
  11. (2003). A Model for Web Services Discovery With QoS. doi
  12. A Roadmap for the Elicitation of Business Rules doi
  13. A Service Level Agreement Language for Dynamic Electronic Services. doi
  14. A Superimposition Control Construct for Distributed Systems. doi
  15. A Survey of current Approaches towards Specification and Management of Quality of Service for Web Services. Freie Universittit Berlin, Institut ffir Informatik Takustr. 9, D- 14195
  16. An Approach to Extract RBAC Models from BPEL4WS Processes. doi
  17. An Expanded Model of the Service Encounter with Emphasis on Cultural Context.
  18. (2000). An introduction and history of software architectures, components, and reuse. In doi
  19. An Overview of AspectJ. doi
  20. (2006). Applying Distributed Business Rules - The VIDRE Approach. doi
  21. (2006). Architectural Handling of Management Concerns in Service-Driven Business Processes. il[SITEIS
  22. Aspect-Oriented Programming. doi
  23. (2005). Business Rules Integration in BPEL -A Service-Oriented Approach. doi
  24. (2003). Business-Oriented Management of Web Services. doi
  25. Categorical Semantics of Parallel Program Design. doi
  26. (2004). Classification of the Current Constraint and Capabilities Protocols in Describing Web Services,
  27. Coloured Petri Nets: Basic Concepts, Analysis Methods and practical Use. Volume 1: Basic Concepts. doi
  28. (2003). Conceptual Modeling of Web Service Conversations, doi
  29. (2004). Consortium: Service-Level Management Definition and Overview, available at: IiI tj). -, /xN'\vwjec. org//oi'i I iiie, "wtonalsi"', cry ice
  30. Contracts and Types. doi
  31. Coordination Architecture for Evolvable Event- Based Systems. doi
  32. Coordination for Distributed Business Systems. doi
  33. Coordination Languages and their Significance. doi
  34. (2002). Coordination Technologies for Just-in-Time Integration. In doi
  35. Coordination Technologies for Managing Information System Evolution. doi
  36. (2002). Defining and Monitoring Service Level Agreements for Dynamic e-Business.
  37. (2001). Description Language (WSDL) LI W3 C Note, World Wide Web Consortium
  38. (1998). Dynamic Management of CORBA Trader Federation.
  39. (1996). Dynamic structure in software architectures. doi
  40. Efficient Selection and Monitoring of QoS-aware Web Services with the WS-QoS Framework. Available at hill): ii'. doi
  41. Encounters: an Overview. In doi
  42. Enforcing Business Policies through Automated Reconfiguration. doi
  43. Expressing and organising business rules. doi
  44. Flexible Coordination of Service Interaction Patterns. doi
  45. (1992). Foundation for the Study of Software Architectures.
  46. (2003). G-QoSM: Grid service discovery using QoS properties.
  47. (2005). Gartner's Positions on the Five Hottest IT Topics and Trends in
  48. (2003). Getting to the Heart of SLM, Editorial, Network World. Available at: www. nwfusion. com,
  49. (2002). How to design a general rule mark-up language?
  50. Hybrid Web Service Composition: Business Processes Meet Business Rules. doi
  51. (2001). Intelligent Management of SLAs for Composite Web Services, LNCS, doi
  52. Introducing a Service Level Culture. Facilities, doi
  53. JAsCo for Linking Business Rules to Object-Oriented Software. doi
  54. (2003). Management Applications of the Web Service Offerings Language (WSOL). doi
  55. (2002). Managing Dynamic Services: A Contract Based. Approach to a Conceptual Architecture. IEEEIIFIP network operations and management symposium, doi
  56. Methodological Support for Service-oriented Design with ISDL. doi
  57. (2003). Migrating to a serviceoriented architecture,
  58. (2004). Model-based Discovery of Web Services. ICWS doi
  59. (2004). Modelling Contracts Using RuleML. In
  60. (2003). MOF-RuIeUML: The Abstract Syntax of RuleML as doi
  61. (2008). New Developments in Web Services and Ecommerce Web Services management approaches. doi
  62. (2004). Practical Service Level Management., Delivering High-Quality Web-Based Services,
  63. Precise Service Level Agreements. doi
  64. (2000). Programming and Prolog (2 ed), doi
  65. Programming finite-domain constraint propagators in action rules. doi
  66. QoS-Aware Middleware for Web Services Compositlon. doi
  67. (2005). RBSLA -A declarative Rule-based Service Level Agreement Language based on doi
  68. RBSLA based Implementation for Architectural Management Laws. doi
  69. Relating evolving business rules to software design. doi
  70. (2007). Rule-Based Service Level Agreements - Knowledge Representation for Automated e-Contract, SLA and Policy Management,
  71. (2000). Rules Group: Defining Business Rules - What Are They Really? httD: //www. bus inessrulesgroup. org/first paper/brOlcO. htm,
  72. (1993). Service Level Agreements - Measuring Cost and Quality in Service Relationships,
  73. (1994). Service Level Agreements.
  74. (2003). Service Level Management: End User's Drive Need to Monitor QoS and Content. Available at: www. telecomasia. net,
  75. (2006). Service Oriented Architecture (SOA) A New Paradigm to Implement Dynamic E-business Solutions. doi
  76. Service-level agreements at the Huddersfield NHS Trust. doi
  77. Service-oriented business and system specification: beyond object-orientation. doi
  78. Service-oriented computing: concepts, characteristics and directions. doi
  79. (2000). Services architecture overview - the next stage of evolution for ebusiness,
  80. (2004). Services-Oriented Dynamic Reconfiguration Framework for Dependable Distributed Computing. doi
  81. SLAng: A language for defining Service Level Agreements. doi
  82. (1996). Software architecture: Perspectives on an emerging discipline,
  83. Software architectures: Advances and applications: doi
  84. (2006). Specification, hqp: //www.
  85. (2002). Strategies for Web Hosting and Managed Services,
  86. Structural and behavioural compatibility of graphical service specifications. doi
  87. The CommUnity Workbench. ICSE, doi
  88. The Coordination Development Environment, doi
  89. (2003). The Impact of the Internet on Marketing and Sales. In doi
  90. (2005). The Rule Markup Initiative, doi
  91. (2006). The rule-ml family of web rule languages. doi
  92. The WSLA Framework: Specifying and Monitoring Service Level Agreements for Web Services.
  93. (2005). Towards a Distributed Service-Oriented Business Rules System. doi
  94. (2002). Towards a flexible deployment of business rules. Expert Systems with Applications, doi
  95. (2003). UDDIe: An Extended Registry for Web Services, doi
  96. (2002). Understanding quality of service for web services.
  97. (2002). Use SLAs in a Web Services context, Part 1: Guarantee your Web service with a SLA. Available at. hup: /. /wwý\ -1 2S. ihm. com deyeloperwmk., ý
  98. (2004). Usefulness of Software Architecture Description Languages for Modeling and Analysis of Federates and Federation Architectures. doi
  99. (2003). Using fuzzy Control to Maximize Profits in Service Level Management. doi
  100. (2003). UX -An Architecture Providing QoS-Aware and Federated Support for UDDI. The doi
  101. (2002). Vijay Machiraju and Akhil Sahai: doi
  102. (2007). Web Consortium doi
  103. (2001). Web Service Level Agreement (WSLA) Language Specification. doi
  104. (2004). Web Services - Concepts, Architectures and Applications. doi
  105. (2001). Web Services Activity Statement, available at: ýýý,
  106. (2004). Web Services Agreement Specification (WS- Agreement),
  107. Web services architect, Part 2: Models for dynamic-business. htlpý_ 100.11)lii. coii. i, "dcN, elol)ei-\vork-s xvehscrvIccs 11hriry (Last accessed:
  108. (2004). Web Services Description Language (WSDL) Version 2.0 part 1: Core language. WX Working Draft,
  109. Web services on demand: WSLA-driven automated management. doi
  110. (2005). Web Services Plaýform Architecture:
  111. What not How The Business Rules Approach to Application Development:

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.