Software Requirements Specification

Report

Software Engineering Principles - SENG8010-22F

Railway Tracking and Arrival Time

Prediction

PRAVEEN JOSE
(8810125)

Prof. Huda Al Ali

1
 TABLE OF CONTENTS

1. Introduction .................................................... 3
1.1 Purpose .............................................................. 3
1.2 Scope ................................................................. 3
1.3 Definitions, Acronyms, and Abbreviations ....... 4
1.4 Reference ........................................................... 4
1.5 Overview ............................................................ 4

2. Overall Description.......................................... 6
2.1 Product Perspective ............................................ 6
2.2 Product Function ................................................ 7
2.3 User Characteristics ..............................................9
2.4 Constraints ........................................................... 9
2.5 Assumptions and Dependencies .......................... 9
2.6 Apportioning of Requirements ............................ 9

3. Specific Requirements ......................................10

3.1 External Interfaces ..............................................10
3.2 Functions ............................................................ 10
3.3 Performance Requirements ................................ 10
3.4 Logical Database Requirements ........................ 10
3.5 Design Constraints.............................................. 11
3.6 Software System Attributes ............................... 11

4. Appendices........................................................ 12

2
 1. INTRODUCTION

1.1 Purpose

It has happened so many times that you have been waiting on railway
station for someone to arrive and you don’t have any exact information about
train timing and other stuff. So here we present to you a project on Railway
Tracking and Arrival time prediction. Using this system users can get the
information about train timing, and is it on time or not, and other information.
The purpose of this system is to track the train timing. That is, at what time the
train departed from a particular station and pass these timing details to other
station’s system where it will display the timing according to train departed from
previous station. If System will find any delay in train due to signal it will
automatically update the train timing in next station and will be displayed to
viewers. Also, there will be an application that works on android and passengers
can check their train timing online. This document will highlight the purpose and
the features of the system, whatthe system will do, the constraints under which it
must operate. This document is intended for both the stakeholders and the
developers of the system and is proposed to the SoftwareEngineering Principles
Professor Huda Al-Ali.

1.2 Scope

In this system there is an admin module controlled by railway

authority, who enters the details about trains and its timing and these details will
be passed through internet server and is fetched by the system on other stations,
and there is other system that shows train information to the viewers on platform.
Second System will get all the information of all trains but will automatically
select the data that refers to particular station and shows that information on the
screen. Also, there is a third system which is a mobile app, were passengers can
directly monitor the status of their train through online.
Apart from the data received from GPS module attached to each train,
station masters on every station have a login wherein they may update train arrival
time at their station when it arrives. The second system is installed on various
locations on station for viewers to view the information. Admin will add
information like train departed from station, expected arrival at destination, delay
in the train schedule, etc. The third system which is a mobile app is available in
both android and iOS version. This project publishes real-time train schedule
events to subscribing multiple client applications.

3
1.3 Definitions, Acronyms & Abbreviations

SRS Software Requirement Specification

MC Micro controller
SMS Short Message Service
iOS iPhone Operating System
GPS Global Positioning System
LCD Liquid Crystal Display

1.4 References

[1] IEEE 830-1998 IEEE recommended practices

[2] https://www.electronicshub.com/
[3] Electronic Devices and Circuits by J. B Gupta
[4] Online train delay recognition and running time prediction -
https://ieeexplore.ieee.org/document/5625081
[5] Bus arrival time prediction using artificial neural network model -
https://ieeexplore.ieee.org/document/1399041
[6] Hybrid dynamic prediction model of bus arrival time based on
weighted of historical and real-time GPS data -
https://ieeexplore.ieee.org/document/6561064/

1.5 Overview

The SRS is laid out as three sections where the first section is the Introduction
section. This section is mainly intended for all the audiences since it contains
a brief idea of what is being made. The purpose of the document is quoted
in the first sub heading and the main reason or the scope of the project is also
included in this section. The abbreviations, acronyms used in this document
is given in the introduction section and also the reference of making this
product is also mentioned in it. Hence the introduction section contains the
overall ideaof the whole system in a nutshell.

4
The second section is the Overall Description section of the SRS, and it gives
an overview of the functionality of the product and explains the informal
requirements and the technical requirements which is used to create this
product. The basic working idea or the mode of operation of the system and
what all features are included in it are all mentioned briefly in the second
section. The memory constraints (if any), hardware interfaces, the whole
system interfaces are all included in the product perspective part of the second
section. The user characteristics and the design constraints which is closely
related to the product which the developers take into consideration are also
discussed. Even the future requirements and the factors that may affect the
SRS is included in this section. Developers and designers use this section for
gaining a brief understanding of the overall system architecture and the main
requirements. This section is mainly intended for audiences that has some
technical knowledge and not for all audiences.
The third section is called the Specific Requirement section. All the technical
requirements which are needed to develop the product is highlighted in this
section. It includes the external interfaces, the detailed functions of the system
and the key requirements such as performance requirements and the logical
database requirements. The constraints while developing the system such as
design constraints is also included in this section. Moreover, the attributes of
the software system such as the vital roles where the system can be used is
also a major part of the specific requirements section. This section is mainly
intended for designers and developers to design the system and testers to check
whether all the requirements of the system is met and test the final product.
Hence audiences with good technical knowledge will only be able to
comprehend this section.
All the sections of the document describe about the same software product but
are intended for different audiences and thus use different languages for
understanding.

5
2. OVERALL DESCRIPTION

2.1 Product Perspective

Fig.1 Block Diagram

The above figure shows the basic block diagram of the product. All
components are directly linked to a server. Hence the server is the heart of the
system. The server for handling this huge database can be obtained from
Google. Each train is installed with a GPS module along with a controller.
The role of microcontroller is to upload the data obtained from the GPS
module to server. These data is very useful to track the train when it is
running. Apart from the data received from GPS module attached to each
train, station masters on every station have a login to the server wherein they
may update train arrival time at their station when it arrives, there by
updating the database. A Display system is installed on various locations on
station for viewers to view the information. The third system which is a
mobile app is available in both android and iOS version. The both systems
will get data from the server.

6
2.2 Product Functions

• Display train timing in the Platform

7
• Display train timing in the Mobile Application

8
2.3 User Characteristics

The end-user need not have any technical knowledge on the product,
since every detail is displayed on the screen and in the Mobile app. In
order to use the app, the user want to create an account. By using their
login id and password they login and access the details. The passengers
can use these app while they are in train also. They can setup an alarm
for a particular station, by utilizing the data from the GPS module of
mobile. Apart from English, the app can be operated in French, Chinese
and Punjabi.

2.4 Constraints

The major constrain is obtaining the data from the GPS module
placed in train. Since there is a chance that train can run through area
where mobile coverage is not available. The microcontroller uploads
the location data using GSM module. Another constrain is admin
module create extra burden for the duty officer. In peak time, in large
stations there will be heavy traffic is there, so it will be very difficult
to upload the data of each train.

2.5 Assumptions and Dependencies

The primary assumption that is being made is in the concept of SIM

placed in the GSM module. We are planning to put Chatr SIM card
with basic plan. If other mobile companies give a better offer surely,
we will consider it.

2.6 Apportioning of Requirements

In future, we have a plan to implement a new module “Automatic

Railway level Crossing” as a part of this system.

9
3. SPECIFIC REQUIREMENTS

3.1 External Interfaces

The input of the system is the data from the GPS module and the
admin module. The output of the system is the data from the server.
So much external interfaces are not included in the system.

3.2 Functions

The primary function of the system is to track the whole train in the
railway network and give live update to the passengers.

3.3 Performance Requirements

To achieve the best performance, it is necessary to have good

quality of components. Once the components are into action, then it is
required that the components are in the ideal working condition atmosphere.
For example, a constant ambient power supply voltage of 5V is needed by the
micro controllerto work properly. As far as the GSM module is concerned,
the GSM Modem is built with Quad Band GSM/GPRS engine SIM900, which
works on frequencies 850/ 900/ 1800/ 1900 MHz. The Modem is coming with
selectable interfacing voltage, which allows us to connect 5V & 3V3
microcontroller directly without any level conversion chips. The baud rate is
configurable from 9600 115200 through AT command. The GSM/GPRS
Modem is havinginternal TCP/IP stack to enable you to connect with internet
via GPRS. It is suitable for SMS, Voice as well as DATA transfer application
in M2M interface. SIM900 is a quad band modem, being able to operate in
850, 900, 1800, 1900 MHz bands it is apt for worldwide compliance.

3.4 Logical Database Requirement

A big database is needed by the system and it will act as server. However,
such a server which can manage huge data can be provided by the google.

10
3.5 Design Constrains
The system can be implemented using a PIC16F877A micro controller, which
is a general purpose 8-bit micro controller that offers high performance and
very low power consumption. If there are other efficient micro controllers
which offers the same functionality and use, then that can also be used. The
main design constrain is to add GPS module in the circuit.

3.6 Software System Attributes

• Maintainability
The whole system is easy to maintain.
The sensors are easily available in the market, so maintenance of the product
is quite simple.
The Server is the heart of the system, and it needs to be maintained properly
and it should not be crashed.
It does not have too many interconnections; hence troubleshooting is easier.

• Usability
The system can be easily used by both passengers and railway
authority.

11
 4. APPENDICES

1. What are the safety measures to be taken for the system?

A. The first safety measure should be taken is for the GPS module,
because it is placed outside the train. Then there must be safety
measures taken for the circuit board for power variations.

2. What are the specific standards to be introduced in the system?

A. There should be good sensors so that there is maximum efficiency.

3. What is the maximum power that can be used by the system?

A. Anything which does not affect the other functionalities of the
circuit board

4. How should the battery be connected to the system?

A. It can be connected normally. But if there are any other better
methods, lets discuss.

5. What should be the final product called?

A. Railway Tracking and Arrival Time Prediction

12