Chapter - 1

INTRODUCTION

-1-

INTRODUCTION
The feeling of acknowledgment something and expressing it in
words Is our weakness , but we heartily admit, that when we surely
wish to express our warm gratitude towards somebody concerned ,
but we are at loss of words.
During the entire course of this demanding and intriguing project.
Which involve lot of creativity and conceptualization? I would like to
express my sincere thanks to my project guide for his.
Valuable guidance, scholarly advice, fruit suggestion and critical
remarks during the course of the present system investigation and
who really timely and duly helped. I am indebted to him for the
knowledge and help he has imparted upon me. It is started fact that
without his guidance and support this project would not have its
end. Therefore and foremost we extend our heart full gratitude to
him.
Knowledge is choicement possession, which should not be shelved
but should be happily with other. In this regard we are extremely
fortune in having Mr. SANJEEV KUMAR Our guide in this project
work.
All concepts knowledge and will to work can be realized in the form
of the project if and only if resources are available. which he could,
and his great help and numerous suggestions in making this
project. Without his help it was not possible to complete this project
under a considered time limit.We should be incomplete in our vote
of thanks if we forgot our batch mates and friends who helped with
their ideas and more so by their encouragement.
Software project is a logical rather than a physical system
Element.

Therefore,

software

has

characteristic

that

are

considerably different than those of physical one. Software is

developed or engineered; it is not manufactured in classical sense
-2-

A computer software is a said to be success when it meet the

Needs of the peoples who use it, when it performers flawlessly over
long period of time, when it is easy to modify and even easier to
use-it can and does change for the better. To succeed, we need
discipline when we design and build software. It needs an
engineering approach.
Welcome to the project. The project title is Computerized
HRTC SYSTEM as the name suggest, this project is on Himachal
Road Transport Corporation(HRTC). This project is very friendly
and created using VB.NET Programming Language.
By using this project we can Reserve the Tickets. Using this
project we can store, search, edit the information about the Routes
and Buses, and See the Reports. This project uses a strong
database.

-3-

Existing system:
The existing system was controlled with a lot of and
efficient computer operators because the software on
which the existing system was dependent were difficult to
understand and handle. due to use of various softwares
the cost was too high because much salary had to be
paid to many operators. moreover all the operators were
required to take training, as they had no knowledge about
the software used.

Proposed system:
The proposed system will remove all the problems in the
existing system. now only few softwares like Visual
Basic 6.0,Version7.0 will be required. The softwares are
too easy to understand that the user can understand it
and once moreover it is so frequently used in daily life
that almost all the users must have gone through it in their
educational level. As the softwares cost is also little. No
special training is required. Not many operators are
required only person can handles the records of whole
department. The accuracy will be there, security will be
there

and

easy

access

will

be

there

Before

designing/developing a new system, it is important to

establish the acceptance criteria so that it can be

-4-

evaluated according to this criteria .The performance

requirements are:
User Friendly : The designed system should be
user friendly, understandable and easy to use so
that even the novice user can easily learn to use the
system.
Flexibility : It should be flexible in nature to allow
likely changes and alteration in the near future.
Error handling : The system must give response
to errors in clear and precise manner as soon as an
error has occurred.
Integrity : The results produced by the system
should be accurate and reliable.
Functional

and

performance

specifications : The performance of the required

system should be good and should fulfill the
required functional specifications.
most of the events are on-click and the user never
required to enter any commands. So, the staff quickly
learns how to use this project.

-5-

Chapter - 2

SYSTEM
DEVELOPMENT LIFE
CYCLE

-6-

SYSTEM DEVELOPMENT LIFE CYCLE

System development is a process ,which started when
system development personnel feel that a new system or
an improvement in the existing system is required.
Software development life cycle is a sequence of
activities carried out by analyst, designer and user to
develop and implement of an information system.
ANALYST:
An analyst studies the requirements of
a customer or user and defines the problem
domain. He identifies need of an organization to
determine how people method and computer
technology can best accomplish improvement of the
business.
DESIGNER:
A designer design a system in terms of
structure of the database, screens, forms and
reports. He also determines the hardware and
software requirements for the development of the
system.
USER:
User is the one who uses the system
-7-

ACTIVITIES OF SDLC
Recognition of needs
Feasibility study
Analysis
Designing
Coding
Testing
Implementation
Post Implementation and Maintenance
RECOGNITION OF NEED
Recognition of need is a kind of document generated by a
user and problem statement is a written document that
will tell software developer what to develop.

FEASIBILITY STUDY:
In this phase, we access whether or not a project should
be undertaken. This stage involves defining the problem
and fixing up its boundaries.

REQUIREMENT ANALYSIS:
-8-

In this phase the user requirement are studied and

analyzed. The technical development team works with the
customer and system end users to identify the various
requirements related to the system to be developed.
DESIGNING:
This is the phase where new system is designed
according to the needs of the user. In this phase the
specification of each and every component of the project
is laid down.
CODING:
This is the phase where system is actually developed.
The

system

design

is

coded

in

some

suitable

programming language in this phase.

TESTING:
In this phase, the system is judged for all its worth. During
this phase, the developed system is reviewed against
each and every customer requirement specification.
IMPLEMENTATION:
This is the phase in which the development system is
handed over to the client. The old system is dispensed,
new system is put into operation for use and all personnel
are trained to manage and maintain the new system.
-9-

Chapter - 3

RECOGNITION OF
NEED

- 10 -

RECOGNITION OF NEED
The basic of the project is recognition of needs for
improving an information system or a procedure. Thus
the first step in SDLC is the recognition of needs
whose purpose is to evaluate the project request, it is
collection of information that helps the committee
members to evaluate the merit of the project request
and to make an informed judgment about the feasibility
of the proposed project.

PROBLEM STATEMENT
Problem statement was to design a module:
Which will be user friendly.
Which will restrict the user from accessing other
users data.
Which will help the user in viewing his data and
privileges.
Which will help the administrator to handle all
changes.
In which further additions can be made without
changing its design drastically.
Which would restrict the server traffic.

- 11 -

Another problem was that the data should be

accessed from the server and accordingly changes
should be made on the data in the server only.
FUNCTIONS TO BE PROVIDED

The various features that the proposed system will

possess will be:
The system will be user friendly and completely
menu-driven so that users shall have no problem in
using all the options provided.
The system will be efficient and fast in response by
careful programming

- 12 -

Chapter - 4

FEASIBILITY STUDY

FEASIBILITY STUDY
- 13 -

An important outcome in the preliminary investigation

is to determine that the system requested is feasible.
Three

key

considerations

involved

in

feasibility

analysis.
TECHNICAL
ECONOMIC
OPERATIONAL
We determine the performance and cost effectiveness
of the proposed system and constraints, it is
recommended in feasibility report.
Technical feasibility
There are number of technical issues which generally
raised during the feasibility stages of investigation which
are as follows: Does the necessary technology exist to do what is
suggested?
Does the proposed equipment have the technical
capacity to hold the data required to use the new
system?
Can the system be upgraded if developed?
Are

there

technical

guarantees

of

accuracy,

reliability, ease of access and data security?

- 14 -

The proposed system is technically feasible because

visual basic 6.0 on windows 98 on client and MS Access
on the server are compatible and support the program
and database design quite efficiently.
Economic Feasibility
Also referred to as cost benefit analysis, is the most
frequently used method for evaluating the effectiveness of
a proposed system. The focus is to determine the benefits
and savings that are expected from proposed system and
compared them with cost. if benefit outweigh cost then
the decision is made and implement the system.
Our proposed system needs only a few
softwares and printer along with a few computer
operators. Keeping in a view the long-term benefits
provided by this proposed system, these inputs costs are
minimum.
Operational Feasibility
Operational feasibility is mainly related to human
organizations and political aspects. The points to be
considered: What changes will be brought with a system?
What organizational structures are disturbed?

- 15 -

 What new skills, if not; can they be trained in due

course of time?
Our proposed system is aimed to simplify the job without
bringing much change in way of working of existing
system.

Chapter - 5

ANALYSIS

- 16 -

REQUIREMENT ANALYSIS
It is the detail study of the various operations performed
by the system and their relationship with in & outside the
organization. The key question is:
What must be done to solve the problem?
Tools used in analysis are DFD, interviews, onsite
observations & questionnaires. Training, experience &
common sense are required for the collection of
information needed to the analysis. System analysis is the
fact finding followed by analysis of the facts. Data
analysis is also considered a pre requisite condition for
cost/benefit analysis. System analyst is a person who
conducts the system study and identifies the activities and
objectives, formulate the set of roles to achieve the
objects. His main activities are system analysis is the fact
finding followed by analysis of the facts. Data analysis is
also considering a pre-requisite condition for cost/benefit
analysis. Requirement analysis plays an essential role in
the SDLC.
One of the most difficult aspects of program development
is in getting both the customer & developers to
understand what each of them is trying to say.
The techniques, which we have used for requirement
gathering for the present project, are interviews and
observations. First of all we interviewed INSTITUTE and
- 17 -

requested details about the present project by asking

various questions.
What is the purpose behind developing the present
software?
What all functioning

he intents to get in the

purposed software?
What all the benefits he intends to get in the
perposed software?
Next , we personally observed their working for 3-4 days
to get a clear cut idea of how they work in their daily
routine and their present style of work with regard to
maintenance of records.

- 18 -

SOFTWARE REQUIREMENTS
SPECIFICATION

Software requirement and specification

is a document

that completely describes what the proposed software

should do without describing how the software do it. The
basic goal of the requirement phase is to produce the
SRS , which describes the complete complex behavior of
the proposed softwares forces the other to identify the
requirements .
Hence the main advantages are:
An SRS establish the basis for agreement between
the client and supplier on what the software product
will do.
An SRS provides a reference for validation of the
final product .
A high quality SRS is a pre-requisite to high-quality
software.
A high quality SRS reduces the development cost.
SOFTWARE REQUIREMENTS
Front end- vb.net
Back end- MS-Access

- 19 -

HARDWARE REQUIREMENTS
Processor Pentium 4 or Higher.
Monitor: - Color Monitor Having Pixel Setting
(800*600), True colors.
Hard Disk: - 80GB or more
RAM: - 512MB RAM or more
Floppy Disk Drive: - 1.44
Mouse Keyboard.
Printer

- 20 -

Chapter - 6

DESIGNING

- 21 -

DESIGNING

The most creative and challenging phase of the system

development life cycle is system design . The
design describes a final system and the

term

process by

which it is developed , i.e. we have moved from logical to

physical aspect of life cycle, the key question in case of
designing is
How the problem should be solved?
The

first step is to determine how the output is to

produced and in what format. Samples of input and output

are also presented. The second step is
input data and the master files have to be designed to
meet the requirement of the and an impact of the system
on the organization are document and

evaluated by the

management .
A lot of factor
preparing

are taken into

good

system

consideration while

design

which

includes

performance analysis , security and control , system

prototyping

designing

user

interface

design

documentation and reviews etc. In the context

of

present project , great care and attention has been

provided to ensure proper security ,password have been
use to restrict access

only to the authorized user .

Moreover ,In order to make the software easy to use, a

- 22 -

user interface that is very much user friendly has been

used with a lot of useful tips displayed while feeding and
retrieving information.

- 23 -

Chapter - 7

DATA FLOW
DIAGRAMS

- 24 -

Data Flow Diagram (DFD)

Data Flow Diagram is another tool use to describe the

design specification. It is also a Pictorial representation of
data flow. The only difference between Flowchart and the
Data Flow Diagram is that DFD show only the flow of data
not the actual procedure or coding to perform that
function. On the other hand Flowchart Show the actual
calculation to perform the task.

The different symbol use in DFD are: SQUARE:

Describe the Source and Destination of data
or information. The Source Must is written
in capital letters.

BUBBLE:
A Circle used to show the Process. These
can be number of process in a program.
Each process must be assign a suitable
number

- 25 -

OPEN RECTANGLE:
An Open Rectangle Used to describe the
storage of database

ARROWS AND LINES:

Arrow Used to shoe the flow of Data . A

DFD can be drawn from top to bottom or
from left to right .

SOME COVENTIONS WHILE DRAWING DFDs:

All external files should always be shown in the

DFD as labeled straight line.
The need for multiple dataflow by the process is
represented by * between the dataflow. Similarly
the or relationship is represented by + between
the data flows.
DFD should not represent procedural information.
So, while drawing a DFD.
One must not involve in the procedural details.
- 26 -

CONSTRUCTING THE DFDs:

Several rules of thumb are used in drawing

DFDs:
Processes should be named and numbered for
easy

reference.

Each

name

should

be

representative of the process.

The direction of flow is from top to bottom and
from left to right.
The

names

of

data

stores,

sources

and

destination are written in capital letter. Process

and data flow names have the first letter of each
word capitalized.
Work your way consistently from the inputs to the
output or vice -versa.
Never try to show control logic like loops or
decisions.
Label each arrow with proper data elements.
Input and output should be carefully identified.
Make use of star and plus operations to show
sufficient details in the data flow graph

- 27 -

Chapter - 8

SNAP SHOTS

- 28 -

SPLASH SCREEN

- 29 -

LOGIN SCREEN

- 30 -

MDI SCREEN

- 31 -

CREATE NEW LOGIN

- 32 -

CHANGE PASSWORD

- 33 -

ADD NEW ROUTE SCREEN

- 34 -

ADD /Update Bus Fare SCREEN

- 35 -

New Booking Screen

- 36 -

Ticket Print

- 37 -

Cancel Booking Screen

- 38 -

All Routes Report

- 39 -

All Bookings Report

- 40 -

Chapter - 9

DEVOPLEMENT
TOOLS

- 41 -

ABOUT MS ACCESS
MS Access is a Relational Data Base Management
System. In MS Access has much advantage over other
DBMS. The user can create Table and store related data
in it. MS access provides easy way to create tables we
can create tables in design mode or by using the in build
Wizards. User can also create form layout in MS Access.

To create table in MS Access follows These Steps.

1) Start MS Access form Start -> Program File -> MS
Office -> MS Access.
2) In the File Menu Select New to create new database.
3) MS Access Ask You to save the database name in
specified location. Type the file name in file save dialog
box and click save button.
4) MS Access opens a table design window in which you
can design the table by using design view of by using
wizard.
5) Select Create Table in Design View to open design
table windows
6) Here you can type the field name, specify the data type
and the size of the fields. This window also allows the
user to define the different constraints like Primary Key
constraints and Not Null Key constraints.
- 42 -

7) Select save button in tool bar to save the table by

giving a suitable name.

- 43 -

THE TABLE DESIGN WINDOW

To attach the MS Access with Visual Basic the three

major tools are widely used.

1) The Data Control

2) The Data Access Object (DAO)
3) The Active Data Object (ADO)
Data Control

With data control we can access database without any

programming. We can set to property of data control i.e.
Database name to database, and Record Source to table
- 44 -

name. We can display the data in regular controls like

textboxes etc.
The Data Access Object
The Data Access Object is a structure of object s for
accessing database through VB code. All the function of
Data Control available in VB Code.

- 45 -

Record Sets

Record Sets are the objects that represent collection of

records

from

one

or

more

tables.

In

database

programming, Record Sets are equivalent of a variable in

regular programming. We can access a table directory via
a Record Set Object. A Record Set is constructed of
columns and rows and is similar to a table, but it can
contain data from multiple tables. The Record Set work
like a bridge between the Visual Basic and The Database.
There are three types of Record Sets
1) DynaSets, which are updateable views of data
2) Snapshots, which are static (read-only) views of data
3) Tables, Which are direct views of tables.

To Connect: (Examples)
Database Name: INSSTITUTE
Table Name : FEE
Start VB DOT NET, select Project ->
References.
In

the

References

dialog

box

Microsoft DAO 3.6 Object Library.

- 46 -

select

 In the general section of the form declare

two variables like.
Dim Db as Database
Dim RS as Record Source
T0 connect follow this code:
Set db = open database (c:\abc\insstitute.mdb)
Set rs = db.OpenRecordSet(Select * from fee)
Now by using rs object we can access each fields of the
room table.

The SQL Statements

The SQL statements are used to extract data from a
database. SQL statements are basically Record Set
definitions. With SQL statements we can extract data from
multiple table at a given time. We can make query, sub
query with SQL statements. The SQL Statements are
beginning with the SELECT statement.

- 47 -

Chapter - 10

VB. NET

- 48 -

What is .NET?
.NET represents an entire range of technologies and
concepts that form a platform on which you can develop
applications. Visual Basic .NET does have an actual
version number, 7.0 the number just isnt used often.
Just as windows 2000 is really Windows NT version 5.0,
the simpler or catchier name will generally be the one
commonly used. Dont expect to hear Visual Basic 7.0
often though; there was even a cash penalty inside
Microsoft for referring to windows 2000 as NT 5.0. .NET is
a layer that exists beneath your programs and provides a
set of base services and functions. This layer contains a
set of applications and operating systems called the .NET
servers; a foundation set of objects called .NET
framework, and a set of services that support all the .NET
languages, called the Common Language Runtime
(CLR). .NET is more than just one thing; it is a collection
of software and concepts that work together to enable the
creation of business solutions.

- 49 -

.NET Servers
A major goal of the .NET concept is to decrease the
building of distributed system, in which the work is done in
several different locations. For the most part, these types
of systems do their work on the back end, at the server
level. Microsoft provides a set of Software products that
together are known as the .NET Enterprise servers. They
are designed to supply the back end features needed by
a distributed system. These products include
The server operating system, Microsoft Windows
Clustering and load balancing software such as
Microsoft App Center and Microsoft cluster server.
A database server, Microsoft SQL server
An e-mail, collaboration, and free-form information storage
System, Microsoft Exchange Server
A data-transformation engine based around XML called
Microsoft Biz Talk Server
A server for accessing legacy systems, such as AS/400s, called
Host Integration server
And more..
Together these servers supply base services to .NET
applications, forming the foundation of systems.

- 50 -

.NET Framework
In the move to Visual Basic .NET, many things have
changed radically; one of them is the development of a new
foundation to all the .NET develo0pment

tools. This

foundation, known as the .NET framework, provides two key

things: the base runtime environment and a set of foundation
classes. The runtime environment is similar to the operating
system in that it provides a layer between your program and
the complexities of the rest of the system, performing services
for your application and simplifying access to the functionality
of the lower layers. The foundation classes provide a large set
of functionality, wrapping, and abstraction such technologies
as Internet protocols, file system access, XML manipulation,
and more. The .NET framework is similar in many ways to the
operating system, and it provides its own set of APIs to make
it easy for programmers to take advantage of its capabilities.
Figure illustrates the frameworks relationship to your code
and to the underlying services of the operating system.

- 51 -

Chapter - 11

TESTING

- 52 -

TESTING
No program or system design is perfect; the
communication between the user and the designer
is not always clear, and time is usually short. The
result is errors and more errors. So before
implementing the system it should be first tested. It
is

tedious

but

necessary

step

in

system

development. There are various testing techniques

which are discussed below with the information
that how they are applied to present system. The
testing of software is done module wise.
VALIDATION CHECKS
Software validation is achieved through a series of
black-box

tests

that

demonstrate

conformity

with

requirements. A test plan outlines the classes of tests to

be conducted and a test procedure defines specific test
cases that will be used to demonstrate conformity with
requirements.
After each validation test case has been conducted, one
of two possible conditions exists:

- 53 -

(1) The function or performance characteristics conform

to specification and are accepted
or
(2) A deviation from specification is uncovered and a
deficiency list is created.
CONFIGURATION REVIEW
An important element of the validation process is a
configuration review. The intent of the review is to ensure
that all elements of the software configuration have been
properly developed, are cataloged, and have the
necessary detail to bolster the support phase of the
software life cycle. The configuration review, sometimes
called an audit.
ALPHA AND BETA TESTING
If software is developed as a product to be used by
many customers, it is I impractical to perform formal
acceptance test with each one. Most software product
builders use a process called alpha and beta testing
uncover errors that only the end-user seems able to find.
A customer conducts the Alpha test at developers site.
The software is used in a natural setting with the
developer looking over the shoulder of the user and
recording errors and usage problems. Alpha tests are
conducted in a controlled environment.
The Beta test is conducted at one or more customer sites
by the end-user of the software. Unlike alpha testing, the
developer is generally not present. Therefore, the beta
- 54 -

test is a live application of the software in an environment

that cannot be controlled by the developer. The customer
records all problems (real or imagined) that are
encountered during beta tasting and reports these to the
developer at regular interval

- 55 -

Chapter - 12

IMPLEMENTATION

- 56 -

IMPLEMENTATION
A crucial phase in the system life cycle is the
successful implementation of the new system designed.
Implementation includes all those activities that take place
to convert from the old system to the new one. The new
system may be completely new, replacing an existing
manual or automated system or it may be major
modification to an existing system. In either case, proper
implementation becomes necessary so that reliable
system based on the requirements of the organization
can be provided.
Implementation includes:
Training of personnel
Conversion procedures
Post-implementation review or evaluation

- 57 -

TRAINING OF PERSONNEL:
The high quality training is an essential step in
systems implementation. Hence to provide the training to
personnel they have been provided user manuals. They
are asked to read it carefully and same thing try
practically on computer. If they dont understand any
thing, can ask without any hesitation. They are asked to
enter the data, which is more frequently entered, and print
the reports are frequently printed. Users are told about
those situations, which he must understand and he
should able to handle it.
CONVERSION METHOD :
The direct conversion method is applied. This
method converts from old to the new system abruptly. The
old system is used till a planned conversion day. The
organization relies fully on the new system.

- 58 -

Chapter - 13

POST
IMPLEMENTATION

- 59 -

POST IMPLEMENTATION
After the system is implemented and conversion is
complete, a review is conducted to determine whether
system is meeting expectations and where improvements
are needed. A post implementation review measures the
systems

performance

requirements.

It

against

pre-determined

determines how well

the system

continues to meet performance specifications. It also

provides information to determine whether major redesign or modification is required. In evaluation system is
checked against the pre-determined requirements. All

the requirements have been fully attained. Where

there was any mistake that had handled through
system life cycle. Problem is solved and checked
against the original facts.
REVIEW PLAN:

For review a team is planned. The Team shall

prepare a formal plan around the objectives of the
review. An overall plan covers the following areas:
ADMINISTRATOR PLAN :
- 60 -

Review area objectives, operating costs,

actual

operating performance and

benefits.

- 61 -

Chapter - 14

SYSTEM
MAINTENANCE

- 62 -

SYSTEM MAINTANENCE:
The last part of system development life cycle
is system maintenance, which is actually the
implementation of the post-implementation plan.
Hence Programmers/ Analyst spends sufficient
time for maintaining programs.
Hence maintenance will cover a wide range
of activities including correcting coding and design
errors, updating documentation and test data and
upgrading user support. Many activities classified
as maintenance actually fall under enhancements.
Hence in maintenance of system enhancement
also takes place. Therefore in maintenance
addition, modification, re-developing of code will
take place to support changes in specification.

- 63 -

BIBLIOGRAPHY

- 64 -

BIBLIOGRAPHY:
1. System Analysis and Design BY Elias
Galgotia Publications.
2. Software

Engineering

By

Roger

S.

Pressman, McGraw- Hill Publications.

3. MS-ACCESS: BPB Publications
4. Mastering in VB.Net By BPB Publications.
5. VisualBasic.Net Programming, Black Book.

- 65 -