Abstract

1 SOA MODELINGAccording to [1] the Service Oriented Architecture (SOA) concept is based on the principle of developing reusable business service and building applications instead of building monolithic applications in silos.SOA has the potential to bridge the gap between business and technology, improve reuse of existing applications and interoperability with new ones. Some authors [2] consider that software services are the building blocks for SOA, and they can be composed to provide a more coarse grained functionality and to automate business processes.A modeling language is an artificial language that can be used to define system, information in the structure defined by the rules of the system. Rules are used to interpret the association of components in the system. There are two types of modeling languages - Graphical Modeling: it used a diagrammatic approach to represent the system. There are symbols and lines that connect the symbols which is used to display the relationship between the systems. Notations are used to define the constraints in the system.- Textual Modeling: it uses the keywords or special characters with parameters to represent certain information in natural language which can be used by computers for processing [3]. Expressions are used to link the relationship among the text.Service Oriented Modeling (SOM) is the first step to model services of SOA. According to the specialists [3], the approach for modeling SOA with the viewpoint from services is required. Various methods for serviceoriented modeling have been proposed to apply SOA in industrial and business environments by many researchers [4]. They can be seen in Table 1 below:Starting from this table we decided, based on the reviewed literature, to pay attention only to specific modeling approaches, which are more common and used today.1.1.SOAMLUML is used for general purpose modeling of SOA and create visual models. The services were modeled as objects and general purpose of the design was made by it. But when the degree of complexity increased it was not that efficient. This is how SoaML (Service oriented architecture Modeling Language) emerged: as a UML profile and meta-model for the modeling and design of services within a service-oriented architecture [3].SoaML was created to support the following features:* Indentifying services and their requirements.* Defining service consumers and providers as well as the service itself.* Specifying message pattern and protocols for the services.* Different Service classification schemes.* Integration and extension with OMG meta-models and BPMN.The Object Management Group (OMG) proposed SoaML in 2009 for representing SOA artifacts using Unified Modeling Language (UML) as a core-modeling standard. Moreover, a meta-model and a UML profile are provided in SoaML for the specification and design of service to SOA (meta-model for modeling the requirement for a service and UML for specifying services) [4].1.2.SOMFService Oriented Modeling Framework (SOMF) is a model driven engineering methodology which focuses on business process, and the IT is part of the lifecycle. It can also be used at standalone designing platform with other modeling languages such as UML, BPMN, or SoaML to enrich the language syntax. It can also set software development priorities during life cycle stages, and enhance the overall implementation view of the system [3].The SOMF offers specialized modeling notation to help model, analysis and identification services that is proposed by Bell. It provides a formal method of service identification at different levels of abstraction including meta-model concept and specific notation [4].1.3.SOMASOMA is a modeling technique for developing and building SOA-based systems proposed by IBM in 2004. SOMA activities focuses include: service identification (discovering candidate service and interaction between them), service specification (making decision for exposing services), and service realization (capturing service realization). …

Highlights

  • Using OWL as a modeling language and Unified Modeling Language (UML) to illustrate classes and properties in Service Oriented Architecture (SOA) modeling No service identification Potential contribution to model-driven SOA implementation Using specialized modeling notations and support Service Oriented Architecture Modeling Language (SoaML) Service identification in granularity level and relationship between services Covering analysis, design and architecture but doesn’t support transformation of existing assets to SOA Developing a meta-model for SOA Covering essential aspects for SOA Supported by WSDL and XSD and UML Using UML Focusing in the basic service modeling concept QoS specification cannot be supported Defining business process choreography and bridging business process to SOA in details Using SoaML QoS can be supported Service identification, service specification and realization Widely used in industry and business area

  • It can be used at standalone designing platform with other modeling languages such as UML, Business Process Modeling Notation (BPMN), or SoaML to enrich the language syntax

  • This may not be completed represented without the help of business rules which represent the multitude of policies, procedures or definitions. These may be external rules, coming from legal regulations that must be observed by all organizations acting in a certain field, or internal rules which define the organization’s business politics and aim to ensure competitive advantages in the market [8]. In this context we introduced the three variables we need for this topic: SOA, Business process management (BPM) and BR

Read more

Summary

BPM to REST-SOA Modeling and Mapping

Proposed Approach In the following chapter we will propose a more specific approach in order to achieve a practical and testable workflow inspired from BPM-SOA mapping models like the one proposed by [9] and [7] and pictured in Figure 5 (Management of services oriented business process) and Figure 4 (Business processes and services relationships in MINERVA). Our approach is based on a multi-step topdown process that aims to establish a comprehensible and, in the same time, a specific enough working procedure. It starts from the generic level of Business Process Model and tries to reach the detailed level of business behavior with REST-HTTP actions and of business data REST-based resource structures. The proposed workflow consists in the following stages: 1. Setting the Business Process Model

BPM Service Integration
Conclusions
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call