Towards a Service-Oriented Development Methodology
2005
Sign up for access to the world's latest research
Abstract
Leveraging a service-oriented paradigm would significantly affect the way people build software systems. However, to achieve this ambitious vision a solid software development methodology should be in place, comprising specific, service-context patterns as well as appropriate supporting tools which altogether integrate methods and best practices into a stable development environment.
Related papers
Service orientation is a new software engineering paradigm that introduces opportunities as well as challenges. Although existing processes and practices can be reused for service oriented development, novel techniques are required to address unique SOA requirements. Work in this area is quite active and only recently is producing some initial results. The aim of this paper is to present a state-of-the-art survey on current service oriented development approaches. The characteristics that distinguish between these approaches are discussed and a number of actual methodologies that have emerged or are still emerging are described and compared.
Innovations in Information Technology ( …, 2012
Service-oriented software engineering (SOSE) is a software engineering approach for building service-oriented solutions by utilizing service-oriented computing paradigm constructs and concepts. Different methods exist to develop service-oriented software. However, no standardized set of service-oriented principles has been defined yet. This paper surveys current principles and provides a comparison framework to identify which are most considered by different SOSE methods at various stages of solution life cycle.
2006
Service Oriented Architectures (SOA) are rapidly emerging as the premier integration and architectural approach in contemporary, complex, heterogeneous computing environments. SOA is not simply about deploying software: it also requires that organisations evaluate their business models, come up with service-oriented analysis and design techniques, deployment and support plans, and carefully evaluate partner/customer/supplier relationships.
ArXiv, 2020
Software systems development nowadays has moved towards dynamic composition of services that run on distributed infrastructures aligned with continuous changes in the system requirements. Consequently, software developers need to tailor project specific methodologies to fit their methodology requirements. Process patterns present a suitable solution by providing reusable method chunks of software development methodologies for constructing methodologies to fit specific requirements. In this paper, we propose a set of high-level service-oriented process patterns that can be used for constructing and enhancing situational service-oriented methodologies. We show how these patterns are used to construct a specific service-oriented methodology for the development of a sample system. Keywords. Service-Oriented Software Development Methodologies, Process Patterns, Process Meta-Model, Situational Method Engineering
Lecture Notes in Computer Science, 2011
Many of today's large-scale software projects in the area of distributed systems and especially enterprise IT adopt service-oriented software architecture and technologies. For these projects, availability of sound software engineering principles, methodology and tool support is of utmost importance. However, traditional software engineering approaches are not fully appropriate for the development of service-oriented applications. The limitations of traditional methods in the context of service-oriented computing have led to the emergence of Software Service Engineering (SSE) as a specialist discipline, but research in this area is still immature and many open issues remain. The WESOA workshop series brings together research community and industry practitioners in order to develop comprehensive engineering principles, methodologies and tool support for the entire software development lifecycle (SDLC) of service-oriented applications.
… FASE 2008, held as part of …, 2008
Ibm Systems Journal, 2008
Service-oriented modeling and architecture (SOMA) has been used to conduct projects of varying scope in multiple industries worldwide for the past five years. We report on the usage and structure of the method used to effectively analyze, design, implement, and deploy service-oriented architecture (SOA) projects as part of a fractal model of software development. We also assert that the construct of a service and service modeling, although introduced by SOA, is a software engineering best practice for which an SOA method aids both SOA usage and adoption. In this paper we present the latest updates to this method and share some of the lessons learned. The SOMA method incorporates the key aspects of overall SOA solution design and delivery and is integrated with existing software development methods through a set of placeholders for key activity areas, forming what we call solution templates. We also present a fractal model of software development that can enable the SOMA method to evolve in an approach that goes beyond the iterative and incremental and instead leverages method components and patterns in a recursive, self-similar manner opportunistically at points of variability in the life cycle. Ó
Realigning Research and Practice in Information Systems Development, 2001
A change in attitudes and approaches to software development is emergingfrom the software engineering community, in which software is no longer regarded as a product, but as a service. This paper outlines the history of this change and reviews the implications of a service-oriented approach to information systems development. The chief impact is the need for software engineers, information systems developers, and managers to take a much broader view of the development and deployment process, with far reaching implications for traditional IS departments.
Service Oriented Computing and Applications, 2011
Service-oriented computing is a paradigm for effectively delivering software services in a dynamic environment. Accordingly, many service-oriented software engineering (SOSE) methodologies have been proposed and practiced in both academia and industry. Some of these methodologies share common features (e.g. cover similar life-cycle phases) but are presented for different purposes, ranging from project management to system modernization, and from business analysis to technical solutions development. Given this diversity in the methodologies available in the literature, it is very hard for a company to decide which methodology would fit best for its specific needs. With this aim, we took a feature analysis approach and devised a framework for comparing the existing SOA methodologies. Different from existing comparison frameworks, ours specifically highlights aspects that are specific to SOA and aims to differentiate the methodologies that are truly service-oriented from those that deal little with service aspects. As such, the criteria defined in the framework can be used as a checklist for selecting a SOSE methodology.
2008
Service Oriented Computing (SOC) is an emerging programming paradigm for designing interoperable applications distributed over the network. It is based upon the concept of service which is an autonomous loosely coupled interoperable platform-independent computational entity which can be dynamically discovered and composed in order to obtain different systems which achieve different tasks. Services can be accessed by public interfaces which are standardized and stored within service registers that aim at being queried by other applications for retrieving, at run-time, a specific service for a specific task. Services can be reused and replaced depending on the execution context of the specific distributed application and they can be exploited by different application systems at the same time. E-government, e-business and e-science are some examples of the IT areas where Service Oriented Computing will be exploited in the next years and, recently, big industries and consortia like Microsoft, IBM, W3C, OASIS only to mention a few, are putting several efforts for developing tools and standards for SOC applications. So far, some frameworks like Corba [OMG], Java RMI [Sun] and Web Services have been proposed in order to deal with service oriented applications. Corba and Java RMI extend the object-oriented paradigm to network applications by supplying a framework where objects can be created and accessed remotely, whereas Web Services is the most credited technology which deals with Service Oriented Computing. The Web Services are a standardized XML-based technology [W3Ca] defined by means of several specification documents developed by different organizations, consortia and industries whose most important goal is the interoperability achievement. There are three specifications that are commonly considered the cornerstone of the Web Services technology: WSDL [W3Cf], SOAP [W3Cb] and UDDI [Oasa]. The WSDL specification deals with a language which allows for the description of a Web Service interface, the SOAP specification defines a protocol for message exchanges among Web Services and the UDDI one deals with the dynamic discovery of a Web Service. Although Service Oriented Computing raises a lot of interests in the computer science and business communities, at the present, there not exists any kind of shared formal definition for SOC nor a formalization of a service oriented programming paradigm. This fact implies that the main concepts service oriented paradigm is based upon can be extracted only from practical experiences and case studies (as in [AKR + 05, CNM06, UE]), technology documentations and informal documents released by industrial consortia like in [OAS06, W3Ce]. Although the present technologies provide powerful means for dealing with SOC application design, the fact that SOC is not precisely defined in terms of formal definitions is becoming, day by day, a strong limit for its development. Features like dynamic discovery and composition indeed, need a common understanding on the basic mechanisms SOC applications are based upon in order to be achieved by different designers by exploiting different tools. Nowadays, it is possible to observe a common interest of the industrial world and the academic one to investigate formal models for describing service oriented approach [CFNS05, WCG + 06, FLB06]. To this end, conferences and workshops are organized for sharing both industrial and academic investigations such as [KLN07, ADR07] and, recently, the European Union has funded an integrated project from which this contribute comes from, that is called SENSORIA [WCG + ] and whose aim is to develop both theoretical foundations and designing tools for SOC applications.

Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.
References (4)
- Papazoglou, M. P. and Dubray, J., 2004, "A Survey of Web Service Technologies," Technical Report DIT-04- 058, Department of Information and Communication Technology, University of Trento, http://eprints.biblio.unitn.it/archive/00000586/4.
- Peltz, C., 2003, "Web Services Orchestration and Choreography" IEEE Computer, Vol. 36, No. 10, pp. 46-52. Rational Software, 2002, "Rational Unified Process for Systems Engineering," A Rational Software White Paper (TP 165A), Rational Software Corporation, Santa Clara, California. Rolland, C., and Prakash, N., 2000, "Bridging the Gap Between Organizational Needs and ERP Functionalities," Requirements Engineering, Vol. 5, No. 3, pp. 180-193.
- Rolland, C., Prakash, N., and Benjamen, A., 1999, "Multi-Model View of Process Modelling," Requirements Engineering, Vol. 4, No. 4, pp. 169-187.
- Wake, W.C., 2000, "Extreme Programming Explored," Addison-Wesley, Reading.