Conference Paper

The EasySOC Project: A Rich Catalog of Best Practices for Developing Web Service Applications

DOI: 10.1109/SCCC.2010.12 Conference: SCCC 2010, Proceedings of the XXIX International Conference of the Chilean Computer Science Society, Antofagasta, Chile, 15-19 November 2010
Source: DBLP


The Service-Oriented Computing (SOC) paradigm has gained a lot of attention in the software industry since represents a novel way of architecting distributed applications. SOC is mostly materialized via Web Services, which allows developers to structure applications as building blocks exposing a clear, public interface to their capabilities. Although conceptually and technologically mature, SOC still lacks adequate development support from a methodological point of view. We present the Easy SOC project, a catalog of guidelines to build service-oriented applications and services. This catalog synthesizes best SOC development practices that arise as a result of several years of research in fundamental SOC-related topics, namely WSDL-based technical specification, Web Service discovery and Web Service outsourcing. In addition, we describe a plug-in for the Eclipse IDE that has been implemented to simplify the utilization of the guidelines. We believe that both the practical nature of the guidelines, the empirical evidence that supports them, and the availability of IDE support that enforces them will help software practitioners to rapidly exploit our ideas for building real SOC applications.

Download full-text


Available from: Marcelo R. Campo,
  • [Show abstract] [Hide abstract]
    ABSTRACT: Service-Oriented Computing (SOC) allows developers to structure applications as a set of reusable services. Web Services expose their functionality by using Web Service Description Language (WSDL). We found that there is a high correlation between well-known object-oriented metrics taken in the code implementing services and the occurrences of ‘anti-patterns’ in their WSDLs. We show that some simple refactorings performed early when developing Web Services can greatly improve the quality of WSDL documents. Then, the contribution of this work is a practical approach to guide practitioners in obtaining better WSDL designs that aligns with the technologies and techniques commonly used in the industry for building services.
    International Journal of Web and Grid Services 01/2011; 7(4):357-387. DOI:10.1504/IJWGS.2011.044710 · 0.76 Impact Factor
  • [Show abstract] [Hide abstract]
    ABSTRACT: To be effective, the systematic reuse in software development process must be supported by an artifact database. Although many organizations do not have such database, generally the Service Repository is the catalog responsible for leveraging Service-Oriented Architecture (SOA) reuse within the development lifecycle. This paper presents a SOA implementation experience, emphasizing the contributions of developing Service Repository extensions. The adoption of SOA occurred along with a new ERP deployment. One of the main goals was to enable the reuse of standard processes and services within a better integration between ERP system and legacy systems. The repository received additional capabilities to maximize searches and usability; to support configuration and release management; and also address performance issues within cache manageability. The benefits of this work are presented, as well as the results of the current situation in the organization considering SOA repository usage and the empirical evidence collected.
    Informatica (CLEI), 2012 XXXVIII Conferencia Latinoamericana En; 01/2012
  • [Show abstract] [Hide abstract]
    ABSTRACT: There is a good consensus on the strategic value of Service Oriented Architecture (SOA) as a way of structuring systems, and a common trend is to migrate legacy applications that use outdated technologies and architectures to SOA. We study the effects in the resulting Web Service interfaces of applying two traditional migration approaches combined with common ways of building services, namely direct migration with code-first and indirect migration with contract-first. The migrated system was a 35-year-old COBOL system of a government agency that serves several millions of users. In addition, we provide a deep explanation of the trade-offs involved in following either combinations. Results confirm that the “fast and cheap” approach to move into SOA, which is commonplace in the industry, may deliver poor service interfaces, and interface quality is also subject to the tools supporting the migration process.
    Enterprise Information Systems 09/2012; In Press(1):-. DOI:10.1080/17517575.2012.717234 · 9.26 Impact Factor
Show more