THE DESIGN AND IMPLEMENTATION OF A DISPATCH/LOGISTICS (DELIVERY) WEBSITE

0
718

ABSTRACT

This Project research depicts a Logistics delivery company application. This application consists of features that can help Individuals across the capital to be able to deliver their goods and products from one point to the other in a very hassle-free manner. The application comes with features like the registration feature, the requested feature, etc. To enable users, access the application fully. Information and data gathering during the development of the system was done through interviews and review of the appropriate literature. This project also consists of the activity diagrams, the application architecture, uses cases, and entity-relationship diagrams. The technologies used in the execution of the objectives of this research are Visual studio as the IDE of choice and MySQL for the database. When compelling appraisal and system verification, the writer sees that the application can be used productively, effectively, and efficiently.

TABLE OF CONTENTS

ABSTRACT……………………………………………………………………………………………………… I

LIST OF TABLES…………………………………………………………………………………………. IX

LIST OF FIGURES…………………………………………………………………………………………. X

LIST OF ABBREVIATIONS…………………………………………………………………………. XI

CHAPTER 1: INTRODUCTION……………………………………………………………………… 1

CHAPTER 2: LITERATURE REVIEW…………………………………………………………. 5

  1. INTRODUCTION…………………………………………………………………………………………………………………. 5
    1. HISTORICAL OVERVIEW………………………………………………………………………………………………… 5
    2. RELATED WORK………………………………………………………………………………………………………………. 7
    3. SUMMARY………………………………………………………………………………………………………………………….. 9

CHAPTER 3: REQUIREMENTS, ANALYSIS, AND DESIGN………………………. 10

CHAPTER 4:  IMPLEMENTATION AND TESTING……………………………………. 27

CHAPTER 5:  DISCUSSION, CONCLUSION, AND RECOMMENDATIONS. 48

REFERENCES………………………………………………………………………………………………. 50

APPENDICES………………………………………………………………………………………………… 51

LIST OF TABLES

TABLE 1.1:    PROJECT RISK ASSESSMENT……………………………………………………………. 3

TABLE 3.1: ADVANTAGES AND DISADVANTAGES OF AGILE FRAMEWORK………………………. 11

TABLE 3.2:    ADVANTAGES AND DISADVANTAGES OF WATERFALL METHODOLOGY………. 13

TABLE 3.3: FUNCTIONAL REQUIREMENT SPECIFICATIONS………………………………………………………… 14

TABLE 3.4:    NON-FUNCTIONAL REQUIREMENT SPECIFICATIONS………………………………………………. 15

Table 3.5:     DATA DICTIONARY FOR THE ADMIN TABLE……………………………….. 18

Table 3.5:     DATA DICTIONARY FOR THE BIKE TABLE…………………………………… 19

Table 3.5:     DATA DICTIONARY FOR THE BOOKING TABLE……………………………. 19

Table 3.5:     DATA DICTIONARY FOR THE BRAND TABLE……………………………….. 19

Table 3.5:     DATA DICTIONARY FOR THE CUSTOMER TABLE…………………………. 19

Table 3.5:     DATA DICTIONARY FOR THE MODEL TABLE……………………………….. 20

Table 3.5:     DATA DICTIONARY FOR THE RIDER TABLE………………………………… 20

TABLE 4.1 TEST PLAN……………………………………………………………………………………… 31

TABLE 4.2 :   TEST SUITE FOR TEST PLAN 01………………………………………………………. 32

TABLE 4.3 :   TEST SUITE FOR TEST PLAN 02………………………………………………………. 34

TABLE 4.4 :   TEST SUITE FOR TEST PLAN 03………………………………………………………. 35

TABLE 4.5 :   TEST SUITE FOR TEST PLAN 04………………………………………………………. 35

TABLE 4.6 :   TEST SUITE FOR TEST PLAN 05………………………………………………………. 36

TABLE 4.7 :   TEST SUITE FOR TEST PLAN 06………………………………………………………. 37

TABLE 4.8 :   TEST SUITE FOR TEST PLAN 07………………………………………………………. 38

TABLE 4.9 :   TEST SUITE FOR TEST PLAN 08………………………………………………………. 39

TABLE 4.10 :   TEST SUITE FOR TEST PLAN 09…………………………………………………….. 40

TABLE 4.11:   TEST SUITE FOR TEST PLAN 10…………………………………………………….. 41

TABLE 4.12:   TEST SUITE FOR TEST PLAN 11…………………………………………………….. 42

TABLE 4.13:   TEST SUMMARY REPORT……………………………………………………………… 44

TABLE 4.14  TEST TRACEABILITY MATRIX……………………………………………………….. 45

TABLE 4.15 ERROR(S) ENCOUNTERED……………………………………………………………………………………………… 47

TABLE 5:    APPENDIX D…………………………………………………………………………………… 56

LIST OF FIGURES

FIGURE 2.1   TIMA LOGISTICS…………………………………………………………………………………………………………….. 7

FIGURE 2.2   KWIK LOGISTICS…………………………………………………………………………….. 8

FIGURE 2.3   GOKADA LOGISTICS……………………………………………………………………….. 8

FIGURE 2.4   DELHIVERY LOGISTICS……………………………………………………………………… 9

FIGURE 3.1   AGILE MODEL……………………………………………………………………………….. 11

FIGURE 3.2   WATERFALL MODEL DIAGRAM…………………………………………………………………………………. 12

FIGURE 3.3   APPLICATION ARCHITECTURE FOR HOMEPAGE…………………………… 17

FIGURE 3.4   APPLICATION ARCHITECTURE FOR ADMIN PAGE…………………………. 17

FIGURE 3.5   USE CASE DIAGRAM……………………………………………………………………………………………………. 18

FIGURE 3.6   ACTIVITY DIAGRAM FOR ADMIN……………………………………………………….. 21

FIGURE 3.7   ACTIVITY DIAGRAM FOR USER……………………………………………………………………………….. 22

FIGURE 3.8 DATA FLOW DIAGRAM……………………………………………………………………………………………… 22

FIGURE 3.9   ENTITY RELATIONSHIP DIAGRAM…………………………………………………………………………….. 23

FIGURE 3.10: HOME PAGE (DEFAULT PAGE)…………………………………………………………….. 24

FIGURE 3.11: REGISTRATION MODEL FOR A USER…………………………………………………………………………. 24

FIGURE 3.12: USER LOGIN PAGE………………………………………………………………………………………………………. 25

FIGURE 3.13: USER PROFILE PAGE…………………………………………………………………………………………………… 25

FIGURE 3.14: ADMIN ADD BIKE……………………………………………………………………………………………………. 26

FIGURE 3.15: ADMIN VIEW BIKES………………………………………………………………………………………………… 26

FIGURE 4.1: ADD BIKE CODE…………………………………………………………………………………………………………….. 27

FIGURE 4.2: ADD RIDER CODE………………………………………………………………………………………………………….. 28

FIGURE 4.3: ADD USER CODE……………………………………………………………………………………………………………. 28

FIGURE 4.4: HOME PAGE CODE……………………………………………………………………………………………………… 29

FIGURE 4.5: REGISTER CODE………………………………………………………………………………………………………………. 29

FIGURE 4.6: HOME PAGE (DEFAULT PAGE)………………………………………………………………. 33

FIGURE 4.7: REGISTRATION MODEL FOR A USER…………………………………………………………………………… 33

FIGURE 4.8: REGISTRATION MODEL FOR A USER DURING REGISTRATION……………………………….. 33

FIGURE 4.9 USER LOGIN PAGE………………………………………………………………………………………………………….. 33

FIGURE 4.10: HOME PAGE AFTER LOGIN………………………………………………………………………………………… 34

FIGURE 4.11: USER PROFILE PAGE…………………………………………………………………………………………………… 34

FIGURE 4.12: ADMIN VIEW BIKES PAGE……………………………………………………………… 35

FIGURE 4.13: ADMIN LOGIN PAGE…………………………………………………………………….. 36

FIGURE 4.14: ADMIN ADD BIKE PAGE…………………………………………………………………. 37

FIGURE 4.15: ADMIN VIEW BIKES PAGE……………………………………………………………… 37

FIGURE 4.16: ADMIN VIEW PAGE………………………………………………………………………. 38

FIGURE 4.17: ADMIN VIEW PENDING BIKES PAGE………………………………………………. 39

FIGURE 4.18: USER LOGIN PAGE……………………………………………………………………….. 40

FIGURE 4.19: USER’S PROFILE DELIVERABLES PAGE…………………………………………………………………….. 40

FIGURE 4.20: USER PROFILE PAGE…………………………………………………………………………………………………… 41

FIGURE 4.21: USER’S PROFILE DELIVERABLES VIEW PAGE………………………………………………………….. 41

FIGURE 4.22: USER’S RATING PAGE…………………………………………………………………………………………………. 42

FIGURE 4.23: ADMIN LOGIN PAGE………………………………………………………………………. 43

FIGURE 4.24: ADMIN VIEW PENDING BIKES PAGE………………………………………………. 43

FIGURE 4.25: ADMIN ASSIGN RIDER PAGE……………………………………………………………. 43

FIGURE 4.26: ADMIN VIEW ACCEPTED REQUESTS THAT HAVE BEEN ASSIGNED RIDER’S PAGE 44

FIGURE 4.27: PIE CHART……………………………………………………………………………………………………………………. 47

INTERVIEW 1……………………………………………………………………………………………………… 52

INTERVIEW 2……………………………………………………………………………………………………… 53

INTERVIEW 3……………………………………………………………………………………………………… 53

INTERVIEW 4……………………………………………………………………………………………………… 53

FIGURE C.1: SOURCE CODE……………………………………………………………………………………………………………….. 54

FIGURE C.2: SOURCE CODE……………………………………………………………………………………………………………….. 54

FIGURE C.3: SOURCE CODE……………………………………………………………………………………………………………….. 54

FIGURE C.4: SOURCE CODE……………………………………………………………………………………………………………….. 55

FIGURE C.5: SOURCE CODE……………………………………………………………………………………………………………….. 55

LIST OF ABBREVIATIONS

CPU – Central Processing Unit ERD – Entity Relationship Diagram IT – Information Technology

MB – Megabyte GB – Gigabyte TB – Terabyte

HOD – Head of Department

IDE – Integrated Development Environment HP – Hewlett Packard

RAM – Random Access Memory FR – Functional Requirement

NFR – Non-Functional Requirements GDS –Go Delivery Services –

API – Application Programming Interface CASE – Computer Aided Systems Engineering UML – Unified Modelling Language

DFD – Data Flow Diagram CFD – Control Flow Diagram

CHAPTER 1: INTRODUCTION

  • Overview

Dispatch or logistics in Nigeria has found its way in becoming a basic part of everyone’s day to day activities. It may be transporting goods and products from one point to another like school, home, market, office, or any random place of visit. Society has gradually evolved into a spot or site where there is now a substantial measure of technological evolution or better still development where everything which is manually and physically done is now virtual or computerized.

                         Background and Motivation

Dispatch or Delivery website is a website that will be used for GO logistics to rent out motorcycle riders to individuals or a professional body. This website contains information to make their services accessible to people in general through the website application and to keep track of their services. In essence, it is described as the need for easier access and a stress-free logistics service for individuals especially for saving cost, time, while also being productive.

Furthermore, extensive insight will be given on the website app, to be built towards improving, enhancing, and putting it in the system. Integrating the GO logistics service with an online platform will make it more competitive, accessible, and reliable for cost.

As this is a current system in place for renting the GO logistics motorcycle rider, in society now as the world has tilted to technological advancement the system will be more effective and computerized. GO logistics is a company that deals with monitoring motorcycles of their clients, providing services like anti-theft systems, bike management for delivery, dispatch services as well as maximum security will be implemented in the system, as security is a very essential part of any business, and again making it will be a good avenue for more profit from the revenue point of view. The main objective of the project is to develop a website app, that will help or assist manage motorcycle renting or ordering or request and will help in promoting the logistics services of the company through the accessibility, availability, and flexibility of the website application online.

In the current system, A client has to search for the company’s Instagram handle, then get the contact of the company, which then the client requests for a motorcycle rider. The client is then asked to send their details via WhatsApp or SMS, which entails the Pick-up address, drop-off address, and the phone number of the sender and recipient phone numbers of the

individual who will be receiving the product or goods, this consumes time as they will need to come online and cross-check the details before checking if there is a rider available or not which causes late deliveries all the time, another troubling issue is having novice riders, that is a rider which isn’t familiar with that particular vicinity which would result in the rider having to call the client all the time to ask them for navigations or descriptions of the address.

A better solution is to have a system website application in a place where all the riders are already registered making it possible for a motorcycle/bike rider to be available with just a few ticks and clicks.

DOWNLOAD PROJECT

RELATED ARTICLESMORE FROM AUTHOR