Courier Tracking System UML Diagram

Posted By freeproject on March 18, 2018

Courier Tracking System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Courier Tracking System which shows the flows between the activity of Manager, Office, Tracking, Customer, Delivery. The main activity involved in this UML Activity Diagram of Courier Tracking System are as follows:

  • Manager Activity
  • Office Activity
  • Tracking Activity
  • Customer Activity
  • Delivery Activity

Features of the Activity UML diagram of Courier Tracking System

  • Admin User can search Manager, view description of a selected Manager, add Manager, update Manager and delete Manager.
  • Its shows the activity flow of editing, adding and updating of Office
  • User will be able to search and generate report of Tracking, Customer, Delivery
  • All objects such as ( Manager, Office, Delivery) are interlinked
  • Its shows the full description and flow of Manager, Customer, Delivery, Tracking, Office
Courier Tracking System Activity Diagram

Courier Tracking System Class Diagram

Posted By freeproject on August 2, 2017

Courier Tracking System Class Diagram describes the structure of a Courier Tracking System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Courier Tracking System are Courier, Customer, Office, Manager, Shipment, Delivery.

Classes of Courier Tracking 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 Tracking 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 Tracking 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 Tracking System :

Class Diagram Image: 
Courier Tracking System Class Diagram

Courier Tracking System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Courier Tracking System which shows components, provided and required interfaces, ports, and relationships between the Office, Tracking, Delivery, Customer and Shipment. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Courier Tracking System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Courier Tracking System:

  • Office Component
  • Tracking Component
  • Delivery Component
  • Customer Component
  • Shipment Component

Featues of Courier Tracking System Component Diagram:

  • You can show the models the components of Courier Tracking System.
  • Model the database schema of Courier Tracking System
  • Model the executables of an application of Courier Tracking System
  • Model the system's source code of Courier Tracking System
Component Diagram: 

Courier Tracking System Dataflow Diagram

Posted By namita on June 30, 2017
Courier Tracking System Data flow diagram is often used as a preliminary step to create an overview of the Courier without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Courier process. It contains all of the userflow and their entities such all the flow of Courier, Customer, Manager, Shipment, Delivery, Office, Tracking. All of the below diagrams has been used for the visualization of data processing and structured design of the Courier process and working flow.

Zero Level Data flow Diagram(0 Level DFD) of Courier Tracking System :

This is the Zero Level DFD of Courier Tracking System, where we have eloborated the high level process of Courier. It’s a basic overview of the whole Courier Tracking System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Delivery,Office and Tracking showing the system as a single high-level process, with its relationship to external entities of Courier,Customer and Manager. It should be easily understood by a wide audience, including Courier,Manager and Delivery In zero leve DFD of Courier Tracking System, we have described the high level flow of the Courier system.

High Level Entities and proccess flow of Courier Tracking System:

  • Managing all the Courier
  • Managing all the Customer
  • Managing all the Manager
  • Managing all the Shipment
  • Managing all the Delivery
  • Managing all the Office
  • Managing all the Tracking
Zero Level Data flow Diagram(0 Level DFD) of Courier Tracking System

First Level Data flow Diagram(1st Level DFD) of Courier Tracking System :

First Level DFD (1st Level) of Courier Tracking 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 Tracking System system as a whole. It also identifies internal data stores of Tracking, Office, Delivery, Shipment, Manager that must be present in order for the Courier system to do its job, and shows the flow of data between the various parts of Courier, Manager, Office, Tracking, Delivery 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.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Courier records and generate report of all Courier
  • Processing Customer records and generate report of all Customer
  • Processing Manager records and generate report of all Manager
  • Processing Shipment records and generate report of all Shipment
  • Processing Delivery records and generate report of all Delivery
  • Processing Office records and generate report of all Office
  • Processing Tracking records and generate report of all Tracking
First Level Data flow Diagram(1st Level DFD) of Courier Tracking System

Second Level Data flow Diagram(2nd Level DFD) of Courier Tracking System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Courier. It may require more functionalities of Courier to reach the necessary level of detail about the Courier functioning. First Level DFD (1st Level) of Courier Tracking System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Tracking, Office, Delivery, Shipment, Manager, Customer, Courier.

Low level functionalities of Courier Tracking System

  • Admin logins to the system and manage all the functionalities of Courier Tracking System
  • Admin can add, edit, delete and view the records of Courier, Manager, Delivery, Tracking
  • Admin can manage all the details of Customer, Shipment, Office
  • Admin can also generate reports of Courier, Customer, Manager, Shipment, Delivery, Office
  • Admin can search the details of Customer, Delivery, Office
  • Admin can apply different level of filters on report of Courier, Shipment, Delivery
  • Admin can tracks the detailed information of Customer, Manager, Shipment, , Delivery
Second Level Data flow Diagram(2nd Level DFD) of Courier Tracking System

Courier Tracking System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Courier Tracking System Entity. The entity-relationship diagram of Courier Tracking 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 Tracking System functionalities. The main entities of the Courier Tracking System are Courier, Customer, Office, Manager, Shipment and Delivery.

Courier Tracking 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 Tracking 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 Tracking System tables for fast query execution.
Courier Tracking System ER Diagram

Courier Tracking System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Courier Tracking System which shows the interaction between the objects of Delivery, Shipment, Office, Courier, Tracking. The instance of class objects involved in this UML Sequence Diagram of Courier Tracking System are as follows:

  • Delivery Object
  • Shipment Object
  • Office Object
  • Courier Object
  • Tracking Object

This is the UML sequence diagram of Courier Tracking System which shows the interaction between the objects of Delivery, Shipment, Office, Courier, Tracking. The instance of class objects involved in this UML Sequence Diagram of Courier Tracking System are as follows:

  • Delivery Object
  • Shipment Object
  • Office Object
  • Courier Object
  • Tracking Object

Courier Tracking 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 Courier Tracking System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Courier Tracking System. The main actors of Courier Tracking System in this Use Case Diagram are: Super Admin, System User, Customer, Delivery Boy, who perform the different type of use cases such as Manage Courier, Manage Customer, Manage Office, Manage Manager, Manage Shipment, Manage Delivery, Manage Tracking, Manage Users and Full Courier Tracking System Operations. Major elements of the UML use case diagram of Courier Tracking System are shown on the picture below.

The relationships between and among the actors and the use cases of Courier Tracking System:

  • Super Admin Entity : Use cases of Super Admin are Manage Courier, Manage Customer, Manage Office, Manage Manager, Manage Shipment, Manage Delivery, Manage Tracking, Manage Users and Full Courier Tracking System Operations
  • System User Entity : Use cases of System User are Manage Courier, Manage Customer, Manage Office, Manage Manager, Manage Shipment, Manage Delivery, Manage Tracking
  • Customer Entity : Use cases of Customer are Check Courier Status, Find Courier Offices, Track Courier
  • Delivery Boy Entity : Use cases of Delivery Boy are Check Couriers, Check Delivery Address, Check Customers

Use Case Diagram of Courier Tracking System :

Courier Tracking System Use Case Diagram

Project Category