This section introduces a typical bank teller scenario, and how to use
the supporting components and branch application components of Business Component
to build such a scenario.
There are two roles in a typical bank teller scenario, teller and supervisor.
For the teller, there are following user activities in the scenario:
- The teller can log on the teller desktop of rich client. The rich client
only displays the navigator items with which the teller’s access control rights
are assigned.
- The teller can execute transactions, such as cash deposit and withdraw.
For some certain transactions, the teller needs the override approval from
the supervisor.
- The teller can manage the cash amount by a cash drawer management application.
- The teller can query the transaction journals by a journal viewer user
interface (UI). The teller can also restore the transaction UI and data for
the journal record of query result.
For the supervisor, there are following user activities in the scenario:
- The supervisor can login on the desktop of rich client. The desktop only
displays the navigator items about management like access control management
and electronic journal (EJ) viewer. The rich client also has an override inbound
request view for the supervisor.
- The supervisor can create and assign access control rights for uses and
roles in a management UI.
- The supervisor can audit transactions by query all teller’s transaction
journals and restore the transaction UI and data.
To implement such a scenario introduced above, the following business components
are required:
- Access Control
- EJ/EJ Viewer
- Override
- Cash Drawer Management
- BTT Remote
- BTT Asynchronous Message
The rich client UI is based on BTT RCP component. Especially, the new component
BTT RCP XUI is used to implement the transaction UI for display and restoring.
What the Business Component application of such a scenario looks like,
and the key points of how to build the application are introduced
in the Tasks section.