Final report Cargo Booking Software PDF

Preview

Summary

asd...

Description

Cargo Booking Software By Habiba Muneer CIIT/SP16-MCS-015/CVC & Mahad Ali CIIT/SP16-MCS-084/CVC

Submitted to the Department of Computer Science in Partial fulfillment of the requirements of the degree of MASTER OF COMPUTER SCIENCE Project Supervisor Kanwal Saeed COMSATS Institute of Information Technology, Virtual Campus, Islamabad Fall, 2018

In the name of ALLAH the most Beneficent and Merciful

II

DEDICATION

Every challenging work needs self-efforts as well as guidance of elders especially those who were very close to our heart. Our humble effort, we dedicate to our sweet and loving Fathers and Mothers, Whose affection, love, encouragement and prays of day and night make us able to get such success and honor. We are also thankful to our respected Supervisor who helped me in this final project.

III

ACKNOWLEDGEMENTS Thanks to Almighty “ALLAH” (The Merciful) and to the Holy Prophet “MUHAMMAD” (Peace be upon him) who is source of guidance for the whole humanity. It is pleasure to acknowledge the help of many people without whom this manuscript could never been completed. First of all we would express our heartiest gratitude to our Supervisors Ms Kanwal Saeed Lecturer, Department of Computer Science, CIIT-Virtual Campus, Islamabad, for their guidance, keen interest, best cooperation and constructive criticism during the study period. Words do not come easy for us to mention the feelings of humble obligation towards our dear parents, brothers & sisters who have been model of human values for us, who always raised their hands for our success. May Allah Almighty bless our parents and family members with well wishes, good health and prosperous long lives and be source of prayers for us.

Habiba Muneer

IV

DECLARATION

We hereby declare that this software, neither whole nor as a part has been copied out from any source. It is further declared that we have developed this software and accompanied report entirely on the basis of our personal efforts. If any part of this project has proven to be copied out from any source or found to be reproduction of some other, we will stand by the consequences. No portion of the work presented has been submitted of any application for any other degree or qualification of this or any other university or institute of learning.

Signature

Habiba MuneerJ

V

CERTIFICATE OF APPROVAL

It is to certify that the final year project of MCS “Cargo Booking Software” is developed by “Habiba Muneer(SP16MCS015)” and under the Supervision of “Kanwal Saeed” and that in her opinion; it is fully adequate, in scope and quality of the degree of Master in Computer Sciences.

---------------------------------------Supervisor

---------------------------------------Project Management Committee

---------------------------------------Head of Department (Department of Computer Science)

VI

ABSTRACT Cargo Booking Software(CBS) is an online web application. Cargo booking software will manage the goods of Supplier (Admin) in the warehouse. This software will have Supplier (Admin) Login and Warehouse Login for different Warehouses. This product will allow the supplier to keep an eye on the goods that he has in Warehouses. The Warehouse Login will allow warehouse to accept goods, check condition of goods if its damaged then system will reorder the same good. And it will create a gate pass for the cargo. It calculate weight and others things of cargo, and will make entry of it. The admin has overall rights over the system and can moderate the process. .

VII

Table of Contents ABSTRACT

VII

LIST OF FIGURES

XI

LIST OF TABLES

XII

LIST OF ACRONYMS

XIII

CHAPTER 1: INTRODUCTION………………………………………………………………….1 1.1

1.2

1.3

Motivation and Objectives……………………………………………...1 1.1.1

Motivation …………………………………………………………………….1

1.1.2

Objective …………………………………………………………………...…1

AIM....................................................................................................... 1 1.2.1

Basic Idea............................................................................................................. 1

1.2.2

Information Goal.................................................................................................. 1

Methodology Introduction ..................................................................... 2 1.3.1

System Planning…….…………………………………..…………………… 2

1.3.2

Development Analysis….….……………………….…..…………………… 2

1.3.3

Requirement Analysis ……………………….……………………………… 2

1.3.4

Functional Requirements…………………….……………………………… 2

1.3.5

Non Functional Requirements…………………………………..….………. 3

1.3.6

Data Analysis………………….………………………………………………3

1.3.7

System Analysis ………………………………………………………………4

1.3.8

System Design …………………………………………………………….….4

1.3.9

Programming ……………………………………………………………….…4

1.4

Applications of Research ....................................................................... 4

1.5

Scope and Limitations ........................................................................... 5 1.5.1

Scope .............................................................................. ...........................…...5

1.5.2

Limitations …………………………………………………………………….5

1.6

Project Outline....................................................................................... 5

1.7

Summary ............................................................................................... 6

CHAPTER 2: RELATED WORK/LITERATURE REVIEW………………………..7 2.1

Background ........................................................................................... 7 VIII

2.2

Related Work......................................................................................... 8

2.3

Summary ............................................................................................... 8

CHAPTER 3: DESIGN AND METHODOLOGY………………………………………..9 3.1

Introduction ........................................................................................... 9

3.2

System Model........................................................................................ 9

3.3

Implementation Methods ....................................................................... 9

3.4

Techniques .......................................................................................... 10 3.4.1 Assumptions …………………………………………………………………10

3.5

Limitations of Technique ..................................................................... 10

3.6

Provided Resources ............................................................................. 11

3.7

Programming Language....................................................................... 11 3.7.1 MYSQL….……………………………………………………….…………..11 3.7.2 HTML ………………………………………………………………………..11

3.8

Data Format ......................................................................................... 12 3.8.1

ERD.................................................................................................................... 12

3.8.2

DFD.................................................................................................................... 13

3.8.3

Flow Diagrams ................................................................................................... 14

3.9

The Environment to be monitored ....................................................... 16

3.10

Summary ............................................................................................. 16

CHAPTER 4: IMPLEMENTATION………………………………………….…………...…..17 4.1

Details of Implementation ................................................................... 17 4.1.1

Choice of Tools.................................................................................................. 18

4.1.2

Programming Languages …………………………………………………….18

4.1.3

Hardware …………………………………………………………………….18

4.1.4

Software ……………………………………………………………………..18

4.2

Complete Model of the System............................................................ 18

4.3

Use Cases…………………………………………………………………………….19 4.3.1

Application Details …………………………………………………………..20

4.4

Sequence Diagrams ................................................................................ 20

4.5

Summary ............................................................................................. 22 IX

CHAPTER 5: RESULTS……………………………………………………………...…………23 5.1

Results ................................................................................................. 23

5.2 Test Cases………………………………………………………………………………...23 5.2.1 Test Cases 01…………………………………………………………………………..23 5.2.2 Test case 02……………………………………………………………………………24 5.2.1 Test Cases 03…………………………………………………………………………..25 5.2.2 Test case 04……………………………………………………………………………26 5.2.1 Test Cases 05…………………………………………………………………………..27 5.2.2 Test case 06……………………………………………………………………………28 5.2.1 Test Cases 07…………………………………………………………………………..29 5.2.2 Test case 08……………………………………………………………………………30

5.3

Summary ............................................................................................. 30

CHAPTER 6: CONCLUSIONS AND FUTURE WORK………………...………….31 6.1

6.2

Conclusions ......................................................................................... 31 6.1.1

Initial Goals and Objectives ............................................................................... 31

6.1.2

Obtained Goal I.................................................................................................. 31

6.1.3

Obtained Goal II ................................................................................................ 31

6.1.4

Obtained Goal III ............................................................................................... 31

6.1.5

Implemented Functionality…………………………………………………...31

6.1.6

Requirement Implemented…………………………………………………...32

Future Work ........................................................................................ 32

References....................................................................................................... 33 Appendix 1 ...................................................................................................... 36 Appendix 2...................................................................................................................... 36

X

List of Figures List of figures should be arranged in the following manner: Figure number according to the chapter followed by title of figure and page number on which the figure is present. Figure 2.1 Data Flow ...................................................................................................07 Figure 3.1 Incremental Model .......................................................................................11 Figure3.2 ER Diagram ..................................................................................................12 Figure3.3 DFA Diagram ...............................................................................................13 Figure3.4 FLOW Diagram ...........................................................................................14 Figure3.5 FLOW Diagram ..........................................................................................15 Figure 4.1 Use Case Diagram ....................................................................................19 Figure4.2 Sequence Diagram ....................................................................................20 Figure4.3Sequence Diagram ....................................................................................21 Figure4.4Sequence Diagram………………………………………………………………21 Figure5.1Results…………………………………………………………...……….23 Figure5.2 Results .....................................................................................................24 Figure5.3 Results .....................................................................................................25 Figure5.4 Results ....................................................................................................26 Figure5.5 Results ....................................................................................................27 Figure5.6 Results ....................................................................................................28 Figure5.7 Results ...................................................................................................29 Figure5.8 Results ...................................................................................................30

XI

List of Tables 5.1 Add Warehouse… … … … … … … . .……………………………………25 5.2 Cargo Order ………. .…………………………..…………………………26 5.3 Shift Order …..……………………………………………………………27 5.4 Track Order………………… ………………….…………………………28 5.5 Dispatch Order …………………………………...………………………29 5.6 Accept order ... ……………………………………………………………30 5.7 Damage Goods……………………………………………………………31 5.8 Gate Pass……………………..……………………………………………32

XII

List of Acronyms CBS

Cargo Booking Software

ERD

Entity Relationship Diagram

DFD

Data Flow Diagram

XIII

Chapter 1: Introduction 1.1

Motivation and Objectives

Motivations & objectives of the project are detailed briefly as below;

1.1.1 Motivation: Nowadays, system of the transportation uses the manual system where needs to fill all records in a file from the system users to the technical writers. This work is handled by staff to fill all the transport reservation form with handwriting. This will give difficult to find file when the same customer come to book transport again. Cargo Booking Software (CBS) is a system to effectively manage information about Cargo order and damage Goods easily. It also manages the transportation system for other communities such as Shift Order , Reorder , Track Cargo and Dispatch Order etc. Customer also can see types of transport that can be booked with faster and make the choice of the transport. Customer does not need to register many times because the profile customer has been saved into database. This systems focus as a reservation form and latest information about the transport availability.

1.1.2 Objectives: The objective of this study is to design and develop an implementable system to achieve among others the following:  To automate all activities of cargo tracking in courier management  Designing a system to eliminate the current manual system of filing, file retrieval problem, and file processing and delivery of progress details to clients.  Records cargo events from source to destination.  To determine the extent to which an online cargo tracking system will help both management and clients.

1.2

AIM 1.2.1 Basic Idea Basic idea for this System is to manage the Cargo Order . This system will help the Transport Goods .

1.2.2 Information Goal The main information goal is to design and develop a web application which facilitates the Supervisor to manage their Cargo Order.

In this way, Supervisor can

Accept order, Dispatch order and create Gate Pass. The application has a simple and intuitive Supervisor interface and work flows. 1

1.3

Methodology Introduction

In this part, we shall introduce the methods for the implementation of the application.

1.3.1 System Planning After selecting the Cargo Booking Software as a final project, we keep on discussion about its origin. We made a planning as system planning, in which we briefly discussed the matter that contains project aims, objectives, scope, Requirements etc.

1.3.2 Development Environment First, we select the development environment and its tools after a huge discussion. We get the different tools for the programming of our project, finally we decided that the project will be developed using Dream viewer and Xampp. It will use PHP and MYSQL. .

1.3.3 Requirement Analysis We discussed the Requirements. Requirements are of two Types.

1.3.4 Functional Requirements             

There must be login process for administrator and authorized users to avoid unauthorized access to the software. The system shall allow to create warehouse. The warehouse has different Cities. The System shall allow admin to update the current progress of the consignments. The System shall verify the information entered by the customer during log in. The System shall allow the Shift Cargo from one warehouse to another. The System shall allow Track Cargo (Cargo is in which Warehouse). The system shall allow admin to display the current tracking information about the order. The system shall allow user to enter the order information for tracking. It shall ask the user to enter the consignment details like shipment number or reference number The system shall allow View Order. The system shall allow to check the goods if damages. The system shall allow Reorder if the status is Damage. The system shall allow the dispatch cargo and create gate pass.

2

1.3.5 Non Functional Requirements In software system engineering, a software requirement that describes not what

the software will do, but how the software will do it, for example, software performance requirements, software external interface requirements, software design constraints, and software quality attributes. Nonfunctional Requirements are difficult to test; therefore, they are usually evaluated subjectively.

Some Non-Functional Requirements are listed below. Non Functional Requirements are as under: 1. Performance 2. Usability 3. Employee friendly 4. Maintainability 5. Flexibility

1.3.6 Data analysis The data is analyzed during the said project development. This data has Supervisor s record and Supervisor records and gate pass record.

3

1.3.7 System Analysis The existing System Cargo Booing Software has been thoroughly studied & surveyed

the

different

business

organizations.

We

finalized

the functional

Requirements.

1.3.8 System Design We have to develop an Cargo Booking Software. It will have good UI so that company and Supervisor may easily interact with each other.

1.3.9 Programming The project has developed in Dream viewer and PHP has used as a Language.

1.4

Applications of Research

The useful areas & applications, which this research includes, are as following;             

1.5

There must be login process for administrator and authorized ...