Abstracting and Applying Business Modeling Patterns from RosettaNet

Abstract

RosettaNet is a leading industry effort that creates standards for business interactions among the participants in a supply chain. The RosettaNet standard defines over 100 Partner Interface Processes (PIPs) through which the participants can exchange business documents necessary to enact a supply chain. However, each PIP specifies the business interactions at a syntactic level, but fails to capture the business meaning of the interactions to which they apply. In contrast, this paper takes as its point of departure a commitment-based approach for business modeling that gives central position to interactions captured in terms of their meaning. This paper defines commitment-based business patterns abstracted from RosettaNet PIPs. Doing so yields models that are clearer, more flexible to changing requirements, and potentially enacted through multiple operationalizations. This paper validates the patterns by applying them to model the Order-to-Cash business process from the RosettaNet eBusiness Process Scenario Library.

Supporting the Analysis of Risks of Violation in Business Protocols: The MiFID Case Study

“…We have proposed a declarative approach to business protocol specification that extends [11] by explicitly including 2CL temporal regulations. We implemented a tuProlog extended commitment machine, which was applied to the MiFID case study, whose output allows the analysis of the business protocol and of possible violations.…”

“…Telang and Singh [11] proposed a commitment-based approach to representing business protocols and identified a set of common patterns of interaction, that can be used by the business analyst. Along this line, also [4] proposes commitment patterns that capture common business patterns, showing which robustness requirements are met by each of them.…”

An Interaction-Oriented Agent Framework for Open Environments

“…Open systems involve autonomous partners with heterogeneous software designs and implementations; hence, the need of identifying high-level abstractions that allow modeling them in a natural way. In order to minimize the effort needed to define proper interfaces and to minimize the altering of internal implementations, Telang and Singh [42] propose that such abstractions should capture the contractual relationships among the partners, which are well-known to the business analysts and motivate the specification of the processes, and identify in commitment-based approaches [41,46] the appropriate features for performing this task. These, in fact, allow capturing the business intent of the system, leaving aside implementative issues.…”

Analyzing Contract Robustness through a Model of Commitments

“…In some cases, researchers have sought to use the tools and techniques of traditional software engineering to enhance AOSE, including efforts in programming tools and methodologies and in formal methods. Examples of the former include several works such as those surveyed by Nunes et al [14], and examples of the latter include works by Meneguzzi et al [13] and Telang and Singh [19,20]. In other cases, researchers have sought to formalize concepts that originate in AOSE in ways that might influence traditional software engineering.…”