A Feature Modeling Support for Non-Functional Constraints in Service Oriented Architecture

Wada, Hiroshi; Suzuki, Junichi; Oba, Katsuya

doi:10.1109/scc.2007.5

Cited by 26 publications

(23 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also in a case study, efficiency and scalability have been considered. [20] is another work with the architectural viewpoint and uses a feature model. It has mostly concentrated on interdependence and mutual exclusion.…”

Section: Taxonomy Evaluation In Comparison With Similar Workmentioning

confidence: 99%

An Approach to Classify Existing Constraints as Inputs for Web Service Composition

Sarraf¹,

Haghighi²

2013

IJCA

View full text Add to dashboard Cite

The selection of an appropriate Web service for a particular task has become a difficult challenge due to the increasing number of Web services offering similar functionalities. Therefore, when one wants to compose web services to catch a goal, she is faced with some preferences and constraints affecting the final configuration; for simplicity, the single terminology "constraint" in place of both "constraint" and "preference" is used throughout the paper. Most of these constraints in real applications are either functional or qualitative. These constraints have been scattered and unstructured until now, and therefore, when combining services, some of them are considered while many of them are forgotten. In addition to the possibility that some constraints are unthinkable to the user, some of them are overlapping and some may even be contradictory. In this paper a well-formed classification of all known composition constraints is presented. The classification structure is a tree whose parent-child relationships shape the proposed categorization. Leaves of the tree can contain metrics to satisfy the constraints, which are their parents. The tree structure of the classification helps one to deliver constraints as an input in the XML format to the composition process. Using a simple case study, the applicability of the presented classification structure is shown. Having this structure in place, the user can determine her constraints and their priorities more easily. Moreover, one can apply this structure to evaluate various composite services from user's point of view.

show abstract

Section: Taxonomy Evaluation In Comparison With Similar Workmentioning

confidence: 99%

An Approach to Classify Existing Constraints as Inputs for Web Service Composition

Sarraf¹,

Haghighi²

2013

IJCA

View full text Add to dashboard Cite

show abstract

“…Encourages and discourages constraints have been suggested as an extension to FM several times, for example in [12,39]. However, no precise semantics have been given to these extensions in the previous work.…”

Section: Related Workmentioning

confidence: 99%

Sample Spaces and Feature Models: There and Back Again

Czarnecki

She

Wąsowski

2008

2008 12th International Software Product Line Conference

View full text Add to dashboard Cite

show abstract

“…For retaining the reusability of services, it is important to separate non-functional properties of applications (e.g., security and reliability) from their functional properties because different applications use each service in different non-functional requirements (e.g., different security policies) [3][4][5]. 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].…”

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

Self Cite

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

A Feature Modeling Support for Non-Functional Constraints in Service Oriented Architecture

Cited by 26 publications

References 12 publications

An Approach to Classify Existing Constraints as Inputs for Web Service Composition

An Approach to Classify Existing Constraints as Inputs for Web Service Composition

Sample Spaces and Feature Models: There and Back Again

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

Contact Info

Product

Resources

About