A Unified Deployment and Management Model for Dynamic and Distributed Software Architectures

Author(s):  
Mohamed Nadhmi Miladi ◽  
Mariam Lahami ◽  
Mohamed Jmaeil ◽  
Khalil Drira

This chapter provides a generic model called Unified deployment and management Model of Dynamic and Distributed software architectures (UMoDD) based on the D&C standard proposed by the OMG. UMoDD has been designed to be suitable to dynamic deployment and management for both architecture styles: the service-oriented and component-based architecture style. The proposed model is based on a model-driven approach. It offers two levels of modelling: a generic level and a specific level to an architecture style.

Author(s):  
Huy Tran ◽  
Ta’id Holmes ◽  
Uwe Zdun ◽  
Schahram Dustdar

This chapter introduces a view-based, model-driven approach for process-driven, service-oriented architectures. A typical business process consists of numerous tangled concerns, such as the process control flow, service invocations, fault handling, transactions, and so on. Our view-based approach separates these concerns into a number of tailored perspectives at different abstraction levels. On the one hand, the separation of process concerns helps reducing the complexity of process development by breaking a business process into appropriate architectural views. On the other hand, the separation of levels of abstraction offers appropriately adapted views to stakeholders, and therefore, helps quickly re-act to changes at the business level and at the technical level as well. Our approach is realized as a model-driven tool-chain for business process development.


2009 ◽  
Vol 121 (1) ◽  
pp. 5-20 ◽  
Author(s):  
Jihed Touzi ◽  
Fréderick Benaben ◽  
Hervé Pingaud ◽  
Jean Pierre Lorré

2011 ◽  
Vol 20 (02) ◽  
pp. 201-220 ◽  
Author(s):  
MARCOS LÓPEZ-SANZ ◽  
JUAN MANUEL VARA ◽  
ESPERANZA MARCOS ◽  
CARLOS E. CUESTA

Model-driven development is recognized as one of the most promising approaches in software engineering. Recent research in the area highlights the importance of using an explicit architectural model in this context. Since service-oriented architectures have also demonstrated to be adequate to overcome current software needs, the idea of using the model-driven approach to generate service-oriented architectural models has successfully flourished in the last years. However, the emphasis on the Service-Oriented Computing (SOC) paradigm has led to the design of architectures lacking some desirable features. Knowing the benefits provided by architectural styles, we have found that their use can help us to overcome those needs. Our goal is to obtain a service-oriented model which satisfies the requirements of the concrete architecture and complies with the constraints and vocabulary defined for a specific architectural style. To achieve this, here, we propose to use a weaving model which merges the concrete architectural model with a model of the architectural style of choice.


2007 ◽  
Vol 46 (01) ◽  
pp. 52-56 ◽  
Author(s):  
B. G. M. E. Blobel

Summary Objectives: As health care develops from an organization-centered via service-centered (disease management) towards a person-centered system (favored homecare, patient monitoring, body area networks), information systems involved have to be semantically interoperable, process-related, decision-supportive, context-sensitive, user-oriented, and trustworthy. Methods: The aforementioned paradigm shift requires highly flexible solutions based on knowledge concepts, provided by a service-oriented and model-driven approach. Results: Information systems’ design, implementation and maintenance have to be realized based on formal grammar. This is true for all considered aspects and views of the system and its components, using metalanguages and reflecting all domains touched. Conclusions: For meeting the challenge, involvement of, and close collaboration between, experts from different domains as well as knowledge and tooling regarding formal modeling and model interchange are required.


Author(s):  
Ingo Zinnikus ◽  
Gorka Benguria ◽  
Brian Elvesæter ◽  
Klaus Fischer ◽  
Julien Vayssière

2014 ◽  
Vol 556-562 ◽  
pp. 6184-6190
Author(s):  
Hui Fang Li ◽  
Hachou Mohamed ◽  
Harbi Mohamed El-Amine

A large number of concepts such as, composition, abstraction, autonomy, lose-coupling, are introduced with Service Oriented Architecture (SOA). This diversity of concept is at the same time the strength and weakness of SOA because it may affect the realization of its benefits if not well controlled. Therefore, it is necessary to adopt an appropriate model based on SOA governance. In this paper, we propose a generic SOA governance model for all service life cycle, from design Time, Run Time to change Time. This model is mainly based on the communication of each phase within a service life cycle among all stakeholders, developers and different department leaders of the organization, so as to check services concerning capability, security and strategic business alignment. This model contains 3 kinds of groups: SOA Board Team is concerned with applying enterprise governance strategy; SOA Core Team is a group of business which takes direction from the SOA Board to help implement the required services, and IT team department which oversees the implementation of SOA related activities. The Case study and its analysis show that the more flexible & efficient organization structure, and a permanent supervisor of the service’s operations and organization goals can be obtained by using our proposed model.


Sign in / Sign up

Export Citation Format

Share Document