
🎓 Student Projects (College Reports) · Class UML
Classes for an ATM system: the ATM and its card reader, keypad, screen, cash dispenser and receipt printer, the bank, accounts, cards, customers and transaction types.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagram…
Class diagram for an ATM system: ATM with CardReader, Keypad, Screen, CashDispenser and ReceiptPrinter; Bank; Account with SavingsAccount and CurrentAccount; Card; Customer; Transaction as an abstract class with Withdrawal, Deposit, Transfer and BalanceEnquiry subclasses. Show attributes, key methods and multiplicities.
classDiagram
class Customer {
+UUID customerId
+string name
+string phoneNumber
}
class Account {
<<abstract>>
+UUID accountId
+string accountNumber
+Decimal balance
+credit(amount: Decimal) void
+debit(amount: Decimal) bool
}
class SavingsAccount {
+Decimal interestRate
+calculateInterest() Decimal
}
class CurrentAccount {
+Decimal overdraftLimit
+checkOverdraft(amount: Decimal) bool
}
class Card {
+string cardNumber
+Date expiryDate
+string pinHash
+int failedPinAttempts
+bool isBlocked
+verifyPin(enteredPin: string) bool
+validateExpiry() bool
}
class ATM {
+UUID atmId
+string location
+Decimal cashOnHand
+bool isOperational
+authenticateUser(card: Card, pin: string) bool
}
class CardReader {
+readCard() Card
+ejectCard() void
+retainCard() void
}
class Keypad {
+getInput() string
}
class Screen {
+displayMessage(message: string) void
}
class CashDispenser {
+Decimal currentCash
+dispenseCash(amount: Decimal) bool
}
class ReceiptPrinter {
+printReceipt(transaction: Transaction) void
}
class Bank {
+string bankCode
+string name
+authorizeTransaction(transaction: Transaction) bool
}
class Transaction {
<<abstract>>
+UUID transactionId
+DateTime timestamp
+TransactionStatus status
+execute() bool
}
class Withdrawal {
+Decimal amount
+execute() bool
}
class Deposit {
+Decimal amount
+execute() bool
}
class Transfer {
+Decimal amount
+string targetAccountNumber
+execute() bool
}
class BalanceEnquiry {
+fetchBalance() Decimal
}
class TransactionStatus {
<<enumeration>>
PENDING
SUCCESSFUL
FAILED
CANCELLED
}
Account <|-- SavingsAccount
Account <|-- CurrentAccount
Transaction <|-- Withdrawal
Transaction <|-- Deposit
Transaction <|-- Transfer
Transaction <|-- BalanceEnquiry
Customer "1" -- "*" Account : owns
Customer "1" -- "1..*" Card : holds
Card "*" -- "1" Account : linkedTo
Bank "1" -- "*" Account : manages
ATM "1" *-- "1" CardReader : contains
ATM "1" *-- "1" Keypad : contains
ATM "1" *-- "1" Screen : contains
ATM "1" *-- "1" CashDispenser : contains
ATM "1" *-- "1" ReceiptPrinter : contains
ATM "*" -- "1" Bank : connectsTo
ATM "1" ..> "*" Transaction : processes
Transaction "*" -- "1" Account : appliesTo
Transaction --> TransactionStatus : hasA class diagram with 18 classes and 19 relationships.
Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.
Who uses a college library system and what each of them can do: members, the librarian and the system administrator.
The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
The main classes of a library system with attributes, methods and UML relationships.
The steps when a member borrows a book: checks, loan record and the copy status update.
What students, examiners and the administrator do in an online examination system.