El conocimiento del uso off-label por los distintos agentes sanitarios

This section is divided into two sections namely: making content Mashup ready and end- users programmed Mashups (i.e., usable Mashup tools). The research first discusses the usability of Mashup first followed by homogenization of web APIs.

3.4.1 Usability in Mashup Tools

This subsection discusses the studies that focused on encompassing usability principles to Mashup tools. The purpose of the conceptual evaluation model was to serve as a meaningful and useful framework or model for identifying the specific usability impact factors of Mashup makers, as indicated in (Sarraj, 2012). The conceptual evaluation model consisted of three main parts, which represent the three main usability aspects of Mashup makers. These three parts are: visual support, user interaction support and functional support. Firstly, the

42

visual support part is concerned with the usability of the user interface of the Mashup maker: layout of components, size, colour, and metaphors. Secondly, the user interaction support addresses the usability of the Mashup Maker from a user interaction perspective. It groups usability aspects such as cognitive and intuitive interaction support. Lastly, the functional support part considers how the Mashup maker supports the users‘ functional requirements. This model was used to serve as the guide for development and evaluation of Mashup tools, but no Mashup tool was implemented to validate the whereabouts of the provided guidelines. In optimizing Mashup for flexible interaction, Dang et al. (2007) proposed a personalisation technique to enhance the functionality of Mashups interaction with users by presenting a robust and flexible service-oriented architecture of personalised Mashups. While Krummenacher et al. (2009) proposed a project funded by European Union to create applications that can be used by all users and it is known as SOA4ALL. With the aim of providing ‖ a comprehensive framework and infrastructure that integrates complementary and evolutionary technical advances (i.e. SOA, context management, web principles, web 2.0 and semantic web) into a coherent and domain-independent services delivery platform‖. This work is one of the main projects that have been developed in collaborating end users with Mashups applications. They proposed Semantic Web sErvice Editing Tool (SWEET) and Sweet is nOt a Wsdl EditoR (SOWER) for annotating web services. SWEET is used to annotate restful web services while SOWER is user to annotate SOAP based web services. To create interactive users interfaces, Daniel et al. (2012a) proposed a domain-specific approach to Mashups that speaks the language of the user. This work focused awareness on the terminology; concepts, rules, and the domain user are comfortable-with. This work enabled end users without programming skills to compose own applications.

Furthermore to give end-users the freedom to customize processes and process activities according to their specific needs, Fisichella and Matera (2011) proposed a reference model. The proposed model allowed for a flexible process definition and process execution to support the dynamic user-based composition process. Yet still there are Mashup tools that use data feeds to create services and uses widgets for user interaction, but still these Mashup tools are not usable to non-technical users. Mashup tools lack the collaborative reasoning emphasized by SOA4All project, though they support both web based data sources and corporate data. Likewise Yahoo Pipes uses widgets and feeds for Mashup creation but still not usable by non-technical users. Yahoo! Pipes are visual tool for data extraction and processing of web sources (Jones & Churchill, 2009).

43

3.4.2 Web APIs Homogenization

In order to facilitate end-user Mashup based application there is a need to transform heterogeneous structures to a homogenous structure. This subsection discusses some of the studies that were conducted in order to handle heterogeneity of web resources.

In the making of web contents web enabled, Soriano et al. (2008) proposed a flexible presentation layer for human users, using SOA based web-services to enhance interactions and usability of services by developing an open Mashup platform known as EzWeb. This work did not provide a mechanism for making web contents ―Mashup-ready‖, because in order to simplify the process of developing end user based Mashups, there is need to solve the issues around heterogeneous resource. In solving the issue around heterogeneous, Momeni (2011) proposed a methodology by analysing the components required for combining and integrating information into machine process-able dataset from different web data sources to a homogeneous structure, using the e-commerce ontology. This work partially solved the process of making resource web-enabled, since it provided different adaptors for each service. Yet again, Upadhyaya (2012) proposed a framework to assists end users in the process of discovering and composing services and to simplify the integration of heterogeneous web resources. This work was achieved using the following two goals: first to identify Mashup-ready web resources from different web applications and SOAP-based Web services, and lastly to providing approaches to discover and compose web resources that are capable of accomplishing user‘s activities. This work did not solve the issue of making web resources Mashup-ready in a global scale of SOA. Furthermore, in increasing the number of web service based resources used by Mashups, Malki & Benslimane (2012) proposed SAWADL which only allowed the semantic annotation of the REST web Service. This work was used to combine web APIs and REST Web services to develop more agile and flexible Mashup application.