FINAL YEAR MAJOR PROJECT REPORT (PROJECT STAGE – I)

MANAGEMENT OF RAILWAY RENT HOUSE

AND HOLIDAY HOMES

(INDUSTRY)

Submitted in Partial Fulfillment for the Award of Degree of Bachelor of

Technology in Information Technology from Rajasthan Technical
University, Kota

COORDINATOR: SUBMITTED BY:

Dr. Basant Agarwal Punit Kumar(15ESKCS136)

(Associate professor) Rajkumar Kachhawa (15ESKCS139)

MENTOR: Sahil Jindal (15ESKCS150)

Mr. Sunil Dhankar Saket Kumar (15ESKCS151)

(Associate professor)
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

SWAMI KESHWANAND INSTITUTE OF

TECHNOLOGY, MANAGEMENT & GRAMOTHAN

Ramnagaria (Jagatpura), Jaipur – 302017

CERTIFICATE

This is to certify that Final Year Minor Project Report (Project Stage – I) entitled
“MANAGEMENT OF RAILWAY RENT HOUSE AND HOLIDAY HOMES
” has been duly submitted by

• Punit kumar (15ESKCS135)

• Rajkumar (15ESKIT045)

• Sahil Jindal (15ESKCS150)

• Saket Kumar (15ESKCS151)

for partial fulfillment of the Degree of Bachelor of Technology of Rajasthan Technical

University. It has been found satisfactory and hence approved for submission as Minor Project
during academic session 2018-2019.

Date:

COORDINATOR: MENTOR: HEAD OF DEPARTMENT:

Dr. Basant Agarwal Mr. Sunil Dhankar Prof. Dr. C.M. Choudhary

(Associate professor) (Associate professor) (HOD, CS)

1
 Final Year Major Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

SWAMI KESHWANAND INSTITUTE OF

TECHNOLOGY, MANAGEMENT & GRAMOTHAN

Ramnagaria (Jagatpura), Jaipur – 302017

ABSTRACT

We are stuck with technology when what we really want is just stuff that works. With the current
paradigm shift in technological field, there is an urgent need to embrace and appreciate the
power of technology. Railway sector remains vigilant to face the challenges of change by
employing a new strategy that facilitates easy management of rental houses.

At present, the allocation of accommodation in Railway Rest Houses, Holidays Homes is done
manually. The request is to be given in writing and there is no mechanism to advise the applicant
about status of booking of rooms. This causes uncertainty and difficulty in planning one’s
programme. Hence there is need to develop a rental house management system that can simplify
work for the rental managers so that all their work can be efficient and effective.

From the information I gathered I realized all work was done manually with a lot of paper work
involved. Papers can easily get damaged or get lost leading to loss of data. It is also expensive to
keep on buying files to store your records. A lot of files make a place look untidy and also
consume a lot of space. Getting a certain file to checkdata from many files becomes a difficult
task. Considering those facts, I decided to develop a rental house management system that can
solve all the problems experienced with the current manual system. The system was developed
such manner that it provides maximum user friendly interface.

Keywords:

Data Management,Ionic,Firebase,MongoDB.

2
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

SWAMI KESHWANAND INSTITUTE OF

TECHNOLOGY, MANAGEMENT & GRAMOTHAN

Ramnagaria (Jagatpura), Jaipur – 302017

DECLARATION

We hereby declare that the report of the project entitled MANAGEMENT OF RAILWAY
RENT HOUSE AND HOLIDAY HOMES is a record of an original work done by us at Swami
Keshvanand Institute of Technology, Management & Gramothan, Jaipur under the
mentorship of Mr. Sunil Dhankar (Dept. of Computer Science and Technology) and
coordination of Mr. Basant Agarwal (Dept. of Computer Science and Technology). This project
report has been submitted as the proof of original work for the partial fulfillment of the
requirement for the award of the degree of Bachelor of Technology (B.Tech) in the Department
of Computer Science and Technology. It has not been submitted anywhere else, under any
other program to the best of our knowledge and belief.

Team Members: Signatures:

Punit Kumar (15ESKCS136)

Rajkumar kachhawa (15ESKCS139)

Sahil Jindal (15ESKCS150)

Saket Kumar (15ESKCS151)

3
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

ACKNOWLEDGMENT

A project of such a vast coverage cannot be realized without help from numerous sources and
people in the organization. We take this opportunity to express our gratitude to all those who
have been helping us in making this project successful.

We are highly indebted to our faculty mentor Mr. Sunil Dhankar. He has been a guide, motivator
& source of inspiration for us to carry out the necessary proceedings for the project to be
completed successfully. We also thank our project coordinator Mr. Basant Agarwal for her co-
operation, encouragement, valuable suggestions and critical remarks that galvanized our efforts
in the right direction.

We would also like to convey our sincere thanks to Prof. C.M. Choudhary, HOD, Department of
Computer Science and Technology, for facilitating, motivating and supporting us during each
phase of development of the project. Also, we pay our sincere gratitude to all the Faculty
Members of Swami Keshvanand Institute of Technology, Management & Gramothan, Jaipur and
all our Colleagues for their co-operation and support.

Last but not least we would like to thank all those who have directly or indirectly helped and
cooperated in accomplishing this project.

Team Members:

Punit Kumar (15ESKCS136)

Rajkumar kachhawa (15ESKCS139)

Sahil Jindal (15ESKCS150)

Saket Kumar (15ESKCS151)

4
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

INDEX

CERTIFICATE.........................................................................................................................................................1

ABSTRACT.............................................................................................................................................................2

DECLARATION.....................................................................................................................................................3

ACKNOWLEDGMENT........................................................................................................................................4

UNIT – 1 PROJECT CHARTER.....................................................................................................................12

1.1 Problem Statement & Objective..................................................................................................12

1.2 Market Survey...................................................................................................................................13

1.3 Introduction to Project....................................................................................................................14

1.4 Proposed Logic.................................................................................................................................15

1.5 Scope of the Project........................................................................................................................17

UNIT – 2 SYSTEM REQUIREMENT SPECIFICATION......................................................................19

2.1 Overall Description..........................................................................................................................19

2.1.1 Product Perspective........................................................................................................19

2.1.1.1 System Interfaces.........................................................................................19

2.1.1.2 User Interfaces..............................................................................................19

2.1.1.3 Hardware Interfaces....................................................................................19

2.1.1.4 Software Interfaces......................................................................................20

2.1.1.5 Communication Interfaces........................................................................20

2.1.1.6 Memory Constraints 20

2.1.1.7 Operations......................................................................................................20
5
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

2.1.1.8 Site Adaption Requirements.....................................................................21

2.1.2 Project Functions...........................................................................................................21

2.1.3 User Characteristics......................................................................................................21

2.1.4 Constraints.......................................................................................................................21

2.1.5 Assumptions & Dependencies...................................................................................22

2.2 Specific Requirements....................................................................................................................22

2.2.1 User Interface Requirements......................................................................................22

2.2.2 System Product Features.............................................................................................23

2.2.2.1 Security...........................................................................................................23

2.2.2.2 Maintainability..............................................................................................23

2.2.2.3 Portability........................................................................................................23

UNIT– 3 SYSTEM DESIGN SPECIFICATION........................................................................................24

3.1 System Architecture........................................................................................................................24

3.2 Module Decomposition..................................................................................................................24

3.3 High Level Design Diagrams........................................................................................................24

3.3.1 Usecase Diagrams..........................................................................................................25

3.3.2 Activity Diagram...........................................................................................................26

3.3.3 Sequence Diagram.........................................................................................................27

3.3.4 Data Flow Diagram……………………………………………………….. 29

3.3.5 Class Diagram.................................................................................................................30

3.3.6 Entity Relationship Diagram......................................................................................31

6
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.7 PERT Chart ………………………………………………………………..32

UNIT– 4 METHODOLOGY & TEAM.........................................................................................................33

4.1 Introduction to Waterfall Model.................................................................................................33

4.2 Team Members, Roles & Responsibilities................................................................................35

UNIT– 5 SYSTEM TESTING...........................................................................................................................36

5.1 Functionality Testing......................................................................................................................37

5.2 Performance Testing......................................................................................................................37

5.3 Usability Testing..............................................................................................................................38

5.4 Server Side Interfacing..................................................................................................................38

5.5 Client Side Compatibility.............................................................................................................38

UNIT– 6 TEST EXECUTION SUMMARY................................................................................................39

UNIT– 7 PROJECT SCREENSHOTS...........................................................................................................40

UNIT– 8 PROJECT SUMMARY AND CONCLUSIONS......................................................................43

UNIT– 9 FUTURE SCOPE................................................................................................................................44

UNIT– 10 REFERENCES..................................................................................................................................45

UNIT– 11 PROJECT PAPER............................................................................................................................48

11.1 Abstract............................................................................................................................................48

11.2 Introduction....................................................................................................................................48

11.3 Ease of use.......................................................................................................................................49

11.4 Solutions........................................................................................................................................50

11.5 Security Requirements...............................................................................................................51

7
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

11.6 Advantages....................................................................................................................................51

11.7 Disadvantages.................................................................................................................................51

11.8 Working Principle........................................................................................................................52

11.9 References.......................................................................................................................................53
8
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT – 1 PROJECT CHARTER

1.1 Problem Statement & Objective

Problem: Lot of man power and paper required in off line booking.

Reasons: There are several reasons for the problem

 At present, the allocation of accommodation in Railway Rest Houses, Holidays Homes is

done manually. The request is to be given in writing and there is no mechanism to advise
the applicant about status of booking of rooms. This causes uncertainty and difficulty in
planning one’s programme. Hence there is need to develop a rental house management
system that can simplify work for the rental managers so that all their work can be
efficient and effective

Solution: In this project, the following solution is given

• We are providing a better platform for the users to view and book Railway Rent Houses
and Holiday Homes.
• The very friendly design will lead the user to every module very easily without any
difficulty.

Objective: At present, the allocation of accommodation in Railway Rest Houses, Holiday

Homes is done manually. The request is to be given in writing and there is no mechanism to
advice the applicant about status of booking of rooms. This causes one's programme. An online
system of submitting request and allocation of rooms is required

1.2 Market Survey

Over the past few years, the use of online booking system has increased globally and this trend
is set to continue. With the internet more accessible and convenient than ever, consumers
are opting to book accommodation online, a move that has seen a change in the way hotels
get their rooms to market (Carter, 2013). Over the past two decades, industrial marketers have
adopted increasingly complex channel strategies inresponse to shifts in consumer shopping
behavior, the globalization of markets, and the advent of the internet (Webb, 2002:96). Business
(B2B) and Business to Consumers (B2C) application has changed the situation rapidly
(Buhalis and Licata, 2002:208). Unarguably, online tourism has successfully emerged as a
platform that enables direct bookings, electronic payments, business to business (B2B) and
business to consumer (B2C) trading among product marketers, accomodation establishments,
travel agents, resellers and customers. Internet and related developments have been quite
instrumental in growth of online tourism and online economy (Dixitet al. 2006).
An online booking /reservation system will let you accept bookings for your services online
(Tani, 2012). Technology has transformed many aspects of life in the 21st century, including the
way many of us make reservations. Whether booking tickets for a show, a seat on an airplane
or a room to spend the night, online booking systems make the process fast and easy (Blank
2014). Online tourism equips a tourist, tour operator or travel agent for convenient exchanges
using electronic medium. User groups globally are finding online technologies supportive
in decision making for availing tourism products and services (Dixit et al., 2006). Airlines,
hotels, and tour operators, all of whom play an important role and have their own web sites, have
been joined by „travel gates‟. These are websites or Internet portals, which allow a consumer to
book a hotel either as a separate service or as part of a package. These travel gates are
newcomers in the market and compete with existing offerors (Alleweldt et al., 2009:3).

1.3 Introduction to Project

As the name recommends, the Online Hotel Management System permits the clients globally to
reserve the rooms in the hotel at any time. It will provide a unique search and book functionally
for the customers anywhere in the world. This project can be used by the clients and the travel
agencies who will help them to reserve the hotel of their choice. Sometimes people face problem
in reserving the hotels in the places where they want to visit. In that situation, this project can be
of great relief to them. The user interface must be simple and easy to understand even by the
common man.
The admin has the right to update or add the hotel or the room information. The clients can
cancel the already booked room in the particular hotel on a particular day. This will be one of the
exciting projects that one can implement in real time world. The highlights that can be added to
the online hotel management system are given below:-

 Access anywhere: The online hotel reservation project can be reached at any time and
anywhere from the world with great efficiency.
 Easy booking: The rooms in the particular hotel can be reserved easily through this site
with great expertise.
 Hotel description: This project will contain the hotel information of the hotels that are
present in the particular area.
 Room availability: The rooms that are open in the particular hotel must be refreshed in
real time.
 Category: The hotels can be classified based on the appropriate region of your
preference.
 Price: The price or rent of the appropriate rooms in the appropriate hotel in the chosen
section will also be updated

14
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

1.4 Proposed Logic

In our project, we have a vehicle equipped with RFID tag and computer connected to Transceiver
positioned at the Toll station. Whenever the vehicle enters into the coverage area of transceiver, it
locates the tag and decodes the code assigned to that particular tag. After receiving the code, it is
forwarded to the computer situated at the Toll station. The computer then recognizes the code
and automatically access the database and if the vehicle has its valid prepaid account at the toll
station, the appropriate toll is deducted from that account and the gate is opened to allow the
vehicle to pass. And if the vehicle doesn’t have a valid prepaid account or it is not a daily
traveler, it will have to pass through a manual check post which will be in another lane. By using
the database we can avoid necessity to transmit entire data from tag thus enabling us to use tag
with very less memory requirement i.e. we store only 4 or 6 digit code number in the Tag. And
this 4 or 6 digit code is related to the database which is related to the database which is present
on the computer. Each Tag has different code number. It also reduces error probability and saves
processing time.

15
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

An RFID tag is comprised of a microchip containing identifying information and an antenna that
transmits this data wirelessly to a reader. At its most basic, the chip will contain a serialized
identifier, or license plate number, that uniquely identifies that item,

Similar to the way many bar codes are used today. A key difference, however is that RFID tags
have a higher data capacity than their bar code counterparts. This increases the options for the
type of information that can be encoded on the tag, including the manufacturer, batch or lot
number, weight, ownership, destination and history (such as the temperature range to which an
item has been exposed). In fact, an unlimited list of other types of information can be stored on
RFID tags, depending on application needs. An RFID tag can be placed on individual items,
cases or pallets for identification purposes, as well as on fixed assets such as trailers, containers,
totes, etc.

Figure 1.1 - Working of online toll payment system

An RFID tag is installed on each vehicle with read/write memory. An RFID reader at the gate
reads this data from the vehicle as it approaches the toll booth. RFID reader communicates with
PC using UART (Universal Asynchronous Receiver/Transmitter). UART takes bytes of data and
transmits the individual bits in a sequential fashion. PC consists of the entire database which is
updated periodically. Now after reading the information, PC compares the data in the database

16
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

and allows the access accordingly by opening/closing the gate. The pressure of the vehicle is
obtained using the pressure sensor and accordingly the pressure of the vehicle is displayed on the
display. A counter is used to count the number of vehicles. The amount on the basis of weight &
the count of vehicles is also displayed on the screen. The amount to be paid is automatically
deduced from the respective bank.

Figure 2.1 - Block Diagram

This tag will continuously emit RF signals. When the vehicle will reach at the toll booth the RF
receiver will detect these RF signals. The signals are amplified and are passed to microcontroller.
Now, with the help of PC interface unit the data collected is passed to PC through serial port.
Software developed will show all the details about the vehicle on the screen. Details like date
time and id will be stored in the access database. Microcontroller will check whether the user is
valid or not, if valid the microcontroller will intimate the gate control which is supported by a
stepper motor. The aftermath details regarding the deducted amount and the main account
balance are intimated to the user’s mobile through GSM technology.
1.5 Scope of the Project

17
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

Implementation of image processing for centralize data recording in our present concept we are
only using the RFID (Radio Frequency Identification Device) system for vehicle detection. So
we can extend the scope of this concept in other way for centralize data recording. For that
purpose we can use the IR counter at the entry gate which is followed by the Camera which will
be continuously capturing the images of the vehicles entering into the toll plaza. And the third
step the RFID is collecting the vehicle number. Now when the vehicle passes through the IR
counter it traces the outline of the vehicle, in the next step the camera will take the image of the
vehicle & followed by the RFID to record the data related to the vehicle. Whenever the matter of
Integration of systems comes to mind, we think of a system having the following important
features viz. Accuracy: All the functionally bonded logical dependencies must be integrated.
Efficiency: The whole system should work under all circumstances and on a long run it should
work efficiently irrespective of their proprietary format. Cost Effectiveness: As our software do
not require any special software for implementation hence is less costly as compared to other
existing system. Any Prerequisite for the use: As the existing systems are not altered, and
integration is done at the background hence there is no need for any training.
18
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT – 2 SYSTEM REQUIREMENT SPECIFICATION

2.1 Overall Description

This section and its subsections contain the description of the project components such as
interfaces, performance requirements, design constraints, assumptions and dependencies etc.

2.1.1 Product Perspective

The application will be a Windows / Linux based, self-contained and independent product.

2.1.1.1 System Interfaces

The main focus in our project is to use the software components. The various software that we
will use for the completion of this project are:

Software Package: VisualCode Studio, Compass, Postman.

Language for Development:

Database: MongoDB,Firebase

2.1.1.2 User Interfaces

 Both users and administrator on internet will be using HTTP protocol.

 User uses Android application for availing the Booking Website services.

 Administrator uses web application to manage the application service for their users.

2.1.1.3 Hardware Interfaces

Here our main focus is on the reduction of the hardware components. Hence the hardware that
we have used in the project can be given as:

1. Computer

2. External Storage Device

3. Connectivity Drivers and routers.

19
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

2.1.1.4 Software Interfaces

The main focus in our project is to use the software components. The various software that we
will use for the completion of this project are:

Software Package: VisualCode Studio, Compass, Postman.

Language for Development: HTML,CSS,TYPESCRIPT,IONIC

FRAMEWORK,MongoDB,Angular Framework,ExpressJS,NodeJS.

2.1.1.5 Communication Interfaces

 Online Booking System will be connected to the World Wide Web.

 The HTTP protocol will be used to facilitate communication between the client and
server.

2.1.1.6 Memory Constraints

 At least 256 MB of RAM and 2 GB of space on hard disk will be required for running the
application on client end.

 Similarly, a minimum of 2048 MB of RAM and 20 GB of space on hard disk will be

required for running the application on server end.

2.1.1.7 Operations

 The DBA at the client side will be assumed responsible for manually deleting or
archiving obsolete or non-required data from the database as per client’s requirements.

 This will include database backup and recovery options also.

 The MongoDB and Firebase web server will host and maintained on a remote server
addressed by a URL based address.

 This software will be operated on mobile phones compatible with every android versions
ranging from version no. -1.0 to version no.-8.1.other application that it uses is GPS
technology and RFID technology.

20
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

2.1.1.8 Site Adaption Requirements

The computing terminals connected to network (internet / intranet) at the client end will be
required to support the hardware and software interfaces specified in above sections.

2.1.2 Project Functions

The system will allow access only to authorized uesrs with specific roles (Administrator, user,
and guest). Depending upon the user’s role, he / she will be able to access only specific modules
of the system.

A summary of the major functions that the software will perform:

a. A Login facility for enabling only authorized access to the system.

b. User (with role Customer/Employee) Who will book the rooms according to their
requirements.

c. Users (with role Administrator) will be able to ‘reset’ the system-leading to deletion of all
existing information from the backend database.

d. Users (with role Administrator) will be able to create / modify / delete new / existing user
accounts.

2.1.3 User Characteristics

The most important user class for this product will be the customers who will book guests
houses and holiday homes on the basis of their requirements and acoomodation needs, also
the people who frequently books rooms in these guest houses and holiday homes.

2.1.4 Constraints

 Due to limited features of DBMS being used, performance tuning features will not be
applied to the queries and thus the system may become slow with the increase of data
records being stored.

 Due to limited features of DBMS, database auditing will also not be provided.

21
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

 As the application runs over a network environment, well documented security policy is
required to prevent and safeguard data as well as services over the network.

2.1.5 Assumptions & Dependencies

 It is assumed that people who will be using the application will certainly know how to
operate mobile phones, if not then it will be a barring factor for the users who wants to
use this application.

 The project is dependent on the use of RFID chip that belongs to other technology.

2.2 Specific Requirements

This section presents the software requirements to a level of detail sufficiency to enable
designers to design and testers to test the system.

2.2.1 User Interface Requirements

Following screens will be provided by the system:

Log-in page:

This will be the first screen to be displayed. It will allow the users to login and validate the
further steps and proceed with bookings. Various fields available on this screen will be as
follows:

Log-in ide: Authentic user to be logged in.

password: Alphanumeric credentials.

Booking Status:

This screen will be showing the room status on the website and the selected room by the user.

Booking Confirmation:

This screen will show the booking confirmation message and will email the booking status and
credentials.

22
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

2.2.2 System Product Features

2.2.2.1 Security

The system will check all username and password given by the users to the system to ensure that
whether the user is authorized one or not. If any mismatch occurs then the users can’t login to
the system. Only authorized user can access the system.

2.2.2.2 Maintainability

The application will be designed in a manner to make it easy to incorporate new requirements in
individual modules such as user accounts activation / deactivation.

2.2.2.3 Portability

The application will be easily portable among any systems that have compatible software and
hardware installed.
23
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 3 SYSTEM DESIGN SPECIFICATION

3.1 System Architecture

System architecture presents the schematic view of the complete system along with its major
components and their connectivity. The overall architecture of the proposed system will be as
follows.

3.2 Module Decomposition

The proposed system can be decomposed into following major modules:

1. Vehicle Selection: Provides information about the fares for different vehicles at different
routes.

2. Balance check: The balance of the account is checked.

3. Balance Update: The balance is updated after deduction.

Module - 1: In this module, the user can select vehicle type and route type and the amount to be
paid is displayed.

Module - 2: In this module, the balance in the account is checked. If it is sufficient then it moves
forward otherwise payment is made at the toll booth.

Module - 3: In this module, the balance in the account is changed. The balance field holds the
new balance after updating.

3.3 High Level Design Diagrams

3.3.1 Use case Diagram

 24

Figure 3.1 – Usecase Diagram

Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur
25
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.2 Activity Diagram

Figure 3.2 – Activity Diagram

26
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.3 Sequence Diagram

Figure 3.3 – Sequence Diagram for Login

27
Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur
Figure 3.4–Sequence Diagram for Toll Payment

28
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.4 Data-Flow Diagram

Figure 3.5 – Dataflow Diagram

29
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.5 Class Diagram

Figure 3.6 – Class Diagram

30
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.6 Entity Relationship Diagram

Figure 3.7 – Entity Relationship Diagram

31
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

3.3.7 PERT Chart

Figure 3.8 – P.E.R.T. Chart

32
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 4 METHODOLOGY & TEAM

4.1 Introduction to Waterfall Model

The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each
phase must be completed before the next phase can begin and there is no overlapping in the
phases.

The waterfall Model illustrates the software development process in a linear sequential flow;
hence it is also referred to as a linear-sequential life cycle model. This means that any phase in
the development process begins only if the previous phase is complete. In waterfall model
phases do not overlap. In "The Waterfall" approach, the whole process of software development
is divided into separate phases. In Waterfall model, typically, the outcome of one phase acts as
the input for the next phase sequentially.

Following is a diagrammatic representation of different phases of waterfall model.

Figure 4.1 – Waterfall Model with Feedback

33
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

The sequential phases in Waterfall model are:

 Requirement Gathering and analysis: All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification doc.

 System Design: The requirement specifications from first phase are studied in this phase
and system design is prepared. System Design helps in specifying hardware and system
requirements and also helps in defining overall system architecture.

 Implementation: With inputs from system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed
and tested for its functionality which is referred to as Unit Testing.

 Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

 Deployment of system: Once the functional and non functional testing is done, the
product is deployed in the customer environment or released into the market.

 Maintenance: There are some issues which come up in the client environment. To fix
those issues patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined
set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model".
In this model phases do not overlap.

Every software developed is different and requires a suitable SDLC approach to be followed
based on the internal and external factors. Some situations where the use of Waterfall model is
most appropriate are:

 Requirements are very well documented, clear and fixed.

34
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

 Product definition is stable.

 Technology is understood and is not dynamic.

 There are no ambiguous requirements.

 Ample resources with required expertise are available to support the product.

 The project is short.

Waterfall Model Pros & Cons

Advantage

The advantage of waterfall development is that it allows for departmentalization and control. A
schedule can be set with deadlines for each stage of development and a product can proceed
through the development process model phases one by one.

Development moves from concept, through design, implementation, testing, installation,

troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order.

Disadvantage

The disadvantage of waterfall development is that it does not allow for much reflection or
revision. Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-documented or thought upon in the concept stage.

4.2 Team Members, Roles & Responsibilities

Team Member Project Role Responsibilities

Punit Kumar
Rajkumar
Sahil Jindal
Saket Kumar

Table 4.1 – Roles and responsibilities

35
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 5 SYSTEM TESTING

The designed system has been testing through following test parameters.

5.1 Functionality Testing

In testing the functionality of the web sites the following features were tested:

• Links

a) Internal Links:

All internal links of the website were checked by clicking each link individually and providing
the appropriate input to reach the other links within.

b) External Links

Till now no external links are provided in our website but for future enhancement we will
provide the links to the employee’s actual profile available online and link up with the our
system online etc.

c) Mail Links

No mail links are provided in our website till this stage but this is also a future enhancement of
our website to trigger mails to people for keeping them updated about the leave sanctioning and
other details.

d) Broken Links

Broken link are those links which so not divert the page to specified page or any page at all. By
testing the links on our website there was no link found on clicking which we did not find any
page.

• Forms

a) Field validation

Checks have been applied on starting and ending dates, ie, the starting dates of leave should
always fall before their respective ending dates.

36
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

b) Error message for wrong input

Error messages have been displayed as and when we enter the wrong details (eg. Dates), and
when we do not enter any detail in the mandatory fields. For example: when we enter wrong
password we get error message for acknowledging us that we have entered it wrong and when
we do not enter the username and/or password we get the messages displaying the respective
errors.

c) Optional and Mandatory fields

All the mandatory fields have been marked with a red asterisk (*) and apart from that there is a
display of error messages when we do not enter the mandatory fields. For example: As the first
name is a compulsory field in all our forms so when we do not enter that in our form and submit
the form we get an error message asking for us to enter details in that particular field.

• Database

Testing is done on the database connectivity.

In the database testing we included following cases:

a) Entries in database through frontend and checked for the same in the tables.

b) Checked for the data types.

c) Checked for range of each type of data.

d) If entries made in one table are affecting other tables then we have checked those entries also.

e) We not just added details in the database by default but also did the same using the frontend.

5.2 Performance Testing

Performance testing can be applied to understand the website’s scalability, or to benchmark the
performance in the environment of third party products such as servers and middleware for
potential purchase. This can only be done once it is put into use on the actual internet server and
tested by the users.

37
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

Till now it is done using the null modem on two systems.

The system load includes:

a) What is the number of users per time?

b) Checking for peak loads and how system behaves.

c) Amount of data accessed by user.

This is done using only 2 systems for now so cannot be tested for load unless we deploy it on a
real server machine.

5.3 Usability Testing

Usability testing is the process by which the human-computer interaction characteristics of a

system are measured, and weaknesses are identified for correction.

a) Ease of learning

b) Navigation

c) Subjective user satisfaction

d) General appearance

As system is not put into the real time use so it’s not yet tested for usability.

5.4 Server Side Interfacing

In this we tested the server side interface. This was done by verifying that communication is
done properly. Also the compatibility of server with software, hardware, network and database
was tested.

5.5 Client Side Compatibility

The client side compatibility is also tested using various browsers like Google Chrome, Mozilla
Firefox and Internet Explorer.

38
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 6 TEST EXECUTION SUMMARY

Execution Test Summary Report is an overall view of Testing Process from start to end. Test Plan
comes at the starting of project while Test Summary Report comes at the end of testing process.
This report is given to the client for his understanding purpose.

The Test Summary Report contents are:

1. Test Case ID generated

2. Total number of resources consumed

3. Passed Test Cases

4. Failed Test Cases

5. Status of Test Cases

S.No Test Test Case Description Expected Test Case No. of

Case Outcome Status Resources
ID Consumed
1. PR01 “Toll_Tax.py” accepts vehicle Accepts 1-3 PASS Monitor,
type only Keyboard
2. PR02 “Toll_Tax.py” accepts route Accepts 1-2 PASS Monitor,
type only Keyboard

Table 6.1 – Test Case Summary

39
Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 7 PROJECT SCREENSHOTS

Figure 7.1 – RFID Application page

40
Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur
Figure 7.2 – Adding new records

41
Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur
Figure 7.3 – Detection of vehicles

42
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 8 PROJECT SUMMARY AND CONCLUSIONS

RFID and sensor network are the foundation technologies of internet of things. With the wide
applications of RFID, many new modeling and optimization problems have emerged. The
research situations on these new problems about two aspects of RFID technology and
applications are surveyed in this paper. The main problems include: RFID reader network
placement optimization; tag load balancing of readers; data allocation optimization of RFID tag
memory; anti-collision algorithms in reading a lot of tags; RFID system ROI analysis and
investment decision; Business Process Reengineering problems within RFID applications;
inventory control optimization in supply chain with RFID; new problems of item-level
management with RFID, dynamic information and quick response with RFID, and so on. The
research and solution of these problems will provide the theoretical support to resource optimal
allocation and economic efficiency enhancement with RFID applications in practices.

OTPS RFID solutions use modern wireless technologies to help your business track inventory
and equipment. An OTPS RFID system is composed of an RFID reader; a standard Windows
based PC, and RFID tags or transponders. The RFID tag is attached or placed inside of the
equipment or inventory. OTPS RFID tags contain microelectronic circuits that store product
information. The tags transmit this information to a remote RFID reader.

43
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 9 FUTURE SCOPE

Implementation of image processing for centralize data recording In our present concept we are
only using the RFID (Radio Frequency Identification Device) system for vehicle detection. So
we can extend the scope of this concept in other way for centralize data recording. For that
purpose we can use the IR counter at the entry gate which is followed by the Camera which will
be continuously capturing the images of the vehicles entering into the toll plaza. And the third
step the RFID is collecting the vehicle number. Now when the vehicle passes through the IR
counter it traces the outline of the vehicle, in the next step the camera will take the image of the
vehicle & followed by the RFID to record the data related to the vehicle. Whenever the matter of
Integration of systems comes to mind, we think of a system having the following important
features viz. Accuracy: All the functionally bonded logical dependencies must be integrated.
Efficiency: The whole system should work under all circumstances and on a long run it should
work efficiently irrespective of their proprietary format. Cost Effectiveness: As our software do
not require any special software for implementation hence is less costly as compared to other
existing system. Any Prerequisite for the use: As the existing systems are not altered, and
integration is done at the background hence there is no need for any training.
44
 Final Year Minor Project Report (Project Stage – I), Academic Session 2018-2019, SKIT, M & G, Jaipur

UNIT– 10 REFERENCES

1. http://nevonprojects.com/toll-collection/
2. www.pragimtech.com/home.aspx
3. www.webcheatsheet.com/php/connect_mysql_database
4. www.stackoverflow.com/questions/8575549/one-time-password-algorithmboth-

matematical-time-based-and-actionbased
5. https://www.wireless-technology-advisor.com/disadvantages-of-rfid
6. https://ieeexplore.ieee.org/document/6561118
7. https://www.edrawsoft.com/uml/?gclid
8. http://www.houstonsystem.com/automatic-toll-gate-system-using-advanced-rfid-gsm-

technology
9. https://www.techwalla.com/articles/advantages-disadvantages-of-rfid

10. https://www.slideshare.net/bingoarunprasath/toll-app-final-year-project
45