Business Rules Segregation for Dynamic Process Management with an Aspect-Oriented Framework

Çetin, Semih; Altintas, N. Ilker; Solmaz, Remzi

doi:10.1007/11837862_20

Cited by 7 publications

(7 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(Report) Business Services Kit: A lightweight kit for development, publishing, administration of business services with a registry, repository, meta-model and policy management services [16]. (Service) RUMBA Business Rules Kit: Business domain independent Aspect-Oriented kit for business rules segregation where all aspects, facts, rules and rule-sets can be defined and managed dynamically by means of a GUI console [14]. …”

Section: Methodsmentioning

confidence: 99%

“…A BRMS enables the segregation of business rules from the application where they crosscut almost every tier from content to service [14]. RUMBA [14] provides a clear separation of a crosscutting concern, and enables dynamic integration of business rules with other business processes or business services using several architectural patterns. RuleML 4 is a DSL to define business rules as independent artifacts.…”

Section: Dslmentioning

confidence: 99%

See 1 more Smart Citation

OCTOPODA: Building Financial Gateways Family System Using Domain Specific Kits

Altintas

Çetin

Surav

2008

Third International Conference on Systems (Icons 2008)

Self Cite

View full text Add to dashboard Cite

Financial institutions have been progressively challenged by being linked to a network of various internaland external systems through different and complex protocols. The way to manage this challenge is exploiting application-specific gateways known as financial gateways. However, the complexities of switch protocols as well as the variety of internal and external systems make the design of financial gateways quite complicated. This paper briefly summarizes the challenges of building family of financial gateway systems and introduces a systematic approach to design and implement them with "Domain Specific Kit" abstraction. This abstraction can separate system design concerns properly, isolate them in discrete building blocks, and finally compose them by means of a structured choreography model. The approach has been implemented within the context of OCTOPODA project and experimented in real life cases. The paper also presents and discusses the results of this experimentation.

show abstract

Section: Methodsmentioning

confidence: 99%

Section: Dslmentioning

confidence: 99%

OCTOPODA: Building Financial Gateways Family System Using Domain Specific Kits

Altintas

Çetin

Surav

2008

Third International Conference on Systems (Icons 2008)

Self Cite

View full text Add to dashboard Cite

show abstract

“…-Implementers (plug-in). The product developer can supply part of an artifact (e.g., rule, service) at runtime, for example, via bytecode engineering facilities similar to those provided by RUMBA [53].…”

Section: Software Asset Metamodelmentioning

confidence: 99%

“…The first one, called RUMBA [53], is a Business Rules Management System (BRMS) which enables the separation of business rules from the application, where they crosscut almost every tier from content to service. As a DSK, RUMBA provides a clear segregation of business rules and enables dynamic integration with other business processes and/or business services.…”

Section: Domain-specific Kitsmentioning

confidence: 99%

“…Furthermore, we also specify the association of artifact types with DSKs. For instance, the RUMBA [53] Business Rules Kit provides the Rule and Composite-Rule artifact types, which are expressed in RuleML, defined and managed using the RUMBA RuleEditor, and executed by the RUMBA Runtime Engine. The artifact dependencies depicted in Fig.…”

Section: Defining the Asset Modeling Languagementioning

confidence: 99%

See 1 more Smart Citation

Modeling Product Line Software Assets Using Domain-Specific Kits

Altintas

Çetin

Doğru

et al. 2012

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

Software Product Line Engineering (SPLE) is a prominent paradigm for the assembly of a family of products using product line core assets. The modeling of software assets that together form the actual products is critical for achieving the strategic benefits of Software Product Lines (SPLs). We propose a feature-based approach to software asset modeling based on abstractions provided by Domain-Specific Kits (DSKs). This approach involves a software Asset Metamodel (AMM) used to derive Asset Modeling Languages (AMLs) that define reusable software assets in domain-specific terms. The approach also prescribes a roadmap for modeling these software assets in conjunction with the product line reference architecture. Asset capabilities can be modeled using feature diagrams as the external views of the software assets. Internal views can be expressed in terms of Domain-Specific Artifacts (DSAs) with Variability Points (VPs), where the domain-specific artifacts are created using Domain-Specific Kits. This approach produces loosely coupled and highly cohesive software assets that are reusable for multiple product lines. The approach is validated by assessing software asset reuse in two different product lines in the finance domain. We also evaluated the productivity gains in large-scale complex projects, and found that the approach yielded a significant reduction in the total project effort.

show abstract

Bringing Agility to Business Process Management: Rules Deployment in an SOA

Kharbili

Keil

2010

Emerging Web Services Technology Volume III

View full text Add to dashboard Cite

Business Rules Segregation for Dynamic Process Management with an Aspect-Oriented Framework

Cited by 7 publications

References 7 publications

OCTOPODA: Building Financial Gateways Family System Using Domain Specific Kits

OCTOPODA: Building Financial Gateways Family System Using Domain Specific Kits

Modeling Product Line Software Assets Using Domain-Specific Kits

Bringing Agility to Business Process Management: Rules Deployment in an SOA

Contact Info

Product

Resources

About