Endnotes
1. Theo Haerder and Andreas Reuter, ???Principles of Transaction-Oriented Database Recovery,??? 1983, ACM
0360??“0300/83/1200??“0287, p. 290
2. http://en.wikipedia.org/wiki/Atomicity.
3. http://en.wikipedia.org/wiki/Database consistency.
4. http://en.wikipedia.org/wiki/Isolation %28computer science%29 .
5. http://en.wikipedia.org/wiki/Durability %28computer science%29 .
6. www.serviceoriented.org/acid transactions.html
7. http://msdn2.microsoft.com/en-us/library/ms942772.aspx
8. ibid
9. www.agilemodeling.com/artifacts/sequenceDiagram.htm
PART SIX
SERVICE-ORIENTED SOFTWARE
ARCHITECTURE MODELING PRINCIPLES
The past couple decades, trends in technology influenced the fundamental change in the way
we conceive now a ???software system.??? This strategic thinking shifts the gravity of the discussion
from ???what is software architecture???? to ???what are we actually architecting???? The answers to these
questions become clearer once we have identified the subjects of our architectural efforts. The later
question is an intrinsic dilemma that leads to the notion that now, in recent history of computing,
we are more concerned with components, services, and distribution of software entities. We are
occupied with the design of small pluggable software units rather than constructing large systems.
We are more tuned to distributability, loose coupling, and interoperability of software aspects
rather than investing in centralized software environments.
Pages:
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529