- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Courier Management System Activity Diagram
This is the Activity UML diagram of Courier Management System which shows the flows between the activity of Payment, Customer, Courier, Office, Shipment. The main activity involved in this UML Activity Diagram of Courier Management System are as follows:
- Payment Activity
- Customer Activity
- Courier Activity
- Office Activity
- Shipment Activity
Features of the Activity UML diagram of Courier Management System
- Admin User can search Payment, view description of a selected Payment, add Payment, update Payment and delete Payment.
- Its shows the activity flow of editing, adding and updating of Customer
- User will be able to search and generate report of Courier, Office, Shipment
- All objects such as ( Payment, Customer, Shipment) are interlinked
- Its shows the full description and flow of Payment, Office, Shipment, Courier, Customer
Login Activity Diagram of Courier Management System:
This is the Login Activity Diagram of Courier Management System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Courier, Payment, Customer, Shipment, Office. All the pages such as Customer, Shipment, Office are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Courier Management System. The various objects in the Shipment, Courier, Payment, Customer, and Office page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Courier Management System Class Diagram
Courier Management System Class Diagram describes the structure of a Courier Management System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Courier Management System are Courier, Customer, Office, Manager, Shipment, Delivery.
Classes of Courier Management System Class Diagram:
- Courier Class : Manage all the operations of Courier
- Customer Class : Manage all the operations of Customer
- Office Class : Manage all the operations of Office
- Manager Class : Manage all the operations of Manager
- Shipment Class : Manage all the operations of Shipment
- Delivery Class : Manage all the operations of Delivery
Classes and their attributes of Courier Management System Class Diagram:
- Courier Attributes : courier_id, courier_product_id, courier_customer_id, courier_name, courier_type, courier_description
- Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Office Attributes : office_id, office_company_id, office_employee_id, office_name, office_place, office_type, office_address
- Manager Attributes : manager_id, manager_name, manager_mobile, manager_email, manager_username, manager_password, manager_address
- Shipment Attributes : shipment_id, shipment_courier_id, shipment_date, shipment_type, shipment_description
- Delivery Attributes : delivery_id, delivery_customer_id, delivery_address, delivery_type, delivery_by, delivery_date, delivery_description
Classes and their methods of Courier Management System Class Diagram:
- Courier Methods : addCourier(), editCourier(), deleteCourier(), updateCourier(), saveCourier(), searchCourier()
- Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
- Office Methods : addOffice(), editOffice(), deleteOffice(), updateOffice(), saveOffice(), searchOffice()
- Manager Methods : addManager(), editManager(), deleteManager(), updateManager(), saveManager(), searchManager()
- Shipment Methods : addShipment(), editShipment(), deleteShipment(), updateShipment(), saveShipment(), searchShipment()
- Delivery Methods : addDelivery(), editDelivery(), deleteDelivery(), updateDelivery(), saveDelivery(), searchDelivery()
Class Diagram of Courier Management System :
- Posted By: freeproject
- Comments: 0
Courier Management System Component Diagram
This is a Component diagram of Courier Management System which shows components, provided and required interfaces, ports, and relationships between the Delivery, Payment, Office, Courier and Shipment. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Courier Management System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Courier Management System:
- Delivery Component
- Payment Component
- Office Component
- Courier Component
- Shipment Component
Featues of Courier Management System Component Diagram:
- You can show the models the components of Courier Management System.
- Model the database schema of Courier Management System
- Model the executables of an application of Courier Management System
- Model the system's source code of Courier Management System
- Posted By: freeproject
- Comments: 0
Courier Management System Dataflow Diagram
Courier Management System Data flow diagram is often used as a preliminary step to create an overview of the Courier Management without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Courier Management process. It contains all of the userflow and their entities such all the flow of Courier, Tracking, Shipping, Offices, Managers, Customer, Address. All of the below diagrams has been used for the visualization of data processing and structured design of the Courier Management process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Courier Management System :
This is the Zero Level DFD of Courier Management System, where we have eloborated the high level process of Courier Management. It’s a basic overview of the whole Courier Management System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Managers,Customer and Address showing the system as a single high-level process, with its relationship to external entities of Courier,Tracking and Shipping. It should be easily understood by a wide audience, including Courier,Shipping and Managers In zero leve DFD of Courier Management System, we have described the high level flow of the Courier Management system.High Level Entities and proccess flow of Courier Management System:
- Managing all the Courier
- Managing all the Tracking
- Managing all the Shipping
- Managing all the Offices
- Managing all the Managers
- Managing all the Customer
- Managing all the Address
First Level Data flow Diagram(1st Level DFD) of Courier Management System :
First Level DFD (1st Level) of Courier Management System shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the Courier Management System system as a whole. It also identifies internal data stores of Address, Customer, Managers, Offices, Shipping that must be present in order for the Courier Management system to do its job, and shows the flow of data between the various parts of Courier, Shipping, Customer, Address, Managers of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of Courier Management.Main entities and output of First Level DFD (1st Level DFD):
- Processing Courier records and generate report of all Courier
- Processing Tracking records and generate report of all Tracking
- Processing Shipping records and generate report of all Shipping
- Processing Offices records and generate report of all Offices
- Processing Managers records and generate report of all Managers
- Processing Customer records and generate report of all Customer
- Processing Address records and generate report of all Address
Second Level Data flow Diagram(2nd Level DFD) of Courier Management System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Courier Management. It may require more functionalities of Courier Management to reach the necessary level of detail about the Courier Management functioning. First Level DFD (1st Level) of Courier Management System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Address, Customer, Managers, Offices, Shipping, Tracking, Courier.Low level functionalities of Courier Management System
- Admin logins to the system and manage all the functionalities of Courier Management System
- Admin can add, edit, delete and view the records of Courier, Shipping, Managers, Address
- Admin can manage all the details of Tracking, Offices, Customer
- Admin can also generate reports of Courier, Tracking, Shipping, Offices, Managers, Customer
- Admin can search the details of Tracking, Managers, Customer
- Admin can apply different level of filters on report of Courier, Offices, Managers
- Admin can tracks the detailed information of Tracking, Shipping, Offices, , Managers
- Posted By: freeproject
- Comments: 0
Courier Management System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Courier Management System Entity. The entity-relationship diagram of Courier Management System shows all the visual instrument of database tables and the relations between Customer, Manager, Courier, Delivery etc. It used structure data and to define the relationships between structured data groups of Courier Management System functionalities. The main entities of the Courier Management System are Courier, Customer, Office, Manager, Shipment and Delivery.
Courier Management System entities and their attributes :
- Courier Entity : Attributes of Courier are courier_id, courier_product_id, courier_customer_id, courier_name, courier_type, courier_description
- Customer Entity : Attributes of Customer are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Office Entity : Attributes of Office are office_id, office_company_id, office_employee_id, office_name, office_place, office_type, office_address
- Manager Entity : Attributes of Manager are manager_id, manager_name, manager_mobile, manager_email, manager_username, manager_password, manager_address
- Shipment Entity : Attributes of Shipment are shipment_id, shipment_courier_id, shipment_date, shipment_type, shipment_description
- Delivery Entity : Attributes of Delivery are delivery_id, delivery_customer_id, delivery_address, delivery_type, delivery_by, delivery_date, delivery_description
Description of Courier Management System Database :
- The details of Courier is store into the Courier tables respective with all tables
- Each entity (Delivery, Office, Shipment, Customer, Courier) contains primary key and unique keys.
- The entity Office, Shipment has binded with Courier, Customer entities with foreign key
- There is one-to-one and one-to-many relationships available between Shipment, Manager, Delivery, Courier
- All the entities Courier, Shipment, Office, Delivery are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Courier Management System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Courier Management System Sequence Diagram
This is the UML sequence diagram of Courier Management System which shows the interaction between the objects of Shipment, Payment, Customer, Courier, Office. The instance of class objects involved in this UML Sequence Diagram of Courier Management System are as follows:
- Shipment Object
- Payment Object
- Customer Object
- Courier Object
- Office Object
Login Sequence Diagram of Courier Management System:
This is the Login Sequence Diagram of Courier Management System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Customer, Shipment, Payment, Office, Courier. All the pages such as Payment, Office, Courier are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Courier Management System. The various objects in the Office, Customer, Shipment, Payment, and Courier page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Courier Management System which shows the interaction between the objects of Shipment, Payment, Customer, Courier, Office. The instance of class objects involved in this UML Sequence Diagram of Courier Management System are as follows:
- Shipment Object
- Payment Object
- Customer Object
- Courier Object
- Office Object
- Posted By: freeproject
- Comments: 0
Courier Management System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Courier Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Courier Management System. The main actors of Courier Management System in this Use Case Diagram are: Super Admin, System User, Courier Boy, Customer, who perform the different type of use cases such as Manage Courier, Manage Customer, Manage Office, Manage Manager, Manage Shipment, Manage Delivery, Manage Payment, Manage Users and Full Courier Management System Operations. Major elements of the UML use case diagram of Courier Management System are shown on the picture below.
The relationships between and among the actors and the use cases of Courier Management System:
- Super Admin Entity : Use cases of Super Admin are Manage Courier, Manage Customer, Manage Office, Manage Manager, Manage Shipment, Manage Delivery, Manage Payment, Manage Users and Full Courier Management System Operations
- System User Entity : Use cases of System User are Manage Courier, Manage Customer, Manage Office, Manage Manager, Manage Shipment, Manage Delivery, Manage Payment
- Courier Boy Entity : Use cases of Courier Boy are Check Couriers, Check Delivery Address, Check Customers
- Customer Entity : Use cases of Customer are Request for Pickup, Track Courier, Make Payments, Courier Booking History