E-Billing Management System Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of E-Billing Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of E-Billing Management System. The main actors of E-Billing Management System in this Use Case Diagram are: Super Admin, System User, Accountant, Customer, who perform the different type of use cases such as Manage Bills, Manage Customer, Manage Transactions, Manage Login, Manage Payment, Manage Receipts, Manage Payment Mode, Manage Users and Full E-Billing Management System Operations. Major elements of the UML use case diagram of E-Billing Management System are shown on the picture below.

The relationships between and among the actors and the use cases of E-Billing Management System:

  • Super Admin Entity : Use cases of Super Admin are Manage Bills, Manage Customer, Manage Transactions, Manage Login, Manage Payment, Manage Receipts, Manage Payment Mode, Manage Users and Full E-Billing Management System Operations
  • System User Entity : Use cases of System User are Manage Bills, Manage Customer, Manage Transactions, Manage Login, Manage Payment, Manage Receipts, Manage Payment Mode
  • Accountant Entity : Use cases of Accountant are Create Bills, Request for Payments, Create Receipts, Collect Payments
  • Customer Entity : Use cases of Customer are Check Bills, Make Payments, Print Receipts, Check Payment History

Use Case Diagram of E-Billing Management System :

E-Billing Management System Use Case Diagram
Get 6 diagrams only in 300/- or $6.99 USD.
Call or WhatsApp us on +91-8470010001 for more details.

Related Usecase Diagrams

 Defect Tracking System Use Case Diagram

Defect Tracking System Use Case Diagram

This Use Case Diagram is a graphic depiction of the interactions among the elements of Defect Tracking System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Defect Tracking System. The main actors of Defect Tracking System in this...
Student Evolution System Use Case Diagram

Student Evolution System Use Case Diagram

This Use Case Diagram is a graphic depiction of the interactions among the elements of Student Evolution System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Student Evolution System. The main actors of Student Evolution System in...
Railway Management System Use Case Diagram

Railway Management System Use Case Diagram

This Use Case Diagram is a graphic depiction of the interactions among the elements of Railway Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Railway Management System. The main actors of Railway Management System...
 Computerized Accounts Reporting System Use Case Diagram

Computerized Accounts Reporting System Use Case Diagram

This Use Case Diagram is a graphic depiction of the interactions among the elements of Computerized Accounts Reporting System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Computerized Accounts Reporting System. The main actors of...
Library Management System Use Case Diagram

Library Management System Use Case Diagram

This Use Case Diagram is a graphic depiction of the interactions among the elements of Library Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Library Management System. The main actors of Library Management System...
Hotel Booking System Use Case Diagram

Hotel Booking System Use Case Diagram

This Use Case Diagram is a graphic depiction of the interactions among the elements of Hotel Booking System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Hotel Booking System. The main actors of Hotel Booking System in this Use Case...