Thursday, June 28, 2012

Using Context Diagram to describe a Bank System


This diagram shows the entirety of our proposed Bank System encapsulated as a single process that sends data to, and receives data from, various external interfaces.
The interfaces to the right represent human actors of the kind you might find on a UML Use Case Diagram, who will interact with our system in various ways. Customers can send deposit and withdrawal requests to our system and can receive statements from it. Bank Managers can sendopen and close account requests to the system and can receive management reports from it.Third Parties can send third party deposits to the system, but obviously not mkae withdrawal requests.
The first interface on the left of our diagram represents the Other Banks which may send or receivemoney transfers when interacting with our system. These other banks are likely to be system actors (i.e. computer programs) rather than human actors.
The second interface on the left of our diagram represents the Sales Agents, which are external affiliate companies or individuals who generate customer introductions for our system.
Note that while the context diagram shows the kind of data that is exchanged between our system and the external interfaces, it implies nothing at all regarding the sequence in which those data exchanges take place.




1 comment: