PROJECT REPORT

COURIER SERVICE MANAGEMENT SYSTEM

by
K. NIRMAL
( Reg.No:2022J0687 )

Guided by

Mr.D. JAYANTH, M.Sc., M.Phil., MBA.,

Assistant Professor And Head of the Department of Information technology,
Bharathidasan College of Arts & Science, Erode.

DEPARTMENT OF INFORMATION TECHNOLOGY

BHARATHIDASAN COLLEGE OF ARTS & SCIENCE
(Affiliated to Bharathiar University, Coimbatore)
ERODE - 638 116.

May– 2022
 COURIER SERVICE MANAGEMENT SYSTEM
Bonafide work done by

K. NIRMAL
(Reg No.:2022J0687)

Project submitted in partial fulfillment of the requirements for the award of

Bachelor of Science (Information technology) of Bharathidasan College of Arts and
Science affiliated to Bharathiar University, Coimbatore-46.

SIGNATURE OF THE GUIDE SIGNATURE OF THE HOD

PRINCIPAL

Submitted for the Viva-Voce examination held on: __________

INTERNAL EXAMINER EXTERNAL EXAMINER

 DECLARATION

I hereby declare that project work entitled “COURIER SERVICE MANAGEMENT

SYSTEM” done at Bharathidasan College of Arts & Science, Erode submitted to
Bharathiar University in partial fulfillment of requirements for the award of Bachelor of
Information technology as a record of work done by me under the guidance of
Mr.D.JAYAJAYANTH, M.Sc., M.Phil., MBA., Assistant Professor of Information
technology, Bharathidasan College of Arts & Science, Erode - 638116.

Place: Erode
Date:
Signature of the
Candidate
K. NIRMAL
(Reg.No.:2022J0687)
 ACKNOWLEDGEMENT

I express my profound gratitude to our Chairman Mr.N.K.K.PERIYASAMY,

and our beloved Treasurer Mr.V.R.MURUGAN for allowing me to undertake this
project work. I express my sincere thanks to Dr.R.Kamesh, Principal Bharathidasan
College of Arts & Science, Erode for having given me this fine opportunity to do the
project. I wish to express my grateful thanks to Mr.D.JAYANTH M.Sc. M.Phil .MBA.,
Head, Department Information technology, Bharathidasan College of Arts & Science,
who has provided all the facilities to complete my project successfully. At outset hereby I
express my heartfelt thanks and deep sense of gratitude to my Mrs. W.I.PREETHI
SHEELIA M.Sc. M.Phil., Assistant Professor of Information technology for his valuable
guidance and useful suggestions throughout the project.

I am extremely happy to thank our Bharathidasan College of Arts & Science

Management. I also thank all the staff members of Information technology Department
who extended their help to complete my project work successfully. I am also thankful to
the computer lab programmers for their kind co-operation. I also thank our Librarian for
the support in completing my project work.

Last but not the least, I proudly thank and express my gratefulness to all my
friends for the kind help rendered by them. I extend my heartfelt gratitude to my parents.

K. NIRMAL
 SYNOPSIS
The project entitled “COURIER SERVICE MANAGEMENT SYSTEM”
which maintains all the information about the courier transaction.
The goal of this project is to minimize the work done by staff in courier
maintenance and transaction details. Since the existing system is a manual one lot of
paper work and manpower are needed with the existing system.
A large number of ledgers, papers, records etc. have to be kept for future use and
this consumer a large amount of office space. This system easily to maintenance of all the
process and to provide a quick view of all the details according to the transactions of
courier booking and delivery.
Transaction process is simple and error free. But it is impossible in the manual
system. Searching and finding a particular detail of a courier number from a large number
of records needs a large amount of time. Also the data can be lost in future.
The main aim of this project maintains the courier booking details and the
delivery details. The main objective of this project is to create software that helps us to
create a database which contains a supporting type of files to report the accounting
transactions in the organization.
CONTENTS
CHAPTER TITLE PAGE No.
ACKNOWLEDGEMENT 4
SYNOPSIS 6
I INTRODUCTION 7
1.1 ABOUT THE PROJECT 7
1.2 SYSTEM SPECIFICATION 8
1.2.1 HARDWARE CONFIGURATION 8

1.2.2 SOFTWARE SPECIFICATION 8

II SYSTEM STUDY 13
2.1 EXISTING SYSTEM 13
2.1.1 DRAWBACKS OF EXISTING SYSTEM 13

2.2 PROPOSED SYSTEM 14

2.2.1 FEATURES OF PROPOSED SYSTEM 14
III SYSTEM DESIGN AND DEVELOPMENT 15

3.1 FILE DESIGN 15

3.2 INPUT DESIGN 15

3.3 OUTPUT DESIGN 16

3.4 DATABASE DESIGN 17

3.5 SYSTEM DEVELOPMENT 18
3.5.1 DESCRIPTION OF MODULES 19
IV TESTING AND IMPLEMENTATION 21
V CONCLUSION & FUTURE ENHANCEMENT 26
BIBLIOGRAPHY 28
APPENDICES 29
DATA FLOW DIAGRAM 30
TABLE STRUCTURE 31
SAMPLE CODING 34
SAMPLE DESIGN 41
 1. INTRODUCTION

1.1 ABOUT THE PROJECT

The project entitled “COURIER SERVICE MANAGEMENT SYSTEM”

which maintains all the information about the courier transaction. The goal of this project
is to minimize the work done by staff in courier maintenance and transaction details.

Since the existing system is a manual one lot of paper work and manpower are
needed with the existing system. A large number of ledgers, papers, records etc have to be
kept for future use and this consumer a large amount of office space.

This system easily to maintenance of all the process and to provide a quick view
of all the details according to the transactions of courier booking and delivery.
Transaction process is simple and error free. But it is impossible in the manual system.

Searching and finding a particular detail of a courier number from a large number
of records needs a large amount of time. Also the data can be lost in future. The main aim
of this project maintains the courier booking details and the delivery details.

This software is competent of producing reports regarding maintenance consists of

various stages. The ultimate aim of project is computerized and easily maintained of
courier service management system.

The main objective of this project is to create software that helps us to create a
database which contains a supporting type of files to report the accounting transactions in
the organization.

By computerizing, the project mainly reduces the manual work. It saves the time.
It can store huge amount of data. By connecting with database, computerizing courier
service management system mainly helps to transfer the mails in a secured manner.
1.2 SYSTEM SPECIFICATION

1.2.1 HARDWARE SPECIFICATION

MONITOR : LCD Monitor 15” Color

PROCESSOR : Intel ® Atom ™ CPU D410 @1.6GHZ
HARD DISK : 250 GB
MOUSE : Optical Mouse
KEYBOARD : 104 Keys
RAM : 2 GB

1.2.2 SOFTWARE SPECIFICATION

OPERATING SYSTEM : Windows XP

FRONT-END : Visual Basic 6.0
BACK-END : MS-Access
VISUAL BASIC 6.0 – AN OVERVIEW

Microsoft Visual Basic is most successful to provide a real high level windows
programming language. Visual basic let's to add menus, textboxes, list boxes, scroll bars
file and directory boxes to blank windows. The grids are used to handle tabular data.

The visual basic offers more internet features, better support for database
development, more language features to make programming jobs easier with more
wizards.

All versions of visual basic are sophisticated and powerful and therefore require a
machine to match. Realistically, even the learning edition of VB requires around 50 MB
of free hard disk space, a fast Pentium class chip and at least 16 MB of RAM. A full
installation of the most powerful version of visual basic, the enterprise edition could
require more than 300MB of hard disk space.

The easiest way to run visual basic under windows is to use the program option on
the start menu. There are lots of ways to run visual basic.

Start the visual basic from Microsoft windows desktop by moving the directory
that contains it through explorer or my computer and then double clicking on the visual
basic icon. The new project dialog box lets start to build all the different types of visual
basic applications.

The visual basic application has two different applications. The first well build
totally by hand will simply by a resizable window with the usual maximize, minimize and
exit buttons. The second application will use to the application wizard supplied with
visual basic to build the frame work for a highly non trivial application. These kinds of
applications are called MDI (Multiple Document Interface) applications.

Features:
 Visual Basic is a powerful, windows based professional client/server
application development too, which allows creating quickly and easily
 sophisticated windows application for PC without being an expert in C++ or
other programming language.
 It is more user friendly and easy to learn commands.
 It has excellent facility for the file handling and manipulation.
 Programs and data are largely independent of each other’s.
 Online and offline help facility available.
 The user can modify the structure of the database without making many
program changes.
 It provides graphics facilities.
 It has easily interfaced with other software system such as word processor,
spreadsheet.
 Support for Active user interactive.
 Custom controls are the building blocks of a visual Basic application. Controls
allow your form to do more than just sit empty on a screen. Some controls,
such as labels, list boxes give users’ feedback, which others, command buttons
and textboxes, elicit responses.
 Other controls sit quickly invisible to the user, and perform some of the gurnt
work that makes your application useful.
 The timer control is one example of an invisible control. Controls are easy to
use and when used properly, can add significant functionally to your
programs.
 Visual Basic is user friendly and it is very powerful language with features of
ADO, RDO, and OLE, Visual Basic 6.0 has powerful report generating
features.
 Visual Basic also provides a very good graphical user interface which is
pleasing and easy for the user to accomplish the desired task.
 Visual Basic also provides a setup wizard, which is used to prepare an
application for distribution. In Visual Basic we can use Dynamic Link Library
(DLL) routine applications.
 Visual Basic can create event-driven application. In a Visual Basic
application, code is executed in response to events. This is different from a
procedural application in which the code is executed according to specific path
defined by the logic of the application.
MS-ACCESS 2003 – AN OVERVIEW
MS Access is a powerful database management system and the user can create
application that requires little or no programming. It supports GUI features and an entire
programming language, Visual Basic Application which can be used to develop richer
and more developed application. The MS Access database can act as a back end database
for Visual Basic as a front end, MS Access supports the user with its powerful database
management functions. A beginner can create his/her own database very simply by some
mouse clicks. Another good reason to use Access as backend tool is that it is a component
of the overwhelmingly popular Microsoft office software suite.

Features:
MS Access is a powerful database management system and the user can create
application that requires little or no programming.

 It supports GUI features and an entire programming language, Visual Basic

Application which can be used to develop richer and more developed application.

 The first being that Access is a feature rich program that can handle any database
related task the user has maintains easily.
 The user can create places to store the user data build tools that make it easy to
read and modify your database contents, and ask questions of the data.
Access is a relational database, a database that stores information about related
objects.
 MS ACCESS however is a relational database, which means that the user can
define relationships among the data it contains.
 Relational database are superior to flat file databases because the user can store
discrete information.
 User can move inside table using the navigator tools supported by the
MS ACCESS database. A table can be accessed in a number of ways like as a
Snapshot and dynast table etc.
 2. SYSTEM STUDY

2.1. EXISTING SYSTEM

The problem definition at which the system undergone the project initially carried
out all its activities manually and with old version software utilities. The manual handling
required huge amount of human efforts because the software requirements lacks the
updating data process and also involved tedious tasks. Thus it has planned to update the
computerized transaction activities. The project concentrates on all transaction works.
The computerized software must hold all the needs of the courier service. While checking
and entering financial procedures it would not discharge any complex situations.

In the existing system, all the activities are done manually. For maintaining the
details about customers, staff, branches, etc., There is a need of maintaining separate
ledgers. In this system, the main drawback is if the user wants to find a particular detail
regarding courier processing, then the user has to check all the ledgers and it will take a
long time. At the same time, the ledgers are damaged after usage of several years. In
addition to this, retrieval is also very difficult one.

2.1.1 DRAWBACKS
 It will take a huge time and human errors will occur in this type of manual
work, which in turn leads to loss of goodwill of the system.
 All the ledgers are very difficult to maintain and also for accessing .
 Very slow processing were also involved.
 Data redundancy problem occurs.
 Courier delivery and pending details not updated very well.
 Reports are not easily generated.
2.2 PROPOSED SYSTEM

The proposed system aims to provide solutions to the observed drawbacks in the
existing system. The proposed system provides the solution for the material details, cost
and analysis details problems in customized report generation. The proposed system also
gives the user an interactive, easy to use interface which reduces his burden to enter the
process details.

2.2.1 Features

 Human errors are eradicated.

 It reduce cost and saves time.
 Helps to analyze the profit and loss account which lead to improving the
business plan and overcome the problems in the existing manual system.
 Facilitates easy editing and viewing of process details whereas existing system
toils to update the data.
 Expenses details are updated very well.
 Courier booking details wise are displayed to the customers.
 Reports are quickly available to the user.
 Future enhancements.

Sometimes due to stress, human beings may make mistakes while doing works
manually. So the need for the computerized system was considered. The effectiveness of
a system depends on the way in which the data is organized. It is very difficult to
maintain all the data in an organized way. The manual work require more cost and time.
 3. SYSTEM DESIGN AND DEVELOPMENT
The design of the system is essentially a blue print or plan for solution of the
system to be developed. A part of the system or subsystem of a whole of the system can
itself be considered a system with its own complements.

3.1 FILE DESIGN

The file design is the last phase that indicates the final system and process of the
final system. In the design phase of “COURIER SERVICE MANAGEMENT
SYSTEM”, the database tables, input screen design and output design etc. are designed.

 The database tables where designed by using all the necessary fields in compact
manner.
 All the input screens in this system are user-friendly and understandable format. Also
the sizes of all the screens are standardized.
 Icons designed in this system are brief, compact and self-explanatory. The icons are
sharp and novice user can invoke the system.
 Reports generated here give the minute information, which helps the manager to take
vital decisions.

The importance of software design can be stated with a single word “QUALITY ”.
Design is a place where quality is fostered in Software Development. Design is the only
way where their requirements are accurately translated into finished software product or
system.

3.2 INPUT DESIGN

Input design is the process of converting user-originated inputs to a computer-

based format.

The system takes input from the users, processes it and produces an output. Input
design is link that ties the information system into the world of its users. The system
should be users friendly to gain appropriate information to the user.
Forms for input design in this project are:

 Employee Details
 Branch Details
 Customers Details
 Courier Booking Details
 Order Details
 Courier Received Details
 Courier Return Details
 Expenses Details

3.3 OUTPUT DESIGN

Output design generally refers to the results and information that are integrated by
the system for many end users. Output is the main reason for developing the system and
the basis on which they evaluate the usefulness of the application.

The objective of a system finds its shape in terms of output; Output of a system
can face various forms. The most command are the reports, screen displays, printed
forms, graphical, drawings etc. The basic requirements of output are that, it should be
accurate, timely and of content, medium and layout for its in tented purpose.

External outputs are those whose destination will be outside the organization.
Interactive outputs are those, in which user uses in communicating directly with
computer.

The reports given in this project are:

 Employee Report
 Customers Report
 Courier Booking Report
 Courier Received Report
3.4 DATABASE DESIGN

The general theme for a database is to handle information as integration. A

database is a collection of integrated data stored with minimum redundancy, to serve
many, more quickly and efficiently. A database file allows the user to organize data into
database. A table is the subset of entire database. A database contains one or more
tables. The table for the “COURIER SERVICE MANAGEMENT SYSTEM” is
designed in such a way as to store information efficiently and to avoid unnecessary
redundancy to make the retrieval of information easier.

The Database Management System (DBMS) consists of a collection of

interrelated data and a set of programs to access that data. The collection of data usually
referred to as database. The primary key goal of DBMS is to provide an environment that
is both convenient and efficient to use in retrieving and storing data information.

The term database design can be used to describe many different parts of the
design of an overall database system. Principally and most correctly, it can be thought of
as the logical design of the base data structures used to store the data. In the relational
model these are the tables and views. In an object database the entities and relationships
map directly to object classes and named relationships.

The most important work in building application software is the design of

database tables. After the inputs and outputs are designed, the table is organized to
ensure that the records are available for processing when designing the database table
structure the programmer would be aware of the possible redundancy data. A database is
an organized collection of inter-related information to serve many quickly and
efficiently.

The project entitled “COURIER SERVICE MANAGEMENT SYSTEM” data

has been design using Ms-Access, which is used to keep all the data in a data
management system proper care has been taken in designing the database to achieve the
objectives listed below.

 Data integrity.
 Data consistency.
  Data independence.

3.5 SYSTEM DEVELOPMENT

A system development project encompasses all the activities undertaken from the
time at which a potential requirement is identified until the resulting system is fully
implemented and accepted by the end user.

The process can involve many stages over a long period. The following section
highlights some fundamental issues to be considered, outlines the main stages in
development and procuring new systems, and indicates when and how the auditor should
be involved.

An information system acquired today must not only satisfy present business
needs; it must also be flexible and capable of being enhanced to meet changing
circumstances well into the future.

Thus a pre-requisite to the introduction of a new system is for management to

identify and understand their organization’s mission and its related information needs.

Writing this down helps to ensure common understanding and direction, and
provides a yardstick against which achievement can be measured.

The first step in which the analyst must undertake is to understand the current
system by gathering all information about it. The required data are collected by several
methods like:

 Study of the current manuals

 Observation of the functioning

 Sampling and Research

3.5.1 DESCRIPTION OF MODULES

The project consist of three modules namely,
 Master Module
 Transaction Module
 Report Module
MASTER MODULE

Employee Details
This sub-module is used to store the details about the employee id, name of the
employee, address, phone number, etc..

Branch Details

This sub-module is used to store the branch number, state, city, address, phone
number, etc.

Customers Details

This sub-module is used to store the customer id, name of the customer, gender,
address, phone number and email id.

Courier Booking Details

This sub-module is used to store the customer id, state, customer name, address,
date, weight, amount, etc..

TRANSACTION MODULE
Order Details
It maintains the order number, customer name, address, number of parcels,
payment and date.

Courier Received Details

It is used to store the courier number, branch number, date, name, address, phone
number, status, etc.

Courier Return Details

It is used to store the courier number, return date, branch number and reason.

Expenses Details
It is used to store the courier number, from, to, petty expenses and total expenses.
REPORT MODULE

Employee Report
Using employee report one can view the details regarding the employees.

Customers Report
Using customers report, one can view the details regarding the received and
unreceived couriers. It gives all the details about the customers.

Courier Booking Report

Using this report, one can view the details about the booked couriers. It gives all
the details about the courier booking transaction.

Courier Received Report

Using this report, one can view the details about the issued couriers to the
customers. It gives all the details about the received transaction.
 4. TESTING AND IMPLEMENTATION

4.1.1 INTRODUCTION

Testing objectives include

1. Testing is a process of executing a program with the intent of finding an error.

2. A good test case is one that has a high probability of finding an as yet

undiscovered error.

3. A successful test is one that uncovers an as yet undiscovered error.

Testing should systematically uncover different classes of errors in a minimum

amount of time and with a minimum amount of effort. A secondary benefit of testing is

that it demonstrates that the software appears to be working as stated in the specifications.

The data collected through testing can also provide an indication of the software's

reliability and quality. But, testing cannot show the absence of defect -- it can only show

that software defects are present.

WHITE BOX TESTING

White box testing is a test case design method that uses the control structure of the

procedural design to derive test cases. Test cases can be derived that

1. Guarantee that all independent paths within a module have been exercised at least

once,

2. Exercise all logical decisions on their true and false sides,

3. Execute all loops at their boundaries and within their operational bounds, and

4. Exercise internal data structures to ensure their validity.

BLACK BOX TESTING

Black box testing attempts to derive sets of inputs that will fully exercise all the

functional requirements of a system. It is not an alternative to white box testing. This type

of testing attempts to find errors in the following categories:

1. incorrect or missing functions,

2. interface errors,

3. errors in data structures or external database access,

4. performance errors, and

5. Initialization and termination errors.

Tests are designed to answer the following questions:

1. How is the function's validity tested?

2. What classes of input will make good test cases?

3. Is the system particularly sensitive to certain input values?

4. How are the boundaries of a data class isolated?

5. What data rates and data volume can the system tolerate?

6. What effect will specific combinations of data have on system operation?

White box testing should be performed early in the testing process, while black

box testing tends to be applied during later stages. Test cases should be derived which

Reduce the number of additional test cases that must be designed to achieve

reasonable testing, and tell us something about the presence or absence of classes of

errors, rather than an error associated only with the specific test at hand.
4.1.2 TESTING STRATEGIES

UNIT TESTING

The most 'micro' scale of testing; to test particular functions or code modules.

Typically done by the programmer and not by testers, as it requires detailed knowledge of

the internal program design and code. Not always easily done unless the application has a

well-designed architecture with tight code; may require developing test driver modules or

test harnesses.

INTEGRATION TESTING

Continuous testing of an application as new functionality is added; requires that

various aspects of an application's functionality be independent enough to work

separately before all parts of the program are completed, or that test drivers be developed

as needed; done by programmers or by testers. Testing of combined parts of an

application to determine if they function together correctly. The 'parts' can be code

modules, individual applications, client and server applications on a network, etc. This

type of testing is especially relevant to client/server and distributed systems.

VALIDATION TESTING

Black-box type testing geared to functional requirements of an application; this

type of testing should be done by testers. This doesn't mean that the programmers

shouldn't check that their code works before releasing it (which of BRANCH applies to
any stage of testing). Black box type testing that is based on overall requirements

specifications; covers all combined parts of a system.

OUTPUT TESTING

Similar to system testing; the 'macro' end of the test scale; involves testing of a

complete application environment in a situation that mimics real-world use, such as

interacting with a database, using network communications, or interacting with other

hardware, applications, or systems if appropriate.

ACCEPTANCE TESTING

Final testing based on specifications of the end-user or customer, or based on use

by end-users/customers over some limited period of time.

SYSTEM IMPLEMENTATION

After having the user acceptance of the new system developed, the

implementation phase begins. Implementation is the stage of a project during which

theory is turned into practice. During this phase, all the programs of the system are loaded

onto the user’s computer. After loading the system, training of the user starts. Main topics

of such type of training are:

 How to execute the package

 How to enter the data

 How to process the data (processing details)

 How to take out the reports

 After the users are trained about the computerized system, manual working has to

shift from manual to computerized working. The following two strategies are followed

for running the system:

(i) Parallel run: In such run for a certain defined period, both the systems, i.e.,

computerized and manual, are executed in parallel. This strategy is helpful because of the

following:

 Manual results can be compared with the results of the computerized system.

 Failure of the computerized system at the early stage does not affect the working

of the organization, because the manual system continues to work, as it used to do.

(ii) Pilot run: In this type of run, the new system is installed in parts. Some parts of

the new system are installed first and executed successfully for considerable time period.

When the results are found satisfactory then only other parts are implemented. This

strategy builds the confidence and the errors are traced easily.
 5. CONCLUSION & FUTURE ENHANCEMENT

5.1 CONCLUSION

The project entitled “COURIER SERVICE MANAGEMENT SYSTEM” is

developed for handling day activities in courier transactions.
It reduces the workload of administrator. The reports that are generated gives the
all needed information maintaining the details through the year is made easy. The project
results in quick retrieval of information, which is very essential for the progress of an
organization.

The software is developed as user friendly one. So the user (admin) may
understand the software and can work with this system by simply selecting the options.
This software has been developed to overcome the problems present in the
existing system. This software reduces the clerical error. It provides user-friendly data
screens and validation for data. Therefore, the data entry and searching for any
information is very easy.

5.2 SUGGESTIONS

The developed system is a secure and user-friendly and ensures that only
authorized users can access it. While designing the system, at most care has been taken to
satisfy all user needs. But there is a chance for the user requirements to change as time
passes by. So provisions have been included to intake new developments.

It is one of the most important functions of the transaction activity. It depends

upon the level of the user. Branching of process should be efficiently carried out without
any interruption.
 It is sure that the operations efficiency is increasing due to the existing system.
Various options become easier as there is no need to have lot of introduction regarding
the software because it is so user friendly.

FUTURE ENHANCEMENT

It is still mature and fully enthusiastically. Any requirements, this project is

completed but still, they want to update and modify some modules. We are always
thinking about association requirements also growing day by day.

We always want to implement something more. This project is completed when

you watch, but we want to implement more things.

 Online Chat
 Overseas Service
 Pickup Request On chat
 Extending geographical research
 BIBLIOGRAPHY
I. BOOK REFERENCE:

1. Elias M.Awad, “System Analysis and Design”, Galgotia Publications (p) Ltd,
Second Edition, 1996.

2. Gary Cornell, “Visual Basic 6.0”, Tata Mc Graw-Hill Publications, Fourth Edition,
1999.

3. Naveen Prakash, “Introduction To Database Management System”, Tata Mc Graw

Hill Publication, Second Edition,1995.

4. Rogers Pressman, “Software Engineering”, Tata Mc Graw-Hill Publications,

Fourth Edition, 1994.

5. Silberschatz, Korth, Sudharsan, “Database System Concept”, Tata McGraw-Hill,

First Edition, 2002.

II. URL REFERENCE:

 .http://www.vb6.us/tutorials/access-and-visual-basic-using-ado
 .http://download.access.com/docs/html/B10952-01/o4o00069.htm
 .http:/Visualbasicnetblogspot.com/2011/03/connect-access-database-using-
visual.html
 6. APPENDICES

A) DATA FLOW DIAGRAM

During 1978-79 Demano, Gane and Sarson introduce Data Flow Diagram
(DFD). DFD is the most commonly used way of documenting the processing of the
current and the required system .Data flow diagram is easily understandable by the users
and are less prone to misinterpretation, that the textual description. A complete set of flow
provides a compact top down representation of a system. Which makes it easier for the
user and analyses to envisage the system as a whole?

The symbols used in Data Flow Diagram are

 Bubbles - Representing the process

 Named arrows - Representing the system flow

 Rectangles - Representing external entities

The following steps are followed to draw a logical DFD:

 Identify environment in terms of sources/destination.

 Identify input and output data flows

 Prepare input/output list.

Symbols in DFD:

Data flow:

Process:
 Data store:

DATA FLOW DIAGRAM

ADMIN

Customer Customer_details

Courier Booking_details
Booking

Employee Employee_details

Branch Branch_details

Courier
Courier Received_details
Return
Received

Return_details
Expenses Expenses_details

Display
B) TABLE STRUCTURE

Table name : Login

Purpose : This table is used to store the administrator details.

FIELDNAME DATA TYPE SIZE CONSTRAINS DESCRIPTION

Uname Text 20 Primary key User Name
Pwrd Text 10 Not Null Password

Table name : Empoyee_details

Purpose : To store the employee details
FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION
Empid Number 6 Primary key Department id
Empname Text 20 Not Null Department name
Gen Text 6 Not Null Gender
Addrs Text 25 Not Null Address
Pho Number 12 Not Null Phone number
Doj Date - Not Null Date of join
Sal Number 6 Not Null Salary
Exp Text 15 Not Null Experience
Sec Text 15 Not Null Section

Table name : Courier booking details

Purpose : To store the courier booking details
FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION
Couno Number 6 Primary key Courier number
State Text 20 Not Null To state
City Text 20 Not Null To city
Name Text 25 Not Null To name
Addrs Text 30 Not Null To address
Phno Number 12 Not Null Phone number
Date Date - Not Null Date
Wt Number 6 Not Null Weight
Amt Number 6 Not Null Amount
Table name : Branch_details
Purpose : To store the branch details

FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Branchno Number 6 Primary key Branch number
State Text 20 Not Null State
City Text 20 Not Null City
Addrs Text 30 Not Null To address
Phno Number 12 Not Null Phone number
Amt Number 6 Not Null Amount

Table name : Courierreturn_details

Purpose : To store the courier return details

FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Couno Number 6 Foreign key Courier number
Rdate Date - Not Null Return date
Branchno Number 6 Foreign key Branch number
Reason Text 25 Not Null Reason

Table name : Expenses_details

Purpose : To store the expenses details

FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Couno Number 6 Foreign key Courier number
From Text 20 Not Null From
To Text 20 Not Null To
Pexp Number 6 Not Null Petty expenses
Texp Number 6 Not Null Travelling expenses
Totexp Number 6 Not Null Total expenses
Table name : Courierreceived_details
Purpose : To store the courier received details
FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION
Couno Number 6 Foreign key Courier number
Branchno Number 6 Not Null Branch number
Dt Date - Not Null Date
Name Text 25 Not Null Name
Addrs Text 30 Not Null Address
Pin Number 6 Not Null Pin code
Phno Number 12 Not Null Phone number
Status Text 20 Not Null status

Table name : Customer_details

Purpose : To store the customer details
FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION
Cusid Number 6 Primary key Customer id
Cusname Text 20 Not Null Customer name
State Text 15 Not Null State
Addrs Text 30 Not Null Address
Pin Number 6 Not Null Pin code
Phno Number 12 Not Null Phone number

Table name : Order_details

Purpose : To store the order details
FIELDNAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION
Orno Number 6 Primary key Order number
Cusname Text 20 Not Null Customer name
Addrs Text 25 Not Null Address
Nparcels Number 6 Not Null Number of parcels
Payment Number 6 Not Null Payment
Dt Date - Not Null Date

C) SAMPLE CODING

Private Sub Command1_Click()

If Text1.Text = "courier" And Text2.Text = "courier" Then
Unload Me
MDIForm1.Show
Else
MsgBox "Enter Correct Username and Password...."
Text1.Text = ""
Text2.Text = ""
Text1.SetFocus
End If
End Sub
Private Sub Command2_Click()
End
End Sub

MDI Form
Private Sub menuexit_Click()
End
End Sub
Private Sub menucourier_Click()
Form1.Show
End Sub
Private Sub menupemployee_details_Click()
Form3.Show
End Sub
Private Sub menurepfru_Click()
DataReport1.Show
End Sub
Private Sub menurepbranch_details_Click()
DataReport3.Show
End Sub
Private Sub menurepbooking_details_Click()
DataReport4.Show
End Sub
Private Sub menureporder_details_Click()
DataReport2.Show
End Sub
Private Sub menutransaction_details_Click()
Form4.Show
End Sub
Private Sub menusearch_Click()
Form5.Show
End Sub
Private Sub menureport_Click()
Form2.Show
End Sub
Courier
Dim con As Database
Dim rs As Recordset
Private Sub Command1_Click()
Call clear
rs.AddNew
End Sub
Sub clear()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text1.SetFocus
End Sub
Private Sub Command2_Click()
Call storedata
rs.Update
MsgBox "Courier Details Saved...."
End Sub
Private Sub Command3_Click()
rs.Edit
End Sub
Private Sub Command4_Click()
rs.Delete
MsgBox "Courier Deleted...."
Call clear
End Sub
Private Sub Command5_Click()
Dim n
n = InputBox("Enter Courier Code")
rs.MoveFirst
rs.FindFirst "Pcode='" & n & "'"
If rs.NoMatch Then
MsgBox "Courier Code Not Valid... Enter Valid Courier Code...."
Else
Call printdata
End If
End Sub
Private Sub Command6_Click()
Unload Me
MDIForm1.Show
End Sub
Private Sub Form_Load()
Combo1.AddItem "Ltr"
Combo1.AddItem "Nos"
Set db = OpenDatabase(App.Path & "\Courier.mdb")
Set rs = db.OpenRecordset("select * from Product")
End Sub
Sub storedata()
rs.Fields(0) = Text1.Text
rs.Fields(1) = Text2.Text
rs.Fields(2) = Combo1.Text
rs.Fields(3) = Text3.Text
End Sub
Sub printdata()
Text1.Text = rs.Fields(0)
Text2.Text = rs.Fields(1)
Combo1.Text = rs.Fields(2)
Text3.Text = rs.Fields(3)
End Sub

Employee Details

Dim con As Database

Dim rs As Recordset
Private Sub Command1_Click()
Call clear
rs.AddNew
End Sub
Private Sub Command2_Click()
Call storedata
rs.Update
MsgBox "Employee Details Saved...."
End Sub
Private Sub Command3_Click()
rs.Edit
End Sub
Private Sub Command4_Click()
rs.Delete
MsgBox "Employee Details Deleted...."
Call clear
End Sub

Private Sub Command5_Click()

Dim n
n = InputBox("Enter Supplier No")
rs.MoveFirst
rs.FindFirst "Scode='" & n & "'"
If rs.NoMatch Then
MsgBox "Employee No Not Valid... Enter Valid Employee No...."
Else
Call printdata
End If
End Sub
Private Sub Command6_Click()
Unload Me
MDIForm1.Show
End Sub
Private Sub Form_Load()
Set db = OpenDatabase(App.Path & "\Courier.mdb")
Set rs = db.OpenRecordset("select * from Employee")
End Sub
Sub clear()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text1.SetFocus
End Sub
Sub storedata()
rs.Fields(0) = Text1.Text
rs.Fields(1) = Text2.Text
rs.Fields(2) = Text3.Text
rs.Fields(3) = Text4.Text
rs.Fields(4) = Text5.Text
rs.Fields(5) = Text6.Text
End Sub
Sub printdata()
Text1.Text = rs.Fields(0)
Text2.Text = rs.Fields(1)
Text3.Text = rs.Fields(2)
Text4.Text = rs.Fields(3)
Text5.Text = rs.Fields(4)
Text6.Text = rs.Fields(5)
End Sub

Branch Details

Dim con As Database

Dim rs As Recordset
Private Sub Command1_Click()
Call clear
rs.AddNew
End Sub

Private Sub Command2_Click()

Call storedata
rs.Update
MsgBox "Courier Purchase Details Saved...."
End Sub
Private Sub Command3_Click()
rs.Edit
End Sub
Private Sub Command4_Click()
rs.Delete
MsgBox "Courier Details Deleted...."
End Sub
Private Sub Command5_Click()
Dim n
n = InputBox("Enter Courier No")
rs.MoveFirst
rs.FindFirst "Courierno='" & n & "'"
If rs.NoMatch Then
MsgBox "Courier No Not Valid... Enter Valid Courier No...."
Else
Call printdata
End If
End Sub
Private Sub Command6_Click()
Unload Me
MDIForm1.Show
End Sub
Private Sub Form_Load()
Set db = OpenDatabase(App.Path & "\Courier.mdb")
Set rs = db.OpenRecordset("select * from Branch")
End Sub
Sub clear()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""
Text12.Text = ""
Text13.Text = ""
Text1.SetFocus
End Sub
Sub storedata()
rs.Fields(0) = Text1.Text
rs.Fields(1) = Text2.Text
rs.Fields(2) = Text3.Text
rs.Fields(3) = Text4.Text
rs.Fields(4) = Text5.Text
rs.Fields(5) = Text6.Text
rs.Fields(6) = Text7.Text
rs.Fields(7) = Text8.Text
rs.Fields(8) = Text9.Text
rs.Fields(9) = Text10.Text
rs.Fields(10) = Text11.Text
rs.Fields(11) = Text12.Text
rs.Fields(12) = Text13.Text
End Sub
Sub printdata()
Text1.Text = rs.Fields(0)
Text2.Text = rs.Fields(1)
Text3.Text = rs.Fields(2)
Text4.Text = rs.Fields(3)
Text5.Text = rs.Fields(4)
Text6.Text = rs.Fields(5)
Text7.Text = rs.Fields(6)
Text8.Text = rs.Fields(7)
Text9.Text = rs.Fields(8)
Text10.Text = rs.Fields(9)
Text11.Text = rs.Fields(10)
Text12.Text = rs.Fields(11)
Text13.Text = rs.Fields(12)
End Sub

Courier Booking Details

Dim con As Database

Dim rs As Recordset
Private Sub Command1_Click()
Call clear
rs.AddNew
End Sub
Private Sub Command2_Click()
Call storedata
rs.Update
MsgBox "Courier Booking Details Saved...."
End Sub

Private Sub Command3_Click()

rs.Edit
End Sub
Private Sub Command4_Click()
rs.Delete
MsgBox "Oil Sales Details Deleted...."
End Sub
Private Sub Command5_Click()
Dim n
n = InputBox("Enter Courier No")
rs.MoveFirst
rs.FindFirst "Billno='" & n & "'"
If rs.NoMatch Then
MsgBox "Courier No Not Valid... Enter Valid Courier No...."
Else
Call printdata
End If
End Sub
Private Sub Command6_Click()
Unload Me
MDIForm1.Show
End Sub
Private Sub Form_Load()
Set db = OpenDatabase(App.Path & "\Courier.mdb")
Set rs = db.OpenRecordset("select * from Booking")
End Sub
Sub clear()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text1.SetFocus
End Sub
Sub storedata()
rs.Fields(0) = Text1.Text
rs.Fields(1) = Text2.Text
rs.Fields(2) = Text3.Text
rs.Fields(3) = Text4.Text
rs.Fields(4) = Text5.Text
rs.Fields(5) = Text6.Text
rs.Fields(6) = Text7.Text
End Sub
Sub printdata()
Text1.Text = rs.Fields(0)
Text2.Text = rs.Fields(1)
Text3.Text = rs.Fields(2)
Text4.Text = rs.Fields(3)
Text5.Text = rs.Fields(4)
Text6.Text = rs.Fields(5)
Text7.Text = rs.Fields(6)
End Sub
D) SAMPLE DESIGN

Fig1 : LOGIN FORM

Fig 2 : MAIN FORM
Fig 3 : EMPLOYEE DETAILS FORM

Fig 4 : BRANCH DETAILS FORM

Fig 5 : COURIER BOOKING DETAILS FORM

Fig 6 : COURIER ORDER DETAILS FORM

 Fig 7 : CUSTOMER DETAILS FORM

Fig 8 : COURIER RECEIVED DETAILS FORM

Fig 9 : COURIER RETURN DETAILS FORM

Fig 10 : EXPENSES DETAILS FORM