Dr.

BABASAHEB AMBEDKAR MARATHWADA

UNIVERSITY, AURANGABAD.

Project Report

On
“Logistic Services”
Developed by
Nimish Kulkarni(3640)
Mahesh Narke(3645)
Utkarsh Phirke(3650)

Guided by
Ms. Ruhi Oberoi

Department of.
(Computer Science & Engineering)
Jawaharlal Nehru Engineering College
2009-10

Mahatma Gandhi Mission’s

JAWAHARLAL NEHRU ENGINEERING COLLEGE,
 N-6, CIDCO, AURANGABAD.

CERTIFICATE
This is to certify that the PROJECT in title “Logistic Services” successfully
completed by Utkarsh Phirke, Mahesh Narke, Nimish Kulkarni. As per the
requirement of the Dr. Babasaheb Ambedkar Marathwada University
Aurangabad in partial fulfillment of Computer Science & Engineering in
Third Year for the academic year 2009-2010.

Guided by H.O.D.
 ACKNOWLEDGMENT

I wish to express my deep sense of gratitude to my guide Ms. Ruhi

Oberoi for his valuable guidance & kind co-operation throughout the period
of work undertook which has been instrumental for the success of our
project work.

I also take this opportunity thanks our Prof. Deepa Deshpande whose
timely help has lead to the successful completion of this project. I am also
thankful to all staff members of C.S.E Dept. who supported us directly or
indirectly and has contributed intellectually & materially in works & deeds
for the preparation of my project.

Thanking you!
 LOGISTIC SERVICES

INDEX
Requirement Gathering
-Introduction
-Purpose
-Scope
-Customer requirement
-Supporting documents
Requirement Analysis
-Problem statement
-Background information
-Environment and technology
-Functional requirement
-Normal requirement
-Expected requirement
-Excited requirement
Time Scheduling
-Project scheduling
-Project work breakdown
-Cracking
-Time line chart
Project Estimation
-LOC based Estimation
Design
-Structural analysis
-Design ER diagram
-DFD diagram
-Object oriented analysis and design
-UML diagram
Coding
-Code for new shipment
-Code for connection
-Code for track status
Testing
 -Test cases
- Black box testing
Review
-Review
-Checklist

Limitation & Conclusion

1. REQUIREMENT GATHERING (Domain Analysis)

A courier is a person or company employed to deliver messages, packages
and mail. Within this definitive context, couriers and courier services can come in
many different types and styles. In past times, before there were vehicles, couriers
were usually just individual messengers, who traveled from one place to another
to deliver news, documents, or products.

Motivation
Couriers are distinguished from ordinary mail services by features such as
speed, security, tracking, signature, specialization and individualization of
services, and committed delivery times, which are optional for most everyday
mail services.
The Courier industry in the World is a $59 billion industry, with 86% of
the business shared by only four companies, including DHL, FedEx and UPS.

1.1 Introduction:-
1) Purpose: In Day to day life we need to send shipments to relatives or
for business purpose. This need is conceptualized to develop software
based on logistics services.
Logistics is the management of the flow of goods,
Information and other resources, including energy and people, between
the point of origin and the point of consumption in order to meet the
requirements of consumers.

2) Definitions, Acronyms and Abbreviations:

AWB (Air Waybill)
The shipping document used for the transportation of air
freight: includes conditions, limitations of liability, shipping
instructions, description of commodity, and applicable
transportation charges. It is generally similar to a straight non-
negotiable bill of lading and is used for similar purposes.
Delivery Confirmation
 A special service that provides the date of delivery or attempted
delivery for Priority Mail and Standard Mail parcels, Bound Printed
Matter and Library Mail.
Direct Mail
A form of advertising often employed by businesses to reach
targeted groups of potential customers by mail.
Prepaid
Payments made in advance of service being provided.

3) References:
FedEx Express
https://www.fedex.com/in
DHL Express http://www.dhl.co.in/publish/in/en.high.html
Blue Dart Express
http://www.bluedart.com/

4) Overview:
This document describes various system requirements, interfaces,
features and functionalities. Customer expects the Air Waybill to be in
printed format and also must be able to track the shipment whenever
necessary.
Courier services consist of no. of departments such as Marketing,
Finance, Administration, Customer Care, Dispatch, Stock management.
5) Supporting document:-
1) Invoice Xerox
2) Shipment Air Waybill
3) Notes
4) Confirmation Letter

1.2 Customer Requirements:-

1.2.1 Tracking System: - It is important for the customer to know the
current status of the shipment. It provides the current status along with
date and time. On producing the AWB no.

1.2.2 Billing System: - Billing system should provide printable bill for
shipment invoice. The invoice should mention:
1) Shipper: The one who sends the shipments with complete
details like contact name, address, phone/email-id.
2) Receiver: The one who receive the shipments. Following details
should be mentioned: - Name, Delivery address, phone/email-id.
 3) Description of Contents: It gives contents and quantity. Also
the dimensions/weight (chargeable), approx. cost of the contents.
4) Cost of Shipment: - The amount charged by the courier
services for the shipment on the basis of dimensions, weight, and the
destination region.

1.2.2 Database: - Database of following things should be maintained.

1) Passwords:
It consists of usernames and passwords of both Administrator and
users.
2) Customers Record:
This database maintains history of customers like no. of shipments
made and its details.
3) Shipments Details:
It consists of complete details of shipments viz. AWB no. , Date,
Consignee name, Destination, Weight, Product, Delivery Address,
Receiver name, Shipper name.
4) Status:
It consists of following fields:
AWB number, Remark (Delivered/Pending), Signed by, Shipment
Delivered (Date & Time)
5) Marketing:
It consists of various zonal records like which advertisements have
been made, Area covered. It maintains information about the
various supporting vendors like finance company, transport, nature
of industries.

2. REQUIREMENT ANALYSIS:-
2.1 Problem Statement:-
To develop software for Logistics Services System to
manage Shipments.
2.2 Scope:-
• This software will generate Air Waybill and Invoice.
• The application will manage the information about shipments
and shippers.
• It will provide signature proof of delivery.
• This application will simplify the task of managing shipments.
• It consists of currency converter which is useful for customer
 • The software will also provide security of the shipment by
means of tracking.
The application’s database is not updated centrally. Guest customers will
not be entertained. New Account should be opened in order to send consignment.

2.3 Background Information:-

Currently they manage their work through means of websites. The
database connected at back end is updated for every single entry delivered and
which is given by customer. At very checkpoint email consisting status of
shipment is sent to customer if required.
After Delivery, email is sent to the shipper confirming the delivery. There
are various departments included in managing courier services.

2.4 Environment & Technology:-

Following are the minimum Hardware and Software requirements:
1) Hardware requirements:-
a) Intel Pentium processor P4 and above
b) 512 MB RAM
c) 200 MB free HDD space
d) Printer
2) Software requirement:-
a) Windows OS such as NT, 2000, XP
b) Printer driver installed
c) Oracle 10G
d) Microsoft Visual Studio 2008

2.5 Functional Requirements:-

The Software provides following functionalities to the users.
Invoice:-
This module provides printable bill of the shipment.
Input: Customer details, shipments details,
Destination Details.
Output: Printed bill with a unique AWB.
 Login:
Administrator:
Input: username, password.
Output: Create, update users,
User:
Input: username, password.
Output: Can check status, View own history only.

Enquiry:
Input: AWB number, user id
Output: Current location, Expected time, Receiver detail (if
delivered)

System inputs
• Customer data (sender).
• Shipment data.
• Offices names.
• Employee data.
System Processes
• Record customer & package
• Provide cost
• Arranging packages
• Receiving package
• Distributing packages
• Enter, search, modify, and remove records in often
processes.
System Outputs
Reports:
• Paid bill.
• Packages lists.
• International packages lists monthly.
• Packages list distributing.
• Delivery Bill.
• Display Result.

2.6 Normal Requirements:-

 Database is maintained for customers, shipments. Billing system is provided to
have printable bills for invoice.
• Paid Bill.
• Arranging packages.
• Provide cost.
• Packages lists.
• International packages lists monthly.
• Packages list distributing.

2.7 Expected Requirements:-

1) Administrator Login:-
Different access permissions to the database should be specified. The
database can be handled in two ways:
a) Modify: Administrator should be able to add, change customer
entries.
b) Display only: Customer should be able to view the data and
he/she should not be able to change data entries.

2) Database Services:-
Status of shipment gets automatically updated in the database according to
sale or purchase.

3) New user prompt:-

When a new user is doing a shipment then application prompts for new
user registration.

2.8 Excited Requirements:-

1) Automatic Backup:-This feature takes automatic backup daily. The
Backup utility helps you create a copy of the information. In the event that
the original data is accidentally erased or overwritten, or becomes
inaccessible; you can use the copy to restore your lost or damaged data.
Due to this exciting feature user is free from task of taking backup every
day.
2) Calculator: To calculate the cost of the shipment.

3) Currency Converter: To convert one currency to

other.
 3. TIME SCHEDULING

Task Scheduled on Actually Expected Actual No. remark

Started completion Completion Persons
Requirement 13/10/09 14/10/09 15/10/09 15/10/09 3 Completed On
Gathering time
Requirement 15/10/09 15/10/09 20/10/09 21/10/09 3 Running late
Analysis
Design 21/10/09 22/10/09 22/10/09 23/10/09 3 Started late
Finished late
Coding 27/10/09 1/11/09 2/11/09 3/11/09 3 Due to
submissions
Reviews & 3/11/09 3/11/09 3/11/09 4/11/09 3 Reviews Given
Checklist by madam
Completion Completed On 4/11/2009 

4. Project Estimation
4.1 LOC based estimation :
Formulae:

1. Expected =( Optimistic + 4(Most likely) + Pessimistic) / 6

2. Cost : Expected * Rs/line

5. DESIGN
Analysis Modeling:
At a technical level, software engineering begins with a series of modeling
tasks that lead to a complete specification of requirement and a comprehensive design
representation for the software to be built. The analysis model, actually a set odf modules,
is the first technical representation of a system.

Data Modeling:
The data model consists of three interrelated pieces of information:
The data object, the attributes that describe the data object, and the relationships that
connect data objects to one another.
Entity Relationship diagram of the project is to be drawn.
Functional Modeling:
Information is transformed as it flows through a computer-based system. The
system accepts in a variety of forms; applies hardware, software, and human elements to
transform it; and produces output in a variety of forms.

Structured analysis and design:

As information moves through software, it is modified by a series of
transformation .a data flow diagram is a graphical representation that depicts information
flow and that are applied as data move from input to output. The basic form of a data
flow diagram, also known as a data flow graph or a bubble sort.

The data flow diagram (DFD) serves two purposes:

(1) To provide an indication of how data are transformed as they move through the
system and to depict the functions (and sub functions) that transform the data flow..
Data flow diagrams (DFDs) reveal relationships among and between the various
components in a program or system. DFDs are an important technique for modeling a
system’s high-level detail by showing how input data is transformed to output results
through a sequence of functional transformations. DFDs consist of four major
components: entities, processes, data stores, and data flows. The symbols used to depict
how these components interact in a system are simple and easy to understand. However,
there are several DFD models to work from, each having its own symbology. DFD syntax
does remain constant by using simple verb and noun constructs.

5.1. ER Diagram:
Entity-Relationship Diagrams (ERDs) are another way of showing information flow for a
process. An ERD shows what data is being used in the process or program, and how the
files are related. The E-R (entity relationship) data model views the real world as a set of
basic objects (entities) and relationships among these objects. It is intended primarily for
the database design
Process by allowing for the specification of an enterprise scheme. This enterprise scheme
represents the overall logical structure of the database. ERDs do not show any program
functions, nor data flow.
5.2 DFD Diagram
5.2.1 Level 0 DFD
 Courier
Packages lists
Customer Customer& distributing
Send Data

Bill paid Customer

Sending
Shipment Courier Office
International
packages list
Offices Manager
names
Copy of DB
Staff

Main
Office

5.2.2 Level 1 DFD

5.3

UML Diagram
5.3.1 Class Diagram

5.3.2Use case Diagram

5.3.3STATE DIAGRAM
5.3.4 Sequence Diagram

5.3.5 Activity Diagram

5.3.5.1 Activity Diagram Customer
5.3.5.2 Activity Diagram Employee

5.3.5.3 Activity Diagram Manager

6. Coding
6.1 Code for shipment
Private Sub Btnsubmit_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Btnsubmit.Click
Trim(txtweight.Text)
Trim(txtRname.Text)
Trim(txtDesti.Text)
Trim(txtRphn.Text)
If txtweight.Text = "" Or txtRname.Text = "" Or txtDesti.Text =
"" Or txtRphn.Text = "" Then
MessageBox.Show("Mandatory fields are not filled", "Invaild
information", MessageBoxButtons.OK, MessageBoxIcon.Warning)
Exit Sub
End If
Dim sdate As String
sdate = cmbDD.SelectedItem + "," + cmbMMM.SelectedItem + "," +
cmbYYYY.SelectedItem
Using connection As New OdbcConnection(connectionString)
connection.Open()
Dim command1 As New OdbcCommand("Insert into SHIPMENT
values(" & txtAWB.Text & ",'" & txtUsername.Text & "','" & sdate & "','"
& txtDesti.Text & "','Pending','" & txtRname.Text & "'," & txtRphn.Text
& "," & txtweight.Text & " , " & txtCost.Text & ")", connection)
Dim returnValue As OdbcDataReader
returnValue = command1.ExecuteReader()
connection.Close()
MessageBox.Show("Ur shipment has been accepeted." & Chr(13)
& " Will be processed soon." & Chr(13) & "Expected delivery is within 4
working days." & Chr(13) & " Any queryes contack manager.", "Sucessful",
MessageBoxButtons.OK, MessageBoxIcon.Information)
End Using
Me.Close()
End Sub

6.2 Code for connection

Using connection As New OdbcConnection(connectionString)
connection.Open()
Dim command1 As New OdbcCommand("Insert into SHIPMENT
values(" & txtAWB.Text & ",'" & txtUsername.Text & "','" & sdate & "','"
& txtDesti.Text & "','Pending','" & txtRname.Text & "'," & txtRphn.Text
& "," & txtweight.Text & " , " & txtCost.Text & ")", connection)
Dim returnValue As OdbcDataReader
returnValue = command1.ExecuteReader()
connection.Close()
End Using

6.3 Code for track Status

Private Sub btnTrack_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles btnTrack.Click
Label2.Show()
Label3.Show()
Label4.Show()
Label5.Show()
Dim connectionString As String
connectionString = "uid=a2z;dsn=A2Z;pwd=123;"
Using connection As New OdbcConnection(connectionString)

connection.Open()
Dim command1 As New OdbcCommand("select USR from TEMP where
no=1", connection)
Dim returnValue1 As OdbcDataReader
returnValue1 = command1.ExecuteReader()
If (returnValue1.Read()) Then
usr = returnValue1(0)
End If

Dim command As New OdbcCommand("select

AWB,SDATE,DESTI,STATUS from SHIPMENT where AWB ='" & TextBox1.Text & "'
AND USERNAME='" & usr & "' ", connection)
Dim returnValue As OdbcDataReader
returnValue = command.ExecuteReader()
If (returnValue.Read()) Then
txtAWB.Text = returnValue(0)
txtDate.Text = returnValue(1)
txtDesti.Text = returnValue(2)
stat = returnValue(3)
If stat = "Pending " Then
txtStatus.ForeColor = Color.Red
ElseIf stat = "Processing " Then
txtStatus.ForeColor = Color.Orange
ElseIf stat = "Delivered " Then
txtStatus.ForeColor = Color.Green
Else
txtStatus.ForeColor = Color.AliceBlue
End If
txtStatus.Text = stat
Else
MessageBox.Show("Incorrect AWB", "Error",
MessageBoxButtons.OK, MessageBoxIcon.Error)
End If
End Using
End Sub

7. Testing
 7.1 Test Case 1:

TEST DESCRIPTION INPUT EXPECTED ACTUAL PASS

CODE DATA OUTPUT OUTPUT /FAIL
1.1 Create account Customer After submit user Next form Pass
information account will created
1.2 Login form User or IF username or Next Form Pass
Employee password is correct
name then go to next form
And
password

1.3 New shipment Shipment Can’t perform Perform shipment even Fail
Validation details Shipment unless if account status is not
account status is activated
activated
1.4 Shipment status AWB Shipment information Shipment information Fail
should displayed is not complete

1.5 Username Username Same username can not Username are not Pass
conflict be repeated repeated

1.6 Confirm Password Password should match Mismatch password is Pass

password in both field not allowed
validation
1.7 Date fill System date Date must be displayed Date is not displayed Fail
validation
1.8 Clear fields Click on All field should be Fields are not cleared Fail
cancel filled
button
1.9 Validation on I/P can be If not gives error Can write character Fail
phone number 10 digit no. message
1.10 Validation on Enter Password must be Less than 4 character Fail
password password greater than 4 are also working
character

7.2 Test Case 2:-

TEST DESCRIPTION INPUT EXPECTED ACTUAL PASS
CODE DATA OUTPUT OUTPUT /FAIL
1.1 New Shipment Shipment Can’t perform Perform shipment even Pass
Validation details Shipment unless if account status is not
account status is activated
activated
1.2 Shipment status AWB Shipment Shipment information is Pass
information not complete
should displayed

1.3 Date fill validation System date Date must be Date is not displayed Pass
displayed

1.4 Clear field Click on button All field must be All field gets clear Pass
clear

1.5 Validation on phone Input data must If not gives error It must be number and Pass
number be greater than message 10 digit only
given range

1.6 Validation on Enter Password must If not gives message Pass

password password be greater than
4 character

8. Review:
 8.1. After the design phase we were suggested to clear our whole idea of design.
The ER diagram and the UML diagrams were specifying different stories.
8.2 After first demo of coding the reviews were to implement validations in the
forms for various fields like phone number, date, and password.
8.3 By buddy check we found some of the loop holes from the project like not to
allow user to submit blank form, repetition of username should be avoided.

9. Limitations & Conclusion

9.1 Limitation
Couriers are usually more expensive than usual mail services, and their use
is typically restricted to packages where one or more of these features are considered
important enough to warrant the cost.
In the logistic services management does not provide database backup.
9.1 Conclusion
Hence we have developed software for logistic services.
That will help manage the shipment in the company

Screen Shots:-
1. Login Form

2. New Account

3. Customer
4. New Shipment
5. Change Password:-

6. Update Status:-