GOVERNMENT POLYTECHNIC COLLEGE

KOTHAMANGALAM

Project

Report On

KMRL
Submitted by

Alif P S(18130851)
Aswin Manikuttan(1713)
Aravind
Krishna(18130867)
Ebin Baby(18130877)
Muhammed Razi(18130885)

DEPARTMENT OF COMPUTER

ENGINEERING 2019-2020
 KOTHAMANGALAM

DEPARTMENT OF COMPUTER ENGINEERING

2019-2020

CERTIFICATE
This is to certify that this project report entitled “KMRL“ is submitted by Muhammed
Razi(18130885), Aswin Manikuttan(), Alif PS(18130851), Ebin Baby(18130877) and Aravind
Krishna(18130867) of Final Year Computer Engineering, Government Polytechnic College
Kothamangalam in partial fulfillment of the requirements for the award of Diploma in Computer
Engineering under the board of Technical Education during the Academic year 2020-2021.

Seminar co-ordinator Head of Department

Internal Examiner External Examiner

 ACKNOWLEDGEMENT

First of all I submit all glory and honor to ‘God Almighty’ for his eternal love and
protection throughout the project. The tremendous amount of help that I received from
a number of people gave me the incentive to complete this project to the best of my
capability.

This project work is the ultimate result of the help and encouragement provided by
many who extended their helping hand and inspired me in the completion of this
course of study and have given support in the submission of my project work. I would
like to express my deep sense of gratitude and acknowledgement for all the help,
inspiration and guidance received throughout the project.

I would like to express my gratitude to Mr. Aiju Thomas , Principal, Govt.

Polytechnic College Kothamangalam, for giving me the opportunity to do this project.

I am also indebted to Mrs. Maya Ben N A, Head of the Department, Computer

Science & Engineering, for her valuable suggestions, supervision and glittering
guidance.

I owe special thanks to the staff-in-charge Mr. Jiby P Joseph, Mrs. Remya
Velayudhan for the corrections, suggestions and sincere efforts to co-ordinate the
project.

I would be failing in my duty if I do not extend my thanks to rest of the learned and
caring staff members of the department for their valuable suggestions and constructive
criticisms.

Finally, I thank sincerely all my team members without whom this project cannot be
completed. Last but not the least I thank my good friends who gave me all the help in
times of trouble.

MUHAMMED RAZI

i
VISION To be an assistant for peoples who daily depend on kochi metro as a travel
assistant.

MISSION To reduce the strain of peoples like students,workers.etc, on the

process of building their future and work as a platform for jobless
peoples to find a best one in metro.
 ABSTRACT

“KMRL “is developed to provide the online tickets to the users and the complete information
related to the METRO system. In this site administrator is the main user and he maintains and
manages the site. Administrator provides an opportunity for the user to know the job vacancies
of KMRL through the Internet. The administrator accepts the booking details from the user and
proper booking are approved and a booking number is given to the customer for the tickets.
Reports are generated by administrator. In KMRL, the user can view the schedule details. Only
the registered users can perform booking and job search function of KMRL. User can view the
new job vacancies. User can give feedback to complaint department based on station, services
or general. The KMRL is developed using Java and MySQL workbench. I design this project
using the tools of Net Beans and connect to the database. The system is based on the three-tier
architecture.

The objective of the project is to make software with a high performance, the software which is
easy to work with. The software is also able to extract details from database easily.
Unauthorized access to this software is blocked. Data redundancy problem is erased. To verify
the validity of data check constraints are provided. Last but not the least, the most important of
all objectives is to consider user satisfaction.
 CONTENTS

CHAPTER TITLE PAGE NO

1 . Indroduction
 KMRL

CHAPTER 1
INTRODUCTION

1.1 OVERVIEW OF THE PROPOSED SYSTEM

The evolution of online system has been driven by technological advance and by the demand and
expectation of the user. On-line must be simple and lead to reduction in both time and effort on part
of the users of the system. KMRL (Kochi Metro Rail Ltd.) Is based on Cochin metro rail project and
is designed for helping the people who are using the services of KMRL in their daily life. This project
gives overall information regarding the KMRL services and the information about the board of
director. This project not only for helping the user who uses the KMRL services but the user who
searching for the job.

Through this site the people will easily get to know the route schedule information along with the
news related to KMRL. This site also provides the facility to inform the job vacancies in Cochin
metro. The user who has an account in this site is able to view and apply for the job. Once the user
applies for a particular job, the management will sort out list manually and inform the corresponding
user via e-mail containing the venue and time of interview. This site also provides the facility for the
user to book a vehicle for further traveling. The user can find the vehicle based on location i.e., where
is want to get a vehicle. Another facility is the reservation of season ticket. If a user using Cochin
metro rail daily, then he need to collect the ticket daily. Sometimes it is a headache process. In such
situation the user can book a season ticket (1 month,3 months, 6-month duration) and the payment is
done through online.

In this site actually 3 type of users are there admin, subadmin and user. The admin has the full
privilege in this site. The subadmin is allocated for a particular department like board news update
department or travel department etc. The subadmin are added by the administrator. The user can
simply view the route schedule even he/she has no account. But to know the news events and career
account is necessary. If the user has any kind of complaint against kmrl then he can register his/her
complaint to KMRL site and the complaint will be processed by a separate department called
Complaint department. They will take necessary action. If they cannot handle the problem, then the
complaint is forwarded to administrator.

Dept of Computer Engineering 9 GPTC Kothamangalam

 KMRL

1.2 ORGANIZATION PROFILE

Syntax Soft is an aggressive catalyst helping customers to leverage technology to accelerate
adaptation.Our focus is singular and clear: offer business benefits to the customer to deliver an
unbeatable edge over competition.  That's the bottom line we like to put on top of everything else.  All
our passion, all our values, our strengths, skills and efforts orbit around this positioning.  The idea of
offering endless value to the customer is the very differentiating principle Syntax was founded
on.Building up from the direction our foundation gave us, our guaranteed, unwavering quality of
delivery was built up by sheer determination, expertise and commitment.

 Having started in 1998 with a one-man team and a single client, Syntax today has a
manpower base of over 150 that is expected to double within the year and a list of clients that reads
like a Who's Who list of companies spread across geographies.  Syntax has now attained the position
of an emergent powerhouse in Technology consulting, product development and Outsourcing
services.

This amazing growth has resulted from the tremendous confidence Syntax has evoked in
everyone alike - Management, Employees, Investors, Partners, Alliances and, of-course, our Clients.
On the ground, Syntax is a people company. The company's backbone is its strong management team
that keeps focused on the magic of the initial vision. In addition, the expertise and energy of the
founders has filtered down to the entire team making it one complete dynamic entity with strong
commitment and focus.

Vision: To be one of the top IT Consulting Companies in India and abroad.

Mission: To leverage Technology & Human Capital for Optimum Productivity.

Philosophy: To create an opportunity & to provide a platform where everybody can grow &
contribute towards making India a 'Super Power' & the World a better place to live in.

Syntax Soft-Tech India Pvt. Ltd

Marine Drive

Cochin-31

Dept of Computer Engineering 10 GPTC Kothamangalam

 CHAPTER 2
SYSTEM STUDY

2.1 INTRODUCTION
KMRL is developed to provide the information related to the KMRL system. In this site administrator
is the main user and he maintains and manages the site. Administrator provides an opportunity for the
user to know the job vacancies of KMRL through the Internet. The administrator accepted the
booking details from the user and proper booking are approved. Reports are generated by
administrator. In KMRL the user can view all/partial the schedule details. Only the registered users
can perform booking and job search function of KMRL. User can view the new job vacancies and if
he/she is qualified to apply for the job send their CV to KMRL and after proper sort the selected
candidates for further interview are informed via email. User can give feedback to complaint
department based on station, services or general. The KMRL is developed using Java and MySQL
workbench. I design this project using the tools of Net Beans and connect to the database. The system
is based on the three-tier architecture.

In my project, the first level is the user interface (presentation logic), which displays controls,
receives and validates user input. The second level is the business layer (business logic) where the
application specific logic takes place. The third level is the data layer where the application
information is stored in files or database. It contains logic about to retrieve and update data. The
important feature about the three-tier design is that information only travels from one level to an
adjacent level. System design transforms a logical representation of what a given system is required
to do in the physical specifications.

2.2 BACKGROUND ANALYSIS

This KMRL is a new project and it is not the modification or the extension of existing system. . I
identified what are the main functions that are currently available in that Metro Rail websites. Based
on the functionalities that are provided by the Delhi or Bangalore metro rail I decided to develop a
new system that is the proposed system called KMRL an online information seeking site. KMRL is a
website which provides information about KMRL services over internet.
 2.3 EXISTING SYSTEM
Actually there is no such system exist for Cochin metro rail because its construction is not yet
completed. There exists similar system in Bangalore, Delhi etc for handling the metro rail.

2.4 PROPOSED SYSTEM

KMRL is developed in JSP, which allows development of database application. It is totally a user
friendly system and in which the data flows are in a user, administrator choice manner. Therefore, all
of them have many benefits. The objective of new system is to make the user quick and direct access
of KMRL services.ie the services provided by the KMRL such as information about the route
schedule and current information of KMRL board directors. Also thosewho searching for a job will
able to get the job vacancy details.
The daily users of KMRL have the facility of booking season ticket and booking of KMRL vehicle as
paid taxi.

ADVANTAGES OF PROPOSED SYSTEM

The main objectives (advantages) of the project are:
Provides all necessary information related to KMRL and the whole system.
The software intends to provide information such as history, details about director board, current
path, station details, and development of KMRL. The passenger can book the season ticket online.

 Software also helps to recruit employees to KMRL.

 Booking of vehicle as Paid Taxi

 Facility to book Metro for entertainment Purpose

 CHAPTER 3
SYSTEM ANALYSIS

3.1 INTRODUCTION
System analysis is the process of dividing the system into parts and establishing relationships
among them. My project was starting with system analysis. I referred some of the existing system
currently available for metro rail. I identified what are the main functions that are currently
available in that Metro Rail websites. Based on the functionalities that are provided by the Delhi or
Bangalore metro rail I decided to develop a new system that is the proposed system called KMRL
an online information seeking site. KMRL is a website which provides information about KMRL
services over internet.

I identified the different operations and data need to develop this proposed system KMRL. The
main operations of the KMRL are registration, view schedule, Booking, Career view. To achieve
these operations, I collected information from my friends and different sites available today for
metro rail. To book metro rail for entertainment purpose I need to know how this booking happened
and at the same time various steps for booking season tickets. For ticket reservation I decided the
type of payment. In this Project payment mode is online banking ie, after paying a specified amount
of money, the corresponding user will get a copy of ticket for travel. Also consider the security
feature of my system that is registered user get the unique username and password and only these
users can enter into the site. The guest user can just visit and view the schedule details of the
KMRL site.

In system analysis, I understand and determine how my new online system KMRL works and its
complete flow. I already specify the main operations of the KMRL, then I analyze each operation
separately and identify the sub operations. That is in my project one operation is the booking and
sub operations of this booking operation are booking registration, Ticket reservation and vehicle
booking. After completing system analysis i get the entire picture of my project.

3.2 FEASIBILITY STUDY

TECHNICAL FEASIBILITY
It is the study of resource availability that may affect the availability to achive an acceptable system.
It is essential that the process of analysis and definitions be conducted parallel with an assessment of

technical feasibility. Database server used in the proposed system is the SQL server, which is very
commonly used in distributed database system applications.

OPERATIONAL FEASIBILITY
The KMRL is very much user friendly and operations on KMRL can be done very easily. And it is
extendable to incorporate modifications in the proposed system is also very easy to do.

3.3 REQUIREMENT SPECIFICATION

FUNCTIONAL SPECIFICATIONS

Functional specification provides a precise idea of the problem to be solved so that they can
efficiently design the system and estimate the cost of design alternatives.

The users of the project are:

 Administrator
 Sub-Administrators
 Users

Administrator

Administrator is the main user of the system, who maintains and manages the site. He can add new train
details, new station details and register new job vacancies into the system. To reduce the working
overhead of main Administrator 3 sub Administrator are added by the main Administrator for various
department (Board updating department, Travel department, Complaint department). Administrator also
generates the report of all booking Details. Registered users can also see by the administrator. The
administrator handles the processing of approving the booking kmrl for entertainment purpose.

Sub Administrator

There are 3 Sub Administrators in this site for reducing the overhead of main Administrator in various
departments. First board update department- this department handles the old and current details of
KMRL. I.e., this department provides the information about controlling authority and current working
details of KMRL. This department also has the authority to modify the news added to the system. And
received job request are processed and selected candidates for further round of interview are informed via
email by this department.Second travel department- this department handles the registration of new
vehicle to provide the vehicle as paid taxi and the booking of vehicle.Third complaint department- this
department handles processing of complaint from the user for providing successful services by the
KMRL. If the sub Administrator cannot handle the feedback from the user, then this site allows this
feedback to be forwarded to the main administrator for taking further decision.Both 3 sub administrator is
able to send their queries to and receive from the main Administrator through this site.

User

The user needs to sign up for access and view the services of KMRL. If they don’t, they can only be able
to view the scheduling details. Once the user is registered and login process is completed, the user can
view the current and old KMRL information’s and if they want, they can send request for booking the
KMRL for entertainment purpose. User can book the season ticket provided by the KMRL for smooth
traveling. If the user is searching for a job, they are also able to seek any vacancies available in KMRL.
And allow them to apply for the job if they are qualified.

SYSTEM REQUIREMENTS

The system requirements of the project include

 Software specification
 Hardware specification

SOFTWARE SPECIFICATION

 Windows7s
 Net Beans 7.2.1
 Java, HTML, CSS, JavaScript
 MYSQL

HARDWARESPECIFICATION
 Processor: Pentium 4 or above
 RAM :2 GB or above
 Hard disk: 40 GB or above.
 CHAPTER 4
SYSTEM DESIGN

4.1 INTRODUCTION
Design is the first in the development phase for any engineered product or system. System design is a
process of evaluating alternate solution, evaluating the choice following up the specification for the
chosen alternative. System design works follows logically system analysis. The object of the system
design is to improve the existing system or design a new system as the case may be and implement
the system with improved facilities.

4.2 MODULE SPECIFICATION

Modular programming is a software design technique that emphasizes separating the functionality of
a program into independent, interchangeable modules, such that each contains everything necessary
to execute only one aspect of the desired functionality. Conceptually, modules represent a separation
of concerns, and improve maintainability by enforcing logical boundaries between components.
Modules are typically incorporated into the program through interfaces. A module interface expresses
the elements that are provided and required by the module. The elements defined in the interface are
detectable by other modules. The implementation contains the working code that corresponds to the
elements declared in the interface.

When creating a modular system, instead of creating a monolithic application (where the smallest
component is the whole), several smaller modules are built (and usually compiled) separately so that,
when composed together, they construct the executable application program. A just-in-time compiler
may perform some of this construction "on-the-fly" at run time. This makes modular designed
systems, if built correctly, far more reusable than a traditional monolithic design, since all (or many)
of these modules may then be reused (without change) in other projects. This also facilitates the
"breaking down" of projects into several smaller projects. Theoretically, a modularized software
project will be more easily assembled by large teams, since no team members are creating the whole
system, or even need to know about the system as a whole. They can focus just on the assigned
smaller task.
KMRL has six modules

MODULES IN THE PROPOSED SYSTEM

 Administration
 User Module
 Careers
 Booking

ADMINISTRATION
This module is the main operator of the software. The system is handled by a Main Administrator and
three Sub Administrators.
Main Administrator
 Client Registration
Details of new client are received from client side, in server.

 Sub Admin Management

Add new sub administrators and assign duties for each of them. The admin can edit the details
regarding each sub admin and can delete the details of sub admin when necessary.
Sub Administrator
 Board updating department

This sub admin handles all the information about the work status (current and recent works) and
updating of gallery (news, events, images and videos)
 Travel department

The metro rail works in associated with UMTA (Unified Metropolitan Transport Authority). This
has to be followed by setting up an administrative structure for the proposed transport authority
and putting effective machinery in place for co-coordinating all forms of transport systems like
buses, railway, water transport, taxi, auto rickshaw services and other modes of public transport.
 Feedback Department

The user can inform the KMRL board about their feedbacks regarding the services provided by
 the

metro rail. This sub admin can take necessary actions in relation to the complaint and give
response to user about the action that the metro had taken regarding the complaint

USER

 User registration
Here user provide their personal information for creating an account
 User Login
Once the registration process is successfully completed. The user can login the site to access
the functionalities
 Complaint
If user have any kind of complaint against KMRL that can be specified in the feedback
session

CAREERS
This is one of the exciting modules in the project and it deals with the recruitment process of KMRL.
Recruitments contain construction works and job placements. The company advertises their needs on
their page and users who are interested with this post and qualified with their needs can apply for the
work/job. Company chooses the right users from the list after the verification of their resume and
contact with them via email to inform the venue and time of interview.

BOOKING

 Booking Vehicle

The users of KMRL system is able to book a vehicle for his /her further travelling. The user can
get the vehicle based on location. Once the user books the vehicle and is not able to come on time,
and another user who tries to book the same vehicle, the allocation is given to the second user.
 Booking Train

The users of KMRL system is able to book the train.

 4.3 INPUT DESIGN

The user interface design is very important for any application. The interface design describes how
the software communicates within itself, to system that interpreted with it and with humans who use
it. The input design is the process of converting the user-oriented inputs into the computer based
format. In KMRL I decided to generate interface screen that is become very useful for the users of my
system. So I design my forms using CSS and HTML without using template downloaded from
Internet. Each form in my site has been supplied with appropriate headings such as the form for
registration of the user is given with the heading User Registration. Each form having a link in
suitable page that is only the registered user can perform booking in my site so the booking page has
link only in the home page of user. In my project data are validated so this ensures that only correct
data have been incorporated in the project. I providing a good input design for my application so it
helps the user to enter the data input and selecting a particular feature very easily.KMRL is user
friendly website. Anyone can easily work in this site and also give attraction because in site home
page there is a image slider with 6 images of KMRL and necessary link with images. This allows the
users can simply switch over to the corresponding services. Internal controls must be established for
monitoring the number of inputs and for ensuring that the data are valid. I designed my input screen
based on the requirements and work flow of the system. That is only the registered user can access
the service of booking and apply for the job provided b the KMRL authority, User can give feedback
to the corresponding department for providing better services. The quality of the system input
determines the quality of the system output. Input specifications describe the manner in which data
enter the system for processing. Input design features can ensure the reliability of the system and
produce result.

4.4 OUTPUT DESIGN

A quality output is one, which meets the requirements of end user and presents the information
clearly. In any system result of processing are communicated to the user and to the other system
through outputs. In the output design it is determined how the information is to be displayed for
immediate need. In the output design first we identify type of output contents such as reports, product
lists etc and its frequency and its volume, the appropriate output media is determined for output.
Determine how the information presents, decide whether to display, print the information. Then we
arrange the information in acceptable format.

In KMRL, to apply for career provided by the authority only the registered user can send their job
request if they are qualified. Once the requests are forward to the corresponding department. The
department sorted out the incoming request and sends the interview time and date via email to the
selected candidates. In the case of booking (Entertainment purpose) the user send the booking
purpose in detail. Once the request seen by the authority, they check the availability and feasibility
after that the authority sends mail to the corresponding user whether their request is accepted or not.
For ticket reservation the user provides the traveling information and after banking transaction the
user will get a printed copy as ticket.KMRL provide efficient and intelligent output design improves
the system’s relationships with the user and helps in decision making. The objective of the output
design is to convey the information of all the past activities, current status and to emphasis important
events. The output generally refers to the results and information that is generated from the system.
Outputs from computers are required primarily to communicate the results of processing to the
users.Efficient, intelligible output should improve the system’s relationship with the user and help in
decision making. The output devices to consider depend on factors as compatibility of the device with
the system, response time requirements, expected print quality, number of copies needed
etc..Administrator can view the booking details, sub administrator details, scheduling details and user
details etc. User can view the scheduling details and career view etc

4.5 DATABASE DESIGN

A database is a collection of interrelated data stored with minimum redundancy to serve many users
quickly and efficiently. The general objective is to make information access easy, quick, inexpensive
and flexible for the users. In my project, I used MySQL workbench for database design.

TABLE STRUCTURE

A database is a collection of interrelated data stored with minimum redundancy to serve many users
quickly and efficiently. The general objective is to make information access easy, quick, inexpensive
and flexible for the users. In my project, I used MySQL workbench for database design. The general
theme behind a database is to integrate all information of my project. Database design is recognized
as a standard of management information system and is available virtually for every computer
system. In database design several specific objectives are considered:

 Ease of learning and use

 Controlled redundancy
 Data independence
 More information at low cost
 Accuracy and integrity
 Recovery from failure
 Privacy and security
 Performance

NORMALIZATION

Designing a database is complete task and the normalization theory is a useful aid in the design
process. The process of normalization is concerned with transformation of conceptual schema into
computer representation form. There will be need for most databases to grow by adding new
attributes and new relations. The data will be used in new ways. Tuples will be added and deleted.
Information stored may undergo updating also. New association may also be added. In such situations
the performance of a database is entirely depend upon its design. A bad database design may lead to
certain undesirable things like:

1. Repetition of information

2. Inability to represent certain information

3. Loss of information

To minimize these anomalies, Normalization may be used. If the database is in a normalized form,
the data can be growing without, in most cases, forcing the rewriting application programs. This is
important because of the excessive and growing cost of maintaining an organization’s application
programs and its data from the disrupting effects of database growth. A normalized database can also
encompass many related activities of an organization thereby minimizing the need for rewriting the
applications of programs. Thus, normalization helps one attain a good database design and there by
ensures continued efficiency of database.

FIRST NORMAL FORM

My project use first normal form. A relation is in first normal form (1NF) if and all its attributes are
based on single domain. The objective of normalizing a table is to remove its repeating groups and

ensure that all entries of the resulting table have at most single value. In KMRL the login table is in
the first normal form.

Login Table

Sl.No Field name Data type Description

1 UserName Varchar Used to store the username (PK)
(20)
2 Password Varchar Used to store the password
(20)
3 Category Varchar Used to store the type of user
(20)

In this Login Table, all entries have at most single value.

SECOND NORMAL FORM

In my project KMRL also use the second normal form. A table is said to be second Normal Form
(2NF), when it is in 1NF and every attribute in the record is functionally dependent upon the whole
key, and not just a part of the key.

The User Table store user information and Uid is the primary key and the Login Table store the login
information and the primary key is UserName. User table makes a relationship with Login Table by
setting the primary key of Login Table UserName as the foreign key of the User Table.

TABLE STRUCTURE

Table is a collection of complete details about a particular subject. These data are saved in rows and
Columns. The data of each Row are different units. Hence, rows are called RECORDS and Columns
of each row are called FIELDS.

Data is stored in tables, which is available in the backend. In my project there are mainly 16 tables
and each table is store different information such as login information, user information, station
information etc. Some tables in my project have relationship.

The tables in my project are,

1. login
2. user_reg

3. train
4. tbl_job
5. tbl_career
6. vehicle_booking
7. train_payment
8. feedback
9. bank
10. motor_reg
11. homestay
12. stay_payment

1) Table Name : login

Table Description : used to store user/admin login details

Primary Key : lid
Foreign Key : uid,mid

SI Field Name Type Description

2)
1 lid NUMERIC (20) Login Id

2 email VARCHAR (20) Email id

3 pass VARCHAR (20) Password

4 uid NUMERIC (10) Set as foreign key from user table

5 mid NUMERIC (10) Set as foreign key from

motor_reg table
6 lstatus NUMERIC (10) Login status

7 utype VARCHAR (20) Type of user admin/user/vehicle

Table Name : user_reg

Table Description : used to store user/admin details

Primary Key : uid

3) Table Name : train

SI Field Name Type Description
1 uid VARCHAR (20) Id of user
2 name VARCHAR (15) Name of user
3 age VARCHAR (15) Middle name of user
4 email VARCHAR (15) Email Address of user
5 phone Date Date of birth
6 place VARCHAR (10) Address
7 aadhar VARCHAR (25) Aadhar Number
8 ustatus VARCHAR (20) User status

Table Description : used to store Train details

Primary Key : tid
Foreign key : null

SI Field Name Type Description

4) 1 tid VARCHAR (20) Id of train
2 sfrom VARCHAR (10) Station from
3 dto VARCHAR (15) Destination to
4 rate Int(6) Rate

Table Name : tbl_job

Table Description : used to store job vacancy details
Primary Ke : jid
Foreign key : uid
 SI Field Name Type Description
1 jid VARCHAR (20) Id of job table
2 jobid VARCHAR (15) Id of job
3 uid VARCHAR (25) Set as foreign key from user
table
4 adate VARCHAR (30) Last date to apply
5)
5 jstatus Int(11) Job status

Table Name : tbl_career

Table Description : used to store job request details
Primary key : career_id

SI Field Name Type Description

1 career_id VARCHAR (20) Id of Career Entry
6) 2 post_date VARCHAR (20) Posted date
3 last_date VARCHAR (20) Last date of submission
4 title VARCHAR (20) Title of job
5 description VARCHAR (150) Description of job

Table Name : vehicle_booking

Table Description : used to store vehicle booking details
Primary key : bid
Foreign key : uid,mid(user_tbl)

SI Field Name Type Description

1 bid VARCHAR (20) Id of booking
7) 2 uid VARCHAR (20) Set as foreign key from user table
3 mid VARCHAR (20) Set as foreign key from motor_reg table
4 bdate Varchar (150) Date of booking
5 status VARCHAR (10) Seen/unseen
6 time VARCHAR (10) Time of booking

Table Name : train_payment

Table Description : used to store schedule details
Primary key : pid
Foreign key : tid,uid
8) SI Field Name Type Description
1 pid VARCHAR (20) Id of train_payment table
2 tid VARCHAR (20) Set as foreign key from train table
3 uid VARCHAR (20) Set as foreign key from user table
4 source VARCHAR (10) Starting Station
5 destination VARCHAR (10) Destination station
6 tfare INT (6) Travel fare
7 tstatus INT (6) Train status

Table Name : feedback

Table Description : used to store feedback details
Primary key : fid
Foreign key : uid

9) SI Field Name Type Description

1 fid VARCHAR (20) Id of complaint
2 uid VARCHAR (20) Id of user
5 comment VARCHAR (100) Feedback Details

Table Name : bank

Table Description : used to store bank details of user
Primary key : bid
Foreign key : uid

SI Field Name Type Description

1 bid Int (11) Id bank user
2 bame VARCHAR (20) Bank name
3 branch VARCHAR (30) address
4 ctype VARCHAR (20) Account Type
5 cnumber Int (20) Account No
6 cvv Secret code of user Secret code of user
7 balance Float Balance amount
8 uid VARCHAR (20) User id
10) Table Name : motor_reg
Table Description : used to store Vehicle details
Primary key : mid

SI Field Name Type Description

1 mid VARCHAR (20) Id of Vehicle
2 name VARCHAR (20) Name of driver
3 age VARCHAR (20) Age of driver
4 email Int (10) Email id of driver
5 phone VARCHAR (20) Phone number of driver
6 place VARCHAR (20) Address location of driver
7 license VARCHAR (30) License Number of driver
8 vnumber Int (13) Vehicle number
9 vtype Int (10) Vehicle type
10 min_rate Int (6) Minimum charge
11 mstation VARCHAR (30) Station from
12 vstatus VARCHAR (10) Booked/Available

11) Table Name : homestay

Table Description : used to store homestay details
Primary key : hid
Foreign key : mid,uid
SI Field Name Type Description
1 hid VARCHAR (20) Id of homestay
2 mstation VARCHAR (20) Name of station

3 type VARCHAR (20) Type of stay

4 rate INT (6) Stay rate
5 hour VARCHAR (20) Maximum number of hours
6 frate INT (6) Food rate
12) Table Name : stay_payment
Table Description : used to store stay payment details
Primary key : sid
Foreign key : mid,uid
SI Field Name Type Description
1 sid VARCHAR (20) Id of homestay
2 mstation VARCHAR (20) Name of station

3 amount INT (6) Total amount

4 uid VARCHAR (20) Set as foreign key from user table
5 bdate DATE Date of payment
6 sstatus INT (6) Stay status
 CHAPTER 5
DATAFLOW DIAGRAM

5.1 DATA FLOW DIAGRAM BASICS

A data flow diagram is a graphical description of a system or portion of a system. It consists of data
flow process, sources, destination, and stores all described through the use of easily understood
symbols. Data flow diagrams are centre tool and the basis from which other components are
developed. The transformation of data from input to output through process may be described
logically and independently of the physical components. Data flow diagrams are powerful enough to
show parallel activities. There are two types of DFDs:
 Physical DFD
 Logical DFD

5.1.1 Physical Data Flow Diagram

There are implementations depend view of current system showing that task is carried out and how
they are performed. They show the actual device departments people etc. involved in the current
system. Physical characteristics include:
 Name of the file.
 Functions descriptions
 Name of controls
 Control properties
 Name of the project

5.1.2 Logical Data Flow Diagram

An implementation independent view of the system, focusing on the flow of data between the
processes without regard for a specific device, storage locations or people in the system. It will not
specify the physical characteristics listed about the physical data.

Advantages:
 Users easily understood the notations
Rules for constructing a Data flow diagram
 Arrows should not cross each other
 Squares, circles and files must bear names.
 Decompose data flow squares and crcles can have same names.
 Choose meaningful names for data flow.
 Draw all data flows around the outside of the diagram.

A DFD does not represent the procedural information. To construct data flow diagrams we use the
following symbols

Process

External Entity

Data flow

Data store

zero level DFD for KMRL

Request
Response

Admin/User KMRL Admin/User

System
First level DFD of KMRL
 Second level DFD for Admin_Management

Station from ,station to

km

Sid Station_tbl
Details

Train no no seats
Registration
ADMIN Tid
Train_tbl
1.1

Job type , qual

Confirm msg

Jid
Job_tbl

V no, v type

Board news Vid

Vehicle_tbl
Entry/Updating

1.1
Date, News

cid
Postid

News_update_tbl

Job request Cid

Career View

1.2 Career_tbl
Jid, Uid

BVid
BVid
Booking Details

Vehicle Booking
Vehicle_Booking_tbl
Vid, Uid Destination
1.3

Cid Cid
Complaint_tbl

Complaint details Type,

Complaint
description,username
management

1.4
 Second level DFD for User Registration

Second level DFD for Career

second level DFD for Booking
 Matter,Date

Booking Details
Booking_tbl
Booking
Entertainment
USER 6.1 Bid
Confirm message

Booking Details

Bid
Bid
Approval
ADMIN 6.2
location Vehicle_tbl

Confirm Message via

Vid,V_No,V_Type
mail

Vid,Uid,destination
Location
Booking Vehicle_Book_tbl
USER Vehicle
6.3 Confirm msg

Confirm Message
Bank, accntno

Station from, station to Bank_tbl

Ticket approval
Booking
Ticket
6.4
Confirm Message, print Username, station from
copy

Reservation_tbl

Res_id
 CHAPTER 6
SYSTEM DEVELOPMENT

6.1 JAVA TECHNOLOGY

The primary motivation of this language was the need for a platform-independent (i.e., architecture
neutral) language that could be used to create software to be embedded in various consumer
electronic devices.Java has had a profound effect on the Internet. This is because; Java expands the
Universe of objects that can move about freely in Cyberspace. In a network, two categories of
objects are transmitted between the Server and the Personal computer.They are: Passive
information and Dynamic active programs.The Dynamic, Self-executing programs cause serious
problems in the areas of Security and probability. But, Java addresses those concerns and by doing
so, has opened the door to an exciting new form of program called the Applet. Java can be used to
create two types of programs-Applications and Applets. An application is a program that runs on
our Computer under the operating system of that computer. It is more or less like one creating
using C or C++. Java’s ability to create Applets makes it important. An Applet is an application
designed to be transmitted over the Internet and executed by a Java – compatible web browser. An
applet is actually a tiny Java program, dynamically downloaded across the network, just like an
image. But the difference is, it is an intelligent program, not just a media file. It can react to the user
input and dynamically change.

6.2 JAVA SERVER PAGES (JSP)

Java server Pages is a simple, yet powerful technology for creating and maintaining dynamic-
content web pages. Based on the Java programming language, Java Server Pages offers proven
portability, open standards, and a mature re-usable component model. The Java Server Pages
architecture enables the separation of content generation from content presentation. This separation
not eases maintenance headaches; it also allows web team members to focus on their areas of
expertise. Now, web page designer can concentrate on layout, and web application designers on
programming, with minimal concern about impacting each other’s work.

FEATURES OF JSP
Portability:Java Server Pages files can be run on any web server or web-enabled application
server that provides support for them. Dubbed the JSP engine, this support involves recognition,
translation,

and management of the Java Server Page life cycle and its interaction components.
Components:It was mentioned earlier that the Java Server Pages architecture can include reusable
Java components. The architecture also allows for the embedding of a scripting language directly
into the Java Server Pages file. The components current supported include JavaBeans, and Servlets.
Processing:A Java Server Pages file is essentially an HTML document with JSP scripting or tags.
The Java Server Pages file has a JSP extension to the server as a Java Server Pages file. Before the
page is served, the Java Server Pages syntax is parsed and processed into a Servlet on the server
side. The Servlet that is generated outputs real content in straight HTML for responding to the
client.

Access Models: A Java Server Pages file may be accessed in at least two different ways. A client’s
request comes directly into a Java Server Page. In this scenario, suppose the page accesses reusable
Java Bean components that perform particular well-defined computations like accessing a database.
The result of the Beans computations, called result sets is stored within the Bean as properties. The
page uses such Beans to generate dynamic content and present it back to the client.

6.3 HTML
HTML, an initialism of Hypertext MarkupLanguage, is the predominant markup language for web
pages. It provides a means to describe the structure of text-based information in a document—by
denoting certain text a sheadings, paragraphs, lists, and soon—and to supplement that text with
interactive forms, embedded images, and other objects. HTML is written in the form of labels
(known as tags), surrounded by angle brackets. HTML can also describe, to some degree, the
appearance and semantics of a document, and can include embedded scripting language code which
can affect the behaviorof web browsers and other HTML processors.

6.4 MySQL
MySQL database has become the world’s most popular open source database because of its
consistency, fast performance, high reliability and ease of use. It has also become the database of
choice for a new generation of applications built on the LAMP stack (Linux, Apachhe, MySQL,
PHP/Perl/Python). MySQL offers a comprehensive range of certified software, support, training
and consulting.MySQL is a multithreaded, multi-user SQL Database Management System.
MySQL’s implementation of a relational database is an abstraction on top of a computer’s file
system. The relational database abstraction allows collection o data items to be organized as a set of
formally described tables. Data can be accessed or reassembled from these tables in many different
ways,

which do not require any organization of the database tables themselves.

 CHAPTER 7
SYSTEM TESTING

7.1 INTRODUCTION
Testing is the process of evaluation a system to detect differences between given input and expected
output and also to assess the features of the system. Testing is a process that should be done during
the development process. In other words, testing is a verification and validation process. Testing is
one of the major hurdles in the development of the system. A good test of course has the high
probability of finding a yet undiscovered error. System test makes a logical assumption that if all
parts of the system are correct, then goal will be successfully achieved. In the testing stage, I try to
achieve some goals; to affirm the quality of the product, to find and eliminate any residual errors
from previous stages, to validate the system as a solution to the original problem, to demonstrate the
presence of all specified functionality in the product, to estimate the operational reliability of the
system.In testing there are three common terms are used. They are test, pass and fail. A test is a
symmetric procedure to ensure that a particular unit of an application is working correctly. A pass
indicates that everything is working correctly. In the case of fail, the functionality being tested has
changed and as a result no longer works as expected. When the test is failed we need to find solutions
to overcome the failure.
Web page testing is part of building a successful web site. During testing, the
website to be tested is with set of test data and the output of the program for the test data is evaluated
to determine if the codes are working as expected. A series of testing are performed for the proposed
system before the system is ready to launch. In webpage testing, the HTML code, CSS (Cascading
Style Sheet) code files should be validated. Design of the website should be evaluated. All links need
to be tested to make sure they work correctly and also the website should also be cross browser
compatible. We have done the following testing strategies in my project ‘KMRL’.

1. Functionality testing
 2. Usability testing
3. Compatibility testing
4. Performance testing
5. Security testing

7.2 FUNCTIONALITY TESTING

Functional testing of web sites includes testing of each particular page of the site. Tests all links in
web pages, database connection, forms used in the web pages for submitting or getting information
from user and cookie testing.

CHECKING ALL LINKS

Test all the outgoing links from the pages and internal links. Test to check if there are any orphan
pages. Lastly in link checking, check for broken links. We tested all the links in my website and
correct the broken links.

TEST FORMS IN ALL PAGES

Forms are the integral part of any web site. Forms are used to get information from users and to keep
interaction with them. So we need to check all the validations on each field, check for all default
values of fields, wrong inputs to the fields in the forms.
Here is an example for validations I have done in User registration form in my project. Each sign up
step is different but dependent on other steps. So sign up flow should get executed correctly. There
are different field validations like email Ids, mobile numbers, and username validations need to be
performed. All these validations should get checked in manual or automated web testing.

COOKIES TESTING
Cookies are small files stored on user machine. These are basically used to maintain the session
mainly login sessions. If you are testing the session cookies (i.e. cookies expire after the session ends)
check for login sessions and user stats after session end. Here is an example for testing the session is
empty or not in my project. Depending on the decision the page is redirected.

if (Session.getAttribute[“user”] == null)
{
Response.sendRedirect(“login_page.jsp”);
}
else
{
Response.sendRedirect(“Home_Page.jsp”);
}

DATABASE TESTING
Data consistency is very important in web application. Check for data integrity and errors while you
edit, delete, modify the forms or do any DB related functionality. Check if all the database queries are
executing correctly, data is retrieved correctly and also updated correctly.

7.3 USABILITY TESTING

Usability testing of web sites is an essential element of quality assurance. A true test of how people
actually use a web site. To conduct this test we need users not involved with the web site in any way.
So we conducted the usability test of KMRL with my friends.

TEST FOR NAVIGATION

Navigation means how the user surfs the web pages, different controls like buttons, boxes or how
user using the links on the pages to surf different pages. Usability testing includes, Web site should be
easy to use. Instructions should be provided clearly. Check if the provided instructions are correct
means whether they satisfy purpose. Main menu should be provided on each page and we have
different menus for different type of users.

CONTENT CHECKING

Content should be logical and easy to understand. Check for spelling errors. Use of dark colors
annoys users and should not be used in site theme. We can follow some standards that are used for
web page and content building. Content should be meaningful. All the anchor text links should be
working properly. Images should be placed properly with proper sizes. These are some basic
standards that should be followed in web development. Your task is to validate all for UI testing.

7.4 COMPATIBILITY TESTING

One of typical tasks when testing web pages is to check whether the web application under test
behaves correctly in any browser or at least in the most popular ones. It is also known as Cross-
Browser Testing. Some applications are very dependent on browsers. Different browsers have
different configurations and settings that web page should be compatible with. My web site coding
should be cross browser platform compatible. If we are using java scripts or AJAX calls for UI
functionality, performing

security checks or validations then give more stress on browser compatibility testing of web
application. Test web application on different browsers like Internet explorer, Firefox, Netscape
navigator, AOL, Safari, Opera browsers with different versions. I have conducted cross-browser
testing of my website using Google Chrome and Mozilla Firefox and it is effective compatible with
both the browsers

Another compatibility testing is OS compatibility testing. Some functionality in your web application
is may not be compatible with all operating systems. All new technologies used in web development
like graphics designs, interface calls like different API’s may not be available in all Operating
Systems. I have also tested OS compatibility testing in Windows 7 and Windows 8 versions.

7.5 PERFORMANCE TESTING

I run my website in different laptops with different configurations and evaluate the performance.
Performance testing mainly focus on my website should sustain to heavy load.

SECURITY TESTING
It is one of the essential parts of testing. Each user has their own username and password to login. If
the user enters an invalid username or password, then an error message will display.
 CHAPTER 8
SYSTEM IMPLEMENTATION

8.1 INTRODUCTION TO SYSTEM IMPLEMENTATION

The implementation is the final stage and it is an important phase. It involves the individual
programming; system testing, user training and the operational running of developed proposed system
that constitute the application subsystem. One major task of preparing of implementation is education of
users, which should relay have been taken place much earlier in the project when they were being
involved in the investigation and design work.

In the implementation stage I started programming. To make the system as real one I need to create the
design and coding. In my project, based on the design create in the system design such as in the home
page all the services must display with image and its description. To get the corresponding service I need
to write the appropriate code.

After coding I started testing. Testing is the second process in the implementation stage. There are
different types testing. In my project first I had done the validation testing. Validation testing is done
in the user registration, sub administrator registration, booking etc.

Other testing is also done. The implementation phase is an important one in which the source code is put
into operation. Before implementing the software careful testing and documentation is necessary. During
the implementation and testing phase’s configuration management and quality assurance of requirements,
design specification and source code are performed. Implementation should be provided with well-
defined software requirements, architectural design specifications. KMRL has the following features:
  Reduced data redundancy.
 Ease of use.
 Controlled flow.

The process of putting the developed system in actual use is called system implementation. The
system is implemented only after through checking is done and if it is found working in according to
the specifications.

8.2 CODING STANDARDS

Coding conventions are a set of guidelines for a specific programming language that recommend
programming style, practices and methods for each aspect of a piece program written in this
language.

PURPOSE

To develop reliable and maintainable applications for Information seeking site, we must follow
coding standards and best practices. The naming conventions, coding standards and best practices
described in this document are compiled from various Microsoft and non-Microsoft guidelines. There
are several standards that exist in the programming industry. We may follow any standard approach,
but it is most important to ensure everyone is following the same standard.

MAJOR CODING STANDARD

Major coding standards used in our project are;

 Naming conventions
 Indentation and spacing

NAMING CONVENTIONS

 Use Pascal casing for Class names, method names and file names.
 Use Camel casing for variables and method parameters
 Use Meaningful, descriptive words to name variables. Do not use abbreviations.
  Do not use single character variable names like i, n, s etc. Use names like index, temp. One
exception in this case would be variables used for iterations in loops:
 Do not use underscores (_) for local variable names.
 All member variables must be prefixed with underscore (_) so that they can be identified from
other local variables.
 Do not use variable names that resemble keywords.
 File name should match with class name.

List of Control Prefixes,

Control Prefix
Label lbl_
TextBox txt_
GridView GridView
Button btn_
Image img_
Image Button img_btn_
Table _tbl

INDENTATION AND SPACING

 Use TAB for indentation. Do not use SPACES.

 Comments should be in the same level as the code
 Curly braces ({}) should be in the same level as the code outside the braces
 Use one blank line to separate logical groups of code
 There should be one and only one single blank line between each method inside the class.
 The curly braces should be on a separate line and not in the same line as if.
 CHAPTER 9
SCOPE FOR FURTHER DEVELOPMENT

9.1 SCOPE FOR FURTHER DEVELOPMENT

There can be further development for this project. There is a special section for the complaints. Users
can post their complaints regarding the services or the problem they are facing. There is a subadmin
who deals with these kinds of problems. The problems that couldn’t solved by the subadmin is solved
by the main admin. So according to the user’s requirements also this site can be modified. And also
once the admin feels when the development is needed, he can modify the project.
 CHAPTER 10
CONCLUSION

10.1 CONCLUSION
This project is based on Cochin metro rail project and is designed for helping the people who are
using the services of KMRL in their daily life. This project gives overall information regarding the
KMRL services and the information about the board of director. This project not only for helping the
user who uses the KMRL services but the user who searching for the job.
 CHAPTER 11

BIBLIOGRAPHY

11.1 BIBLIOGRAPHY

 http://www.fcamin.nic.in/dfpd_html/index.asp
 http://planningcommission.gov.in/plans/mta/mta-9702/mta-ch8.pdf
 http://planningcommission.nic.in/plans/planrel/fiveyr/10th/volume2/v2_ch3_4.pdf
 UID AND PDS System report.

.
 KHAAM CIRCLE

Kothamangalam
 KHAAM

Dept of Computer Engineering 272 GPTC Kothamangalam