Metro Ticketing System Using RFID

Software Design Document

Version 1.0
Group Members: Abin stephen Prasanth M M Ninto Antony Vishwajeet Nair Under guidance of: Mr. Ajay James March 29 2011

Introduction
The project is an automated ticketing system for metro railways using RFID. It consists of a RFID reader residing on host system which reads an RFID tag from a passenger and sends the passenger id to the master system. The user id uniquely identify the passenger and is stored in the journey database along with the station id catogarized as source or destination station and also the date of the journey. Once the user completes his journey, the RFID tag is read again. The information is again sent to the master system and destination station id is stored in the journey database. The master system checks for the cost of the journey from the station database and stores it in the journey database. Finally the cost of the journey is automatically deducted from the passenger account . This design document provides the various design details regarding the implementation of the prototype.

System Design
The UML Use Case Diagram gives the product view from user perspective.

1.Data flow diagram.

DFDs are used to represent the flow of data through different modules of the system. An Integrated Data Flow Diagram is used to represent the overall system.

System View When the RFID reader senses the tag the host system authenticat the user and updates the station details. These details are then sent to the master system for database updation

Administrator View The main job of administrator is to manage passenger,station and journey databases. The administrator has access to basic detaiols of the passenger and can view and modify them as required. Simillarly the administrator can manege a stations details as well as the cost of the journey.

Passenger View
The passenger only has privilages to view his details but not modify them .

2.Activity Diagram
Activity diagrams are graphical representations of of stepwise activities and actions with support for choice, iteration and concurrency. Activity diagrams can be used to describe the operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control. The RFID reader checks wether a tag is legitimate. If found valid the details of the passenger as well as station is send to the master system where the cost of the journey is deduced from these details and nessesary database modification were performed.

3. Use case diagram

Use case diagram is a type of behavioral diagram defined by and created from a use case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases.The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted. The purpose of the RFID system is to identify a passenger and record his/her journey details the administrator maneges the details of the passenger as well as station and journey details.THe passenger can use the system by carrying a valid RFID tag and can also view his details when needed.

4.Sequence diagram
A sequence diagram is a kind of intraction diagram that shows how processes operate with one another and in what order. It is a construct of a messegge sequence chart. Sequence diagrams are sometimes called event diagrams. Sequence diagrams are used to represent or model the flow of messages, events and actions between the objects or components of a system. The below sequence diagram showcases the relation between the functions performed by a passenger, an RFID reader and the administrator.

Database Design
The syatem mainly uses three differint databases for its functioning 1. Passenger database
It consists of the basic details of the passenger including his/her account details and the details of his/her last journey. The Passenger_Id field serves as the primary key. Field Passenger_Id First name Last name Address Contact no Account no Account balance Date of last journey Cost of last journey Type Varchar(20) Varchar(30) Varchar(20) Varchar(100) Int(10) Varchar(6) Real(7,2) Date Real(7,2) NOT NULL NOT NULL NOT NULL NOT NULL Attribute constraints NOT NULL NOT NULL NOT NULL NOT NULL

2. Station database
The details in station database include the station id and name and the cost of journey from one station to all the other stations. The Station_id field is the primary key here. Field Station_id Station name Cost2stn1 Cost2stn2 Cost2stn3 Cost2stn4 Type Varchar(20) Varchar(20) Real(5,2) Real(5,2) Real(5,2) Real(5,2) Attribute constraints NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL

3. Journey database
It stores the data of a passenger's journey in terms of the passenger id, the source station id, the destination station id, the date of the journey and the cost of the journey. Passenger_id field is the primary key.

Field Passenger _id Source Station Destination station Cost of journey Date of journey

Type Varchar(20) Varchar(20) Varchar(20) Real(7,2) Date

Attribute constraints NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL