How aditya24rathore/atm-project works
Project type and purpose (what you are diagramming)
This repo is a single-process C console application (“ATM System”) meant for educational ATM-like flows:
• PIN setup + PIN verification
• Lockout after 3 failures
• Menu-driven transactions: balance, deposit, withdraw
• All state is in-memory for the lifetime of the process (no DB/files/network)
What the file tree implies about architecture scope
From the tree:
• ATM.c is effectively the entire system (monolithic source)
• output/ATM.exe is a build artifact, not an architectural component
• No src/, include/, tests/, no persistence layer, no external services
main → Auth Gate → calls PIN() repeatedly
• Auth Gate reads PIN state, increments failed-attempt state
• If failed attempts == 3 → transition to Blocked/Exit
main → OS/System Layer (system("cls")) at relevant points
• Monolith / Single executable
• Layering by concern (logical, not physical folders):
• UI (CLI) vs Control vs Domain/Transactions vs State vs OS calls
• Gatekeeper pattern for authentication (PIN check) before allowing access to menu
• In-memory state store (global balance variable)