The major inputs that make this deliverable possible are the two service-oriented design diagrams
that were discussed in Chapters 12 and 13: service relationship and logical design composition.
Depiction of transaction activities would be sufficient for small-scale projects. For
larger initiatives, employ sessions that can illustrate a large amount of transactions and facilitate
transaction grouping and partitioning based on various business imperatives. Sessions should also
be employed to delineate between long-lived and short-lived transactions.
SUMMARY
The service-oriented transaction planning includes six major success criteria aspects:
??? Relative atomicity
??? Compensation policy
??? Short-lived and long-lived transaction activities
??? Synchronous and asynchronous transaction activities
??? Transaction isolation with relative activity locking
Summary 305
??? Tightly coupled and loosely coupled transaction capabilities
??? Orchestration and choreography
A service-oriented transaction diagram is composed of four major sections: consumer and
service, session, transaction, and activity.
An activity section includes a concurrency flag, an activity management label, and an
atomicity flag.
A transaction activity section should include a transaction timeline, depicted by activity
connectors and functionality descriptors.
A service-oriented transaction diagram should be based on two major service-oriented
design artifacts: service relationships diagrams and logical design compositions.
Pages:
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528