Model Driven Development of Context-aware Service Oriented Architecture

2008 ◽  
Author(s):  
Samyr Vale ◽  
Slimane Hammoudi
Keyword(s):  
Service Oriented Architecture ◽  
Context Aware ◽  
Model Driven Development ◽  
Model Driven ◽  
Service Oriented ◽  
Context Aware Service

A Model-Driven Development Framework for Non-Functional Aspects in Service Oriented Architecture

2011 ◽  
pp. 358-389 ◽  
Author(s):  
Hiroshi Wada ◽  
Junichi Suzuki ◽  
Katsuya Oba
Keyword(s):  
Service Oriented Architecture ◽  
Unified Modeling Language ◽  
Empirical Evaluation ◽  
Independent Manner ◽  
Model Driven Development ◽  
Unified Modeling ◽  
Model Driven ◽  
Functional Aspects ◽  
Service Oriented ◽  
New Applications

Service oriented architecture (SOA) is an emerging style of software architectures to reuse and integrate existing systems for designing new applications. Each application is designed in an implementation independent manner using two major abstract concepts: services and connections between services. In SOA, non-functional aspects (e.g., security and fault tolerance) of services and connections should be described separately from their functional aspects (i.e., business logic) because different applications use services and connections in different non-functional contexts. This paper proposes a model-driven development (MDD) framework for non-functional aspects in SOA. The proposed MDD framework consists of (1) a Unified Modeling Language (UML) profile to model non-functional aspects in SOA, and (2) an MDD tool that transforms a UML model defined with the proposed profile to application code. Empirical evaluation results show that the proposed MDD framework improves the reusability and maintainability of service-oriented applications by hiding low-level implementation technologies in SOA.

A Model-Driven Development Framework for Non-Functional Aspects in Service Oriented Architecture

2009 ◽  
pp. 942-974
Author(s):  
Hiroshi Wada ◽  
Junichi Suzuki ◽  
Katsuya Oba
Keyword(s):  
Service Oriented Architecture ◽  
Unified Modeling Language ◽  
Empirical Evaluation ◽  
Independent Manner ◽  
Model Driven Development ◽  
Unified Modeling ◽  
Model Driven ◽  
Functional Aspects ◽  
Service Oriented ◽  
New Applications

Service oriented architecture (SOA) is an emerging style of software architectures to reuse and integrate existing systems for designing new applications. Each application is designed in an implementation independent manner using two major abstract concepts: services and connections between services. In SOA, non-functional aspects (e.g., security and fault tolerance) of services and connections should be described separately from their functional aspects (i.e., business logic) because different applications use services and connections in different non-functional contexts. This paper proposes a model-driven development (MDD) framework for non-functional aspects in SOA. The proposed MDD framework consists of (1) a Unified Modeling Language (UML) profile to model non-functional aspects in SOA, and (2) an MDD tool that transforms a UML model defined with the proposed profile to application code. Empirical evaluation results show that the proposed MDD framework improves the reusability and maintainability of service-oriented applications by hiding low-level implementation technologies in SOA.

scholarly journals Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

2011 ◽  
Vol 22 (2) ◽  
pp. 93-123 ◽  
Author(s):  
Hiroshi Wada ◽  
Junichi Suzuki ◽  
Katsuya Oba
Keyword(s):  
Functional Properties ◽  
Business Process ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Mutual Exclusion ◽  
Model Driven Development ◽  
Model Driven ◽  
Development Framework ◽  
Service Oriented ◽  
Process Strategy

In Service Oriented Architecture (SOA), each application is designed with a set of reusable services and a business process. To retain the reusability of services, non-functional properties of applications must be separated from their functional properties. This paper investigates a model-driven development framework that separates non-functional properties from functional properties and manages them. This framework proposes two components: (1) a programming language, called BALLAD, for a new per-process strategy to specify non-functional properties for business processes, and (2) a graphical modeling method, called FM-SNFPs, to define a series of constraints among non-functional properties. BALLAD leverages aspects in aspect oriented programming/modeling. Each aspect is used to specify a set of non-functional properties that crosscut multiple services in a business process. FM-SNFPs leverage the notion of feature modeling to define constraints among non-functional properties like dependency and mutual exclusion constraints. BALLAD and FM-SNFPs free application developers from manually specifying, maintaining and validating non-functional properties and constraints for services one by one, reducing the burdens/costs in development and maintenance of service-oriented applications. This paper describes the design details of BALLAD and FM-SNFPs, and demonstrates how they are used in developing service-oriented applications. BALLAD significantly reduces the costs to implement and maintain non-functional properties in service-oriented applications.

scholarly journals Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

2013 ◽  
pp. 233-264
Author(s):  
Hiroshi Wada ◽  
Junichi Suzuki ◽  
Katsuya Oba
Keyword(s):  
Functional Properties ◽  
Business Process ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Mutual Exclusion ◽  
Graphical Modeling ◽  
Model Driven Development ◽  
Model Driven ◽  
Service Oriented ◽  
Application Developers

In Service Oriented Architecture (SOA), each application is designed with a set of reusable services and a business process. To retain the reusability of services, non-functional properties of applications must be separated from their functional properties. This paper investigates a model-driven development framework that separates non-functional properties from functional properties and manages them. This framework proposes two components: (1) a programming language, called BALLAD, for a new per-process strategy to specify non-functional properties for business processes, and (2) a graphical modeling method, called FM-SNFPs, to define a series of constraints among non-functional properties. BALLAD leverages aspects in aspect oriented programming/modeling. Each aspect is used to specify a set of non-functional properties that crosscut multiple services in a business process. FM-SNFPs leverage the notion of feature modeling to define constraints among non-functional properties like dependency and mutual exclusion constraints. BALLAD and FM-SNFPs free application developers from manually specifying, maintaining and validating non-functional properties and constraints for services one by one, reducing the burdens/costs in development and maintenance of service-oriented applications. This paper describes the design details of BALLAD and FM-SNFPs, and demonstrates how they are used in developing service-oriented applications. BALLAD significantly reduces the costs to implement and maintain non-functional properties in service-oriented applications.

Sign in / Sign up

Export Citation Format

Share Document