Projects

✕

  1. Leave Management System

    Question 1 of 5

      Project Overview
      1. This system is used to manage employee leave requests in a company.
      2. Employees can apply for leave and managers can approve or reject it using a command-line interface (CLI).
      Real-World Example
      1. An employee wants leave from 10 June to 15 June.
      2. Instead of sending messages or emails manually, they submit a leave request in the system.
      3. The manager checks the request and decides whether to approve or reject it.
      Core Features (CLI Mandatory)
      1. Employee registration and login using CLI menu.
      2. Employee can apply for leave by entering start date, end date, and reason.
      3. Employee can view their leave status (Pending / Approved / Rejected).
      4. Manager login using CLI.
      5. Manager can view all leave requests in table format in CLI
      6. Manager has option to export leave requests to CSV file.
      7. Manager has option to generate bar chart of leave status distribution.
      8. Manager can approve or reject leave using leave ID.
      9. Email notification is sent to employee after decision.
      10. All data is stored in SQLite database.
      Example Flow
      1. Employee logs in through CLI menu.
      2. Employee applies for leave with dates and reason.
      3. Request is saved in database with status "Pending".
      4. Manager logs in and views all requests.
      5. Manager approves or rejects the request.
      6. Employee receives email notification.
      Optional GUI (Bonus)
      1. Simple window showing leave requests in a table format.
      2. Buttons to approve or reject requests.
      3. GUI is optional and only for students who want to explore further.

  2. Support Ticket Handler

    Question 2 of 5

      Project Overview
      1. This system is used to manage customer complaints or support requests.
      2. Users create tickets and support staff resolve them step by step using CLI.
      Real-World Example
      1. A user cannot log in to a website.
      2. They create a support ticket describing the problem.
      3. The support team checks and updates the status until the issue is solved.
      Core Features (CLI Mandatory)
      1. User can create a support ticket using CLI.
      2. Each ticket has title, description, and priority (Low / Medium / High).
      3. System assigns a unique ticket ID automatically.
      4. Support staff can login and view all tickets in CLI.
      5. Support staff can export ticket list to CSV file.
      6. Support staff can generate pie-chart for number of tickets per status
      7. Support staff can update ticket status (Open / In Progress / Resolved).
      8. User can check ticket status using ticket ID.
      9. Email notification is sent when status changes.
      10. All data is stored in SQLite database.
      Example Flow
      1. User creates ticket: "Internet not working".
      2. Ticket is saved with status "Open".
      3. Support staff views the ticket list.
      4. Status is updated to "In Progress".
      5. Finally marked as "Resolved".
      6. User receives email updates at each stage.
      Optional GUI (Bonus)
      1. Dashboard showing all tickets in table form.
      2. Filters for status and priority.
      3. Buttons to update ticket status.

  3. Course Management

    Question 3 of 5

      Project Overview
      1. This system is used to manage students and course enrollment in schools or institutes.
      2. Students can register and enroll in available courses using CLI.
      Real-World Example
      1. A student wants to join a Python course.
      2. They select the course from the system and get enrolled.
      3. The system confirms the enrollment and stores the record.
      Core Features (CLI Mandatory)
      1. Student registration using CLI.
      2. Admin can add and manage courses using CLI.
      3. Students can view available courses.
      4. Students can enroll in a course.
      5. System prevents duplicate enrollment.
      6. Students can view their enrolled courses.
      7. Admin can export course enrollment list to CSV file.
      8. Admin can generate bar chart for number of students enrolled in each course.
      9. Email confirmation is sent after successful enrollment.
      10. All data is stored in SQLite database.
      Example Flow
      1. Student registers in the system.
      2. Admin adds a course like "Python Basics".
      3. Student selects and enrolls in the course.
      4. System stores enrollment in database.
      5. Email confirmation is sent to student.
      Optional GUI (Bonus)
      1. Course list displayed in table format.
      2. Simple buttons for enrollment.
      3. GUI is optional and not required.

  4. Expense Tracker

    Question 4 of 5

      Project Overview
      1. This system helps users track their income and expenses.
      2. It provides monthly summaries to understand spending habits.
      Real-World Example
      1. A student records daily expenses like food and transport.
      2. At the end of the month, they check how much money they spent and saved.
      Core Features (CLI Mandatory)
      1. Add income and expense entries using CLI.
      2. Each entry has category, amount, and date.
      3. View total income, expenses, and balance.
      4. View monthly report in CLI.
      5. Export report to CSV file
      6. Generate bar chart of category wise expenditure.
      7. Email monthly report to user.
      8. All data is stored in SQLite database.
      Example Flow
      1. User adds income: Pocket money ₹5000.
      2. User adds expense: Food ₹200.
      3. System calculates current balance.
      4. At month end, report is generated.
      5. Report is sent via email.
      Optional GUI (Bonus)
      1. Dashboard with charts (income vs expense).
      2. Graphical monthly summary view.
      3. GUI is optional enhancement.

  5. Inventory System

    Question 5 of 5

      Project Overview
      1. This system is used to manage product stock in a shop or small business.
      2. It helps track products, sales, and stock levels.
      Real-World Example
      1. A shop sells products like laptops and phones.
      2. When a product is sold, stock is reduced automatically.
      3. If stock becomes low, the system alerts the manager.
      Core Features (CLI Mandatory)
      1. Add new products using CLI.
      2. Update product quantity and price.
      3. Delete products from system.
      4. View all products in CLI table format.
      5. Track stock changes after sales.
      6. Low stock alert system using email.
      7. All data stored in SQLite database.
      Example Flow
      1. Admin adds product: Laptop (10 units).
      2. Sale happens, stock reduces to 8.
      3. System checks stock level.
      4. If stock is low, email alert is sent.
      5. Admin updates stock if needed.
      Optional GUI (Bonus)
      1. Product dashboard with stock table.
      2. Search and filter products visually.
      3. Buttons for add/update/delete.