Chapter 1

INTRODUCTION

1
 Introduction

They have to maintain various records manually which

involves making Car Details, Customer Details, Booking
Details, Borrowed Details and many more. They have to
check manually for each and every activity going inside
particular institutions. To overcome this problem a computer
based Car Rental System is required.

The project aims to develop software, which will store

data about Car Details, Customer Details, Booking Details,
Borrowed Details, etc

2
 Chapter 2

PROJECT DESCRIPTION

3
 Company Profile

“Car Rental System” is create for the maintain Cars and

Booking information with a user-friendly Graphics User
Interface (GUI).

Company Name : Sonali Tour & Travel

Company Address : Swami CHS, C10, Room No-4,

Sector -24, Juinagar, Navi Mumbai

They have to maintain various records manually which

involves making Rent Details, Car Details and many more.

4
 Existing System

Current Car Rental System is not able to maintain

dynamic information and not able to keep records of that
particular event. To maintain all these records they have to use
old process of record keeping system that is by using files and
papers. This information can be misused or may include fault
entry which will not able to provide correct information. If
any error occurs then manual searching and updating process
required to correct that particular information.

5
 Limitations Current Method

Since the present system is manual, due to this it has the

following limitations.

1. The work is done manually and there is only one person

appointed to do the transaction work and keeping the
record in the registers.
2. To keep track of information is much more difficult.
3. It is difficult to find a particular Customer’s records from
the registers.
4. It is very difficult to know how any information are
given by a particular Customer.
5. Updating the registers about all the information takes a
lot of time.

Due to these limitations, there is a need of a system

which could solve all these problems.

6
 Objectives

1. To provide security of data.

2. To prepare various types of reports.
3. Automatic transaction of data.
4. To increase accuracy & fast execution of transaction.
5. Achieve goals with estimated results.
6. Reduces the time i.e. wasted in updating the file
manually.
7. Reduces data redundancy as once data is entered, it will
be carried forward for any requirement. no need of
reentering the data.

7
 Chapter 3
SYSTEM ANALYSIS &
DESIGN

8
 Existing System

The user is working on the MS Excel worksheet and

papers. His system is not the graphical user Interface. The
current system is time consuming because it involves lot of
paper works. To manually handle such a system was very
difficult task. In the existing system user update the records
manually at every time. But now a day because of
computerization and the graphical user interface the job
becoming easier.
The following are the reasons why the current system should
be computerized:
 To increased efficiency with reduced cost.
 To reduce the burden of paper work.
 To keep track of information is much more
difficult.
 It is very difficult to know how any
information are given by a particular
customers.
 Updating the registers about all the information
takes a lot of time

9
 System Analysis

Analysis is a detailed study of the various operations

performed by a system and their relationships within and
outside of the system. A key question is what must be done
to solve the problem? One aspects of analysis are defining
the boundaries of the system and determining whether or not
a candidate system should consider other related system.
During analysis, data are collected on the available files,
decision points, and transactions handled by the present
system. Some logical system models and tools are used in
analysis. DFD interviews, onsite observations, and
questionnaires are examples.

The interview is a commonly used tool in analysis. It

requires special skills and sensitivity to the subjects being
interviewed. Bias in data collection and interpretation can be
a problem. Training, experience, common sense is required
for collection of the information needed to do analysis. In
this project the details and the procedures of the students are
studied so as to make the system efficient to use.

10
 REQUIREMENT ANALYSIS & SPECIFICATION

Analysis categories requirement and organize them into

related subsets; explore each requirements in relationship to
other; examines requirement consistency, omission and,
ambiguity; and rank the requirement based on the need of the
customer. So first thing analyze to do is information
gathering. That is, gathering information about making the
software of automation of sales. For this, the analysts and
staff members of the sales department conduct a meeting and
the basic requirements of the new system are elicited. After
gathering information, the analyst’s setout system services in
detail in requirement specification and properly organizes the
basis of system services. For example, in developing a project
for purchasing goods on line, we held meeting to gather
information about the assumed data flow of the information
system.

11
System Planning
Perform and evaluate feasibility studies like cost-benefit
analysis, technical feasibility, time feasibility and operational
feasibility for the project. Project Scheduling should be made
using PERT charts.

Feasibility study is carried out decide whether the

proposed system is feasible for the company. The feasibility
study is to serve as a decision document it must answer three
key questions:

1. Is there a new and better way to do the job that will benefit
the user?
2. What are the cost and the savings of the alternative(s)?
3. What is recommended?

12
Feasibility Study
In the conduct of feasibility study, three important tests of
feasibility were taken:

Technical feasibility

While performing the technical feasibility a number of

technical issues arose. They are as follows:
1. Had the necessary technology existed to do what had
been suggested (or it could be acquired)?
2. Did the proposed equipment have the technical capacity
to hold the data required to use the new system?
3. Could the system be upgraded if developed?
4. Were there technical guarantees of accuracy, reliability,
ease of access and data security?

13
Operational feasibility

Operational feasibility study was conducted to sort out

the problems mainly related to the human organizational and
political aspects. Following points were considered to
compete with the esteem of operational feasibility:
1. What changes would be brought by the system?
2. What new skills would be required? Did the staff
members have these skills? If not, could they be trained in due
course of time?
3. Would there be resistance from users that will undermine
the possible application benefits?

14
Economical feasibility

Economical feasibility study was conducted to find out

whether the proposed system would be viable and effective.
The following questions were made to test the system on the
parameters of economy:
Were there sufficient benefits in creating the system to make
the costs acceptable?

Was the cost of not creating the system so great that it was
advisable to undertake the project?

15
 Chapter 4

SYSTEM
SPECIFICATIONS

16
  Hardware Recommendations

Processor 1.7 GHz

RAM 1 GB

Mother Board Intel, AMD

HDD 320 GB

Network Card On Board

17
  Software Recommendations

Operating System Windows XP SP2 or above

Language Visual Basic 2008

Database Microsoft Access

Connectivity Microsoft Access

18
 Chapter 5

SYSTEM
DESIGN DIAGRAM

19
  Functional Decomposition Diagram (FDD)

Basically, functional decomposition takes something

complicated and simplifies it. The individual elements of the
process and their hierarchical relationship to each other are
commonly displayed in a diagram called a functional
decomposition diagram.

Other common business methods for simplifying

complex problems and processes include decision trees,
which allow users to consider multiple possible solutions to a
problem, and flow charts, which show the sequence of a
process.

20
 Context Level Diagram (CLD)

A Context Diagram (and a DFD for that matter) provides

no information about the timing, sequencing, or
synchronization of processes such as which processes occur in
sequence or in parallel. Therefore it should not be confused
with a flowchart or process flow which can show these things.

Some of the benefits of a Context Diagram are:

 Shows the scope and boundaries of a system at a glance

including the other systems that interface with it
 No technical knowledge is assumed or required to
understand the diagram
 Easy to draw and amend due to its limited notation
 Can benefit a wide audience including stakeholders,
business analyst, data analysts, developers.

21
 Entity Relationship Diagram (ERD)

An Entity Relationship Diagram (ERD) is a graphical

tool to express the overall structure of a database. It is based
on a perception of a real world which consists of a set of basic
objects.

An entity is a person, place, thing or event of interest to

the organization and about which data are captured, stored or
processed. - The attributes are various kinds of data that
describes an entity. - An association of several entities in an
Entity-Relationship model is called relationship.

An ERD consists of the following major components:

Rectangles:

Used for representing entity types

22
Ellipses :

Used for representing attributes

Diamond :

Used for representing relationship types

Lines :

Used for linking attributes to entity types

23
Entity Relationship Diagram

24
 Data Flow Diagram (DFD)

The transformation of data from input to output,

through processed, may be described logically and
independently of physical components associated with the
system. These are known as the logical data flow diagrams.
The physical data flow diagrams show the actual implements
and movement of data between people, departments and
workstations. A full description of a system actually consists
of a set of data flow diagrams. Using two familiar notations
Yourdon, Gane and Sarson notation develops the data flow
diagrams. Each component in a DFD is labeled with a
descriptive name. Process is further identified with a number
that will be used for identification purpose. The development
of DFD’S is done in several levels. Each process in lower
level diagrams can be broken down into a more detailed DFD
in the next level. The lop-level diagram is often called
context diagram.

25
Data Flow Diagram

26
 Class Diagram

A UML class diagram describes the object and

information structures used by your application, both
internally and in communication with its users. It describes
the information without reference to any particular
implementation.

Its classes and relationships can be implemented in many

ways, such as database tables, XML nodes, or compositions of
software objects.

27
Class Diagram

28
 Component Diagram

Components are wired together by using an assembly

connector to connect the required interface of one component
with the provided interface of another component. This
illustrates the service consumer - service provider relationship
between the two components.

An assembly connector is a "connector between two

components that defines that one component provides the
services that another component requires. An assembly
connector is a connector that is defined from a required
interface or port to a provided interface or port."

29
 Use Case Diagram

This is an abstraction of a set sequence of a set of

sequences that yield some functionality. E.g. Login, Add a
Rooms, Make Reservation. Login can be correct login or
incorrect login where user may have provided the username,
password or both incorrectly. So under the use case login both
these scenarios will be captured. There is no need to specify
two separate use cases login correctly and login incorrectly.
As also the three possibilities for incorrect login will be
covered.

30
Use Case Diagram

31
 Chapter 6

SYSTEM DESIGN

32
 Database Table Design

Admin

Field Name Data Type Size

User_ID Auto Number Long Integer
Username Text 50
Password Text 50
Full_Name Text 50

33
 Customer
Field Name Data Type Size
Customer_ID Auto Number Long Integer
First_Name Text 50
Last_Name Text 50
Age Number Long Integer
Cellphone_No Number Long Integer
Telephone_No Number Long Integer
Street_address Text 50
City/Town Text 50

34
 List Of Cars

Field Name Data Type Size

Car_ID Auto Number Long Integer
Plate_No Text 50
Car_Name Text 50
Color Text 50
Quantity Number Long Integer
Rent/Day Currency
Picture OLE Object

35
 Rent

Field Name Data Type Size

Rent_ID Auto Number Long Integer
First_Name Text 50
Last_Name Text 50
Age Number Long Integer
Cellphone_No Number Long Integer
Telephone_No Number Long Integer
Street_Address Text 50
City/Town Text 50
Car_ID Number Long Integer
Car_Name Text 50
Plate_No Text 50
Color Text 50
nDate Date/Time Short Date
Rent/Day Currency
No_of_Days Number Long Integer
Total_Due Currency
Processed_By Text 50

36
 Customer
Field Name Data Type Size
RentDetails_ID Auto Number Long Integer
Rent_ID Number Long Integer
Car_ID Number Long Integer
Plate_No Text 50
Car_Name Text 50
Color Text 50
Quantity Number Long Integer
Rent/Day Currency
Picture OLE Object

37
 Form Design

Login Form

38
MDI FORM

39
Add / Update Car Details

40
List Of Cars

41
Add Admin

42
Add / Update Customers Details

43
Add / Update Admin Details

44
Booking

45
Borrowed Details

46
 Chapter 7
SOFTWARE
DESCRIPTION

47
  Front End

Introduction to Visual Studio 2010

Microsoft Visual Studio is an integrated development

environment (IDE) from Microsoft. It is used to
develop computer programs for Microsoft Windows, as well
as web sites, web applications and web services. Visual
Studio uses Microsoft software development platforms such
as Windows API, Windows Forms, Windows Presentation
Foundation, Windows Store and Microsoft Silverlight. It can
produce both native code and managed code.

Visual Studio includes a code editor supporting

IntelliSense (the code completion component ) as well as code
refactoring. The integrated debugger works both as a source -
level debugger and a machine-level debugger. Other built-in
tools include a forms designer for building GUI
applications, web designer, class designer, and database
schema designer. It accepts plug-ins that enhance the
functionality at almost every level including adding support
for source-control systems (like Subversion) and adding new
toolsets like editors and visual designers.

48
Editions

Microsoft Visual Studio is available in the following editions

or SKUs.

Visual Studio Community

On 12 November 2014, Microsoft announced Visual

Studio Community, a new free version similar in functionality
to Visual Studio Professional. Unlike Express, Visual Studio
Community supports multiple languages, and provides
support for extensions. Visual Studio Community is oriented
towards individual developers and small teams.

Visual Studio Professional

Visual Studio Professional Edition provides an IDE for

all supported development languages. As of Visual Studio
2010, the Standard edition was dropped. MSDN support is
available as MSDN Essentials or the full MSDN
library depending on licensing. It
supports XML and XSLT editing, and can create deployment
packages that only use Click Once and MSI. It includes tools
like Server Explorer and integration with Microsoft SQL
Server also. Windows Mobile development support was
included in Visual Studio 2005 Standard; however, with

49
Visual Studio 2008, it is only available in Professional and
higher editions. Windows Phone 7 development support was
added to all editions in Visual Studio 2010. Development
for Windows Mobile is no longer supported in Visual Studio
2010; it is superseded by Windows Phone 7.

Visual Studio Enterprise

Visual Studio Enterprise provides a set of software and

database development, collaboration, metrics, architecture,
testing and reporting tools in addition to the features provided
by Visual Studio Professional.

Visual Studio Test Professional

Visual Studio Test Professional is an edition which was

introduced with Visual Studio 2010. Its focus is aimed at the
dedicated tester role and includes support for the management
of test environments, the ability to start and report on tests and
to connect to Team Foundation Server. It does not include
support for development or authoring of tests.

50
Visual Studio Express

Visual Studio Express Editions are a set of free

lightweight individual IDEs which are provided as stripped-
down versions of the Visual Studio IDE on a per-platform
basis or per-language basis, i.e., it installs the development
tools for the supported platforms (web, Windows, phone) or
supported development languages (VB, C#) onto individual
Visual Studio Shell AppIds. It includes only a small set of
tools as compared to the other systems. Versions prior to 2013
Update 2 do not include support for plug-ins. x64 compilers
are not included in the Visual Studio Express edition IDEs,
but are available as part of a Windows Software Development
Kit that can be installed separately. After an initial
announcement that the Express 2012 release would be
restricted to creating Windows 8 Metro-style applications,
Microsoft responded to negative developer feedback by
reversing that decision and announcing that desktop
application development would also be supported. Microsoft
targets the Express IDEs at students and hobbyists. Express
editions do not use the full MSDN Library but use the MSDN
Essentials Library.

51
  Back End

Introduction to MS ACCESS 2007

Microsoft Access is a DBMS (also known as Database

Management System) from Microsoft that combines
the relational Microsoft Jet Database Engine with
a graphical user interface and software-development tools.
It is a member of the Microsoft Office suite of applications,
included in the Professional and higher editions or sold
separately.

Software developers and data architects can use

Microsoft Access to develop application software, and
"power users" can use it to build software applications.
Like other Office applications, Access is supported
by Visual Basic for Applications (VBA), an object-
based programming language that can reference a variety of
objects including DAO (Data Access Objects), ActiveX
Data Objects, and many other ActiveX components. Visual
objects used in forms and reports expose their methods and
properties in the VBA programming environment.

52
Chapter 8

TESTING

53
Definition:-
There are many approaches to software
testing. Reviews, walkthroughs, or inspections are considered
as static testing, whereas actually executing programmed code
with a given set of test cases is referred to as dynamic testing.
Static testing can be (and unfortunately in practice often is)
omitted. Dynamic testing takes place when the program itself
is used for the first time (which is generally considered the
beginning of the testing stage). Dynamic testing may begin
before the program is 100% complete in order to test
particular sections of code (modules or discrete functions).
Typical techniques for this are either using stubs/drivers or
execution from a debugger environment. For
example, spreadsheet programs are, by their very nature,
tested to a large extent interactively ("on the fly"), with results
displayed immediately after each calculation or text
manipulation

54
  Testing Methods

The box approach Software testing methods are

traditionally divided into white- and black-box testing. These
two approaches are used to describe the point of view that a
test engineer takes when designing test cases.

White box

White box testing is when the tester has access to the

internal data structures and algorithms including the code that
implement these.

Types of white box testing

The following types of white box testing exist:

 API testing (application programming interface) - testing
of the application using public and private APIs
 Code coverage - creating tests to satisfy some criteria of
code coverage (e.g., the test designer can create tests to
cause all statements in the program to be executed at
least once)

55
Black box Testing

 Black box testing treats the software as a "black box"—

without any knowledge of internal implementation.
Black box testing methods include: equivalence
partitioning, boundary value analysis, all-pairs
testing, fuzz testing, model-based testing, traceability
matrix, exploratory testing and specification-based
testing

 Testing levels

Tests are frequently grouped by where they are added in

the software development process, or by the level of
specificity of the test.

Unit Testing

Unit testing refers to tests that verify the functionality of

a specific section of code, usually at the function level. In an
object-oriented environment, this is usually at the class level,
and the minimal unit tests include the constructors and
destructors.

56
 These types of tests are usually written by developers as
they work on code (white-box style), to ensure that the
specific function is working as expected. One function might
have multiple tests, to catch corner cases or other branches in
the code. Unit testing alone cannot verify the functionality of
a piece of software, but rather is used to assure that the
building blocks the software uses work independently of each
other.

Integration Testing

Integration testing is any type of software testing that

seeks to verify the interfaces between components against a
software design. Software components may be integrated in
an iterative way or all together ("big bang"). Normally the
former is considered a better practice since it allows interface
issues to be localized more quickly and fixed.
Integration testing works to expose defects in the
interfaces and interaction between integrated components
(modules). Progressively larger groups of tested software
components corresponding to elements of the architectural
design are integrated and tested until the software works as a
system.
57
System Testing

System testing tests a completely integrated system to

verify that it meets its requirements.

Regression Testing

Regression testing focuses on finding defects after a

major code change has occurred. Specifically, it seeks to
uncover software regressions, or old bugs that have come
back. Such regressions occur whenever software functionality
that was previously working correctly stops working as
intended. Typically, regressions occur as an unintended
consequence of program changes, when the newly developed
part of the software collides with the previously existing code.
Common methods of regression testing include re-running
previously run tests and checking whether previously fixed
faults have re-emerged. The depth of testing depends on the
phase in the release process and the risk of the added features.
They can either be complete.

58
Acceptance Testing

Acceptance testing can mean one of two things:

1. A smoke test is used as an acceptance test prior to
introducing a new build to the main testing process, i.e.
before integration or regression.
2. Acceptance testing performed by the customer, often in
their lab environment on their own hardware, is known
as user acceptance testing (UAT). Acceptance testing
may be performed as part of the hand-off process
between any two phases of development.

59
 Chapter 9

CONCLUSION

60
 CONCLUSION

It has the facility to the authorized user can login in

system and view details of customers and cars.
This application provides facility for adding
customer details, adding cars details and it automatically
calculates amount of rent.
It also provides Automation of the entire system
improves the efficiency, it provides a friendly graphical
user interface which proves to be better when compared
to the current system, updating of information becomes
so easier.

61
 Chapter 10
BIBLIOGRAPHY

62
 Books Referred

 Developing windows-based applications with Microsoft

Visual Basic.Net and Visual C#.net

 Mastering Vb.Net – BPB publications

 Websites Referred

 www.wikipedia.com
 www.youtube.com
 www.slideshare.com

63