 Introduction:

In Current era, The packages in the showrooms must be registered using paper works,
also the packages showroom manager has to register all the packages and also has to
provide a bill for packages packages services.

Thus, a lot of paper work is need to be done and it’s all time-consuming assumptions, So
these packages showrooms always has to go through the files and registers to search for
specific car details or even for certain customer records. Also there’s no printed invoice
bill for packages are provided to the customers, they have their hand written bill, So to
overcome this pandemic, We have developed a C# Application which will help the
showroom managers to search the packages, Registration of packages in less than a
minute, Also our application promises to provide invoice, thanks to crystal report
technologies, The time and effort of the human beings are reduced by 70%.

Our system gathers details from the customers, Car suppliers, Dealers, and of packages.

The Automobile Management System plays an important role to manage the stock and
customers. Each and every single record is stored and retrieved as per requirement
anytime,

Our system promises of preventing the data loss of records, The user-interface is user-
friendly and admins who are gonna use this system will surely gonna love it.

The main objective of our system is to provide a system in which end users will get a
error free environment and a bug-free system.
  EXISTING SYSTEM:

In this section, we will discuss the existing system and some of its drawbacks which
force us to plan this whole idea of developing an Courier Service System. Let us take an
example: By the existing system, The current work is not computerized system.

In the current work is very difficult, because each and every record is written into the
record book add, deletion, change, etc. functions make it complex. In this we to also
collect the customer information. In the customer record, when a customer comes for
car packages they have to first check their validity. If one customer change her or his
house so it is difficult to update or change his or her profile into register. The stock
record is also have to maintain. Daily stock record is also have to update regularly.

 Scope and Features

Scope

The scope of a system means that which modules are being covered by the
system. The scope clearly defines the boundaries of the proposed system.
The functional areas of this application that lies under the scope of the
proposed system are the management of the availability of packagess and
also to make the problems solve of packages faults. using this system, User
can book the packages, register number of new connections, even though
user is also legible to register the complaints from customers like they
have received empty packages or faulty ignition, also if it has regulator
problems.
The user will receive a phone calls for maintaining the packages, the packages
will be delivered to desire users whose details are recorded in this system,
Features

 Be easy to understand by the user and operator

 Be easy to operate
 Have a good user interface
 It satisfy the user requirement
 PROPOSED SYSTEM
1. Objectives

The “Courier Service System” is a Desktop-based application. The main purpose of

“Courier Service System” is to provide a convenient and easy way for new
packages registration, complaints, employees , booking of packagess and generating of
bills to record the data. This has been tried to achieve thought making the whole
system computerized along with the basic task.
Easy data Access.
Systematic working environment.
Easy data Storage.
No chance for Errors, as data validation is done at every step.
Less paper work required, everything is done electronically in the computer.
Security of Database.
Saving a lot of time and effort on the part of employees.
Improved processing of the information, which help in the future decision making.

2. Requirement Engineering
The software is always part of a large system and is built using modular approach. The very
scratch work begins by establishing requirements for all system elements and then
allocating some subset of these requirements for all system elements and then allocating some
subset of these requirements to the software. This system view is essential whenever the
software is intended to interact with other system elements such as hardware, people, and
database. In due course the system engineering and the analysis encompass
requirements gathering at the system level with a small amount of top-level design
and analysis. Information engineering encompasses requirements gathering at the
strategic business level and at the business area level.
3. Requirement Gathering
The requirements gathering process is performed and later intensified and focused on the
software. To understand the various characteristics of the software to be built, first we must
have to understand the information domain for the software, and the required
function, behavior, performance, and interface. Requirements for both the system and the
software are documented and must be reviewed with the customer. Keeping this software
engineering paradigm we are having a proper documentation on our web site so
that Customer’s requirement should be reviewed with the user. It helped us to
minimize the distance between the actual requirement and the software required and
hence kept and will keep the customer’s satisfaction very high.
4. Feasibility Study
i. Technical Feasibility:

The technical feasibility study carried out for the system determined whether the planned
system could be developed and designed in the organization using the shopping
cart, the technical evaluation also determined whether the shopping cart can be
upgraded to use new website and whether the organization has the expertise to use
customers.

ii. Economic Feasibility:

While considering economic feasibility, it is checked in points like performance,

information and output for the system. Economic of the system looks at the
financial aspects of the projects.

iii. Operational Feasibility:

Operational feasibility refers to the measure of solving problems with the help of a
new proposed system. It helps in taking advantage of the opportunities and fulfills
the requirements as identified during the development of the project. It takes care
that the management and the users support the project.
Site Maps:
DFD:
ERD:
Homepage

Login Page
11. Splashscreen
  System Requirement

 Hardware and Software

A. Software Requirement

Operation System : Windows 7,8,8.1,10, 11.

Addition Runtime engines : Crystal Reports

Database services : SQL SERVER 2019

B. Hardware Requirement:

Hard Disk RAM : 1GB free

space

: 512 MB
 REFERENCE

Books:

1.Murach’s Visual
Basic: Anne Boehm
2.Microsoft Visual Basic 2010 Step by step:
Michael Halvorson Websites:
1.www.Docs.Microsoft.Com
2.www.CodeSnippet.com
3.www.programmingTutorials.com