-
Final Workshop @ ICSE 2012
Proceedings are availabe from here.
|
- Info
Business Transaction
Definitions
Term:
Business Transaction |
Domain: Cross-cutting
issues |
Engineering and Design
(KM-ED) |
Adaptation and Monitoring
(KM-AM) |
Quality Definition, Negotiation and
Assurance
(KM-QA) |
Generic
(domain independent) |
D
o
m
a
i
n
:
L
a
y
e
r
s
|
Business Process Management
(KM-BPM) |
|
|
|
A Business Transaction is a consistent
change in the state of the business that is driven by a well-defined
business function. [Papazoglou,2003]
__ALT___
A business transaction is driven by well-defined business tasks and
events that directly or indirectly contribute to generating economic
value, such as processing and paying an insurance claim, and has also
an associated number of parameters that represent Security and timing
requirements. Business transactions always either succeed or fail with
respect to the business tasks (functions) that initiated them and
govern them throughout their execution. If a business transaction
completes successfully then each participant will have made consistent
state changes, which, in aggregate, reflect the desired outcome of the
multi-party business interaction.
At structural level, a business transaction is made up of a requesting
(initiating) business activity performed by an
initiating partner (party) and a responding business activity performed
by the responding business partner. The initiating business activity
sends a business document to a responding business activity that may
return a business signal (signifying the completion of an activity) and
possibly a business document as the last responding message. A
transaction is associated with an SLA that
describes the agreed upon Quality of Service (QoS)
requirements and usually outlines what each party can do in the event
the intended actions are not carried out (e.g., promised services not
rendered, services rendered but payment not issued).
[PO-JRA-2.1.1]
__ALT___
A series of collaborative activities that explicitly enforces the
achievement of an agreed-upon business objective in end-to-end
processes. This objective is subject to service-level agreements that
govern the choreographed/orchestrated behavior, non-functional and
timing requirements, correlated exchange of information, and control
flow of composed services. [CD-JRA-2.1.3]
|
Service Composition and
Coordination
(KM-SC) |
In a Web Service environment, business
transactions essentially signify transactional web service interactions
between organisations in order to accomplish some well-defined shared
business objective.
[Papazoglou,2003] |
|
|
|
Service Infrastructure
(KM-SI) |
|
|
|
|
Generic
(domain independent) |
|
|
|
|
Competencies
References
- [PO-JRA-2.1.1]
"Survey on Business Process Management"
- [Papazoglou,2003] M. P. Papazoglou, "Web Services and Business
Transactions," World Wide Web, vol. 6, no. 1, pp. 49-91,
2003.
- [Papazoglou&Kratz,2006] M. P. Papazoglou, B. Kratz, "A
Business-Aware Web Services Transaction Model," in Proceedings of
the 4th International Conference on Service-Oriented Computing
(ICSOC'06), 2006, pp. 352-364.
- [CD-JRA-2.1.3]
"Business Transaction Language".
http://www.s-cube-network.eu/working-area/activities-and-workpackages/jra-2/WP-JRA-2.1/deliverables/cd-jra-2.1.3/CD-JRA-2.1.3%20Final.pdf/view
|
|