• Author / Uploaded
• Afu Angel

Citation preview

Courier Management System

SYNOPSIS

2

Introduction: The Courier Management Systemsoftware package is basically designed to make the work of CourierManagementdepartmentvery.

Problem Definition: The Organization was holding the system where the records in the database were not completely secure. In the current system, where whole records were handled by various employees and the data were stored in registers and excel sheets. This results in data redundancy . The general requirements of this project are as follows: 1. Reliable 2. Error free 3. User friendly 4. Secure 5. Low maintenance

3

Solution of the problem: Considering all these aspects we have tried to develop a system that will help the Courier department a much better way to approach at there work ,save lots of valuable time and benefit a lot from this system. The proposed system is so designed that it can be used by multiple users at a time with different access right granted to them by the administrator. The software completely eliminates the threat of information leakage, saves a lot of time and also successfully estimates the working hours of the employees. You don’t have to do different posting for the same in generating reports. Using this systemyou can provide security to your database, save your valuable time, and also estimate the hours worked.

4

Process Involved: The proposed system as the following modules:1. Login 2. Administrator 3.

Customer Information

4.

Consignment Details

5.

Delivery Boy Details

6.

Reports

Objective of the Project 1. To provide security to the records in the database 2. To estimate the working hours of the employee 3. To generate the multiple reports form the information provided as per requirement.

5

Hardware and software used: Hardware: Processor

:

Intel Pentium D

Ram

:

1GB

Utility

:

Printer

:

Microsoft WindowsXP2

Software: Operating System Front end

:

Microsoft visual studio 2005

Back end

:

Microsoft sql server 2005

6

Index: TOPIC

PAGE NO

1. Objective and Scope of the Project

10-11

2. Theoretical Background 3. Definition of Problem 4. System Analysis and Design 5. Detailed Lifecycle of the Project i. Tree Diagram, FDD, ERD, CLD, DFD ii.

Event Table

iii.

Table Structure

iv.

Input and Output Screen Design

7

OBJECTIVE AND SCOPE OF PROJECT

8

Object and Scope The software aims at making the work of the entire staff of the Courier Department very easy, to save their time.To maintain their documents, to maintain their tasks performed in timely manner. The system saves your time and gives out the accurate documentation. To generate various reports for their documentation. The proposed system has been designed in such a way that can be operated by various kinds of users. The working of software is very easy to understand it is very graphical and it is user friendly.

9

THEORITICAL BACKGROUND

10

THEORITICAL BACKGROUND

 The system prevailing in the organization was manually based  The work was done using Excel Sheets.  The Excel Sheets was used to maintain customersand Delivery Boys monthlyrecords and different individuals were working on the same data to produce various.

11

DEFINITION OF PROBLEM

12

Definition of Problem: The organization presently holds a manual system, which is unable to cope with the monthly and yearly transaction of the organization; hence with the implementation of this system, the management becomes very efficient.

Time consuming :Since the work was carried and maintained on the excel sheets it was very time consuming whenever one wanted to retrieve data or wanted to go through the earlier transactions. This made the process tedious.

Complex Infrastructure: Since the work was carried on excel sheets it was very difficult to carry the transactions.

Person engaged: - Since the system was manually handled a person is continuously engaged in entering the data and updating its data.

13

SYSTEM ANALYSIS AND DESIGN

14

SYSTEM ANALYSIS: In system analysis we have found number of fact finding techniques about the system, which is under study. These facts helped us to understand what the existing system is, the flow of the existing system and what the problems are in the existing system. I.

Fact finding by observation By observing the activities of the Courier Department. The system flow of the departments is examined. All the details of the department process are given to the administrator. This report has to be maintained properly.

II.

Fact finding by document analysis. This method involves the collecting of desired documents. These documents were analyzed. This method was use to calculate the actual data element required in the system.

15

DETAILED LIFECYCLE OF PROJECT

16

Functional Decomposition Diagram:

Courier Management System

Login

Add User

Consignment

Customer

Regular

Delete User Information `

Change Password

View

Reports

Consignment

General Customers Consignment

Consignment Information

Regular Customers Consignment

Regular Customer

General General Customer

Regular Customers Undeliverd consignment Regular Customer General Customer

17

Context Level Diagram:

Customer

Regular Customers Info

Consignment Details

Consignment

General Customer Info

Regular Customers View General Customer View

Courier Regular Customers Info Management System General Customer Info

Delivery Boy Details

Delivery Boy Report

Delivery Boy

18

Data Flow Diagram:

Add User Admin

Login

Delete User Change Password

19

Admin

Admin

Login

20

Add User Admin

Delete User

Admin

Change Password

21

Regular Customers Info Admin Regular Customers View

customers

22

General Customers Info Admin General Customers View

gcustomer

23

Consignment

Admin

Consignment

Consignment

General Customers View Consignment Regular Customers View

24

Admin

Delivery Doy

dbdetails

\

25

Entity Relationship Diagram

Manages

Admin

Manages

Delivery Boy Details

Manages

Consignment Details

Customers Information

Manages

26

SCREENSHOTS

27

MDICourier:

28

frmLogin:

29

frmRegCustIno:

30

frmRegCustView:

31

Frmgencustview:

32

frmGencustinfo:

33

frmConsignment:

34

frmDelboy:

35

Frmgencustconsignrpt:

36

Table structure: Table name: Admin Table name

Fields Name

Type

Description

admin

Username

varchar(30)

Describes Admin name

Password

varchar(8)

Gives password

Table name: dbdetails Table

Fields Name

Type

Description

dbdetails

Delid

varchar(40)

Delivery Boys ID

Delname

varchar(20)

Delivery Boys name

City

varchar(20)

City

Address

varchar(30)

Address

Mobileno

varchar(50)

Mobile Number

Table name: enquiry Table name

Field name

Type

Description

enquiry

Cityname

nvarchar(50)

City Name

approximatecharges

nvarchar(50)

Approximate charges

branches

nvarchar(50)

Branch Name.

37

Table name: gcustomer Table name

Field name

Type

Description

gcustomer

Id

varchar(50)

Customer ID

Name

Varchar(50)

Customer Name

Address

Varchar(50)

Customer Address

Tel

Varchar(50)

Telephome Number

mob

Varchar(50)

Mobile Number

date

smalldatetime

Date

month

Varchar(50)

Month

consignment

Varchar(50)

Consignment

weight

Varchar(50)

Weight

destination

Varchar(50)

Destination

city

Varchar(50)

City

amount

Varchar(50)

Amount

status

Varchar(255)

Status

38

Table name: rconsignment Table name

Field name

Type

Description

rconsignment

Custid

Varchar(300)

Customer ID

accno

nvarchar(50)

Account Number

cname

nvarchar(50)

Customer Name

destination

nvarchar(50)

Destination

city

nvarchar(50)

City

date

Datetime

Daet

month

nvarchar(50)

Month

consignment

nvarchar(50)

Consignment

weight

nvarchar(50)

Weight

amount

nvarchar(50)

Amount

status

nvarchar(50)

Styatus

39

Tablename:rcustomer Table name

Field name

Type

Description

rcustomer

accno

nvarchar(50)

Accoumt Number

name

nvarchar(50)

Name

address

nvarchar(50)

Address

tel

nvarchar(50)

Telephone

mob

nvarchar(50)

Mobile Number

40

CODE

41

Feasibility Study

42

Feasibility Study For System Implementation Before the system was designed the feasibility study is carried out.

1. Operational Feasibility: The Admin was finding it difficult to keep track of the performance of the HR department with the manual system, and insurance department were not comfortable with their manual system and data redundancy .As the new system will decrease workload, strain, work time, redundancy of data, and proper view of each user efficiency by each process. The user of two departments has welcomed new system and is ready to switch over with new implementation. The management is willing to switch over because of individual. Moreover, the will receive timely and accurate reports which indeed helpful for the company. So the system is operational feasible.

2. Technical Feasibility: Technical feasibility center around the existing computer system and what extent it can support the proposed additions. This involves no financial considerations to accommodate enhancement. Since, the entire required technical platform available, organization were technical sound to execute the project.

3. Economically feasibility: The system is economically feasible due to the following reasons. The user is already having the required hardware and software, so major cost will be in terms of development of the new system.

43

System Implementation Hardware And Software Used

44

Fourth Generation Techniques Fourth Generation Technique means the use of software tool to define or specify among some of the characteristics of the software of the higher level. The tool to define or generates source code as to the developer specifications. Software development environment that supports 4GT includes the following tool: Procedural language for database query.  Report Generation.  Data manipulation.  Code Generation.  High-level graphic ability.  Spread sheet capability.

These tools are used for specific application domain and it cannot be applied to all types of software.

4GT passes through following phases: Requirement Gathering.  Design strategy  Implementation  Testing

45

Advantages:  Dramatic reduction in software development time.  Improves productivity of software developers.  Coding is reduced or eliminated.  More satisfied users.  Higher quality software with less error.  Improves communication between different users.  4GT can be used for small and medium sized projects.  Reduced Testing time.  Improved organizational effectiveness.

46

Fourth Generation Techniques

Requirement Gathering System Design Implementation Using 4Gt Testing Final Product

47

 Requirement Gathering: At this stage, the documents involved for the system development were collected. Requirement gathering includes detail study of inadequacies in the legacy systems and it involves the determination of things that are required to overcome the adequacies.

 System Design: During the phase, we identify data dictionaries to visualize database structure or database design. Process involved in the legacy system or the current systems are identified. These are the process, which manipulates the data, and the F.D.D. (Functional Decomposition Diagram) is drawn. And after determining the process involved, the D.F.D. (Data Flow Diagram) is prepared. By considering data dictionary list of processes and data flow entities involved, of the process and flow entities involved are short-listed and E.R.D. (Entity Relationship Diagram) is prepared.

 Implement Using 4GT: Implement stage involves preparing the source code to carry out processes that manipulates the data. The source code is prepared by keeping in mind the list of possible errors. Source code deploys the mechanism to avoid these types of errors.

 Testing: For testing purpose we have used Whit-box method-a widely used technique in which paths of the logic are tested to determine how well they produce predictable results. With this commonly used testing technique, we have examined the internal structure of the object.

 Final Product: After applying 4GT techniques successfully and effectively, we get robust application software, which satisfies the objectives, which are determined at designing phase i.e. it takes proper input &produce desired output.

48

Hardware and software used: Hardware: Processor

:

Intel Pentium D

Ram

:

1GB

Utility

:

Printer

Operating System

:

Windows Vista Home Premium

Front end

:

Microsoft visual studio 2008

Software:

Back end

:

Microsoft sql server 2005

49

System Maintenance & Evaluation

50

System Maintenance & Evaluation Authentication:  User Management: In this mode user add user profile i.e. Username &Password as well as User mode (Administrator \ Normal). Administrator user has only access to master database. Normal User can do other transaction except master maintenance. User can change password also so as to secure its profile.

 Log off: By using this user can logoff from the application and can log on as a different user.

51

TESTING METHODOLOGY

52

Testing Methodology For testing purpose we have used White – box method – a widely used technique in which path of logic are tested to determine how well they produce predictable results. With this commonly used tested technique, we have examined the internal structure of the object. With the help of White – box testing we have tested the source code without taking into account the external description for that source code. Because of the use of this testing method we came to know about the unintentional items such as infinite loops, paths through the code which should be allowed but which cannot be executed and dead(unreachable) code.

The key points that we have considered in White – box technique are as follows  Path Testing: In this we have tested every possible path in the code i.e. all conditions to assure that every line of code is working properly.  Condition Testing: In this we have tested for errors in condition (Boolean, Arithmetic / Relational errors).  Data Flow Testing: In this we have tested paths according to location of definitions and their users.  Loop Testing: In this we have checked the validity of the loop constructs.  Data validationTesting: Here we have implemented the code that validates the input data before storing it in that database. This prevents duplication of data.

53

Reports

54

Annexure

55

Organization Profile The World of Willis We are one of the world's No.3 risk management and insurance intermediaries. We're in the business of identifying, analyzing and managing risk. We deliver professional risk transfer, risk management, loss management and actuarial services to companies, as well as financial and employee benefits consulting. What makes us different is our entrepreneurial approach and commitment to the delivery of customized solutions. We concentrate on what we do best - broking, risk management and consulting. We provide clients with excellent local service, while enabling them to access our extensive network of global resources. We constantly strive to improve our offerings - from state-ofthe-art product solutions to excellent claims processing.

56

BIBLOGRAPHY  Visual Basic .Net Programming [Black book]  Steven Holzner

 Programming in Visual Basic 6.0  Julia Bradley  Anta Millspaugh  The Complete Reference SQL  James R. Groff & Paul N. Weinberg

 Web sites: 

www.CodeGuru.com



www.planetsource.com



www.MSDN.com



www.microsoft.com

57