A Methodology for Evolving E-Contracts Using Templates

Abstract

E-contract evolves over a period of time due to changes in e-contract environment. E-contract evolution adversely affects the execution of e-contracts. An e-contract is specified by a model at conceptual level, supported by a database management system (DBMS) at logical level and by both DBMS and workflow management system (WFMS) at implementation level. Any changes in the design as well as runtime environment during e-contract enactment must be reflected at all levels.Conventional modeling approaches simply model the e-contracts as specified workflows and execute them. Since, e-contracts are complex in nature, such models have to undergo large number of transformations during e-contract enactment. Metamodeling approach guides the correctness of transformed models by generating appropriate model instances according to e-contract constraints to support evolution. A metamodel has structural artifacts to capture the relationships among contract elements and model the required specifications and semantics present in an e-contract as a template. In this paper, we develop 1) an active metamodeling approach by a) introducing the taxonomy of evolution operations and b) handling metaevents to facilitate the structural and behavioral conformance during e-contracts evolution, and 2) an ER ÃEC architecture for enacting evolving e-contracts. Our methodology actively capture behavior features from e-contract executions to drive e-contract evolution.

A Review and Comparison of Service E-Contract Architecture Metamodels

“…It has been continuously updated, the most recent updated version of the metamodel being published in 2013 [8]. The ER EC model is shown in Figure 1.…”

“…Despite changes and evolution in the architecture of the ER EC , the fundamental structure of the e-contract model remains the same [9]. In the most recent version of the ER EC model [8], the authors proposed the metamodeling approach which is able to dene template for contracts.…”

“…The evolved ER EC metamodel organises the most abstract entities as core entities and denes a contract template. The template or model instantiates the ER EC metamodel that includes the domain constraints and relationships for the e-contract application [8]. The use of the template allows the e-contract model to evolve.…”

“…Furthermore, the template has several features such as adding new concepts into the model and reecting the most real entities by modeling these concepts in the domain application. In addition, the latest versions of the ER EC have proposed a meta-modeling approach to respond to the events that trigger run-time changes to the e-contract or exceptions due to violation in an existing contract clause [8]. Now, the ER EC metamodel architecture will be analysed from its structure, behavior and technology perspectives.…”

“…iv Build: This is used when there is a need to change the structure of the e-contract model by adding new concepts [8].…”