Externalizing component manners to achieve greater maintainability through a highly re-configurable architectural style

Arsanjani, Ali; Zedan, Hussein; Alpigini, James J.

doi:10.1109/icsm.2002.1167827

Cited by 13 publications

(8 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One of the early formalizations of the variation-oriented analysis and design (VOAD) principle can be found in [1]. Our paper incorporates and extends these ideas by applying it to the specific case of business process-based solutions and deriving associated service variations.…”

Section: Related Work and Discussionmentioning

confidence: 93%

See 1 more Smart Citation

Deriving service variants from business process specifications

Ponnalagu

Narendra

2008

Proceedings of the 1st Bangalore Annual Compute Conference

View full text Add to dashboard Cite

Software service organizations typically tend to develop custom solutions upon entry to a project engagement. This is not a scalable proposition. Today, driven by the need for enhancing profitability, reuse of existing assets across customer engagements is a more viable strategy. This is leading to the transformation of software services organizations from a labor-based to an assetbased model. In the enterprise application development domain, business processes are used to model the dynamic behavior of enterprise applications. Hence one highly prevalent asset-based approach in this domain is to build a scalable portfolio of services using a service-oriented architecture (SOA) approach. This provides a mechanism for representing business processes as a set of business-aligned, loosely-coupled services that can be iteratively composed and re-composed to create loosely coupled composite applications that mirror and support business processes.A key research problem that arises here is how to instantiate a stated business process specification as a combination of variants of existing services in the portfolio. We show via an illustrative example that this problem is non-trivial and scalable, and it depends on the semantics of the business process specification, especially with respect to the inter-service data and control flow dependencies that the instantiated business process specification has to satisfy. To that end, we also present our Variation-Oriented Service Design (VOSD) algorithm for automatically deriving service-level variants from the stated business process specifications. We also show that our algorithm is scalable, since its asymptotic complexity is linear in the number of service variants. We also illustrate our algorithm via the example.

show abstract

Section: Related Work and Discussionmentioning

confidence: 93%

“…For example, in [1], several variation types such as type, process and rules have been introduced, and they can be represented here as Variation Feature Types. The same variation point can admit more than one variation feature, and one variation feature can be applied to many variation points.…”

mentioning

confidence: 99%

Deriving service variants from business process specifications

Ponnalagu

Narendra

2008

Proceedings of the 1st Bangalore Annual Compute Conference

View full text Add to dashboard Cite

show abstract

“…This paradigm is an evolution of the notion of the object paradigm: an object having identity, state, and behavior; a component exposing services, contracts, and manners and is, most importantly, configurable without requiring intrusive changes for using it [1]. Modularization and separation of concerns (for example, interface from implementation) are key elements of this paradigm.…”

Section: By Ali Arsanjani Guest Editormentioning

confidence: 99%

Introduction

2002

Commun. ACM

View full text Add to dashboard Cite

“…Arsanjani et al [88] addresses the issue of software maintenance of component based systems by identifying encapsulating and externalizing the variations around design decisions. The approach is based on the notation of Enterprise Component (EC).…”

Section: Maintainabilitymentioning

confidence: 99%