OF

Shri Krishana Tour & Travel

Submitted in partial fulfillment of the requirement of the degree

Master of Computer Application

of
PUNJAB TECHNICAL UNIVERSITY

Under the Guidance of

Submitted by: Shivi Papneja

DEPARTMENT OF COMPUTER SCIENCE

PUNJAB TECHNICAL UNIVERSITY

LUDHIANA
 CERTIFICATE

This is to certify that this project entitled “OFFICE

AUTOMATION SYSTEM” submitted by Shivi Papneja to Punjab
Technical University, Jalandhar, is an original work and has not
been submitted earlier either to Punjab Technical University or to
any other Institution for fulfillment of the requirement of a course
of study.

Date:

____________________________

Project Guide Head of the Institute

 STUDENT DECLARATION

We hereby declare that project report entitled

“Shri Krishana Tour & Travel”

In “PTU LEARNING CENTRE, LUDHIANA” submitted by Shivi

Papneja in Partial fulfillment of the requirement for MASTERS OF
COMPUTER APPLICATION to “Punjab Technical University
Jalandhar”, is an original work and has not been submitted for
the award of any degree/ Diploma/Scholarship or any other title
or prizes.

Place: Ludhiana Shivi Papneja

Date:
 ACKNOWLEDGEMENT

It has been a great privilege to conduct the present project

under the aegis of our Project Guide Mr. Department of
Computer Science. Our sincere thank and deep gratitude is due to
his effective guidance and encouragement, which gave us the
confidence to complete the project work.

We are also grateful to Mr. , Head of the Institute for all

their support during the project.
Our cordial and sincere thanks are to all the teachers of
Department of Computer Science.

We are deeply indebted to our families and our friends for

their unconditional support, deep affection and unabated
inspiration, which kept us going.

We wish to thank all the respondents who extended their

whole-hearted cooperation in carrying out this study.
Last but not the Least, we thank God who always showers
His blessings upon all of us.

Ludhiana Shivi

Date:
 PREFACE

Practical knowledge is an important suffix to theoretical

knowledge. One cannot merely rely upon the theoretical
knowledge. Classroom lectures help us to understand the
fundamental concept and also facilitates the learning of practical
things. However, these lectures must be correlated with the
practical training situations.

So this report is an effort to integrate all the aspects of the

programming (front end & back end), system analysis, system
design, data management, networking & implementation. In the
programming side the report tries to give the advantage of SQL
EXPRESS whish provides powerful, flexible, simplified Data Access
& Visual Basic which offers fast, automatic formatting of code.

A number of figures and screen captures are provided in the

report to make it attractive and more readable.
In all a best effort have been made from our side to make this project a
success.
 PROJECT

A Project is a series of activities taken by a programmer to

practically apply and implement the knowledge gained during
course of study.

In general one can say that a project is not a physical

objective, nor is the end result. It has something to do with the
going in-in between, which must be same, whether we built a
high technology process plant or merely hold an election, it is
termed as a project.
Starting from the mission, planning activities involved to
reach the goal, resources required and their utilization for the
same till the mission is fulfilled all constitutes the project.
The goal or requirement of a project decides the path and
mode wise that a project is to be executed.
 PURPOSE

Learning by doing is a trusted concept. A project provides an

opportunity to the student to implement the concept in real life
situation while reflecting their special area of interest.
It is putting one’s knowledge gained to real test. The effort put
into planning and executing through different stage till end goal is
achieved give a practical experience to the student. And practical
experience is must in each and every aspect of life. One
encounter many difficulties on the way add to one’s experience.

The experience gained in real situation can never be achieved

without going through the whole process oneself.
 OBJECTIVE OF PROJECT

The aim of the project is to highlight different aspects of software

development like: Modular programming, optimizing code
preparation, program and data flow representation. It should
have the following features:
►Easy Interface: Aim of any project is to fulfill the goal for
which it had been created. The interface is easy to understand.
The user feels comfortable while working on it i.e. it should be
user friendly.
►Easy to update: Changes have to be made because errors are
encountered when the end user uses the product. The software
has to be adapted to the changing external environment e.g. new
operating system or peripheral device. The customer may require
new additions or enhancements.
►Documentation: It should have a good documentation to
ensure readability and ease of maintenance.
 DEVELOPMENT PROCESS OF SOFTWARE

A development process consists of various phases ending with

defined output. The phases are performed in an order. The
phases break the problem of development software, so that each
handling a different concern of software development. This
results into the low cost of development of the software. A
phased process allows proper checking for quality and progress at
some defined points during the development.
Different process models have been proposed for developing
software. The different process can have different activities. In
general, any problem solving in software must consist of these
activities requirement specification: - for understanding and
clearly stating the problem, design for deciding plan for a
solution, coding for implementing the planned solution and
testing for verifying the program. For small problems, these
activities may not be done explicitly. The start and end
boundaries of these activities may not be clearly defined. These
phases are shown in our model on next page.
 SDLC DATA MODEL:

The linear sequential model

(HIERARCHICAL MODEL)
 SDLC Phases

Problem Analysis - An effort to understand the purpose of the

software & problems faced by company.
SRS Documentation – Software requirement specification,
collecting the requirement of the client to furture plan the
working of project.
Design Phase – Draft of the design & data flow diagam of the
software, which finally resuts to the actual designing of the
software, i.e. forms etc.
1. logical design
2. physical design
Development – Developing the code for the software & attaching
it to the forms.
Testing – Testing the softwarewith acual values & checking if the
software provides the functionality required by the client.
 Integration testing.
 System testing.
 Acceptance testing.
Deployment & Implementation of the software - creating
distributable file like exe to be deployed at client machine
Maintainance – Last but not the least to maintain the software,
in case of any upgradation, addition, etc. at the time of client
requirement.
 S/w REQUIREMNT ANALYSIS

Requirement analysis is done in order to understand the

problem, which the software system is to solve. The problem
could be automating an existing manual process, development a
new automated system of a combination of the two. The
emphasis in requirements analysis is on identifying what is
needed from the system, not how the system will achieve the
goals.

This task is complicated by the fact that there are often at

least two parties involved in software development i.e. client and
a developer. The developer has to develop the system to satisfy
the client’s needs. The developer usually does not understand the
client’s needs. The developer usually does not understand the
issues involved in software system. This causes the
communication gap, which has to be bridged during requirement
analysis.

This phase ends with a document describing all the

requirements. The goal of this phase is to produce the software
requirement specification document. The person responsible for
the requirement analysis is often called the analyst.
There are two major activities in this phase: problem
understanding analysis and requirement specification. The analyst
has to understand the problem and its context. This requires a
thorough understanding of the existing system, parts of which
has to b automated. A clear understanding is needed of the
important data entities in the system, major centers where action
is taken, the purpose of the different action that are performed,
and the inputs and the outputs.
 SOFTWARE DESIGN

The purpose of the design phase is to plan solution of the

problem specified by the requirement document. This phase is
the first step in moving the problem domain to the solution
domain. This starts with what is needed, design takes us towards
how to satisfy the needs. The design of a system is perhaps the
most critical factor affecting the quality of the software. It has
major impact on the later phases, particularly testing and
maintenance. The output of this phase is to design document.
This document is similar to a blueprint or plans for the solution
and is used during implementation, testing and maintenance.

The design activity is often divided into different phases-system

design and detailed design. System design, which is sometimes
also, called top-level design, aims to identify the modules that
should be in the system, the specification of these modules, and
how they interact with each other to produce the desired results.
At the end of system design all the major data structure, file
formats, output formats, and the major modules in the system
and their specification are decided.

In detailed design, the internal logic of the module specified in

the system design is decided. During this phase further details of
the data structures and algorithmic are design of each of the
modules is specified. The logic of a module is usually specified in
high-level description language.
 CODING

Once the design is complete, most of the major decisions about

the system have been made. The details about coding the design
depend on the programming language chosen. The goal during
the coding phase to translate the design of the system into code
in a given programming language i.e. the design is to be
translated into a machine-readable form.
The coding phase affects both the testing and maintenance
efforts. Well-written code can reduce the testing and maintenance
efforts during coding the focus should be on developing programs
that are easy to write. Simplicity clarity should be starved for
during the coding phase.
An important concept that helps the understanding of programs is
structured programming. The goal of structured programming is
to linearize the control flow in program. The program should be
organized as sequence of statements, and during execution the
statements are executed in sequence given in the program. For
structure programming, a few single entry-exit constructs should
be used. These constructs include selection (if-then-else) and
iteration (while-do, repeat until, for loop). With these constructs
it is possible to construct a program as a sequence of single-
enter-single-exit constructs
 TESTING

Testing is the major quality measure used during software

development. Its basic function is to detect errors in the
software. During requirement analysis and design, the output is a
document that is usually textual and non-executable. After the
coding phase computer programs are available that can be
executed for testing purposes. This implies that the testing will
uncover the errors introduced in coding phase as well as earlier
phases. Testing starts with unit testing. In this each module is
tested separately and is performed by the programmer
simultaneously along the coding of the module. During
integration of modules, integration testing is preformed to detect
design errors y focusing on testing the interconnections between
modules. System testing is done after integrating testing. The
system is tested against the system requirements to see if all the
testing. The system is tested against the system requirements to
see if all the requirements. Finally acceptance testing is
performed to demonstrate to the client, on the real-life data of
the client, the operation of the system. Software typically
undergoes many levels of testing from unit testing to system or
acceptance testing. In high-order the entire software is tested
with the focus on testing the functionality or external behavior of
system.
Testing classes are fundamentally different from testing function,
as a function has a clearly defined input-output behavior, while a
class does not have an input-output behavior. We can test a
method of a class using approaches for function testing, but a
class cannot be tested using these approaches, so for testing
methods individually, the control flow-based and data-flow based
structural testing techniques can be applied.
 LEVELS OF TESTING

The basic of testing are unit testing, integrated testing and

system acceptance testing. These different levels of testing
attempt to detect different types of faults.
The first level of testing is called unit testing. The different
modules are tested against the specification produced during
design of the modules. The internal logic of the modules is
checked.
The next level of testing is often called integration testing.
Different modules are combined into subsystem, which is then
tested.
The next levels are system testing and acceptance testing; the
entire software system is tested. The reference document for this
purpose is the requirements document and then goal is to see if
the software performed with realistic data of the client to
demonstrate that software is working satisfactorily.
In this case of the entrance examination system the modules are
generated step by step and then unit testing is performed.
Like/*student* data module, query module etc. then these are
integrated and system testing is done by executing the system
software and in order to perform the acceptance testing some
data from imaginary answer sheets are entered in order to
execute the software.
 IMPLEMENTATION

Implementation is the process of having system

personnel check and put new equipment into use, train user,
install the application and construct any files of data needed to
use it. This phase is less creative that system design. Depending
on the size of the organization that will be involved in using the
application and there risk in its use, software developer may
choose the testing the operation in only one area of organization
with only one or two persons. Sometimes, they will run both old
and new system in parallel way to compare the results, I some
situations, software developers stop using the old software one-
day and start using the new one the next.
Evaluation of the software is performed to identify its
strength and weakness.
The actual evaluation can occur along the following
dimensions:
1. Operational evaluation: Assessment of the manner in
which the software functions, Include ease of use, response
time, overall reliability and level of utilization.
2. Organizational impact: Identification and measurement of
benefits to the organization in such areas as financial
concerns, operational efficiency and competitive impact.
3. User manager assessment: Evaluation of the attitude of
senior and user manager within the organization, as well as
end users.
 MAINTENANCE

Software maintenance is defined as the process of

modifying a software product, component, or system subsequent
to delivery and installation that corrects faults, improves product
performance or other product attributes, or adapts the product to
a changed operational environment.
It is safe to say that day that a large software product
goes into service, functional, performance operator and
environmental requirements will undergo changes. Moreover the
delivered software product will contain some latent defects that
were not detected during testing. S/w maintenance can be
divided into corrective actions to fix latent defects, adaptive
actions to deal with changing environments, and perceptive
actions to accommodate new requirements. To conduct an
effective maintenance action, s/w configuration control, good
quality documentation is extremely helpful. Maintenance activities
test the quality of the software, the quality of SRS and SDS and
the ability of architecture to accommodate growth and functional
additions or changes.
 Hardware Requirement

~ An IBM Compaq personal computer with

 Minimum 1 GB Ram, 2 GB recommended
 Minimum 12 GB of free HDD
 Monitor with min 640*480 resolution
 Keyboard and Mouse

Software Requirement

This software requires the following softwares pre installed on the

computer under stand alone conditions
● Windows 2000 and above
● Microsoft Visual Basic 6.0
 WHAT IS A DATABASE?

It is coherent collection of data with some inherent meaning,

designed, built and populated with data for a specified purpose. A
database stores data that is useful to us. This data is part of
entire data available in the world around us. To be able to
successfully design and maintain databases we have to do the
following:
1. Identify which part of world’s data is of interest to us.
2. Identify what specific objects in that part of world’s data are
of interest to us.
3. Identify a relationship between the objects.

WHAT IS A RDBMS?

A relational database management system (RDBMS) is a

database management system (DBMS) that is based on the
relational model as introduced by E. F. Codd. Most popular
commercial and open source databases currently in use are based
on the relational database model.
While relational database systems remain the dominant
choice for both transactional and analytical applications, newer
structures are competing with RDBMSs in data warehouse
applications including column-oriented and correlation database
systems.