A model driven and clustering method for service identification directed by metrics

2020 ◽  
Vol 51 (2) ◽  
pp. 449-484
Author(s):  
Mohammad Daghaghzadeh ◽  
Seyed Morteza Babamir
2012 ◽  
pp. 102-125 ◽  
Author(s):  
Michael Gebhart

This chapter focuses on the identification and specification of services based on prior modeled business processes and legacy systems. The resulting service interfaces and service components formalized by using the Service oriented architecture Modeling Language (SoaML) describe the integration of legacy systems into a service-oriented application landscape. The legacy systems provide services for integration purposes and represent the implementations of service components. Additionally, the resulting architecture allows functionality of legacy systems to be replaced with functionality provided by external cloud services. According to model-driven development concepts, the formalized service interfaces and service components as part of the service designs can be used to automatically derive service interface descriptions using the Web Services Description Language (WSDL). These descriptions enable the technical integration of legacy systems. If necessary, service implementations based on the Service Component Architecture (SCA) and the Business Process Execution Language (BPEL) can be generated.


2009 ◽  
Vol 38 (38) ◽  
pp. 119-130
Author(s):  
Erika Asnina

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.


Sign in / Sign up

Export Citation Format

Share Document