Maintenance types and severity levels in Bus Reservation System
BUS RESERVATION SYSTEM
INTRODUCTION
Travelling is a large growing business across all contries. Bus
Reservation System deals with maintenance of records of details of each
passenger. It also includes maintenance of information like schedule and
details of each bus. In the existing systems they have to do many works
manually. It takes a lot of time and causing many errors while data entry. Due
to this, sometimes a lot of problems occur and they were facing disputes with
customers. To solve the above problem, and further maintaining records of
passenger details, seat availability, price per seat and other things, we are
offering this proposal of computerized reservation system.
PROBEM STATEMENT
Bus Reservation Systems
that were suggested
till now, are not up to the desired level. There is no single system which
automates all the process.
In order to build the system, all the processes in the business should be
studied, System study helps
us under the problem and needs of the application. System study aims at
establishing requests for the system to be acquired, development and installed.
It involves studying and analyzing the ways of an organization currently
processing the data to produce information. Analyzing the problem thoroughly
forms the vital part of the system study. In system analysis, prevailing
situation of problem is carefully examined by breaking them into sub problems.
Problematic areas are identified and information is collected. Data gathering
is essential to any analysis of requests. It is necessary that this analysis
familiarizes the designer with objectives, activities and the function of the
organization in which the system is to be implemented.

Existing system
· Existing
system is totally on book and thus a great amount of manual work has to be
done. The amount of manual work increases exponentially with increase in
services.
· Needs a lot of working staff
and extra attention on all the records.
· In existing
system, there are various problems like keeping records of items, seats
available, prices of per/seat and fixing bill generation on each bill.
· Finding out details regarding
any information is very difficult, as the user has
to go through all the books manually.
· Major problem was lack of security.
Proposed system
The system is very simple
in design and to implement. The system requires
very low system resources and
the system will work in almost all configurations. It has got following
features:
·
Needs a lot of working staff and extra attention on all the records.
· Ensure data accuracy.
· Records are efficiently
maintained by DBMS.

A software has to be developed for automating the manual bus reservation
system. The system should have distributed functionalities as described below.
1.RESERVE SEAT
A passenger should be able to reserve a seat in the
train specified by him if available. For this he has to fill reservation form
with the details about his journey. The clerk checks for the availability of
the seat in the bus and if the seat available then he makes entries regarding
bus name, bus number, date of journey, boarding station, destination.
2.CANCEL RESERVATION
There may arise a case when the passenger wants to
cancel his reservation. For this he has to fill a cancellation form providing
all details about the bus reserved by him. The clerk then checks for the
entries from the database and cancels the reservation finally returning the
ticket amount with some deduction.
3.LOGIN
Only the user with specified login id & password
can get access the system. This provides security from unauthorized access.
4.
IEW RESERVATION STATUS
All the users should be able to see the information
about the reservation status & bus schedule, train name, bus number.

TYPES OF MAINTENANCE
CORRECTIVE MAINTENANCE
It is reactive modification of a software product
delievery to correct discovered problems.
PERFECTIVE MAINTENANCE
Is concerned with the change
in the software that occurs
while adding new functionalities in software.
ADAPTIVE MAINTENANCE
It is usable in a changed or changing environment.
Adaptable to new environment such as to run software in different OS.
PERFECTIVE MAINTENANCE
Modification
of a software product after delievery to detect and correct
latent faults.
Problems
|
Types of maintenance
|
After delievery of the BRS, inspite of correct username and password
the system show invalid messages.
Incorrect details in the view reservation status
like bus number, destination etc.
Incorrect information about the transcation the
amount and refunding.
|
Corrective Maintenance
|

Adding of new functionalities into the system like update bus
information and report generation will not cause any error to the system like
slow performance, incorrect behavior etc. The system will perform same with the
addition of new functionality.
|
Perfective Maintenance
|
The system should be able to run in
any platform like android, desktop with different OS.
The system able to perform the same in all the platforms. Some
Functionalities should be supported in desktop and not supported in mobile
phones this should be avoided.
The system should be developed for
both desktop and mobile
application.
|
Adaptive Maintenance
|
Modification of a functionalities after delievering the system based
on the user finding the errors when using the
information.
The user may find incorrect bahaviour
of the system, wrong
results etc
|
Preventive Maintenance
|



PROBLEM RESOLUTION
PROBLEMS
|
CATEGORIZE
|
LEVELS
|
SOLUTION
|
Computer loses power or crashes when you book the ticket there is a
possibility in loss of data.
|
Types of software (Disk Corruption)
|
Severity-1
|
Use
strong RAID encoding.
Backup to
multiple nodes.
Backup prevents
the
Disk corruption.
|
Compilers also affects the implementation of the c++program
in
windows 7.
|
Development tools (Compilers)
|
Severity-1
|
Use linux which will have gcc preinstalled.
|
Sometimes when you book the ticket with payment.sometimes the loss of transaction
occurs due to slow of internet acces etc Showing of incorrect results foe you
showing the
transcation
|
Internet Software (Loss of transaction)
|
Severity-1
|
Check your strength internet connection before doing transcation
processing.
|


successful but not updated in
database.
|
|
|
|
Sometimes the
system performance is
slow.Inspite of correct username and password the users may not able to
login.
|
Database software
|
Severity-1
|
This occurs because of problems in the updation of database. This
should be check by the development team of the software
and rectify it.
|
In bus reservation system the main functionality is
viewing reservation status this
functionality shows incorrect details to the user and in somecase sthe
functionality may
fail.
|
Application Software
|
Severity-1
|
The all functionality should be designed in well and secured manner.
This may be avoided.
|
Sometimes the
system
|
Performance is
slow
|
Severity-2
|
The sytem should
be maintained and
|


performance is
|
|
|
allow ceratin
|
slow because of
|
amount of users
|
||
many users handle
|
for a particular
|
||
the system at a
|
time.
|
||
time.
|
|
||
Customer find
|
Finding wrong
|
Severity-2
|
The coder wants
|
wrong results like
|
results
|
|
to design the
|
the date of booking,
|
|
|
system in a error
|
bus number
|
|
|
free and test cases
|
|
|
|
should be checked
|
|
|
|
before releasing
|
|
|
|
the software.
|
Minimal
|
Minimal
|
Severity-3
|
The error should
|
performance of the
|
performance
|
|
be checked and
|
software due to the
|
|
|
rectified.
|
error of the
|
|
|
|
software.
|
|
|
|
Incorrect behavior
|
Sotware error
|
Severity-3
|
The system
|
of the system with
|
|
|
should be easy to
|
the impact on the
|
|
|
operable. The
|
operation of the
|
|
|
functionalities
|
system.
|
|
|
should be clearly
|
|
|
|
defined.
|
Comments
Post a Comment