Index

Acknowledgement
No.
Topics
Chapter[1]: Introduction
1.1
Purpose
1.2
Glossary
1.3
Overview of Document
Chapter[2]: Introduction of CSM
2.1
Introduction
2.2
Meaning of courier services
2.3
Scope
2.4
Aim of project:
2.5
Vision statement:
2.6
Objective
Chapter[3]: Project Planning
3.1
The software process
3.2
software process model
3.3
Team Structure
3.4
Deliverables and Milestones
3.5
Gantt chart
Chapter[4]: Software Requirements Specification
4.1
How existing system work
4.2
Limitation of existing system
4.3
Proposed System & Its Advantages
4.4
Requirements Specification
4.5
Other Nonfunctional Requirements
4.6
Feasibility Study
4.7
Stakeholder
Chapter[5]: System Analysis
5.1
Fact-Finding Techniques
5.2
Interview & Questionnaire
5.3
Sample Interview Questions & Related Topics

Page

5.4
A sample Questionnaire
5.5
Activity Dependencies, Activity network and Activity Timeline
5.6
Use Case diagram
5.7
Activity diagram
5.8
Sequence diagram
5.9
Class Diagram
5.10
Entity Relationship Diagram
Chapter[6]: Implementation
6.1
Introduction
6.2
Considerations
6.3
Implementation
Chapter[7]: Construction & Deployment Considerations
7.1
Considerations
7.2
Testing
7.3
Implementation
7.4
Post Implementation and Maintenance
Chapter[8]: Discussion and Conclusion
8.1
Discussion
8.2
Conclusion
8.3
Future work
References & Conclusion

Chapter [1]
Introduction
(1.1) Purpose
This Software Requirements Specification (SRS) document will provide a detailed description of the
steps, phases and design necessary for the Courier System Management (CSM). This SRS document
will allow for a complete understanding, of what is to be expected of the CSM to be constructed. A
clear understanding of the CSM and its functionality will allow for the correct software system to be
developed for the users of the software, and will be used for the development of the future stages of
the project. This SRS document will provide the foundation for the project. From this SRS
document, the CSM can be designed, constructed, and finally implemented and tested.
This SRS document will be used by the software engineers for helping and working side-by-side
with the system analysts while constructing the CSM, and the Courier end users. The software
engineers will also use the SRS document to fully understand the expectations of this CSM, to
construct the appropriate software. The Courier end users will be able to use this SRS document as a
test, to see if the software engineers and system analysts will be able to construct the system
according their expectations. If it is not to their expectations, then the end users can specify how it is
not to their liking, and the software engineers will change the SRS document and ultimately the
software, to fit the end users needs.

(1.2) Glossary
CSM
SRS
Software

Software Engineering

Courier System Management

Software Requirements Specification
Software is a generic term for organized collections of computer data
and instructions, often broken into two major categories: system
software that provides the basic non-task-specific functions of the
computer, and application software, which is used by users to
accomplish specific tasks.
The computer science discipline concerned with developing large
applications. Software engineering covers not only the technical

SRS document

Systems Analysis

Systems Design

Deliverables

Stakeholder
Flowchart

System Flowchart
Project Management

Information System

Heuristic

Data Modeling

aspects of building software systems, but also management issues,

such as directing programming teams, scheduling, and budgeting.
A SRS document, a requirements specification for a software system,
is a complete description of the behavior of a system to be developed
and may include a set of use cases that describe interactions the users
will have with the software. The software requirements specification
document enlists all necessary requirements that are required for the
project development.
(1) Analyzing in detail the components and requirements of a system.
(2) Analyzing in detail the information needs of an organization, the
characteristics and components of presently utilized information
systems, and the functional requirements of proposed information
systems.
Deciding how a proposed information system will meet the
information needs of end users. Includes logical and physical design
activities, and user interface, data, and process design activities that
produce system specifications that satisfy the system requirements
developed in the systems analysis stage.
A project management term for the quantifiable goods or services that
will be provided upon the completion of a project. Deliverables can be
tangible or intangible parts of the development process, and are often
specified functions or characteristics of the project.
Any person, who is not a developer, but has a proper role with interest,
in the project.
A graphical representation in which symbols are used to represent
operations, data, flow, logic, equipment, and so on. A program
flowchart illustrates the structure and sequence of operations of a
program, while a system flowchart illustrates the components and
flows of information systems.
System flowchart represents a graphic diagramming tool used to show
the flow of information processing activities as data are processed by
people and devices.
Managing the accomplishment of an information system development
project according to a specific project plan, in order that a project is
completed on time, and within its budget, and meets its design
objectives.
(1) A set of people, procedures, and resources that collects, transforms,
and disseminates information in an organization. (2) A system that
accepts data resources as input and processes them into information
products as output.
Pertaining to exploratory methods of problem solving in which
solutions are discovered by evaluation of the progress made toward the
final result. It is an exploratory trial-and-error approach guided by
rules of thumb. Opposite of algorithmic.
Data modeling defines primary data objects, composition of each data
object, and attributes of the object, relationships between each object
and other objects and between objects and the processes.

(1.3) Overview of Document

Chapter [1] describes the purpose and scope of this SRS document, and its contribution on the
overall software engineering project. It also includes a section, where some important keywords,
used throughout this document, are defined. Thus, this chapter fulfills the needs of introductory
discussions.
Chapter [2] describes the meaning, scope and aim of the courier system project. It also includes
about the vision and objective of this system.
Chapter [3] discusses about the plan for approaching the project. Here, the model to be used to
develop the software is generally discussed. Some discussions about the structure of the team along
with the schedule of deliverables with Gantt chart are also covered in this chapter.
Chapter [4] discusses about the core components related with Software Requirements Specification
(SRS). Here, the present or the existing system is compared with the proposed system. The
requirements are specified in general. Later in the chapter, some discussions about the different
stakeholders of the software system are also included.
Chapter [5] describes about the analysis phase of the project. It includes some general techniques
that can be used to find facts about the software system very easily in the context of this project.
Later in the chapter, different UML diagrams related with the analysis phase, such as use-case
diagrams, activity diagrams, sequence diagrams, Class Diagram and so on are illustrated.
Chapter [6] describes in detail about implement phase.
Chapter [7] discusses about the construction and deployment considerations. The different types of
testing that should be performed on the software system are theoretically discussed here. Later in the
chapter, some discussions about implementation, post implementation and maintenance are also held
in short.
Chapter [8] discuss about deduction and future work of the project.

Chapter [2]
Introduction of CSM
(2.1) Introduction
In modern age, as time increase, needs & requirements of the person are also increased. They want
more facility & try to do their task quickly & within time.
Within the country, the things can be imported through post service. However, it consumes the time
& sometimes problem of damage or missing occur. The courier service is one of the solutions of
these problems. It is used to send some things to any person within time.
The courier company has number of branches, which are spread over the country. So that when
person wants to send things then he has to contact at nearest courier service branch. The courier
company creates the schedule & gives internal/external services. The courier service work as
destination office or source office. The source office branch receives the order means consignments
& sends it to the destination courier branch. The company has certain rules according to the weight.
Using the courier service person can easily send his/her parcel to other person in the particular
destination within the time. Now days, 50% of companies of the world uses the services of various
courier company.

(2.2) Meaning of courier services

Courier services means any services provided to a customer, by a courier agency in
relation to door-to-door transportation of time sensitive documents, goods or articles.
Courier agency means a commercial concern engaged in the door-to-door
transportation of time sensitive documents, goods or articles, utilizing the services of
person, either directly or indirectly, to carry or accompany such goods, documents or
articles.

(2.3) Scope
This project provides the facility to all users to send and receive the courier. They can get the
information of the status of the courier. System development is also considered as a process backed
by engineering approach. Courier agency is considered as an expansion of business relations. It

contributes a lot by providing quick & fast services of sending documents letters (formal & informal
both) to business as it enables any business to flourish.
This project is for only Domestic Courier Management. In this project we only focus on Client
Management and partially Employee Management .

(2.4) Aim of project

The main aim of the project is to develop an application system that meant to partially
computerize the work performed by the department. The major function are collecting
information about courier agency.

(2.5) Vision statement

Being the best at creating the solution that simplify your system.

(2.6) Objective
When we have already entered the 21st century, we may not afford to listen words like Sorry,
Misrouting, Confusion, Late deliveries, loss of Packets, No-response, No feedback etc. We have
tried to make all these miss happening & feel pleasure to couriers. The main object of this project is
given below:
1. The main object of this project is that it facilitate user to communicate in a faster manner in
comparison of manual system. Through this system, the status of the courier can be known easily
whereas in manual system it is difficult.
2. To propose all in one system that include both tracking & Courier System.
3. To develop a software solution for courier service system that provide best service, error free and
last longer.
4. To study their current information system and identify how business processes handle by an
information technology solution.

Chapter [3]
Project Planning
(3.1) The software process
A process is a collection of activities, actions, and tasks that are performed when some work product
is to be created. In addition, a software process is a set of activities that leads to the production of a
software product. These activities may involve the development of software from scratch in a
standard programming language like Java or C/C++. Although there are many software processes,
some fundamental activities are common to all software processes:

Specification - what the system should do and its development Constraints.

Development - production of the software system.
Validation - checking that the software is what the customer wants.
Evolution - changing the software in response to changing Demands.

(3.2) Software process model

A simplified representation of a software process, presented from a specific perspective.
Some process model are:
Waterfall model
Incremental Process Models
The Spiral Model
Evolutionary Process Models
However, we choose the Water model. So Courier System Managements based on Linear Sequential
Model (Waterfall Model) because of the following reasons:
In the waterfall model, software development is split up into a number of
independent steps. Each step is well defined.
It provides a framework for a development. The waterfall model says nothing
about what methods are used at any of its stages.
All requirements for the system have been explicitly stated at the beginning.
There is very little scope of user derivation from current requirements.
There is no modular structure as there is only one team consisting of just four
members to develop the system and do all related task to the system.

Figure: Waterfall Model

(3.3) Team Structure

Software developers seldom work alone. More commonly, several developers share an office,
working on different projects or collaborating on larger projects. Therefore, software development is
essentially a social activity.
The principles of teams: Two major aspects of team activity are:
1. The communication between the people in the team
2. Deciding who does what work.
Our system has Democratic Decentralized (DD) team structure, as there is no permanent team leader.
Problem of the system is solved by discussion among the five members and decisions on problems
and approach are made by group consensus.

(3.4) Deliverables and Milestones

Project planning is concerned with identifying the activities Milestones and deliverables produced by
a project. Because software is intangible, this information can only be provided as reports and
documents that describe the state of the Software being developed. Without this information, it is
impossible to assess how well the work is progressing.
A milestone is recognizable end-point of a software process activity. At each milestone, there should
be a formal output, such as a report, that can be presented to management. Milestone reports need
not be large documents.
A deliverable is a project result that is delivered to the customer. It is usually delivered at the end of
some major project phase such as specification or design.

(3.5) GANTT CHART

Following Gantt chart can assist our group to keep track of time and be aware of the
schedules of deliverables:

Task

Activity by Weeks from the start of the project

April - 13

May - 13

June - 13

1 2 3 4 5 6 7 8 9

Proposal

Requireme
nts
Specificati
on

Modelling:
Analysis

Modelling:
Design

Presentatio
n

1
0

1
1

July - 13
1
2

1
3

1
4

August - 13
1
5

1
6

1
7

1
8

1
9

September - 13
2
0

2
1

2
2

2
3

2
4

Chapter [4]
Software Requirements
Specification
(4.1) How existing system work
Description of the event-flow of present system is pointed out below:
1. Client go to the nearest courier branch office and collect information about the destination
branch office.
2. Then client calculate the cost for sending courier.
3. Now client fill the form. The Details included in the form are

Full name of sender

Sender mobile no

Sender full address.

Mention the destination branch office

Mention this courier for home delivery or not.

Full name of Receiver

Receiver mobile no.

Receiver full address.

4. Now Customer will hand over his or her good to the branch.
5. If everything is okay way bill is printed out. It contains all the information to identify the
delivery .

6. Then the data for a particular courier maintained in a proper file. A person summarizes all
the data of the courier in a register, this work require a high-level of attention since it has to
be taken care that no wring entry goes into the register.

(4.2) Limitation of existing system

1. There have no tracking system to know the current location for courier.

2. Manual data entry.

3. Data may lost or damage
4. Any unauthorized person can access confidential data.
5. Any information cannot be easily searched.
6. Redundancy of data.
7. More time consuming.
8. Inaccuracy in transactions.
9. Slow processing.
10. All connection between Courier Company and client is mobile based.

(4.3) Proposed System & Its Advantages

After a detailed study of the existing system, it is evident that is does not fulfill the objective of the
organization. To make the objective possible for the organization, it is required to have a
computerized information system with the help of which all tasks can be processed more accurately
and quickly. To achieve this, it is necessary to design and develop a new system. Proposed system is
being designed in such a way that many users can have a view with the system simultaneously. It
makes effective and perfect utilization of manpower and resources.
By new system client get a tracking no (which is the bar code or QR code) and password by this
track his courier. Also, get update information by E-mail or SMS.
New system has following advantage:
Online tracking system: A sender can track the courier and identified the location.
Easy to get Branch office info: A navigator can show all branch office info via webpage so
it is not necessary to go branch office for destination branch office info.
Easy comparison: Navigator can calculate the cost and easily compare other courier service.
Information access: A navigator easily can get info about company and other like lost
courier.

 Online chat room: User can chat with company through online chat room.
Be update: Client get all update via Email or SMS about courier e.g., whether packet is
delivered, pending or returned to the client etc.
Easy Redirect: Client can easily redirect the courier.
Easy in maintaining information: Staff can be easily update information about a specific
courier using bar code reader or QR code reader.
Routing Information: A Sender can see the all routing information and estimated date of
delivery.
User satisfaction: The system is such that is stands up to the user expectations like easy and
faster retrieval of information.
Safety: The system will be accessible by only the authorized users. As information, being the

most crucial for the organization, then the safety of information is importation.
Highly accurate: resources being used by the system will be compatible with the latest
technologies available in the market, as proposed system uses highly technically compatible
resources, there will be very less wear and tear.
Less time consuming: work carried out by the staff at various stages will be less time
consuming

(4.4) Requirements Specification

Development Tools:
o Front End: Visual C# Enterprise Edition (ASP.NET)
o Back End: Microsoft Office Access 2007 or higher
Server End:
o PLATFORM: Windows XP sever or higher
o Hardware specification:
Processor:
1 GHz (x86 or x64)
Memory:
1 GB
Disk Space:
1 TB (in addition to the disk space required by the O/S)
These are the minimum system requirements and will support running thousands of jobs per day.
Bar code Reader or QR code Reader.
Client End:
o Software specification:

 Mozilla Firefox 10.0 or higher (equivalent)

o Hardware specification:
Any device that supports above browser

(4.5) Other Nonfunctional Requirements

Safety Requirements:
New system is safe to use. Its usage will not provide any damage or any type of loss to the systems
already in use. In addition, the security model is prepared regarding the safety of Database so that
data is not lost in case of any damage to the system.

Security Requirements:
Security of the system shall be definitely be maintained through the password system. Each
employee of every branch office will need to be authenticated with a login id and password. Any
employee cannot change the system date to make proxy presentation of yourself.

Software Quality Attributes

Our proposed system shall provide a automate software product for the different department of the
courier company. The system will be highly Adaptable, Available, and Portable.

(4.6) Feasibility Study

Every software project begins with a judgment as to whether the project is valuable or not. This is
called a feasibility study. Sometimes this assessment is carried out in a detailed and systematic
fashion.
Software feasibility has three solid dimensions:
Technical Feasibility
Operational feasibility
Cost-benefit analysis(Economic Feasibility)
Before beginning a project, there is a crucial decision that must be made: Is the proposal technically
feasible? That is, will the technology actually work?
The answer of the above question is: This project is technically feasible. It successfully satisfies the
users basic requirements. The tools and application softwares used in this project are very popular
and easily available across the world.
ASP.NET provides a complete environment for building, deploying and running .NET Web
Applications.

Some of the most general advantages of ASP.NET are listed below is short:
Ease of Development
o Simplified page development model
o Modular, well-factored, extensible architecture
o Superior debugging and tracing support
Performance, Scalability, Reliability
o Compiled, not interpreted
o Rich Caching Support
o Web form scalable session state
o Automatically detects and recovers from errors
Ease of Deployment and Configuration
o No need to bring down web server
o XML Configuration files
The .NET Framework provides a feature-rich application environment, simplified
development and easy integration between a numbers of different development languages.
Bar code reader now a day is it not a very expensive technology.

Operational feasibility:

The system will have easy to understand interface for different modules. It does not require any
programming skill to use the system. After a little training, the users will be able to work with it at
ease.

Cost-benefit analysis (Economic Feasibility):

Money provides the ready-made metric for measuring value. This kind of investigation is called
investment appraisal or a cost-benefit analysis. The organization expects a return on investment. In
this approach, two quantities are calculated:
1. The cost of providing the system
2. The money saved or created by using the system the benefit.
If the benefit is greater than the cost, the system is worthwhile; otherwise, it is not. If there is some
other way of accomplishing the same task, which may be manually, then it is necessary to compare
the two costs. Whichever technique gives the smaller cost is the one to select, if the benefit is greater
than the cost. With each of these criteria, we can associate a cost, though for some it is less easy:
cost to buy equipment, principally the hardware
cost to develop the software
cost of training
cost of lost work during switchover
cost to maintain the system
cost to repair the equipment in the event of failure
cost of lost work in the event of failure
cost to upgrade, in the event of changed requirements.
In This project, it also requires the salary structure of the employees. We could not manage to get
those data for some unavoidable reasons. At this level, the project may be called a demo project at
desktop level. Such study can be made when the project advances to a higher level.

(4.7) Stakeholder

Stakeholder refers to any person, who is not a developer, but has a proper role with interest, in the
project.
Stakeholders for the proposed system are as follows:
Manager of the Branch:
o He can provide details about the overview of company under a single roof. Since the
workability of staff will be increase and the owner will get benefits from it.
Administrator:
o He will access the Whole software.
User:

o They will access some part of the system.

Staff:
o They will access some part of the software.

Chapter [5]

System Analysis
(5.1) Fact-Finding Techniques
Fact-finding techniques are extremely important because these are the facts based on which analysts
can or should build the system that comprises of a friendly environment for the end user to work
with. This is the reason why fact-finding is an important activity.
Some of the most simple and useful fact finding techniques that can or should be followed are
pointed out below:
Interview & Questionnaire.
Document Sampling (Detailed examination of checking-in & out, billing forms and other
related documents).
Work Site Observation.

(5.2) Interview & Questionnaire

This is considered as one of the best fact finding techniques. This includes direct interaction with the
customer. It is considered as the best technique, because it is the only way the user can reveal the
details & facts about his past, present & expected working, requirements, technologies, desertions to
analysts. This is the information, which gives us the description of the system, we have to implement
our logic & our own ideas & make this description to turn to a reality, to work as a real module,
which the user desires.
In the following few pages, some example, structured interview and questionnaire sample documents
are given. These documents have been used or can be used, directly or as a model, for gathering data
under the context of this project.

(5.3) Sample Interview Questions & Related Topics

About Courier company:

1)
2)
3)
4)
5)

Courier company Name:

Company Location:
Manager Name:
Manager Contact Number:
Interview Time/Date:

The 1st service (From Whom & What), a sender receives;

when he/she comes/arrives/inquires at the branch office.

Questions From A Senders Point Of View:

1)
2)
3)
4)
5)

How sender contact branch office and get info about destination?
How track the courier and get update.
How much is the cost to send a courier according to weight?
What is the route of courier & estimated time needed to deliver the courier?
How handle such acts like those that pending or return backed to the client etc.

6) What happened if courier lost or damaged.

7) Some other related services?

Courier Services:
1) Process of handling a customer (How & by whom), when he/she comes/arrives the 1st
time.
2) Booking process of a customer.
3) The delivery process of a courier to a customer.

Billing Process:
1) How (& by whom) the bill payment process of a customer is done?
2) What happen if the courier is redirect?
3) Is there any advanced processes related with the billing process?

Summary of the Whole Management Process; That Takes

Place, in between a user and the service company.

(5.4) A sample Questionnaire

Information of Interviewed Personal:
Name:
Contact Number:

E-Mail ID:
Position/Post:
Experience:
Interview
Time/Date:
Approval:
_______________________
Signature With Date

Short Answer Based simple Questions:

1) How many employee do you have?
Answer:
2) What about your company web service?
Answer:
3) How redirect the courier?
Answer:
4) How is your whole working process?
a) Manual
b) Mixed
c) Automated/Computerized

1)
2)

5)

7)

Yes/No Question
1) Have any online tracking system:
Yes / No
2) Have any online branch info: Yes /
No
3) Billing Form: Yes / No
4) If any other types of forms
available:

Manual/Mixed
1) How does this system work?
3)
Answer:
2) What is the Educational Qualification about Employee?
Answer:
3) Approximately how much time is consumed by the current
working process?
Answer:
4) How calculate the cost of courier?
Answer:
5) Are you satisfied with the current working system?
Answer:
6) What happen if courier lost or damage?
Answer:
7) Do you think Your employee cope with new system?
Answer:

Computerized
1) How & by whom the
computerized system is user?
Answer:

2) Have you used any

computerized technology?
Answer:
8) 3) Does the system hold
employee data?
Answer:
1) 4) The whole working process
of the current computerized
system in short.
Answer:
2) Do you think computerized
system will be helpful / useful
to you?
Answer:

8) What are the most noticeable advantages a computerized

system will give you?
Answer:
9) What you think about the reaction of staff If new system is
implemented?
Answer:

(5.5) Activity Dependencies, Activity network

and Activity Timeline

Tasks:
T1=Data collection
T2=Administration
T3=Branch management
T4=document handling
T5=Customer management

Activity Dependencies:
Task
T1
T2
T3
T4
T5

Activity network

Duration(Days)
7
5
6
7
4

Dependency
T1(M1)
T2(M2)
T2(M3)
T1(M4)

Activity Timeline

(5.6) Use Case diagram

(5.7) Activity diagram

(5.8) Sequence diagram

(5.9) Class Diagram

(5.10) Entity Relationship Diagram

Admin

Manag
es

Company details

Consignme
nt

n Employee
details

Manag
es

Delivery Boy
n

Delive
r

Customers
Information
n

Manag
es

Manag
es
1
1
Staf
n

Manag
es

Chapter [6]
Implementation
6.1 Introduction
In this phase, the coded programs were tested using different testing methodology in order to
drag out the errors of at the time of execution in practical or in simulation environment. The
full code has been successfully compiled and interpreted where the syntax errors have been
identified and carefully solved. The program design checking methods was used while
coding to define the logical errors. Desk checking method had been used to check the
program design and then running method was used for the corresponding code.

6.2 Considerations
We have thus far completed up to modeling phase. The next phases are construction and
deployment. Construction phase includes Coding and Testing; and deployment involves
Implementation and Maintenance. Short descriptions of the phases after coding are described
in the following sections.

6.3 Implementation
When the new system is completed, replacing/modifying the existing manual system in an
appropriate manner is a major task to the success of the project. Improper installation can
prevent the improvement of the organization, even if the designed software is a quality
product.
In the implementation phase, following tasks occur:
Training personnel
Conversion procedures
Post-implementation review
Conversion is the process of changing from the old system to the new one. It must be properly
planned and executed.

Chapter [7]
Construction & Deployment
Considerations
(7.1) Considerations
We have thus far completed up to modeling phase. The next phases are construction and
deployment. Construction phase includes Coding and Testing; and deployment involves
Implementation and Maintenance. Short descriptions of the phases after coding are described
in the following sections.

(7.2) Testing
Testing is a process of executing a program with the intent of finding an error. A good test
case is one that has a good probability of finding yet undiscovered error. All tests should be
traceable to customers requirement. Test should be planned long before testing begins.

Testing Principles
A good test case is one that has a high probability of finding a yet undiscovered error.
A good test is not redundant.
A good test should be neither too simple nor too complicated.

Types of testing
There are two basic approaches to testing functional and structural. Functional testing is also
called Black Box Testing Structural testing is called white Box testing.
The black box approach to testing is to devise sample data that is representative of all possible
data. We then run the program, input the data and see what happens. This type of testing is
termed black box testing because no knowledge of the workings of the program is used as part
of the testing; we only consider inputs and outputs.

Black box testing enables the software engineer to find error in the following categories:
Incorrect or missing functions.
Interface Errors.
Errors in data structure or external database access.
Performance errors
Initialization errors.
White box testing makes use of knowledge of how the program works the structure of the program
as the basis for devising test data. In white box testing every statement in the program is executed at
some time during the testing. This is equivalent to ensuring that every path (every sequence of
instructions) through the program is executed at some time during testing. This testing help the
software engineer in the following directions:

Guarantee that all the independent paths within the module have been exercised at least once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their validity.
Exercise internal data structure to ensure their validity.

Levels of Testing
The basic levels of testing are:
o Unit testing
o Integration testing
o System testing
o Acceptance testing

Unit Testing
Unit testing focuses verification effort on the smallest unit of software design the software
component or module. Using the component-level design description as a guide, important control
paths are tested to uncover errors within the boundary of the module. Therefore, Unit testing tests
each component in isolation.
The goal of this testing level is to see if the modules have been be integrated properly. In other
words, the emphasis is on testing the interactions among the modules. This testing activity can be
considered as testing the design.

Integration Testing

The goal of this testing level is to see if the modules have been be integrated properly. In other
words, the emphasis is on testing the interactions among the modules. This testing activity can be
considered as testing the design. There have two type of different incremental integration strategies
are given below:

o
o

Top-down integration.
Bottom-up integration.

System Testing
In this testing entire software is tested. The goal is to see if the software meets its requirements.
System testing is actually a series of different tests whose primary purpose is to fully exercise the
computer-based system. Although each test has a different purpose, all work to verify that system
elements have been properly integrated and perform allocated functions.
The types of system tests that are worthwhile for software-based systems.

Recovery Testing
Security Testing
Stress Testing
Performance Testing

Acceptance Testing
Acceptance testing is preformatted using real data of the client to demonstrate that software is
working satisfactorily.

Validation Checks
Validation refers to different set of activities that ensure that the software that has been built is
traceable to the customer requirement. Validation is the check that the product made is what was
required.

(7.3) Implementation
When the new system is completed, replacing/modifying the existing manual system in an
appropriate manner is a major task to the success of the project. Improper installation can prevent the
improvement of the organization, even if the designed software is a quality product.
In the implementation phase, following tasks occur:
Training personnel
Conversion procedures
Post-implementation review

Conversion is the process of changing from the old system to the new one. It must be properly
planned and executed. Three methods are common in use, these are:
Parallel System.
Direct Conversion.
Pilot System.

(7.4) Post Implementation and Maintenance

After system is implemented and conversion is complete, a review should be conducted to determine
whether the system is meeting expectations and where improvements are needed. A post
implementation review measures the systems performance against predefined requirements.
Suggestions regarding changes and improvements are asked for.
In this, phase the programmer or some other technical employers of the company, which is
developing the software in order to manage the hanging requirements of the client from time to time,
do review.

The keys to reduce the need for maintenance while making it possible to carry on with essential
tasks more efficiently are as follows:
More accurately defining the users requirement during systems development.
Preparation of system documentation in a better way.
Using more effective ways for designing processing logic and communicating it to project
team members.
Making better use of existing tools and techniques.

Chapter [8]
Discussion and Conclusion
8.1 Discussion
The software is verified and validated for different critical inputs and it produces accurate result. The
software can be modified according to user requirements. The database files used in this software are
designed carefully to overcome the problems of storing and retrieval of information generally related
to traditional file processing system. A well-designed Graphical User Interface (GUI) was designed
carefully to make it user friendly.

8.2 Conclusion
There is always a scope of betterment and this system is not against this perception. At present the
software system satisfies most of the functions of a very general Courier system management
system.
1. The courier services are automated as hand written documentation is minimized to a bare
minimum the software is fully implemented.
2. The data can be easily backed up onto a reliable media so that no or minimal data loss is there in

case of system crash.

3. Unauthorized access to the data is nearly eliminated by providing password authentication
system.
4. This project has made us require a professional outlook towards problem statement and solving it
to the best and maximum.

8.3 Future work

The main scope of future work and improvements may be:
1. Provide GPS tracking system for vehicle, which provide better tracking information.
2. Online bill payment and provide full support of the debit card, credit card and others.
3. Storing large amount of data for future usage.
4. Reducing manual efforts for maintaining the system.
5. Emphasis on accurate data and reuse of stored data.
6. Complete automation, almost no need for manual human intervention.

References
Software Engineering
By Sommerville
Software Engineering: Theory and Practice
By Forrest Shull and Roseanne Tesoriero
Software Engineering for Students, 4th edition
By DOUGLAS BELL

System Analysis and Design

By Elias M. Awad
Database System Concepts
By Silberschatz, Korth & Sudarshan
Electronic Commerce
by by Elias M. Awad

www.wikipedia.org
www.google.com