Application Level Atomicity
by
Rafiq Haque
—
last modified
Apr 26, 2012 09:45
Definitions
| Term: Application Level Atomicity |
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) |
Application level atomicity {SYN: Non-Conventional Atomicity} is atomic behavior of business transaction. This type of atomicity is governed by application related atomicity criteria. Each criterion is treated as a single individual logical unit of work that determines a set of vital or viable outcomes for a business transaction. The outcomes of a business transaction may involve non-critical partial Failure, or selection among contending service offerings rather than the conventional strict atomicity (all or nothing). [CD-JRA-2.13] |
|||
| Service Composition and
Coordination (KM-SC) |
|||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
|||||
Competencies
- Tilburg: E-Business; http://www.tilburguniversity.nl/eriss/research/; Mike Papazoglou, Willem-Jan van den Heuvel, Rafiq Haque
References
- [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
