A UML profile for service oriented architectures

Amir, Rafik; Zeid, Amir

doi:10.1145/1028664.1028745

Cited by 34 publications

(23 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In most of the current practice in separating functional and non-functional properties, non-functional properties are specified on a per-service basis (?, ? ; Amir & Zeid, 2004;Lodderstedt, Basin, & Doser, 2002;Jrjens, 2002;Nakamura, Tatsubori, Imamura, & Ono, 2005;Soler, Villarroel, Trujillo, Medina, & Piattini, 2006;Vokäc, 2005;Baligand & Monfort, 2004;G. Wang, Chen, Wang, Fung, & Uczekaj, 2004).…”

Section: Introductionmentioning

confidence: 99%

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

Oba

Wada

Suzuki³

2011

Journal of Database Management

View full text Add to dashboard Cite

In Service Oriented Architecture (SOA), each application is often designed with a set of reusable services and a business process. In order to retain the reusability of services, it is important to separate non-functional properties of applications (e.g., security and reliability) from their functional properties. This paper investigates an end-to-end model-driven development framework that separates non-functional properties from functional properties and consistently manages them from high-level business processes to low-level implementation configurations. This framework proposes two key 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 the notion of 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 leverages the notion of feature modeling in order to explicitly define constraints among non-functional properties such as dependency and mutual exclusion constraints. BALLAD and FM-SNFPs can free application developers from manually specifying, maintaining and validating non-functional properties and constraints for services one by one, thereby 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. Empirical evaluation results show that BALLAD significantly reduces the costs to implement and maintain non-functional properties in service-oriented applications. BALLAD and FM-SNFPs are designed and implemented efficient and scalable.

show abstract

Section: Introductionmentioning

confidence: 99%

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

Oba

Wada

Suzuki³

2011

Journal of Database Management

View full text Add to dashboard Cite

show abstract

“…In most of the current practices of separating functional and non-functional properties in SOA, non-functional properties are specified on a per-service basis [4][5][6][7][8][9]. However, with this per-service strategy, application developers need to manually ensure that each nonfunctional property is properly configured in a series of services in an ad-hoc manner because each non-functional property tends to cover multiple services simultaneously.…”

Section: Introductionmentioning

confidence: 99%

Early Aspects for Non-Functional Properties in Service Oriented Business Processes

Wada

Suzuki

Oba³

2008

2008 IEEE Congress on Services - Part I

View full text Add to dashboard Cite

In Service Oriented Architecture, each application is often designed with a set of reusable services and a business process. In order to retain the reusability of services, it is important to separate non-functional properties of applications (e.g., security and reliability) from their functional properties. Currently, non-functional properties are often defined on a per-service basis. In contrast, this paper investigates a new per-process strategy, and proposes an aspect oriented language to separate functional and nonfunctional properties in business processes. Each aspect formally specifies non-functional properties that crosscut among multiple services. The proposed language frees applications developers from manually specifying and validating non-functional properties for services one by one, thereby reducing the burdens/costs of application development and maintenance. This paper describes the design of the proposed language and demonstrates how each aspect (i.e., a set of non-functional properties) is woven to a business process and transformed to application code.

show abstract

“…In most of these UML-based approaches, we noticed the methods presented by Baresi et al [5,6] and AMir et al [7]. Baresi et al describe SO A by the static model and dynamic model in UML, then, encode the model into a transition system.…”

Section: Related Workmentioning

confidence: 99%

“…However it is impossible to describe SOA sufficiently by the current popular UML-based approach [5][6][7] and BPEL [8,9] since UML is short of the support to describe some elements involved in software architecture and BPEL focuses on the specification of abstract or executive business processes but not on the description of functional units of system architecture. On the other hand, the existing ADLs (architecture definition languages) [10][11][12][13][14] cannot specify SOA very well in spite that we can benefit from the approaches based-on them.…”

Section: Introductionmentioning

confidence: 99%

A Modeling Approach for Service-Oriented Architecture

Zhang

Ying

Cao

et al.

IFIP International Federation for Information Processing

View full text Add to dashboard Cite

Abstract. Specifying service-oriented system, which is a new type of Enterprise Information System, is critical with the rapid development of Web Services. For the purpose, this paper presents an approach to model ServiceOriented Architecture (SOA). We do not exclude the traditional opinions of software architecture description as the current specification approaches; on the contrary, some similar conceptions, such as service components and connectors are defined in this paper. For architectural reuse, the notion of composite service components is specified to model services composition and that of composite connectors is defined to abstract the complex communication protocols. Within the context of the Travel Reservation System (TRS), we demonstrate the usage and practicability of our approach based-on Web Services.

show abstract

A UML profile for service oriented architectures

Cited by 34 publications

References 0 publications

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

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

Early Aspects for Non-Functional Properties in Service Oriented Business Processes

A Modeling Approach for Service-Oriented Architecture

Contact Info

Product

Resources

About