This example of UML class diagram models bank account system.
"A bank account is a financial account between a bank customer and a financial institution. A bank account can be a deposit account, a credit card, or any other type of account offered by a financial institution. The financial transactions which have occurred within a given period of time on a bank account are reported to the customer on a bank statement and the balance of the account at any point in time is the financial position of the customer with the institution. a fund that a customer has entrusted to a bank and from which the customer can make withdrawals." [Bank account. Wikipedia]
This bank account system UML class diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
"A bank account is a financial account between a bank customer and a financial institution. A bank account can be a deposit account, a credit card, or any other type of account offered by a financial institution. The financial transactions which have occurred within a given period of time on a bank account are reported to the customer on a bank statement and the balance of the account at any point in time is the financial position of the customer with the institution. a fund that a customer has entrusted to a bank and from which the customer can make withdrawals." [Bank account. Wikipedia]
This bank account system UML class diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
This bank account UML package diagram was redesigned from the Wikimedia Commons file: Package diagram1.jpg.
[commons.wikimedia.org/ wiki/ File:Package_ diagram1.jpg]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
"A very important concept in object-oriented design, inheritance, refers to the ability of one class (child class) to inherit the identical functionality of another class (super class), and then add new functionality of its own. (In a very non-technical sense, imagine that I inherited my mother's general musical abilities, but in my family I'm the only one who plays electric guitar.) To model inheritance on a class diagram, a solid line is drawn from the child class (the class inheriting the behavior) with a closed, unfilled arrowhead (or triangle) pointing to the super class. Consider types of bank accounts: Figure 4 shows how both CheckingAccount and SavingsAccount classes inherit from the BankAccount class.
Figure 4: Inheritance is indicated by a solid line with a closed, unfilled arrowhead pointing at the super class." [ibm.com/ developerworks/ rational/ library/ content/ RationalEdge/ sep04/ bell/ index.html]
This bank account UML package diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
[commons.wikimedia.org/ wiki/ File:Package_ diagram1.jpg]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
"A very important concept in object-oriented design, inheritance, refers to the ability of one class (child class) to inherit the identical functionality of another class (super class), and then add new functionality of its own. (In a very non-technical sense, imagine that I inherited my mother's general musical abilities, but in my family I'm the only one who plays electric guitar.) To model inheritance on a class diagram, a solid line is drawn from the child class (the class inheriting the behavior) with a closed, unfilled arrowhead (or triangle) pointing to the super class. Consider types of bank accounts: Figure 4 shows how both CheckingAccount and SavingsAccount classes inherit from the BankAccount class.
Figure 4: Inheritance is indicated by a solid line with a closed, unfilled arrowhead pointing at the super class." [ibm.com/ developerworks/ rational/ library/ content/ RationalEdge/ sep04/ bell/ index.html]
This bank account UML package diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
ATM UML Diagrams
The ATM UML Diagrams solution lets you create ATM solutions and UML examples. Use ConceptDraw PRO as a UML diagram creator to visualize a banking system.
"An automated teller machine or automatic teller machine" (ATM) (American, Australian, Singaporean, Indian, and Hiberno-English), also known as an automated banking machine (ABM) (Canadian English), cash machine, cashpoint, cashline or hole in the wall (British, South African, and Sri Lankan English), is an electronic telecommunications device that enables the clients of a financial institution to perform financial transactions without the need for a cashier, human clerk or bank teller.
On most modern ATMs, the customer is identified by inserting a plastic ATM card with a magnetic stripe or a plastic smart card with a chip that contains a unique card number and some security information such as an expiration date or CVVC (CVV). Authentication is provided by the customer entering a personal identification number (PIN). The newest ATM at Royal Bank of Scotland allows customers to withdraw cash up to £100 without a card by inputting a six-digit code requested through their smartphones.
Using an ATM, customers can access their bank accounts in order to make cash withdrawals, get debit card cash advances, and check their account balances as well as purchase pre-paid mobile phone credit. If the currency being withdrawn from the ATM is different from that which the bank account is denominated in (e.g.: Withdrawing Japanese yen from a bank account containing US dollars), the money will be converted at an official wholesale exchange rate. Thus, ATMs often provide one of the best possible official exchange rates for foreign travellers, and are also widely used for this purpose." [Automated teller machine. Wikipedia]
The UML activity diagram example "Cash withdrawal from ATM" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
On most modern ATMs, the customer is identified by inserting a plastic ATM card with a magnetic stripe or a plastic smart card with a chip that contains a unique card number and some security information such as an expiration date or CVVC (CVV). Authentication is provided by the customer entering a personal identification number (PIN). The newest ATM at Royal Bank of Scotland allows customers to withdraw cash up to £100 without a card by inputting a six-digit code requested through their smartphones.
Using an ATM, customers can access their bank accounts in order to make cash withdrawals, get debit card cash advances, and check their account balances as well as purchase pre-paid mobile phone credit. If the currency being withdrawn from the ATM is different from that which the bank account is denominated in (e.g.: Withdrawing Japanese yen from a bank account containing US dollars), the money will be converted at an official wholesale exchange rate. Thus, ATMs often provide one of the best possible official exchange rates for foreign travellers, and are also widely used for this purpose." [Automated teller machine. Wikipedia]
The UML activity diagram example "Cash withdrawal from ATM" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
HelpDesk
How to Create a Bank ATM Use Case Diagram
UML diagrams are often used in banking management for documenting a banking system. In particular, the interaction of bank customers with an automated teller machine (ATM) can be represented in a Use Case diagram. Before the software code for an ATM, or any other system design, is written, it is necessary to create a visual representation of any object-oriented processes. This is done most effectively by creating a Unified Modeling Language (UML) diagram, using object-oriented modeling. UML works as a general purpose modeling language for software engineers or system analysts, offering a number of different diagram styles with which to visually depict all aspects of a software system. ConceptDraw PRO diagramming software, enhanced and expanded with the ATM UML Diagrams solution, offers the full range of icons, templates and design elements needed to faithfully represent ATM and banking information system architecture using UML standards. The ATM UML Diagrams solution is useful for beginner and advanced users alike. More experienced users will appreciate a full range of vector stencil libraries and ConceptDraw PRO's powerful software, that allows you to create your ATM UML diagram in a matter of moments.Use Case Diagrams technology with ConceptDraw PRO
Use case diagrams are used at the development of software and systems for definition of functional system requirements or system of systems. Use case diagram presents the consecution of object’s actions (user’s or system’s) which are executed for reaching the definite result.Data Flow Diagrams (DFD)
Data Flow Diagrams solution extends ConceptDraw PRO software with templates, samples and libraries of vector stencils for drawing the data flow diagrams (DFD).
This example of bank ATM UML activity diagram was created on the base of UML use case diagram of automated teller machine from the course "Thinking in Java, 2nd edition, Revision 9" by Bruce Eckel published on the website of the Computer Science and Electrical Engineering Department of the University of Maryland, Baltimore (UMBC).
"If you are designing an auto-teller, for example, the use case for a particular aspect of the functionality of the system is able to describe what the auto-teller does in every possible situation. Each of these “situations” is referred to as a scenario, and a use case can be considered a collection of scenarios. You can think of a scenario as a question that starts with: “What does the system do if...?” For example, “What does the auto-teller do if a customer has just deposited a check within the last 24 hours, and there’s not enough in the account without the check having cleared to provide a desired withdrawal?”
Use case diagrams are intentionally simple to prevent you from getting bogged down in system implementation details prematurely...
Each stick person represents an “actor,” which is typically a human or some other kind of free agent. (These can even be other computer systems, as is the case with “ATM.”) The box represents the boundary of your system. The ellipses represent the use cases, which are descriptions of valuable work that can be performed with the system. The lines between the actors and the use cases represent the interactions.
It doesn’t matter how the system is actually implemented, as long as it looks like this to the user."
[csee.umbc.edu/ courses/ 331/ resources/ tij/ text/ TIJ213.gif]
This automated teller machine (ATM) UML use case diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
"If you are designing an auto-teller, for example, the use case for a particular aspect of the functionality of the system is able to describe what the auto-teller does in every possible situation. Each of these “situations” is referred to as a scenario, and a use case can be considered a collection of scenarios. You can think of a scenario as a question that starts with: “What does the system do if...?” For example, “What does the auto-teller do if a customer has just deposited a check within the last 24 hours, and there’s not enough in the account without the check having cleared to provide a desired withdrawal?”
Use case diagrams are intentionally simple to prevent you from getting bogged down in system implementation details prematurely...
Each stick person represents an “actor,” which is typically a human or some other kind of free agent. (These can even be other computer systems, as is the case with “ATM.”) The box represents the boundary of your system. The ellipses represent the use cases, which are descriptions of valuable work that can be performed with the system. The lines between the actors and the use cases represent the interactions.
It doesn’t matter how the system is actually implemented, as long as it looks like this to the user."
[csee.umbc.edu/ courses/ 331/ resources/ tij/ text/ TIJ213.gif]
This automated teller machine (ATM) UML use case diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
"Credits and deposits.
To add credit to an account by bringing cash to a bank in person, the account holder can fill a small credit slip or deposit slip. The total amount of each note and coin is counted and entered on the slip, along with who it is paid in by and the date. The cash and details are counted and checked by the teller at the bank, if everything is in order the deposit is credited to the account, the credit slip is then kept by the bank and the credit slip booklet is stamped with the date and then returned to the account holder.An account holder uses their passbook to record their history of transactions with their bank." [Passbook. Wikipedia]
The UML activity diagram example "Deposit slip processing" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
To add credit to an account by bringing cash to a bank in person, the account holder can fill a small credit slip or deposit slip. The total amount of each note and coin is counted and entered on the slip, along with who it is paid in by and the date. The cash and details are counted and checked by the teller at the bank, if everything is in order the deposit is credited to the account, the credit slip is then kept by the bank and the credit slip booklet is stamped with the date and then returned to the account holder.An account holder uses their passbook to record their history of transactions with their bank." [Passbook. Wikipedia]
The UML activity diagram example "Deposit slip processing" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
- UML use case diagram - Banking system
- Draw A Uml Class Diagram For Opening A Bank Account
- Draw A Uml Diagram For Opening A Bank Account
- Draw A Uml Class Diagram For Opening Account
- Draw A Uml Diagram To Opening A Bank Account
- UML class diagram - Bank account | How to Create a Bank ATM Use ...
- Uml Diagram For Opening Bank Account
- UML class diagram - Bank account | UML package diagram for Bank ...
- Uml Class Diagram For Opening Bank Account
- Class UML Diagram for Bank Account System | Bank UML Diagram ...
- Class UML Diagram for Bank Account System | UML package ...
- UML for Bank | ATM UML Diagrams | UML use case diagram ...
- Create Diagram Money Bank Account
- Drow A Uml Use Case Diagram For Opening A Bank Account
- UML for Bank | UML use case diagram - Banking system | Class ...
- DFD - Process of account receivable | Data Flow Diagram Process ...
- UML for Bank | How to Create a Bank ATM Use Case Diagram ...
- Class UML Diagram for Bank Account System | UML use case ...
- UML for Bank | UML use case diagram - Banking system | UML ...
- UML use case diagram - Banking system | UML for Bank | Class ...