Problem Statement

Overview

Build a bank system to create and manage user accounts, simulate deposits, withdrawals, interest accrual, and overdraft penalties.

Goals

• Support multiple account types with different rules
• Simulate real-world banking logic like minimum balance and interest
• Track user actions securely

Suggested Classes

• BankAccount: account_number, owner, balance, deposit(), withdraw()
• SavingsAccount(BankAccount): interest_rate, apply_interest()
• CheckingAccount(BankAccount): minimum_balance, penalty
• User: name, password, accounts[]

Features

• Create new accounts (checking/savings)
• Deposit money to account
• Withdraw money (with rules):
  • Checking: maintain minimum balance or pay penalty
  • Savings: limit to 3 withdrawals/month
• Apply interest monthly for savings
• Show account summary

OOP Concepts

• Inheritance: SavingsAccount and CheckingAccount from BankAccount
• Encapsulation: Balance, account actions hidden inside methods
• Polymorphism: Overridden withdraw() method in each subclass

Optional Extensions

• Password protection (simple CLI input masking)
• Transaction history with timestamp
• Monthly bank statement generation

Problem Statement

Overview

Design a command-line-based Library Management System that simulates the basic operations of a library for both users and administrators. It should manage books, user accounts, borrowing/returning of books, and enforce library rules like book limits per member.

Goals

• Allow members to search, borrow, and return books.
• Allow admins to manage the library’s inventory.
• Track book availability.
• Prevent double borrowing of a book.

Actors

• Admin
• Member

Suggested Classes

• Book: ID, title, author, genre, is_available
• User: username, role, user_id
• Member(User): borrowed_books (max 3 at a time)
• Admin(User): can add/remove books
• Library: manages collections of books and users

Features

• Admin:
  • Add a book with metadata
  • Remove a book by ID or title
  • List all books
• Member:
  • Register or login
  • View available books
  • Borrow a book (limit 3)
  • Return a book
• Library:
  • Handles storage, availability, and user-book mappings

OOP Concepts

• Inheritance: Admin and Member inherit from User
• Encapsulation: Book’s availability status and member’s borrow list
• Polymorphism: Different view_dashboard() method for Admin vs Member

Optional Extensions

• Track borrowing history (borrow date, return date)
• Due dates and overdue penalties
• Persistent data storage (JSON or SQLite)