Online Reservation For Cine Malls: Software Requirement Specification
Online Reservation For Cine Malls: Software Requirement Specification
Online Reservation For Cine Malls: Software Requirement Specification
PARADIGM SHIFT
Team members Anshul Gupta 0201CS081016 Shubham Singh 0201CS081079 Shubhang Agrawal 0201CS081080 Vaishali Mangwani 0201CS081087
Page 1 of 1
Online Reservation for Cine Malls Software Requirement Specification TABLE OF CONTENTS
1.0 Introduction 1.1 Methodology 1.2 Purpose 1.3 Scope 1.3.1 General Requierements 1.3.2 Interface Enhancements 1.4 Definitions, Acronyms and Abbreviations 1.5 Tools Used 1.6 References 1.7 Technologies to be used 1.8 Overview -4-5-5-5-5-5-6-8-9-10-10-
2.0 Usage Scenario 2.1 Interface 2.1.1Interface diagram 2.1.2 Interface Enhancements 2.2 Software Interface 2.2.1 Recommended Requirements 2.3 Assumptions and Constraints 2..3.1 Assumptions 2.3.2 Constraints 2.4 Data Flow Diagram 2.5 Relationships 2.6 Use Case 2.7 Special Usage Considerations
-11-11-11-11-11-12-12-12-13-14-15-15-16-
Page 2 of 1
Page 3 of 1
1. Introduction
1.1 Methodology
Rational Unified Process The Rational Unified Process brings together elements from all of the generic process models, supports iteration and illustrates good practice in specification and design. The RUP is normally described from three perspectives: A dynamic perspective that shows the phases of the model over time. A static perspective that shows the process activities that are enacted. A practice perspective that suggests good practices to be used during the process.
Page 4 of 1
1.2 Purpose
The main purpose of our online ticket booking system is to provide another way for the customer to buy cinema ticket. It is an automatic system. After inserting the data to database, staff need not to due with the order receive through the system. In fact, there is similar system on the internet, but there is no refund method found in the existing system. The goals of our system are: 1 To provide a anytime anyplace service for the customer 2 To provide refund which is not available in the existing system 3 To minimize the number of staff at the ticket box 4 To promote the film on the internet 5 To increase the profit 6 To obtain statistic information from the booking record.
1.3 Scope
Page 5 of 1
A way in which the customer can check the ticket record according to the transaction number. 8. A way in which the staff can use the system to add data(e.g. film description) to the database. 9. The system can verify the data before transaction. 10. The system can generate the time table automatically(by just input the length of the film) or the time table is set by the staff.(2 operating mode for the staff to insert data). 11. The system can generate some statistic information according booking and ticket selling record. Our web-based system needs about 30 interfaces to handle all the functions.
Staff
One of the main purpose of our system is to reduce the number of staff in the ticket box. So, most of the job is done by the system automatically. Staff only need to insert new film data and due with the refund part.
Customer
To make the system more user-friendly, customer need not to enter lots of data. An order will be commit step by step with guideline (request about 7 webpage for an order).
Page 6 of 1
Page 7 of 1
Page 8 of 1
Design tool Rational Software Modeler IBM Rational Software Modeler, (RSM) made by IBM's Rational Software division, is a Unified Modeling Language UML 2.0-based visual modeling and design tool. Rational Software Modeler is built on the Eclipse open-source software framework and includes capabilities focused on visual modeling and model-driven development (MDD) with the UML for creating resilient, thought-out applications and web services.
1.6 References
Software Engineering ,Pressman Software Engineering, Seventh Edition, Ian Sommerville. IBM Red Books. IBM TGMC Sample Synopsis. IBM www.ibm.in/developerworks . Java - www.sun.com Wikipedia - www.wikipedia.com
Database Management Systems - Navathe. Complete Reference - J2EE - TMH Java Blackbook
Page 9 of 1
1.8 Overview
Existing System:
Registration for users Discussion forum
Drawbacks:
No Refund Remote area users and people who doesn't have knowledge of internet cannot use the system
Proposed System:
Registration for users, cinema halls, kiosks Kiosk Managers - help the Web camera interaction. Refund would be provided on time hierarchal process as done by IRCTC
Our Plan:
Registration for users. Online maintenance of health record. Online prescription from doctor. Advance cum instant booking Centralized system
Page 10 of 1
2.1.2 Interface Enhancements Our web-based system needs about 30 interfaces to handle all the functions. Staff One of the main purpose of our system is to reduce the number of staff in the ticket box. So, most of the job is done by the system automatically. Staff only need to insert new film data and due with the refund part. Customer To make the system more user-friendly, customer need not to enter lots of data. An order will be commit step by step with guideline (request about 7 webpage for an order).
Client on Intranet
Web Browser, Operating System (any)
Development End
RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows), WebSphere(Web Server)
2.2.1 Recommended Requirements: Client Side Processor Internet Explorer 6 Web cam All Intel or AMD - 1 GHZ RAM 256 MB Disk Space 100 MB
5.0 Megapixel Camera Server Side Processor RAM 2 GB All Intel or AMD - 2 GHZ Disk Space 3.5 GB 500 MB 512 MB (Excluding Data Size)
RAD
DB2 - 9.5
2.3 Assumptions and Constraints 2.3.1 Assumptions Ticket type Every film has 3 ticket types(adult /student /elderly or children). That means there are 3 different prices for each film. Also, this assumption is work in the whole year, even in Tuesday and public holiday.
Page 12 of 1
Transaction We cannot do a real transaction, so we can only simulate the process of transaction and save the necessary data in the database System requirement and performance Since our system is a web-based system, almost all the popular perform can use the system if a web browser is included. We will sure use some java script and java applet in the system, so the browser must enable these functions to use the system normally. In addition, to improve the security, a browse support SSL is needed. Also, users computer must able to connect to internet.
Page 13 of 1
Page 14 of 1
2.5 Relationships
2.6 Use-case The Read/Write/Modify own group are the main user of this software. Full Control Group(IT Support) IT Support is a team which manipulates and maintains the system. Since further improvement and testing of the system is needed, the team will be inside the full control group.
Page 15 of 1
3.0 Functional Requirements Since the staff and the customer are the main target group of our software, we will only concern about some important functions for the staff and the customer. 3.1 Customer The following diagram is the main page of the system, which most of the customer will start using the system from this page. In this page, the customer can check the film detail by clicking on each film(e.g. film description, seat booking situation). The customer can start the buy ticket process after checking the film detail. Also, the customer can register as a member of the system. After registration, customer can login to its own account to modify its own data and return ticket if they have order a ticket before.
Page 16 of 1
Fig.2 The overall state diagram for customers action 3.1.1 Buying ticket The buying ticket process is the most important function in our system. We will describe this process in detail. 1. Choose the film ,time and venue 2. Check the status of select venue at certain time.(by system) (Since the above function is open to public, customer need to login before they can
Page 17 of 1
3.1.2 Return ticket(refund/cancel seat) This is one important feature of our system. By examine the existing system on the internet, we found that there is no such function available at this moment, so we try to include it in our system. To protect the benefit the cinema, we will not give the money back to the customer, but insert a record to database, write down how much the customer is remain in the system. So, the customer can use the remaining money. To do so, both the customer and the cinema can satisfy the win condition. Also, customer will come to the website more frequently, since they have some money remain in the system. The steps of performing return ticket process: 1. Customer login into the system from the main page. 2. Customer information will be shown in the user main page (including the information about booked seat). 3. Customer cancel the seat by clicking some button 4. System check the time weather it is possible for the customer to cancel the seat(by system) 5. If the seat is cancelled successfully, increase the cancelled amount of money to customers record. (by system) 6. Return to the user main page.
3.2 Staff The system for the staff part is not shown in the main page. Before the staff to perform any operation, he/she must login to the system first. Once the staff login to the system, the statistic information will be shown. And the staff can choose
Page 18 of 1
Page 19 of 1
Page 20 of 1
Page 21 of 1
3.3.2 Web Camera Interaction Activity Webcam interaction activity is recommended for users to ensure non transferability of tickets. The user will interact with the webcam and the latest version of users photo will be recorded in the database.. The face recognition system at the cinema hall will verify the user and hence ensure security.
Page 22 of 1
3.4 User Profiles There will be three levels of users: 1. Full Control(IT Support) 2. Read/Write/Modify Own(Customer/Staff) 3. Read Only(General Public)
Read Only Group(General Public) All the people can browse the webpage but cannot make any change to the system.
Page 23 of 1
The customers email address. Customer_password: The customers password for login the system. Customer_amount: The amount of money that the customer have refund and will be use in next time. Customer_creditcard: The customers credit card number. Movie information Movie_id: The key for each movie. Movie_name: The name of the movie. Movie_director: The director of the movie. Movie_casting: The actor of the movie. Movie_duration: The length of the movie. Movie_cateory: The cateory of movie like I,II,III. Movie_language: The language of the movie. Movie_synopsis: The main description of the movie. Record Information: Record_id: The key for each record. Record_seat: The seats which is sold in this record. Sale Information
Page 24 of 1
Page 25 of 1
Special Thanks
We convey a special thanks to our department and to our college. We also convey a special thanks to all these softwares and websites, they have been helping a lot in doing the project.
Page 26 of 1