Management System
2.1 Product Perspective:
1.6 Overview:
The SRS include two main sections,namely, Overall Description:
This section will describe major components of the system, interconnections, and external interfaces.
Specific Requirements:
This section will describe the functions of actors, their roles in the system and the constraints faced by the system.
2.0 Overall Description:
The online ticketing system is developed to facilitate the administration system to manage the various information of the user and service provider and processes involved in online ticketing. So that the organisation can access accurate information quickly and easily as and when required.Also users will analyse the service provider through the
chat options provided by the system.
2.1 Product Perspective:
Online Ticketing is a web product for running powerful and customized. The product may also be used also to empower existing websites for online ticketing. The system contains administration space with functionality for the users to edit their profile, consult the tickets, manage their Details .
2.2 Software Interface:
Operating System: Windows 9x/xp ,Windows ME . Database: SQL Server.
Application: ASP (Active Server Pages) Java Virtual Machine.
Front End Client:
Online Ticketing system uses the front end as Java, Java Server Pages and HTML at the client side.
Advanced Tools:
Netbeans 6.7.1 and JDK.
Webserver :
Apache Tomcat is used as the web server for the Online Ticketing System.
Data Base Server :
MySQL server is used as the database server for Online Ticketing.
Back End:
Online Ticketing system uses MySQL Ver 14.12 Distrib 5.0.75 as a back end database.
2.3 Hardware Interface:
Processor minimum: Intel Pentium 2 processor Memory(RAM): 256 MB DDR
Hard disk: 4GB Display: 1024*786
Keyboard: Any normal keyboard 2.4 Product Functions:
Login capabilities: The system shall provide the users with logon capabilities.
• Alert:
The system can alert in case of any problem.◦
The system shall allow the users to access the system from Internet using HTML. It◦ uses web browser interface at client side.
2.5 User Characteristics:
Customer:
• The customer login to the system and updates his profile.
• The Customer books for the ticket with the Origin,Destination,Dates and Pricepreferences • The price amount based on the credit,cash,DD etc..
• Selection of seat by the customer.
• Looks for the payment details.
Service Provider:
• The provider update his datas.
• Gives the information about the transport like Origin,Destination,Dates,Price
preferences,transport number.
• Update the transport details.
Admin:
• Application manager manages the entire details about the system and get the updates regularly.
Use Case Diagram:
Class Diagram:
ER Diagram:
Sequence Diagram:
DB Design:
create table role(role_id int NOT NULL,name char(20) NOT NULL,primary key(role_id));
create table address(address_id varchar(20) NOT NULL,street_1 varchar(20) NOT
NULL,street_2 varchar(20) NOT NULL,city_id int NOT NULL,primary key(address_id),foreign key(city_id)references city(city_id));
Query OK, 0 rows affected (0.00 sec)
mysql> show tables;
Tables_in_ticket address role
2 rows in set (0.00 sec)
mysql> create table city(city_id int(20)NOT NULL,city_name char(20),state_id intNOT NULL,primary key(city_id),foreign key(state_id)refernces state(state_id));
Query OK, 0 rows affected (0.00 sec) mysql> show tables;
Tables_in_ticket
address city role
3 rows in set (0.00 sec)
mysql> create table state(state_id int NOT NULL,state_name char(20),country_id int NOT NULL,primary key(state_id),foreign key(country_id)references country(country_id));
Query OK, 0 rows affected (0.02 sec) mysql> show tables;
Tables_in_ticket
address city role state
4 rows in set (0.00 sec)
mysql> create table country(country_id int NOT NULL,country_name char(20),primary key(country_id));
Query OK, 0 rows affected (0.00 sec) mysql> show tables;
Tables_in_ticket address city country role state
5 rows in set (0.01 sec)
mysql> create table user(user_id int NOT NULL,user_name char(20),password varchar(20)NOT NULL,role_id int NOT NULL,address_id varchar(20)NOT NULL,contact_no int NOT
NULL,primary key(user_id),foreign key(role_id)references role(role_id),foreign key(address_id)references address(address_id));
Query OK, 0 rows affected (0.01 sec)
mysql> show tables;
Tables_in_ticket address city country
role state user
6 rows in set (0.01 sec)
mysql> create table customer(customer_id int NOT NULL,user_id int NOT NULL,address_id varchar(20)NOT NULL,contact_no int NOT NULL,payment_id int NOT NULL,primary key(customer_id),foreign key(payment_id)references payment_type(payment_id),foreign key(address_id)references address(address_id),foreign key(user_id)references user(user_id));
Query OK, 0 rows affected (0.00 sec)
mysql> show tables;
Tables_in_ticket address city country customer role state user
7 rows in set (0.00 sec)
create table bus_type(type_id int NOT NULL,type_name char(20),description char(20),transport_id int NOT NULL,no_of_seats int NOT NULL,fare_id int NOT NULL,foreign key(fare_id)references fare(fare_id),foreign key(transport_id)references bus(transport_id),primary key(type_id));
Query OK, 0 rows affected (0.01 sec) show tables;
Tables_in_ticket address bus_type city country customer role state user
create table bus(transport_id int NOT NULL,service_id int NOT NULL,customer_id int NOT NULL,isavailable varchar(20),route_id int NOT NULL,foreign key(route_id)references
route(route_id),foreign key(customer_id)references customer(customer_id),primary key(transport_id));
Query OK, 0 rows affected (0.01 sec)
mysql> show tables;
Tables_in_ticket address bus bus_type city country customer role state user
9 rows in set (0.00 sec)
mysql> create table route(route_id int NOT NULL,transport_id int NOT NULL,source char(20),destination char(20),primary key(route_id),foreign key(transport_id)references bus(transport_id));
Query OK, 0 rows affected (0.00 sec)
mysql> show tables;
Tables_in_ticket address bus bus_type city country Customer role route state user
10 rows in set (0.00 sec)
mysql> create table sub_route(subroute_id int NOT NULL,place_name char(20),arrival_time varchar(20)NOT NULL,departure_time varchar(20)NOT NULL,route_id int NOT
NULL,primary key(subroute_id),foreign key(route_id)references route(route_id));
Query OK, 0 rows affected (0.00 sec)
mysql> show tables;
Tables_in_ticket address bus bus_type city country customer role route state sub_route user
11 rows in set (0.00 sec)
create table book_seat(seat_id int NOT NULL,book_ticket_id int NOT NULL,seat_no int NOT NULL,passenger_name char(20),passenger_gender char(10),passenger_age int NOT
NULL,passenger_contact_no int NOT NULL,customer_id int NOT NULL,primary key(seat_id),foreign key(book_ticket_id)references book_ticket(book_ticket_id),foreign key(customer_id)references customer(customer_id));
Query OK, 0 rows affected (0.01 sec)
mysql> show tables;
Tables_in_ticket address book_seat bus bus_type city country customer role route state sub_route 12 rows in set (0.00 sec)
mysql> create table book_ticket(book_ticket_id int NOT NULL,user_id int NOT
NULL,datestamp date,fare_id int NOT NULL,foreign key(user_id)references
user(user_id),primary key(book_ticket_id),foreign key(fare_id)references fare(fare_id));
Query OK, 0 rows affected (0.01 sec)
mysql> show tables;
Tables_in_ticket address book_seat book_ticket bus bus_type city country customer role route state sub_route user
13 rows in set (0.00 sec)
mysql> create table online_payment(transaction_id int NOT NULL,creditcard_no int NOT NULL,expire_date int NOT NULL,code_no int NOT NULL,foreign
key(transaction_id)references transaction(transaction_id));
Query OK, 0 rows affected (0.01 sec)
mysql> show tables;
Tables_in_ticket address book_seat book_ticket bus bus_type city country customer role
route state sub_route user
mysql> create table transaction(transaction_id int NOT NULL,book_ticket_id int NOT NULL,amount int NOT NULL,payment_type_id int NOT NULL,datestamp date,primary key(transaction_id),foreign key(book_ticket_id)references book_ticket(book_ticket_id),foreign key(payment_type_id)references payment_type(payment_type_id));
Query OK, 0 rows affected (0.02 sec)
mysql> show tables;
Tables_in_ticket address book_seat book_ticket bus bus_type city country customer online_payment role
route state sub_route transaction user
15 rows in set (0.01 sec)
mysql> create table payment_type(payment_id int NOT NULL,transaction_id int NOT NULL,payment_type_id int NOT NULL,primary key(payment_type_id),foreign
key(transaction_id)references transaction(transaction_id));
Query OK, 0 rows affected (0.01 sec)
mysql> show tables;
Tables_in_ticket address book_seat book_ticket
bus bus_type city country customer online_payment payment_type role
route state sub_route transaction user
mysql> create table fare(fare_id int NOT NULL,from_subroute_id int NOT
NULL,to_subroute_id int NOT NULL,charge int NOT NULL,primary key(fare_id));
Query OK, 0 rows affected (0.02 sec)
mysql> show tables;
Tables_in_ticket address
book_seat book_ticket bus bus_type city
country customer fare
online_payment payment_type role route state sub_route transaction user
17 rows in set (0.00 sec) 3.0 Specific Requirements:
3.1 Use Case Reports:
In Usecase diagram there are three actors.Each actor has different activities of their own.
Actors in system are 1. Customer
2. Setrvice Provider 3. Admin
3.2 Supplementary Requirements:
Supplementary requirements for Online Ticketing is Internet. Because this system can run in online, so we need to internet to access this system.Then we need some softwares to run
this web application.