Architectural Model of the ATM System

Architectural Model of the ATM System

Multiprocessor architecture model

The model is the simplest ATM system is multiprocessor systems where the system consists of a number of processes that can run on multiple processors do not have to separate. This model is common in large real time systems. This Sistemsitem gather information, make decisions using this information, then sends a modified signal to the actuator system environment. The logic of the process associated with gathering information, decision-making and control actuators can be run on a processor with penjadual handled. Users lot of processors are useful for improving the performance and flexibility of the system. The distribution process can be determined prior to the processor. Design approach for this type of system is basically the approach used for real-time traffic control system example.
Client-server architecture model

Client and server are different processes, the client receives services from the server and not from other clients, the server can act as a client to receive services from another server but did not request service from the client, the client must know how to contact serverserver this. Client-server system design should reflect the logical structure being developed.

Kind of model client-server architecture client-server architecture model has two models:
Thin-client model

In thin-client model all processing and data management applications performed on the server. Client is responsible for running the presentation software.

implement the software on the client application logic and interaction with the user model fatclient


Distributed object architecture model of the more common approach for a distributed system is to eliminate the difference between client and server and designing the system architecture as a distributed object architecture.


Excess model of distributed object architecture

Excess model of distributed object architectures, among others:

• The model allows the system designer to delay decisions on where and how services should be provided.

• This model is a very open architecture that allows new resources be added if necessary.

• This system freksibel and scalable. The events of different systems the same services provided by different objects or a replicated object can be created to handle different system loads. New object can be added with increasing system load, without disturbing other system objects.

• Dynamically Reconfiguring the system will allow to immigrate across the network object bilaman required.
The weakness of distributed object architecture model

The weakness of this distributed system model is primarily designed architecture is difficult compared to client-server system.
Model CORBA (Common Object Request Broker Architecture)

This model for distributed object architecture implimentasikan require middleware to handle communication between distributed objects. In principle, the objects in the system can be implemented using different programming languages, can run on different platforms and his name does not need to know all the other objects on the system.