UML deployment diagram - Real estate transactions

"A real estate transaction is the process whereby rights in a unit of property (or designated real estate) is transferred between two or more parties, e.g. in case of conveyance one party being the seller(s) and the other being the buyer(s). It can often be quite complicated due to the complexity of the property rights being transferred, the amount of money being exchanged, and government regulations. Conventions and requirements also vary considerably among different countries of the world and among smaller legal entities (jurisdictions).
In more abstract terms, a real estate transaction, like other financial transactions, causes transaction costs. To identify and possibly reduce these transaction costs, the Organization for Economic Co-operation and Development (OECD) addressed the issue through a study commissioned by the European Commission, and through a research action.
The mentioned research action ‘Modelling Real Property Transactions’ investigated methods to describe selected transactions in a formal way, to allow for comparisons across countries / jurisdictions. Descriptions were performed both using a more simple format, a Basic Use Case template, and more advanced applications of the Unified Modelling Language. Process models were compared through an ontology-based methodology, and national property transaction costs were estimated for Finland and Denmark, based on the directions of the United Nations System of National Accounts." [Real estate transaction. Wikipedia]
The UML deployment diagram example "Real estate transactions" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

A four level pyramid model of different types of Information Systems based on the different levels of hierarchy in an organization. The first level represents transaction processing systems for workers. The second level represents management information systems for middle managers. The third level represents decision support systems for senior menegers. The fourth level represents executive information systems for executives.
"The "classic" view of Information systems found in the textbooks in the 1980s was of a pyramid of systems that reflected the hierarchy of the organization, usually transaction processing systems at the bottom of the pyramid, followed by management information systems, decision support systems, and ending with executive information systems at the top. Although the pyramid model remains useful, since it was first formulated a number of new technologies have been developed and new categories of information systems have emerged, some of which no longer fit easily into the original pyramid model.
Some examples of such systems are:
data warehouses,
enterprise resource planning,
enterprise systems,
expert systems,
search engines,
geographic information system,
global information system,
office automation." [Information systems. Wikipedia]
This diagram was redesigned using the ConceptDraw PRO diagramming and vector drawing software from Wikimedia Commons file Four-Level-Pyramid-model.png. [commons.wikimedia.org/ wiki/ File:Four-Level-Pyramid-model.png]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
The triangle chart example "Information systems types" is included in the Pyramid Diagrams solution from the Marketing area of ConceptDraw Solution Park.