A

Major Project Report

on
Smart Public Address System
Submitted to

RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL (M.P)

In Partial fulfillment for the award of degree of

BACHELOR OF ENGINEERING
IN
COMPUTER SCIENCE & ENGINEERING

By

Bhagyashree Mulye (0818CS151060)

Bhupendra Rai (0818CS151063)
Devesh Yadav (0818CS151071)
Dhananjay Wagh (0818CS151072)
Dhruv Parmar (0818CS151074)
Kunal Kandhari (0818CS151109)

Under the Guidance of

Dr. V.R. Raghuveer

Professor, CSE Dept.

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

INDORE INSTITUTE OF SCIENCE &TECHNOLOGY
PITHAMPUR ROAD, OPPOSITE IIM, RAU, INDORE 453331, M.P.
(Affiliated to RGPV, Bhopal Approved by AICTE, New Delhi.)

DECEMBER-2018
 I N D O R E I N ST I T U T E OF S C I E N C E &T E C H N O L O G Y
PITHAMPUR ROAD, OPPOSITE IIM, RAU, INDORE 45333 1, M.P.
(Affiliated to RG PV, Bhopal Approved by AICTE, New
Delhi.)

DECLARATION

We hereby declare that the work, which is being presented in this

dissertation entitled "Smart Public Address System" in partial fulfillment
of the requirements for the award of the degree of Bachelor of
Engineering in Computer Science & Engineering, is an authentic record of
work carried out by us.

The matter embodied in this dissertation has not been submitted by us

for the award of any other degree.

Bhagyashree Mulye Bhupendra Rai

0818CS151060 0818CS151063

Devesh Yadav Dhananjay Wagh

0818CS151071 0818CS151072

Dhruv Parmar Kunal Kandhari

0818CS151074 0818CS151109
 I N D O R E I N ST I T U T E OF S C I E N C E &T E C H N O L O G Y
PITHAMPUR ROAD, OPPOSITE IIM, RAU, INDORE 45333 1, M.P.
(Affiliated to RGPV, Bhopal Approved by AICTE, New
Delhi.)

Department of Computer Science & Engineering

CERTIFICATE
This is to certify that the dissertation entitled “Smart Public Address
System” submitted to RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA
(RGPV), Bhopal (M.P.) in the Department of Computer Science & Engineering
by
Ms. Bhagyashree Mulye (0818CS151060)
Mr. Bhupendra Rai (0818CS151063)
Mr. Devesh Yadav (0818CS151071)
Mr. Dhananjay Wagh (0818CS151072)
Mr. Dhruv Parmar (0818CS151074)
Mr. Kunal Kandhari (0818CS151109)
in partial fulfillment of the requirement for the award of the degree of
Bachelor of Engineering in Computer Science & Engineering during the
academic year 2018-19.

PROJECT GUIDE PROJECT COORDINATOR

Dr. V.R. Raghuveer Mr. Nitin Rathore
Principal, IIST Asst. Professor, CSE Dept.

HOD PRINCIPAL
Mr. Anil Khandekar Dr. V.R. Raghuveer
CSE Dept.
 I N D O R E I N ST I T U T E OF S C I E N C E &T E C H N O L O G Y
PITHAMPUR ROAD, OPPOSITE IIM, RAU, INDORE 453331, M.P.
(Affiliated to RGPV, Bhopal Approved by AICTE, New
Delhi.)

APPROVAL CERTIFICATE

This is to certify that the dissertation entitled “Smart Public Address

System” submitted to RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA
(RGPV), Bhopal (M.P.) in the department of Computer Science & Engineering
by

Ms. Bhagyashree Mulye (0818CS151060)

Mr. Bhupendra Rai (0818CS151063)
Mr. Devesh Yadav (0818CS151071)
Mr. Dhananjay Wagh (0818CS151072)
Mr. Dhruv Parmar (0818CS151074)
Mr. Kunal Kandhari (0818CS151109)

in partial fulfillment of the requirement for the award of degree of Bachelor

of Engineering in Computer Science & Engineering

Sign. Of the Internal Examiner Sign. Of the External Examiner

with date with date

 Acknowledgement
The success and final outcome of this project required a lot of guidance and assistance from
many people and we are extremely fortunate to have got this all along the completion of our
project work. Whatever we have done is only due to such guidance and assistance and we
would not forget to thank them.

We owe our profound gratitude to our project Coordinator Mr. Nitin Rathore, who took keen
interest on our project work, us all along, till the completion of our project work by providing
all the necessary information, constant encouragement, sincere criticism and sympathetic
attitude. The completion of this dissertation would not have been possible without such
guidance and support.
We owe our profound gratitude to our project Guide Dr V.R. Raghuveer, who took keen
interest on our project work and guided,

We extend our deep sense of gratitude to our, Mr. Anil Khandekar, HOD, Department of
Computer Science & Engineering for his/her support and suggestions during this project
work.

We respect and thank to our Hon’ble Principal Dr V.R. Raghuveer, for giving us an
opportunity to do the project work in campus and providing us all the necessary resources,
support and constant motivation which made us to complete the project on time.

We are thankful to and fortunate enough to get constant encouragement and guidance from
all teaching staffs of department of Computer Science & Engineering which helped us in
successfully completing our project work.

We would like to extend our sincere regards to all the non-teaching staff of department of
Computer Science & Engineering for their timely support.

Bhagyashree Mulye Bhupendra Rai

0818CS151060 0818CS151063

Devesh Yadav Dhananjay Wagh

0818CS151071 0818CS151072

Dhruv Parmar Kunal Kandhari

0818CS151074 0818CS151109
 TABLE OF CONTENTS

Content Page No.

Declaration I
Certificate II
Approval Certificate III
Acknowledgment IV
Table of Contents V
List of Figures VI
List of Tables VII

Abstract 1
1. INTRODUCTION ........................................................................................................... 2
2. PROBLEM STATEMENT
2.1 Literature Review ...................................................................................................... 2
3. OBJECTIVE & SCOPE OF THE PROJECT
3.1 Objective ..................................................................................................................... 2

3.2 Scope........................................................................................................................... 2

4. EXISTING SYSTEM

5. PROPOSED SYSTEM(MODULES)

5.1 Modules ...................................................................................................................... 2

6. SOFTWARE REQUIREMENTS SPECIFICATION ................................................... 2
6.1 Hardware Requirement .................................................................................................

6.2 Software Requirement ..................................................................................................

7. SYSTEM PLANNING (PERT Chart) ............................................................................ 2

7.1 PERT Chart .....................................................................................................................

8. Detailed Life Cycle of the Project .................................................................................. 2

9. UML Modelling ............................................................................................................... 2
9.1 Goals of UML .................................................................................................................
 9.2 Description of Used Tools ..............................................................................................

9.3 P-UML Modeling Diagram ............................................................................................

9.4 UML Diagram.................................................................................................................

9.4.1 Class Diagram .........................................................................................................

9.4.2 Use Case Diagram...................................................................................................

9.4.3 Activity Diagram .....................................................................................................

9.4.4 Sequence Diagram .................................................................................................

9.4.5 Collaboration Diagram ...........................................................................................

9.4.6 State Chart Diagram ...............................................................................................

10. DFD ................................................................................................................................. 2

11. ER Diagram ................................................................................................................... 2

12. Database Dictionary ...................................................................................................... 2
12.1 Database Dictionary Contains .....................................................................................

12.2 Types of Database Dictionary ......................................................................................

12.3 Database Dictionary Tables .........................................................................................

13. Input and Output Screen Design snapshots.................................................................. 2

14. Methodology used for testing DFD .............................................................................. 2
14.1 Data Flow testing .........................................................................................................

14.2 Types to Performs Data Flow Testing ..........................................................................

14.3 Data Flow Testing Limitations .....................................................................................

14.4 Advantages of Data Flow Testing ................................................................................

15. User/Operational Manual.............................................................................................. 2

16. Future Enhancement ..................................................................................................... 2
17. Conclusion ...................................................................................................................... 2
References ............................................................................................................................ 2
 LIST OF FIGURES

S. No. Fig. No. Title / Description Page No.

1. Fig. 7.1 PERT Chart of Public Address System 5

2. Fig. 8.1 Life Cycle Diagram of System 6

3. Fig. 9.1 Class Diagram of Public Address System 9

4. Fig. 9.2 Use Case Diagram of Train Ticket Booking 10

5. Fig. 9.3 Use Case Diagram of Add on Services 12

6. Fig. 9.4 Use Case Diagram of IVR and Text Msg Notification 15

7. Fig. 9.5 Use Case Diagram of Alarm Notification 17

8. Fig. 9.6 Use Case Diagram of Calendar Notification 17

9. Fig. 9.7 Use Case Diagram of Pantry Food Service 20

10. Fig. 9.8 Use Case Diagram of Ticket Wi-Fi Connection 21

11. Fig. 9.10 Activity Diagram of Public Address System 22

12. Fig. 9.11 Sequence Diagram of Public Address System 25

13. Fig. 9.12 Collaboration Diagram of Public Address System 26

14. Fig. 9.13 State Chart Diagram of Public Address System 27

15. Fig. 10.1 Data Flow Diagram of Public Address System 28

16. Fig. 11.1 Entity relationship Diagram of Public Address System 29

 LIST OF TABLES

S. No. Table No. Title / Description Page No.

1. Table. 12.1 Registration Database Table 5

2. Table. 12.2 Pantry Database Table 6

3. Table. 12.3 Train Details Database Table 9

4. Table. 12.4 Add on Services Database Table 10

5. Table. 12.5 Emergency Database Table

 ABSTRACT

Public Address System for railways in suburbs was introduced in order to authenticate
and authorize valid commuters to suit one’s comfort, purpose or needs while travelling.
Due to very high job prospects in Metro cities, the population which started travelling
through train increased immensely, which resulted in various issues such in never
stampede at stations, overcrowding, rush at foot over bridges, never ending queues,
wastage of paper, lots of resource and staff utilization. The alternatives techniques
introduced to resolve this issue failed drastically. Moreover, in spite of having such a
massive amount of data generated of the commuters, no analysis was ever done ever to
improve the railway service and the commuter’s experiences. To overcome the above
pitfalls this paper proposes a smart public system architecture for railways which
completely scraps the stampede, false announcement rush paper tickets and completely
harness the amount of money commuters has invested for their travelling. The
commuters will be benefited with the provision of using the android app as per their
requirements. This model also enables the authorities to detect those commuters who
fail to carry their tickets or while travelling. The proposed system will also have features
like crowd analysis and suggesting cost effective offers to the railway commuters.
 Chapter - 1
INTRODUCTION

We had observed that communication is compromised sometimes at Railway station,

Bus station and other gatherings of colleges and the events as well. The problem at these
places are the lack of communication between the announcer and the receiver that leads to the
hefty problems. For examples, the announcements at a college gathering between organizer
and their volunteers about the arrangement or any other kind of relevant information that
needs to be circulated among them. Either the organizer needs to call them individually or to
text them. That could be problematic if the volunteers are in different locations and in more
numbers, the problem will be more exaggerated.
There are different measures are taken to counter these problems in every field
whether to counter the proper announcement at railway stations or bus stations, and other
events, that are stated as: -
 Informing the passengers about the platform change, half an hour before the
departure.
 Informing volunteers in additional or via messenger.
 By increasing the speaker’s frequency in comparison to the crowd at stations.
However, the above stated solutions don’t stand smart whether to convey a proper
notification instantly without causing any havoc in the passengers or to provide a long-term
benefit about crowd addressing.
The problem is a pandemic and needs a solution that can be widely accepted and have
an easy to accessibility and can be easily Implemented without any incompetency. We are
coming up with improvised and innovative solution that will possibly end the problem of the
public addressing systems in every sector.
We are crafting an application with Wi-Fi direct technology to locate the cell phones
and connect the passengers or volunteers with the source addressing system with one way
sharing information protocol.
In terms of providing accurate information to the passengers via the same application,
we are providing passengers accessibility to the data base of the railways that is under open to
all.
 Chapter - 2
PROBLEM STATEMENT

It is observed that the announcement from the Public Address System at railway
system at times not audible it may due to train noise crowding at the station, technical defects
in Public Address System etc. A solution needs to be evolved so that the passenger can listen
to such announcements clearly on their personal mobile devices etc.
[1]
On Monday morning on April 23, the Lucknow railway station witnessed heavy
footfall. As the passengers were waiting for a train to arrive, the announcer suddenly
announced a platform change, causing stampede as passengers scrambled to board. In the
confusion, a 25-year-old man got by the train and died. Two others got injured.
There are futile attempts had been made in the past but we did not find any permanent
solution to address this problem. There is solution but they are not accessible by everyone.
We come up with subtle ideas to curb the problem of railways.
The problem with the incompetency in communication is vast and possibly create a
stampede in sector of an organization: -
 The problem undertaken via messenger but that is incompatible as the number of
participants is fixed to a number and a staff can be in hundreds.
 It is also taken via mail to curb the problem but regardless these attempts are
apprehensive.
 It is also taken in account by revising the announcements at railway stations however
the results were not in favor.
The previous attempts that are made, were not directly depend on technology they
were primarily based on the modulation and demodulation of the sound frequency more or
less depend on the precaution instead of instant assistance.
For the instant assistance to the people and by causing least stampede the solution
needs to be based on real time and possibly allows the communication or the notifications
flash on the screen of cell phones.

2.1 Literature Review:-

There are many solutions proposed for the solution but none of them were appropriate
as the solution miserably failed in some aspects.
 A solution was provided by a group of students they created a portable speaker which
can be attached to the mobile phones with the help of AUX or Bluetooth. Once the speaker is
attached to the device the user can listen to the announcements. This system also failed
because in order to hear the announcement the device must have the information to announce
and they were unable to solve this issue.
Indian railway itself increased the frequency of the speakers installed at the station
from 40db – 70db to 90db – 120db and as the frequency goes above 100db a normal human
being cannot hear it for a long period of time as it causes discomfort and pain.
Dr. Mahesh Bedeker, an ENT specialist in Thane (Mumbai) who had some patient
who have condition of tinnitus where one constantly hears the buzzing and the doctor said
that they hear some voices over human’s comfort level that is over 100db.
Railway officially said that they are planning to change the existing display board
with new display boards as the existing display boards cannot be seen from a long distance
and are power consuming. The new display boards will be visible from long distance and will
save power consumption by around 30% than that of existing display board. The estimated
cost of installing this boards at Indore and Ujjain is around 6.10 lakh. The monthly electricity
consumption in 9 lakh units, for which the railway is paying around 6-7crore rupees per
month.
 Chapter - 3
OBJECTIVE AND SCOPE OF PROJECT

3.1 Objective :-
We are coming up with an idea that is desirable to the railways as well as to the
public. In course of addressing the last desirable person, our emphasize is to develop cheaper
and more reliable solution in addition to effectiveness of the application.
We stand to create an innovative application that compatible to both end user and rely
on the least cost of maintenance and can be achieved by existing resource that are already in
use and gain a more productive solution.
The idea of application is compatible as each hand has an android device and
connectivity of the Wi-Fi direct is provided in every android phone and the railways and
institution has already a hotspot network. That provide a cost effective to the end users.
By providing the accessibility to the data base, we are omitting the need to install
other application for the enquiring the different services of the railways. The research in the
field of Wi-Fi direct in going on and can provide more functions in the later stages as well.

3.2 Scope:-
Our application has a more durability and the effectiveness of the application can be
increased by adding informatics in the future.
Cheap maintenance of the Wi-Fi direct and managing of the hotspot network provide
a scope for general usage and the range of the hotspot can be increased if the place is
overcrowded.
 Chapter - 4
EXISTING SYSTEM

 Indian railway itself increased the frequency of the speakers installed at the station from
40db – 70db to 90db – 120db and as the frequency goes above 100db a normal human
being cannot hear it for a long period of time as it causes discomfort and pain.
PA by Raspberry Pi
The proposed system is aimed at designing and development of voice alert notice or a
notice announcement system which can be solve the problems as mentioned in the above
chapter. The system will be built on single board known as Raspberry Pi, which includes
ARM8 quad core processor from Broadcom which satisfy the size and also low cost. The
notices will directly receive to the system by a wireless mean of SMS or an Email. So, the
user can send any notice to the system from the remote place.
Public addressing by Zigbee
This system focuses on the development of low cost, low power, easily expandable
and effective PA Systems using Zigbee. It has two modules namely server module and client
module. The Server is responsible for controlling, delivering and monitoring of data and
client modules responsible for receiving and delivering of data through speakers. The system
has a single server.
Public addressing by NetworkableIP
When it comes to professional communication and security, private and public
operators all over the world rely on solutions by Commend. NetworkableIP
loudspeakers and IP amplifiers are the perfect Intercom add-on: secure, simple and
straightforward.
Public Address and General Alarm (PA/GA) systems in tunnel
In the experiment, five horn-type directional loudspeakers were set at an interval of
150 meters in the tunnel under construction and the time-delaying networks providing the
delay-time estimated from the sound speed in the field was applied. From the loudspeakers,
announcements for emergency evacuation for the subjective hearing test and a swept-sine
signal for the measurements of impulse response were reproduced with/without the time-
delay technique.
Public addressing by Praesideo
This is a fully digital Public Address System that meets all the requirements placed by
professional users on a public address/emergency system. Public Address and General Alarm
(PA/GA) systems.
Public Address and General Alarm (PA/GA) systems in Gas Platforms
Elemec3 (E3) is a network enabled Public Address and General Alarm (PA/GA)
system designed for life critical installations in the world’s toughest industrial
communications markets. Using IP technologies to fully utilize end user infrastructure, the
Elemec3 high integrity PA/GA systems are commonly used on Oil & Gas Platforms, FPSOs,
Power Generation Plants, Refineries, Chemical Plants and industrial facilities worldwide
where the safety of all personnel is primary importance. The equipment is specifically and
fundamentally designed for failsafe operation, with extensive system and fault status
monitoring for maximum availability at all times. Prioritized paging and emergency
broadcasts, alarms may be automatically or manually initiated from any point on the system
with system expansion being defined by the user’s network.
PaMic – Bluetooth PA system
Once you have wired your phone to the speakers and the app PaMic app is running,
you are good to go. Just tap on the mic and when it turns blue, start talking. The top two
sliders are for the gain and the master volume and can help you to reduce noise and echo. The
app also works with Bluetooth speakers.
 Chapter - 5
PROPOSED SOLUTION

We are crafting an application that will provide an instant assistance as well as a

solution to the above-mentioned problem that will be based on the real time and possibly
helpful and accessible at all the addressing location whether to address a volunteer or public
addressing at stations.
We are using a WI-FI direct technology for connecting the cell phones of the
volunteers or the public to the provided hotspot network to establish a connection between
both ends. The application contains a public data base that is accessible by public. Wi-Fi has
become a choice for short range communication in many applications, due to the cost elective
deployment of Wi-Fi networks, its large-scale implementation and availability of Wi-Fi
devices e.g. Smartphone's, consumer electronics and industry sensors.
Wi-Fi Direct, also named Wi-Fi P2P, is a popular technology that enables device to
device communication in Wireless LAN. It allows Wi-Fi Direct-enabled devices to
dynamically negotiate and select one of the mobile devices as Group Owner. The Group
Owner plays the role of an Access Point as in Wi-Fi infrastructure mode. Wi-Fi Direct
protocol was initially released to connect Wi-Fi enabled devices on the fly. However, due to
the enhanced features, the protocol has the potential to be used in several applications such as
files transferring, sharing resources, online gaming, social networking, etc.
 In case of the Railways, they have their own hotspot at most stations. The passengers
needs to install our application and connect to the Wi-Fi to access the information shared by
the Railways in accordance with your train arrival and departure. The message in also
available in the message section of the application in the form of IVR (interactive voice
response) that can be heard by the passengers and can be readable as well, in case of
inaudible announcements.
In case of institution, the volunteers need to connect to the provided hotspot of the
institution over which the data or the information is exchanged and possibly allow to instant
assistance via instruction from the organizer.
If the sender is either a railway station or a organization they can allow their
passenger to excess their data bases that is open in public domain and provides a real time
enquiry as well though the announcements of the railway platforms are more effective and
could be in proportional to the information disbursed.
This application will successively curb the problem statement of public addressing
system with ease and efficiency.

5.1 Modules:-
Modules is a logical separation of a functionality in a project. We can have as some
modules in an application, they are basically used for easiness, reusability and provide a
better interface to the user:
 Single screen information about the train including the train no., train name, originating
and destination station and departure time and journey time has now been arranged
without login.
 Better interface for ticket related information which will allow the user to inquire about
the train, train fare without login and for booking time user redirect to irctc website.
 An option for food ordering through the pantry (if available) as well as dominos (need to
login for this).
 Updates and notify the user via notification (IVR audio as well as message).
 In general purpose, the application can be used in the short-range communication during a
event or gathering to address volunteers.
 File sharing is possible through the Wi-Fi direct either in one way or both.
 Chapter - 6
SOFTWARE REQUIREMENTS SPECIFICATION

6.1 Hardware Requirement:-

 Processor- Intel i5
 Processor speed - 2.5 GHz
 RAM:- 4GB minimum required
 Hard Disk Drive - 50GB (Minimum space required)

6.2 Software Requirement:-

 IDE -Android studio 3.0.1
 Language - Android (JAVA)
 Frontend language - XML
 Database - MySQL
 Server - Apache Tomcat
 Chapter - 7
SYSTEM PLANNING (PERT CHART)

Public address management is term that covers array of the systems and processes
within a railways to create and use of information. Public address Systems Planning is critical
in developing and executing successful strategic plans in global level. It is observed in current
business situation that the markets are very uncertain which pushes companies to adopt
effective, pro-active strategies in order to gain competitive advantage. The strategy formula is
oriented through operation and objectives based on a cautious analysis of the involving
project. Objectives of public address system planning are desired future positions and
destinations the organizations intend to reach in order to fulfill its mission. Its policies are a
general guideline that directs and constraints decision making within a group.
Information technology enable a set of opportunities to gain competitive advantage
and to adjust the public address Systems for the benefit of railways.
In present scenario, public address system planning is key issue faced by senior
executives of railways. Address management planning mainly involves in identification of
the stage of problem faced in the railways in simultaneous announcing the train timing, and
frequent notices & identification of the applications of Railway information systems,
evaluation of each of these applications, based on established evaluation criteria, establishing
a priority ranking for these applications and determining the optimum architecture for serving
the top priority applications. Theoretical literature of the information systems suggests one
challenging theories of effective planning in a turbulent environment. One predicts that once
the Railways using a formal, comprehensive planning approach will be more successful.

Stage model of Information System planning:

1. Strategic planning:
a. Derivation from the public addressing previous plans.
b. Strategic fit with railways culture and needs.
c. set transformation from the previous technology.
2. Information requirement analysis:
a. Define underlined railway requirement.
b. Develop sub system with resemblance to railways.
c. Define and evaluate information requirements for railways sub-systems.
 3. Project planning:
a. Pert chart

To sum up, the public address Systems Planning is a key process for the success and
competitiveness in present business environment. Plans explain the structure and content of
information system and the way it is developed. The major aim of public address Systems
Planning is to recognize the stages of planning in the railways.

7.1 PERT chart:-

A PERT chart is a project management tool used to schedule, organize, and
coordinate tasks within a project. PERT stands for Program Evaluation Review Technique.
A PERT chart presents a graphic illustration of a project as a network diagram
consisting of numbered nodes (either circles or rectangles) representing events, or milestones
in the project linked by labeled vectors (directional lines) representing tasks in the project.
The direction of the arrows on the lines indicates the sequence of tasks.

Fig. 7.1. PERT Chart of Public Address System

 Chapter - 8
DETAILED LIFE CYCLE OF THE PROJECT

Every project has certain phases of development. A clear understanding of these

phases allows managers and executives to maintain control of the project more efficiently. By
definition, a project has a beginning and an end and passes through several phases of
development known as life cycle phases. These phases are varied depending upon the
industry involved but all follow the same basic steps.
It is important to realize that the project life cycle for each project may differ, in both
the number of phases it may have and the detail within each of these phases.

Evolution Requirement
Analysis

Testing Design

Implementation

Fig. 8.1. Life Cycle Diagram of System

 Requirements Analysis: -
Several people with hearing impairment reported difficulties arising from not hearing
travel announcements.
Here some typical transport stories from the people:
I have missed so many trains through not hearing announcements Sometimes I have
been on the wrong platform and sometimes I have not heard that the service is going to be
late or has been cancelled It was not a nice experience and I had to wait another hour for the
next train I’ve always thought that each station should have a screen to show the
announcement in text at the same time as it comes through the loudspeaker.
Most users we consulted said that while they could see clear benefits in a wireless
public announcement system People expressed interest in being able to set up the system to
show text and audio messages for specific services.

 Design :-
Based on the user requirements and the detailed analysis of a new system, the new
system must be designed. This is the phase of system designing. It is the most crucial phase in
the development of a system. The logical system design arrived at as a result of system
analysis and is converted into physical system design The logical design produced during the
analysis is turned into a physical design - a detailed description of what is needed to solve
original problem In the design stage, the programming language and the hardware and
software platform in which the new system will run are also decided There are several tools
and techniques used for describing the system design of the system. These tools and
techniques are: Flowchart, Data flow diagram.

 Implementation:-
We are crafting a application that will provide an instant assistance that will be based
on the real time and possibly helpful and accessible at all the addressing location whether to
address a volunteer or public addressing at stations.
We are using a WI-FI direct technology for connecting the cell phones of the
volunteers or the public to the provided hotspot network to establish a connection between
both ends. The application contains a public data base that is accessible by public. Wi-Fi has
become a choice for short range communication in many applications, due to the cost elective
deployment of Wi-Fi networks, its large-scale implementation and availability of Wi-Fi
devices e.g. Smartphone's, consumer electronics and industry sensors.
In case of the Railways, they have their own hotspot at most stations. The passengers
need to install our application and connect to the Wi-Fi to access the information shared by
the Railways in accordance with your train arrival and departure. The message in also
available in the message section of the application in the form of IVR (interactive voice
response) that can be heard by the passengers and can be readable as well, in case of
inaudible announcements.

 Testing:-
Before implementing the new system into operations, a test run of the system is done
removing all the bugs, if any. It is an important phase of a successful system. After codifying
the whole programs of the system, a test plan should be developed and run on a given set of
test data. The output of the test run should match the expected results. Sometimes, system
testing is considered as a part of implementation process.

Using the test data following test run are carried out:
 Program test
 System test

Program test: When the programs have been coded and compiled and brought to working
conditions, they must be individually tested with the prepared test data. All verification and
validation be checked and any undesirable happening must be noted and debugged (error
corrected).
System Test: After carrying out the program test for each of the programs of the system and
errors removed, then system test is done. At this stage the test is done on actual data. The
complete system is executed on the actual data. At each stage of the execution, the results or
output of the system is analyzed. During the result analysis, it may be found that the outputs
are not matching the expected output of the system.

 Evolution:-
A Wireless Public Announcement System is proposed based on already available
mainstream radio digital technology. The main objective has been the replacement of the
competing solutions based on a magnetic loop or on FM message broadcasting.
Digital Wireless based solution provides the flexibility necessary to render the service
to a multiplicity of users of different interests and profiles with a variety of language and
accessibility limitations. The service can be as well provided in a multiplicity of formats from
text and audio.
 Chapter - 9
UML MODELING

UML is a standard language for specifying, visualizing, constructing, and

documenting the artifacts of software systems. UML was created by the Object Management
Group (OMG) and UML 1.0 specification draft was proposed to the OMG in January 1997.

OMG is continuously making efforts to create a truly industry standard.

 UML stands for Unified Modeling Language.
 UML is different from the other common programming languages such as C++, Java,
COBOL, etc.
 UML is a pictorial language used to make software blueprints.
 UML can be described as a general-purpose visual modeling language to visualize,
specify, construct, and document software system.
 Although UML is generally used to model software systems, it is not limited within this
boundary. It is also used to model non-software systems as well. For example, the process
flow in a manufacturing unit, etc.
 UML is not a programming language but tools can be used to generate code in various
languages using UML diagrams. UML has a direct relation with object-oriented analysis
and design. After some standardization, UML has become an OMG standard.

9.1 Goals of UML:

A picture is worth a thousand words, this idiom absolutely fits describing UML.
Object-oriented concepts were introduced much earlier than UML. At that point of time, there
were no standard methodologies to organize and consolidate the object-oriented development.
It was then that UML came into picture. There are a number of goals for developing UML
but the most important is to define some general-purpose modeling language, which all
modelers can use and it also needs to be made simple to understand and use.

9.2 Description of used Tools:-

VISUAL PARADIGM is the tool that has been used to design the UML diagrams.
Visual Paradigm (VP-UML) is a UML CASE Tool supporting UML 2, SYSML and
BUSINESS PROCESS MODELLING NOTATION (BPMN) from the OBJECT
MANAGEMENT GROUP (OMG). In addition to modeling support, it provides report
generation and code engineering capabilities including code generation. It can reverse
engineer diagrams from code, and provide roundtrip engineering for various programming
languages.

Product Editions:-
i. Community Edition:- A free edition for non-commercial use. Supports all 13 UML
diagram types. For projects with one diagram only, exported diagram contains small
watermark, if it has more diagrams, a full watermark is placed instead.
ii. Personal Edition:- For non-commercial use only:
 Modeler Edition
 Standard Edition
 Professional Edition
 Enterprise Edition Supports
BPMN 2.0 for modeling of business processes.

9.3 P-UML Modeling Diagram:-

P-UML supports 13 types of diagrams:
 Class diagram
 Use case diagram
 Sequence diagram
 Communication diagram
 State machine diagram
 Activity diagram
 Component diagram
 Deployment diagram
 Package diagram
 Object diagram
 Composite structure diagram
 Timing diagram
 Interaction overview diagram
9.4 UML Diagrams:-
Diagrams are generally made in an incremental and iterative way. There are two
broad categories of diagrams and they are again divided into subcategories:
 Structural Diagram
 Behavioral Diagram

Structural Diagram:-
The structural diagrams represent the static aspect of the system. These static aspects
represent those parts of a diagram, which forms the main structure and are therefore stable.
These static parts are represented by classes, interfaces, objects, components, and nodes. The
four structural diagrams are:
 Class diagram
 Object diagram
 Component diagram

Behavioral Diagram:-
Any system can have two aspects, static and dynamic. So, a model is considered as
complete when both the aspects are fully covered. Behavioral diagrams basically capture the
dynamic aspect of a system. Dynamic aspect can be further described as the changing/moving
parts of a system.

UML has the following five types of behavioral diagrams:

 Use case diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram

9.4.1 Class Diagram:-

 Class diagrams are the most common diagrams used in UML. Class diagram consists
of classes, interfaces, associations, and collaboration. Class diagrams basically
represent the object-oriented view of a system, which is static in nature.
 Active class is used in a class diagram to represent the concurrency of the system.
 Class diagram represents the object orientation of a system. Hence, it is generally used
for development purpose. This is the most widely used diagram at the time of system
construction.

Purpose of Class Diagram:

The purpose of class diagram is to model the static view of an application. Class
diagrams are the only diagrams which can be directly mapped with object-oriented
languages and thus widely used at the time of construction.UML diagrams like activity
diagram, sequence diagram can only give the sequence flow of the application, however
class diagram is a bit different. It is the most popular UML diagram in the coder
community. The purpose of the class diagram can be summarized as:
 Analysis and design of the static view of an application.
 Describe responsibilities of a system.
 Base for component and deployment diagrams.
 Forward and reverse engineering.
Class Diagram:

Fig. 9.1. Class Diagram of Public Address System

9.4.2 Use Case Diagram:-
 Use case diagrams are a set of use cases, actors, and their relationships. They
represent the use case view of a system.
 A use case represents a particular functionality of a system. Hence, use case diagram
is used to describe the relationships among the functionalities and their
internal/external controllers. These controllers are known as actors.

Purpose of Use Case Diagram:-

The purpose of use case diagram is to capture the dynamic aspect of a system.
However, this definition is too generic to describe the purpose, as other four diagrams
(activity, sequence, collaboration, and State chart) also have the same purpose. We will
look into some specific purpose, which will distinguish it from other four diagrams. Use
case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. Hence, when a
system is analyzed to gather its functionalities, use cases are prepared and actors are
identified. When the initial task is complete, use case diagrams are modeled to present the
outside view.

In brief, the purposes of use case diagrams can be said to be as follows:

 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.
Use Case Diagram:

Fig. 9.2. Use Case Diagram of Train Ticket Booking

Fig. 9.3. Use Case Diagram of Add on Services
Fig. 9.4. Use Case Diagram of IVR and Text Msg Notification
Fig. 9.5. Use Case Diagram of Alarm Notification
Fig. 9.6. Use Case Diagram of Calendar Notification
Fig. 9.7. Use Case Diagram of Pantry food Service

Fig. 9.8. Use Case Diagram of Wi-Fi Connection

9.4.3 Activity Diagram:-
 Activity diagram describes the flow of control in a system. It consists of activities and
links. The flow can be sequential, concurrent, or branched.
 Activities are nothing but the functions of a system. Numbers of activity diagrams are
prepared to capture the entire flow in a system.
 Activity diagrams are used to visualize the flow of controls in a system. This is
prepared to have an idea of how the system will work when executed.

Purpose of Activity Diagram:-

The basic purposes of activity diagrams is similar to other four diagrams. It captures
the dynamic behavior of the system. Other four diagrams are used to show the message flow
from one object to another but activity diagram is used to show message flow from one
activity to another. Activity is a particular operation of the system. Activity diagrams are not
only used for visualizing the dynamic nature of a system, but they are also used to construct
the executable system by using forward and reverse engineering techniques. The only missing
thing in the activity diagram is the message part. It does not show any message flow from one
activity to another. Activity diagram is sometimes considered as the flowchart. Although the
diagrams look like a flowchart, they are not. It shows different flows such as parallel,
branched, concurrent, and single.
The purpose of an activity diagram can be described as:
 Draw the activity flow of a system.
 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.
Activity Diagram:

Fig. 9.9. Activity Diagram of Public Address System

9.4.4 Sequence Diagram:-
 Sequence Diagrams are interaction diagrams that detail how operations are carried
out. They capture the interaction between objects in the context of a collaboration.
Sequence Diagrams are time focus and they show the order of the interaction
visually by using the vertical axis of the diagram to represent time what messages
are sent and when.

Purpose of Sequence Diagram:-

 Model high-level interaction between active objects in a system
 Model the interaction between object instances within a collaboration that realizes a
use case
 Model the interaction between objects within a collaboration that realizes an
operation
 Either model generic interactions (showing all possible paths through the
interaction) or specific instances of a interaction (showing just one path through the
interaction)
Sequence Diagram:-

Fig. 9.10. Sequence Diagram of Public Address System

9.4.5 Collaboration Diagram:-
 Collaboration diagram is another form of interaction diagram. It represents the
structural organization of a system and the messages sent/received. Structural
organization consists of objects and links.
 The purpose of collaboration diagram is similar to sequence diagram. However, the
specific purpose of collaboration diagram is to visualize the organization of objects
and their interaction.

Purpose of Collaboration Diagram:-

Collaboration diagram will show how a system made up of individual software pieces
works in real time. The flow chart objects may represent a more abstract interaction, such as a
general cause-and-effect or event-driven collaboration that may happen over time.

Collaboration Diagram:

Fig. 9.11. Collaboration Diagram of Public Address System

9.4.6 State Chart Diagram:-
A State chart diagram describes a state machine. State machine can be defined as a
machine which defines different states of an object and these states are controlled by external
or internal events.

Purpose Of State Chart Diagram:-

Following are the main purposes of using State chart diagrams −
 To model the dynamic aspect of a system.
 To model the life time of a reactive system.
 To describe different states of an object during its life time.
 Define a state machine to model the states of an object.

State Chart Diagram:-

Fig. 9.12. State Chart Diagram of Public Address System

 Chapter - 10
DATA FLOW DIAGRAM

The Data flow diagram can be explained as the separate levels indicating the
individual complexity in each level of the system and gives a detailed explanation in the
further levels that are following them:

Fig. 10.1. Data Flow Diagram of Public Address System

 Chapter - 11
ER DIAGRAM

An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how

“entities” such as people, objects or concepts relate to each other within a system. ER
Diagrams are most often used to design or debug relational databases in the fields of software
engineering, business information systems, education and research. Also known as ERDs or
ER Models, they use a defined set of symbols such as rectangles, diamonds, ovals and
connecting lines to depict the interconnectedness of entities, relationships and their attributes.
ER diagrams are related to data structure diagrams (DSDs), which focus on the
relationships of elements within entities instead of relationships between entities themselves.
ER diagrams also are often used in conjunction with data flow diagrams (DFDs), which map
out the flow of information for processes or systems.

Fig. 11.1. Entity Relationship Diagram of Public Address System

 Chapter - 12
DATABASE DICTIONARY

Database dictionary is a dictionary about the data that we store in the database. It
contains all the information about the data objects. It is like storing all up-to-date information
about the objects like tables, columns, index, constraints, functions etc. It makes us easily
identify access and understand the factors about the object. One can imagine data dictionary
as storing information about house like house name, address, how many live in the house,
who is the eldest/youngest person, responsibilities of each member in the house etc. or a
personal details of an employee in the company.

12.1 Database Dictionary Contains:-

 The definitions of all database objects like tables, views, constraints, indexes, clusters,
synonyms, sequences, procedures, functions, packages, triggers etc.
 It stores the information about how much space is allocated for each object and how
much space has been used by them.
 Any default values that a column can have are stored.
 Database user names – schemas.
 Access rights for schemas on each of the objects.
 Last updated and last accessed information about the object.
 Any other database information.

All these information is stored in the form of tables in the data dictionary.

12.2 Types of Data Dictionary:

There are two types of data dictionary: Active and Passive.

 ACTIVE DATA DICTIONARY:-

Any changes to the database object structure via DDLs will have to be reflected in
the data dictionary. But updating the data dictionary tables for the changes are
responsibility of database in which the data dictionary exists. If the data dictionary is
created in the same database, then the DBMS software will automatically update the data
 dictionary. Hence there will not be any mismatch between the actual structure and the
data dictionary details. Such data dictionary is called active data dictionary.

 PASSIVE DATA DICTIONARY:-

In some of the databases, data dictionary is created separately from the current
database as entirely new database to store only data dictionary information. Sometimes it
is stored as xml, excels or in any other file format. In such case, an effort is required to
keep data dictionary in sync with the database objects. This kind of data dictionary is
called passive data dictionary. In this case, there is a chance of mismatch with the
database objects and the data dictionary. This kind of DD has to be handled with utmost
care.

12.3 Database Tables:-

i. Registration:-

P/F Key Field Name Caption Data Type Size

User Name User Name Varchar 45
P User ID User ID Varchar 45
Password Password Varchar 10
Confirm Password Confirm Password Varchar 10
Age Age Int 2
Gender Gender Varchar 6
Mobile no. Mobile no. Int 10
Table 12.1. Registration Database Table

ii. Pantry:-

P/F Key Field Name Caption Data Type Size

Item Name Item Name Varchar 300
P Item ID Item ID Int 30
Item Rate Item Rate Int 5
Table 12.2. Pantry Database Table
iii. Train Details:-

P/F Key Field Name Caption Data Type Size

P Train no. Train no. Varchar 10
Train name Train Varchar 50
Arrival Time Arrival Time Varchar 10
Departure Time Departure Time Varchar 10
No. of stations No. of stations Int 3
No. of stations halt No. of stations halt Int 3
Table 12.3. Train Details Database Table

iv. Add On Services:-

P/F Key Field Name Caption Data Type Size

P Tourist place name Tourist place name Varchar 100
Distance from Distance from Varchar 5
Station Station
Table 12.4. Add on Services Database Table

v. Emergency:-

P/F Key Field Name Caption Data Type Size

P Doctor ID Doctor ID Int 10
Doctor Name Doctor Name Varchar 20
Specialization Specialization Varchar 10
Table 12.5 Emergency Database Table
 Chapter - 13
INPUT AND OUTPUT SCREEN DESIGN SNAPSOTS
 Chapter - 14
METHODOLOGY USED FOR TESTING DFD

14.1 Data flow testing:-

It is one of the testing strategies, which focuses on the data variables and their values,
used in the programming logic of the software product, by making use of the control flow
graph. Data flow testing is the form of white box testing and structural type testing, which
generally keeps check at the points, where the data values are being received by the variables,
and at the points, when it is called for use. It is used to fill the gap between the path testing
and branch testing.
14.2 Types to Perform Data Flow Testing:
The process of data flow testing may be carried out through two different approach or
methodology.
 Static Data Flow Testing:-
In static testing, study and analysis of code is done without performing the actual
execution of the code such as wrong header files or library files use or syntax error.
Generally, during this type of testing, d-u-k pattern, i.e. definition, usage and kill pattern
of the data variables is monitored and observed with the help of control flow graph.
 Dynamic Data Flow Testing:-
It involves the execution of the code, to monitor and observe the intermediate results.
It basically, looks after the coverage of data flow properties. This type of testing may
comprise of following activities:
 Identification of all d-u pairs, i.e. definition and usage in the code.
 Detecting feasible path between each definition and usage pair.
 Designing & creating sets of test cases for each path.

14.3 Data Flow Testing Limitations:-

With the advantages of using the exploratory testing in the agile environment, some
limitations are also associated with it such as:
 Testers need to have sufficient knowledge of the programming.
 Time-consuming and costly process.
14.4 Advantages of Data Flow Testing:-
Data Flow testing helps us to pinpoint any of the following issues:
 A variable that is declared but never used within the program.
 A variable that is used but never declared.
 A variable that is defined multiple times before it is used.
 De-allocating a variable before it is used.
 Chapter - 15
User/Operational Manual

 Overview OUR APP provides Android App for Android users, which helps to view and
listen to your world anywhere anytime. The following steps will show you how to setup
App and enjoy it.
 Install App Search and install our app on Google Play. Note that the publisher is our app.
Then you will see the shortcut icon on the device screen.
 Add Apps to App Click Enjoy to enter App, Add app to app drawer and click enjoy to
enter App.

Step1: Tap Search Button to scan all apps in LAN. Choose the app you want to add and click
OK, the app can be added to the IPC list.

Step2: Choose the app you want to connect. The App will pop-up Input Username and
Password page automatically. Input the Username and Password of your app, click OK
Step3: Modify the Username and Password (If you have modified the Username and
Password, you can do not perform this step.) Input the new username and password, and click
OK

Notes: The High Definition and Standard Definition models use different coding, you
should select one first. If your bandwidth is sufficient, such as on 3G or LTE. The Device
Name here is just used to distinguish the app on your phone, won’t modify the app name
of your IPC.
 Edit Device Press the app in the Device List for more than one second, it will pop-up
several options as Connect/Disconnect, Settings, Edit and Delete. Connect/Disconnect:
You can connect the device have been added, or disconnect the device.
Edit: If you need to modify the device, tap "Edit", renew setup info, and then save.
Settings: "Settings" will allow you to change the user name and password of the app, and
set the IR led lights mode, wireless settings, PTZ, motion detection.
Delete: You can also tap "Delete" to remove the device.
 Chapter - 16
FUTURE ENHANCEMENT

 Smart Ticketing system is a total express railway ticketing solution architecture that will
change everything in railways business.

 Smart public addressing app offers a wide variety of benefits build for commuters and
Railway authorities by adding local vendors and food chain distributers to deliver food in
the running trains.

 Commuters travel is unified, simplified, cost-effective and comfortable. By tracking the

live location and the train.

 They are notified with attractive offers based on their travelling patterns and details of
station and the history of the station they passed by.

 For Railway authorities, only authorize commuters travel, no wastage of paper, security
of commuters is ensured, as the ticket will be checked through the app.

 With this Smart public addressing architecture implemented on cloud, give an added
benefit of scalability and performances at any point of time. The home page will be saved
foe no internet zone.

 Information of the nearby places and the video of the cultural heritage will benefit the
commuters on the entertainment purpose.

 The magazine will be added in the app for the reader commuter though they can easily
take their travel under paid on attractive offers.

 The passengers will be offered with the coolie services at the station and the wheelchair
excess at the coach no. itself to provide a comfortable journey, with the scheme of the
fare off.

 Commuters are enabled with the coach security and contacting the police to police.

 Medical services will be provided to the unreserved coaches as well.

 Paid on services (premium services will be provided for entertainment).

 Chapter - 17
CONCLUSION

Smart public addressing system is a total addressing module architecture that will
change everything in railways business. Smart public addressing offers a wide variety of
benefits build for commuters and Railway authorities. For commuter’s travel is unified,
simplified, cost-effective and comfortable. Even they are notified with attractive offers based
on their travelling and details of their respective trains, which make their journey safe, happy
and comfortable. For Railway authorities, only authorize commuters travel, no stampede and
overcrowding at stations, and rush on foot over bridges, no wastage of paper, security of
commuters is ensured, No cash money transaction needs to be done and less staff and
resources required. With this Smart public addressing architecture implemented on cloud,
give an added benefit of scalability and performances at any point of time.
 References

 "To refer a Research Paper"

B. N. Jagadale and Kusuma Hegde “SMS based alerting system for train passengers”
Department of Electronics Kuvempu University, Shankaragatta, INDIA 2J.M.J.First
Grade College Sirsi, North Kanara, INDIA

 "To refer a Journal Paper"

S. P. Kesavan and M. Dhanasekaran, "Automatic Station Announcement System in
Railways", ECE, Nandha college of technology, Erode, India, vol.-3, issue-3

 "To refer a Websites"

Indian Railway Catering and Tourism Corporation, Indian Railway. How to show and
manage train schedule.
https://www.irctc.co.in/nget/train-search (accessed 17 Oct 2018).
LinkedIn SlideShare, Slide hosting service. Project planning and feasibility study.
https://www.slideshare.net/marsmfyam/project-planning-and-feasibility-study (accessed
19 Oct 2018).

Research Design and Standards Organisation, Indian Railways. Maintenance handbooks

on Public Address System.
http://www.rdso.indianrailways.gov.in/works/uploads/File/Maintenance%20handbook%2
0on%20Public%20Address%20System (accessed 20 Oct 2018).
[1] India news, India. Sudden Announcement of Platform Change Causes Stampede;
Passenger Dead.
https://www.india.com/news/india/lucknow-sudden-announcement-of-platform-change-
causes-stampede-passenger-dead-3015601/ (accessed 23 Oct 2018).