Article

SOMA: A method for developing service-oriented solutions

IBM Global Business Services, 625 32nd Avenue SW, Suite 130, Cedar Rapids, IA 52404, USA
Ibm Systems Journal (Impact Factor: 1.79). 07/2008; 47(3):377-396. DOI: 10.1147/sj.473.0377
Source: DBLP

ABSTRACT

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.

Download full-text

Full-text

Available from: Ali Arsanjani, May 28, 2014
    • "The most relevant works on evolution process for service based business process provide evolution guidelines. Authors of [24] proposed incremental phases based on a fractal model of software development for evolving services. An iterative method has been developed by Schuster et al. [25]. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Today, SOA is the most dominant and broadly adopted architecture style by enterprises. It defines how to use services to achieve business goals, and allows interoperability with multiple customers within different business domains. The growing use of SOA has increased research interest on how to improve the reuse of services. Hence, managing services variability was introduced by many approaches as a new leading edge concept for improving reuse. Indeed, variability refers to the characteristic of a system to adapt, specialize and configure itself with the context of use. Several proposals have been made in this respect. However, none of these seem to deal with the evolution of these configurable services. In service oriented systems, the evolution of services is usually introduced by the evolution of the associated business process. Therefore, if a configurable process model (CPM for short) should evolve in reaction to changing business needs, the associated configurable services (CS for short) are also impacted by this change. In our previous work, we proposed a complete methodology for managing evolution in configurable process models. In this paper, we extend our proposed approach to develop an evolution process for managing the changes of configurable services (variable services) caused by changing the associated configurable process model.
    No preview · Conference Paper · Nov 2014
  • Source
    • "Regarding the completion of specification phase, we conduct service refactoring and rationalizing using Service Litmust Test (SLT) [13], [19], [20]. This activity is performed in order to ensure that services in the services hierarchy are refactored in such a way which lower-level services that have some kind of logical affinity are going to be grouped together under a higher-level service [8], [13]. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Service oriented architecture (SOA) enables organizations to easily integrate systems, data, and business processes. Implementation of SOA solution in private sector is widely used and successfully proven to increase their profit. But there are different challenge in public sector which is not profit oriented and has different business model. In public sector, user satisfaction on government agencies is one of common indicator to measure quality of public service. This paper presents SOA solution for public sector using SOMA to conduct a service integration for optimizing public satisfaction. We also combined SWOT and Porter's Value Chain to support business modelling analysis. The result shows that there is a simplicity and feasibility for users to access the service after SOA integration, which improves user satisfaction.
    Full-text · Conference Paper · Sep 2014
  • Source
    • "We decided to work with his methodology because it is well-rated compared to other initiatives [8]. Moreover, the main other SOSE methodologies have all at least one significant weakness, e.g., the SOMA methodology proposed by IBM is proprietary and very prescriptive [24], the SOAF methodology is incomplete because it does not cover all the six phases mentioned above [25] and the methodology proposed by Erl does not tackle the project issue and is mainly oriented on technical considerations [26]. The reader can refer to [23] and [27] for a more complete comparison between SOA implementation methodologies. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Bringing together the ICT and the business layer of a service-oriented system (SoS) remains a great challenge. Few papers tackle the management of SoS from the business and organizational point of view. One solution is to use the well-known ITIL v.3 framework. The latter enables to transform the organization into a service-oriented organizational which focuses on the value provided to the service customers. In this paper, we align the steps of the service provisioning model with the ITIL v.3 processes. The alignment proposed should help organizations and IT teams to integrate their ICT layer, represented by the SoS, and their business layer, represented by ITIL v.3. One main advantage of this combined use of ITIL and a SoS is the full service orientation of the company.
    Full-text · Article · Sep 2014
Show more