Circumstantial-evidence-based effort judgement for web service composition-based SOA implementations

Abstract

Considering web service composition (WSC) has increasingly become a significant practice in SOA implementations, WSC-based SOA projects would be particularly worth more attention. However, effort estimation for WSC-based SOA implementations may suffer from challenges because of the numerous and various approaches to WSC. This paper proposes circumstantial-evidence-based effort judgement as a supplementary to expert judgement to achieve qualitative effort comparison between different implementation proposals of a WSC-based SOA project. In detail:

Open kitchen vs closed kitchen

“…Then, the attribution of blame influences their responses toward restaurants (Choi and Mattila, 2008; Yen et al , 2004). Direct evidence, such as an eyewitness, immediately and precisely establishes attribution, whereas circumstantial evidence does not prove a fact but instead provides a basis for insufficient but reasonable inferences (Carlson and Dulany, 1988; Li et al , 2012). For example, if customers experiencing slow service at a restaurant find the chefs working hard in the kitchen, they are likely to interpret it as circumstantial evidence and infer the cause, the delay, as external to the situation, such as peak hours, rather than blame the restaurant.…”

Προσαρμογή Και Ευθυγραμμία Σχεδιαστικών Υποδειγμάτων Διεπαφών Σε Υπηρεσιοστρεφείς Αρχιτεκτονικές

“…Furthermore, recent studies indicate that the time performance and message size of RESTful web services are better than their SOAP and XML based counterparts [90], [34]. In addition, studies that examined the effort of certain service engineering activities, indicate that RESTful services are more maintainable on the server side than the corresponding SOAP-based services [40], and RESTful services are easier to compose than SOAP-based services [79]. Finally, new generation applications such as Semantic Web applications, and applications that utilize Linked Data can benefit from having a RESTful API according to related research [14].…”