Towards a Service-Oriented Development Methodology
2005, Journal of Integrated Design and Process Science
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. This paper presents a structured approach to analyzing software development methodologies in light of the specific features of service-oriented ...
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.
cerc.wvu.edu
The Service-Oriented paradigm, which conceives software resources as discoverable services available on a network, is proving an effective approach for providing business solutions in distributed and heterogeneous computing environments. However, due to the different and numerous issues to face, it is witnessing a growing interest in the use of methodologies suitable for supporting the development of service-oriented applications. The paper proposes an approach, centered on the Method Engineering paradigm, which enables the definition of new methodologies tailored to address specific issues arising in developing of service-oriented applications through the exploitation of fragments of methodologies existing and experimented. In particular, it is shown how to obtain, through composition of method fragments, a complete process which covers from requirements specification to testing of service-oriented applications. The complete definition of a method fragment (MF-Web Services Builder) and a related CASE tool are also presented along with a case study showing their exploitation for building a real service.
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.
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.
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.
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. Ó
2012
In order to realize Service-Oriented Architecture (SOA) with Web Services (WSs), a new engineering approach is required; we refer to it as Service-Oriented Software Engineering (SOSE). This approach would sketch out a method, including a process, models, languages, tools, and notations. It encompasses three dimensions: (i) services, (ii) compositions, and (iii) management of both services and compositions. The existing methods have not considered the three perspectives neither they have considered how these perspectives can be achieved together through a comprehensive approach. This paper presents an architecture, a specification, and an implementation of a CASE tool for developing and managing Service-Oriented Software (SOS). The CASE implements: (1) a metadata that represents WSs from four perspectives: description, deployment platforms, legacy systems, and composite software, and (2) a set of management artifacts built on top of the metadata. The metadata is implemented as repository, the core component of the CASE tool architecture.
2010
Service-Oriented Software Engineering is based on concepts and principles for constructing complex enterprise systems in which services as building block of the system, are distributed in large networks. The main goal of the serviceoriented methodologies is to define a process for development and maintenance of service-based systems. Most of the Service-Oriented methodologies are not mature enough compared with traditional software development methodologies such as Object-Oriented or Component-Based. Hence, defining an evaluation framework will be useful for comparing methodologies for identifying their strengths and weaknesses, defining new methodologies or extending existing Service-Oriented methodologies. At the time being, there is no complete evaluation framework for evaluating Service-Oriented methodologies. The principal objective of this paper is to introduce a comprehensive evaluation framework for evaluating Service-Oriented methodologies. This evaluation tool is appropriate for methodology engineers to develop new methodologies, as well as project managers to select an appropriate methodology at a specific project.

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.