Collaboration Diagram Atm


ATM (Collaboration Diagram (UML)) Use Creately’s easy online diagram editor to edit this diagram, collaborate with others and export results to multiple image formats. We were unable to. UML Collaboration Diagram depicts the interactions between objects or parts in terms of sequenced messages and describes both the static structure and dynamic behavior of a system.

Class Diagram for Example ATM System


Shown below is the class diagram for the ATM system. The basic structure of theclass diagram arises from the responsibilities and relationships discovered whendoing the CRC cards and Interaction Diagrams. (If a class uses another classas a collaborator, or sends a message to an object of that class during anInteraction, then there must either be an association linking objects of those classes,or linking the 'sending' class to an object which provides access to an object ofthe 'receiving' class.)

Collaboration Diagram Atm

In the case of the ATM system, one of the responsibilitiesof the ATM is to provide access to its component parts for Session and Transactionobjects; thus, Session and Transaction have associations to ATM, which in turn hasassociations to the classes representing the individual component parts. (Explicit'uses' links between Session and Transaction, on the one hand, and the componentparts of the ATM, on the other hand, have been omitted from the diagram to avoidmaking it excessively cluttered.)


Collaborative Diagram Tool

The need for the various classes in the diagram was discovered at various points inthe design process.

Collaboration diagram meaning

Collaboration Diagram For Atm System With Explanation

  • Some classes were discovered when doing analysis (see the Analysis Class Diagram developed earlier.)
  • Some classes were discovered when doing CRC cards
    • Message - used to represent a message to the bank.
    • Receipt - used to encapsulate information to be printed on a receipt.
    • Status - used to represent return value from message to the bank.
    • Balances - used to record balance information returned by the bank.

  • Some classes were discovered when doing detailed design or writing code
    • Money - used to represent money amounts, in numerous places.
    • AccountInformation - contains names of various types of accounts customer can choose from

That is, OO design is not a 'waterfall' process - discoveries made when doing detaileddesign and coding can impact overall system design.

To prevent the diagram frombecoming overly large, only the name of each class is shown - the attribute andbehavior 'compartments' are shown in the detailed design, but are omitted here.

Click on a class icon for links to further information about it


Copyright © 2000, 2001, 2002 - Russell C. Bjork. Permission for non-commercial reproduction for educational use is hereby granted; all other rights are reserved.