How ochiengedwin/water-billing-system works
This is a small Tkinter water-billing application. Users register or sign in, view their account, enter a meter reading, and receive an updated bill; administrators can sign in and change charges. The code also includes account deletion and activity logging. The excerpt shows SQLite access using waterbill.db, while the tree contains database.db; their relationship is unclear. check_bill is imported from waterBill, which is absent from the tree, so its implementation and downstream behavior cannot be verified.
Main entry points: edu.py Tkinter screens
Components 11
User interface
- Tkinter screens
edu.py - Activity logging
edu.py
Accounts
- User authentication
edu.py - User registration
edu.py - Account deletion
edu.py - SQLite store
Billing
- Bill check
- Meter bill update
edu.py - Charge settings
edu.py
Other components
- User
- Administrator
Connections 14
- User → Tkinter screens: uses
edu.py - Administrator → Tkinter screens: uses
edu.py - Tkinter screens → User authentication: submits credentials
edu.py - Tkinter screens → User registration: registers
edu.py - Tkinter screens → Bill check: requests bill check
edu.py - Tkinter screens → Meter bill update: submits meter reading
edu.py - Tkinter screens → Charge settings: opens charge settings
edu.py - Tkinter screens → Account deletion: requests deletion
edu.py - User authentication → SQLite store: queries credentials
edu.py - User registration → SQLite store: inserts account
edu.py - Account deletion → SQLite store: deletes records
edu.py - Meter bill update → SQLite store: updates bill
edu.py - Charge settings → SQLite store: updates charges
edu.py - Tkinter screens → Activity logging: appends events
edu.py