Bank Example

We will use as an example the construction of an ATM application.
The basic use case is
1. User walks up to ATM and enters password.
2. If password is correct user is allowed to make transactions until card is removed.
3. User is given choices: get balance, withdraw money, deposit money, transfer money.
4. After choosing an action the user is given a list of valid accounts for that choice.
5. After a few transactions the user leaves.
The environmental constraints are that we must use the legacy database and the ATMs are physically distributed.

Client responsible for managing interaction with user, via GUI.
Stub implicitly handles connection.
Registry maintains mapping of human-readable names to server stubs and returns them when asked.
Skeletons and launch code do the work on the database.
Servers handle the business logic by running the skeletons, communicate with database.
Database system is responsible for long-term persistence and integrity of important data.