CHANDIGARH UNIVERSITY

Project Title:

Railway Problem Analysis, Reporting and Inspecting System (RPARIS)

Chetan Sen1 Anivesh Jain2

1
 INDEX
1. INTRODUCTION
1.1. Problem Definition
1.2. Objective
1.3. Hardware Specification
1.4. Software Specification
2. Literature Survey
2.1. Existing System
2.2. Proposed System
2.3. Feasibility Study
2.3.1. Technical Feasibility
2.3.2. Economical Feasibility
3. System Analysis and Design
3.1. Requirement Specification
3.1.1. Functional Requirement
3.1.2. Non – Functional Requirement
3.2. Database Design Process
3.3. Non-Functional Testing Parameter
3.4. Data Flow Diagram
3.5. Testing Process
3.6. System Testing
3.6.1. Introduction to System Testing
3.6.2. Types of Testing
3.7. USE case Diagram
4. WORK-PROGRESS
5. RESULTS / OUTPUT
5.1. Start Frame
5.2. Main Frame
6. REFERENCES

2
 CHAPTER 1
INTRODUCTION
1.1 Problem Definition
In current scenario, as a passenger uses twitter to register their complaint by tagging the
railway minister and each complain is managed by a team of 100-150 people, which is
very hectic work and sometime problem remains unsolved and people who don’t use
twitter are unable to register their complaint.
1.2 Objective
A system that is very useful for passengers as well as for Indian Railway Department. There
are a lot of problems which are not resolved by current methodology, so to overcome these
issues and provide the better facility to passengers we have created the Railway Problem
Analysis, Reporting and Inspecting System (RPARIS).
1.3 Hardware Specification
• Desktop
• RAM: 2GB
1.4 Software Specification
• NetBeans
• phpMyAdmin
• Java
• jdk

3
 CHAPTER 2

LITERATURE SURVEY

2.1 Existing System

In current scenario, as a passenger uses twitter to register their complaint by tagging the
railway minister and each complain is managed by a team of 100-150 people, which is
very hectic work and sometime problem remains unsolved and people who don’t use
twitter are unable to register their complaint.
The toll-free services provided by railway service are not efficient and result in long
waiting queues.
Currently railway is using IVRS (Interactive Voice Responsive System) for solving
problems of the passengers.

2.2 Proposed System

This project is functional on a touch screen-based panels designed for Indian Railways
coaches including railway stations. Emphasis on problem solving of railway passengers
and improving the working efficiency of Indian railway is the key factor for this system.

A system that is very useful for passengers as well as for Indian Railway Department. There
are a lot of problems which are not resolved by current methodology, so to overcome these
issues and provide the better facility to passengers we have created the Railway Problem
Analysis, Reporting and Inspecting System (RPARIS).

2.3 Feasibility Study

A feasibility study is an analysis used in measuring the ability and likelihood to complete a
project successfully including all relevant factors. It must account for factor that affects it
such as economic, technological, legal and scheduling factors. Project managers uses
feasibility study to determine potential positive and negative outcome of a project before
investing a considerable amount of time and money into it.

4
 2.3.1 Technical Feasibility
In this step, we verify that proposed systems are technically feasible or not i.e., all the
technologies required to develop the system are available readily or not. Technical
feasibility determines whether the organization has the technology and skills necessary to
complete the project and how this should be obtained.
The System can be feasible because of the following grounds:
1. All necessary technology exists to develop the system. This system is flexible and it can
be expanded further.
2. This system can give guarantees of accuracy, ease of use, reliability and the data
security.
Our project is technically feasible because, all the technologies needed for our project
are readily available.

2.3.2 Economical Feasibility

Economically, this project is completely feasible because it does not require any extra financial
investment. In this step, we verify which proposal is more economical. We compare the
financial benefits of the new system with investment. Economic feasibility analysis is the most
commonly used method for determining the efficiency of a new project. It is also known as
cost analysis. It helps in identifying profit against investment expected from a project. Cost
and time are the most important factors that involved in this field of study.

Financial benefits must be equal or exceeds the costs. In this issue, we should consider:

1. The cost of the conduct a full system investigation.

2. The cost of hardware for the class of the application being consider.

3. The development tools.

4. The cost of maintenance etc.

5
 CHAPTER 3
SYSTEM ANALYSIS AND DESIGN
3.1 Requirement Analysis
The basic requirement is:
1. Tough facility in the train
2. Login facility
3. Touch panel on each station

3.1.1 Functional Requirement

Required software is for conducting online examination and providing results. The system
should satisfy the following requirements:
1. Administrator Aspect
1. Taking backup of the database.
2. Editing/Deleting/Creating the records.
3. Adding employee, department.
4. Changing the super password.

2. Department Aspect
1. Creating id of the employee.
2. Setting the master password.

3.1.2 Non – Functional Requirement

1. Performance Requirements:

1. After registering the complaint, the passengers shall get the notification.

2. The software shall support use of multiple users at a time.

2. Safety Requirements:

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.

6
3.2 Database Design Process

The overall objective in the development of database technology has been to treat data as an
organizational resource and has integrated whole. It is fair to say that database play a critical
role in almost all area where computers are used, including Business, electronic commerce,
engineering, medicine, law, education and library science. Database management system
allows data to be protected and organized separately from other resources.

List of Tables:

1. Current Status
2. Division
3. Dutyreg
4. Employee
5. Ps
6. Problemrt
7. Prt
8. Rstdetail
9. Rtproblem
10. Station
11. Route
12. Train
13. Zone

3.3 Non – Functional Testing Parameters

1) Security: This parameter defines how a system is safeguarded against deliberate and
sudden attacks from internal and external sources. This is tested via Security Testing.
2) Reliability: The extent to which any software system continuously performs the
specified functions without failure, this is tested Reliability Testing.
3) Survivability: The parameter checks that the software system continues to function
and recovers itself in case of system failure. This is checked by Recovery Testing.
4) Availability: The parameter determines that the degree to which user can depend on
the system during its operation. This is checked by Stability Testing.

7
 5) Usability: The ease with which the user can learn, operate, prepare inputs and outputs
through interactions with a system. This is checked by Usability Testing.
6) Scalability: The term refers to the degree in which any software application can its
processing capacity to meet an increase in demands. This is tested by Scalability
Testing.
7) Interoperability: This is a non – functional parameter that checks a software system
interface with other software systems. This is checked by Interoperability Testing.
8) Efficiency: The extent to which any software system can handle capacity, quantity and
response time.
9) Flexibility: The term refers to the ease with which the application can work in different
hardware and software configurations. Like minimum RAM, CPU requirements.
10) Portability: The flexibility of software to transfer from its current hardware to software
requirement.
11) Reusability: It refers to a portion of the software system that can be converted for use
in another applications.

3.4 Data Flow Diagrams (DFDs)

A data-flow diagram (DFD) is a way of representing a flow of a data of a process or a system

(usually an informative system). The DFD also provides information about the outputs and
inputs of each entity and the process itself. A data-flow diagram has no control flow, there are
no decision rules and no loops. Specific operations based on the data can be represented by a
flowchart.

8
3.5 Testing Process:

3.5.1 INTRODUCTION TO SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality
of components, sub-assemblies, and/or a finished product. It is the process of exercising
software with the intent of ensuring that the software system meets its requirement and user
expectation and does not fail in an unacceptable manner. There are various types of tests, each
type addresses a specific testing requirement.

3.5.2 TYPES OF TESTING

1. Unit Testing: Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid outputs. All
decision branches and internal code flow should be validated. It is the testing of individual
software units of the applications. It is done after the completion of an individual unit before
integration. This is a structural testing, that relies on knowledge of its construction and is
invasive. Unit tests perform basic tests at component level and test a specific business process,
application, and/or system configuration. Unit tests ensures that each unique path of business
process performs accurately to the documented specifications and contains clearly defined
inputs and expected results.

2. Integration testing: Integration tests are designed to test integrated software components to
determine if they actually run as one program. Testing is event driven and is more concerned
with the basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.

3. System Testing: System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An example of
system testing is the configuration-oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration points.

9
4. White Box Testing: White Box Testing is a testing in which in which the software tester
has knowledge of the inner workings, structure and language of the software, or at least its
purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.

5. Black Box Testing: Black Box Testing is testing the software without any knowledge of the
inner workings, structure or language of the module being tested. Black box tests, as most
other kinds of tests, must be written from a definitive source document, such as specification
or requirements.

3.6 USE CASE DIAGRAM

To model a system, the most important aspect is to capture the dynamic behaviour. Dynamic
behaviour means the behaviour of the system when it is running/operating.

Only static behaviour is not sufficient to model a system rather dynamic behaviour is more
important than static behaviour. In UML, there are five diagrams available to model the
dynamic nature, there should be some internal or external factors for making the interaction.
These internal and external agents are known as actors. USE CASE diagrams consist of actors,
use cases and their relationships. The diagram is used to model the system/subsystem of an
application. A single use case diagram captures a particular functionality of a system.

10
 CHAPTER 4

WORK-PROGRESS

PHASES WEEK WORK STATUS

Phase I 1st Data/Information Completed
Collection
Phase II 2nd Development In-process
Phase III 3rd Testing NA
Phase IV 4th Report/Submission NA

CHAPTER 5

EXPECTED OUTCOME

Fig 5.1 Start Frame

11
 Fig 5.2 Main Frame

CHAPTER 6

REFERENCES

[1] "Java SE Overview". Oracle Corporation. Retrieved February 26, 2017.

[2] "Java SE 6 Release Contents". Oracle Corporation and/or its affiliates.
Retrieved January 1,2013.
[3] "Java SE 7 Features and Enhancements". Oracle Corporation. Retrieved
2016-05-04. [...] JDK 7,Oracle's implementation of Java SE 7.
[4] www.tutorialspoint.com
[5] www.coms.indianrailways.gov.in/criscm/home.seam

12