Software Requirements Specification for <Project>

Page 1

Software Requirements Specification

for

Book A Movie Ticket By Online

Prepared by

Amborkar Sarang Raghunath

Contents
1 INTRODUCTION...........................................................................................................................................................2

Software Requirements Specification for <Project>

Page 2

2 OVERALL DESCRIPTION..........................................................................................................................................4 3 SPECIFIC REQUIREMENTS.......................................................................................................................................6 2 OTHER NON-FUNCTIONAL REQUIREMENTS..................................................................................................10 3 OTHER REQUIREMENTS.........................................................................................................................................11

1 Introduction
1.1 Document Purpose
This Software Requirements Specification (SRS) will provide detail description of requirements for Online Movie Booking System (OMBS). This SRS helps end users, project managers and software engineers to have clear understanding of the OMBS and it's functionality that allows correct software to be developed. This SRS provides the foundation for the OMBS project. From this SRS, the OMBS system will be developed and tested. This SRS will be used by software engineers as guideline to develop the OMBS.End users and project managers will be able to see if the software engineer will be developing the system according to their requirements. If not according to their expectation, end users and project managers can specify how to change the relevant requirements to conform with their expectations and software engineer will change this SRS to conform with the end users and project managers need.

1.2 Product Scope

The software product to be produced is the Online Movie Booking System which will provide online movie booking system to customers to purchase the movie ticket easily from website protal. This will help to add a new sales channel, minimize operational cost and improve sales. OMBS will have two user interface layers, first one is Guest Interface (OMBS) and the second one is Movie Management Interface (OMBS). Customer can purchase the movie ticket from website portal which is actually Guest Interface (OMBS). OMBS-GI will have function for visitor to view movie details and search movies. Plus, customer can purchase movie ticket and view purchase history by creating an account in the system.

Software Requirements Specification for <Project>

Page 3

OMBS system shall use Paypal system to process customer payment using Credit Card, Debit Card or Paypal Balance. To automate the process staff will update and maintain the OMBS using Movie Management Interface (OMBS). Movie Management Interface (OMBS) will have the following functions and modules in the system. * Login Function * Staff Module * Reservation Module * Ticket Module * Membership Module * Movie Module * Pricing Module * Availability Module * Branch Module * Report Module Access to the module determined by staff account type and branch/head office location. By managing the OMBS via Movie Management Interface (OMBS), can provide facility for customers to purchase movie ticket online.

1.3 Intended Audience and Document Overview

The intended audiences for this document are as follows: * End users * Project Managers * Software Engineers This document will reviewed frequently by the above audiences to check if the project follows the requirements. Any changes to requirements during the project will be updated in this document by making necessary changes.

1.4 Document Conventions

The following are list of conventions and acronym used in this document and the project. Customer : customer who have created an account. Interface : Something used to communicate across different mediums OMBS : Online Movie Booking System OMBS-MMI : Movie Management Interface OMBS-GI : Guest Interface SRS : Software Requirements Specification User : User of the system such as customer, counter clerk, branch manager, branch supervisor, visitor, head office personnel and credit unit personnel. Anyone who interact with the system using the user interface layer. Use Case : A broad level diagram of the project showing basis overview.

Software Requirements Specification for <Project>

Page 4

1.5 References and Acknowledgments

http://www.uml-diagrams.org/ http://www.google.com/static/use_case_example.html http://www.visual-paradigm.com/VPGallery/diagrams/Sequence.html

2 Overall Description
2.1 Product Perspective
The OMBS is an independent standalone system. It is totally self contained.

2.2Product Functionality
OMBS will have two user interface layers, first one is Guest Interface (OMBS-GI) and the second one is Movie Management Interface (OMBS-MMI). Guest Interface (OMBS-GI) Guest Interface (OMBS-GI) will have the following functions View Movie Details * Allows visitors view the movie details Search Movie * Allow visitor to search movie. Create Account * Allow customer to create account Customer Login * Enable customer to login the system. * Allow customer to access to Purchase Movie and Purchase History sections in the system. Purchase Movie * Enable customer to purchase movie ticket online. Purchase History * Enable customer to find purchase history.

2.3Users and Characteristics

* Educational level of OMBS Low * Experience of using OMBS Low

Software Requirements Specification for <Project> * Technical Expertise Low

Page 5

2.4Operating Environment
<Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist. In this part, make sure to include a simple diagram that shows the major components of the overall system, subsystem interconnections, and external interface TO DO: As stated above, in at least one paragraph, describe the environment your system will have to operate in. Make sure to include the minimum platform requirements for your system. >

2.5Design and Implementation Constraints

The OMBS shall be web based system that run on different type of browser such as Internet Explorer, Mozilla and Google Chrome. The system shall be developed using Java, Javascript, Ajax and Php programming languages. The system shall run using Apache Server and MySql Database Server.

2.6User Documentation
List of documents that shall be delivered with OMBS * User Manual * Online Help * System Maintenance Documentation.

2.7Assumptions and Dependencies

OMBS will use Paypal payment gateway to process customer payment using Credit card, Debit card or Paypal Balance.

Software Requirements Specification for <Project>

Page 6

3 Specific Requirements
1.6 External Interface Requirements
1.6.1 User Interfaces
Keyboard, mouse and printer.

1.6.2 Hardware Interfaces

Server Side * Operating System : Red Hat Enterprise Linux * Processor : Intel Chipset * Memory : 192GB * Hard Drive Capacity : 750GB, expandable Client Side * Operating System : Window XP, Window Vista or Window 7 * Browser : Internet Explorer 6 and above. Mozilla or Google Chrome. * Memory : 1 GB

1.6.3 Software Interfaces

Database * MySql Server version 5 or above. Web Server * Apache Server version 2.2.6 Programming Languages * Javascript * Java * Php

1.6.4 Communications Interfaces

* Dial Up Modem * Broadband Internet * All transaction between client and server for Movie Management Interface (OMBS-MMI) must be done using Secure Socket Layer (SSL) technology to encrypt the data.

Software Requirements Specification for <Project>

Page 7

* Transaction between client and server for Guest Interface (OMBS-GI), only applicable for account creation, purchase movie and purchase history functions must be done using Secure Socket Layer (SSL) technology to encrypt the data.

1.7 Functional Requirements

Functional requirements define the fundamental actions that system must perform. ABC Sdn Bhd (ABC) online movie booking system (OMBS) could be divide into two interface that works together seamlessly. The first interface is only accessible to the customers and visitors called Guest Interface (OMBS-GI) . And the second interface is only accessible by ABC staff called Movie Management Interface(OMBSMMI) Guest Interface (OMBS-GI) Functional Requirements Guest Interface (OMBS-GI) will have the following functional requirements. Accessible via ABC main website portal. 3.1.1. View Movie Details. 3.1.1.1. The system shall enable customer or visitor to view list of movies showcased at each venue by date and time. 3.1.2. Search Movie 3.1.2.1. The system shall have search function. Customer or visitor can search movies based on movie name, date, time and venue 3.1.3. Create Account 3.1.3.1. The system shall function to create account. The system shall record all the following data from the customer, except for the optional fields, all other data is mandatory. a) Username b) Password c) Password Confirmation. d) First Name e) Last Name f) Identity Card Number g) Street Address 1, h) Street Address 2, (Optional) i) Zip Code, j) City/Town k) State l) Country m) Telephone Number n) Fax Number (Optional) o) ABC Priority Card No (Optional) p) Security Questions q) Security Answer r) Check box, whether customer want to receive newsletter via email (Optional) 3.1.3.2. The system shall send activation link via email to customer to activate the account. 3.1.4. Customer Login

Software Requirements Specification for <Project>

Page 8

3.1.4.1. The system shall have customer login function. Once activated, customer can login using username and password. 3.1.4.2. The system shall have username and password recovery function. The system shall ask Security Questions that customer entered during registration. If the customer enters correct Security Answer, the system shall email username and password to the customer. 3.1.5. Purchase Movie 3.1.5.1. The system shall enable customer to purchase the movie ticket from Guest Interface (OMBSGI). 3.1.5.2. The system shall display list of movies showcased at each venue. 3.1.5.3. The system shall display for each movie at the venue the following details a) Date b) Time c) Price 3.1.5.4. The system shall have Book Now button. When the Book Now is pressed, the system shall prompt customer to login or register account. 3.1.5.5. The system shall allow customer who have login only to continue to purchase the ticket. If customer haven't login, prompt customer to login or create an account. Then only customer can continue. 3.1.5.6. Once login, the system shall record the following details in (Booking Screen). a) Number of adults b) Number of children c) Date d) Time 3.1.5.7. The system shall have Next button and Cancel button. 3.1.5.8. The system shall display the seating position (Seating Screen) still available for the movie based on time and date. 3.1.5.9. The system shall record the seatings selected by the customer. 3.1.5.10. The system shall have lock function. OMBS will prevent customers or counter clerk from booking the same ticket based first come first serve policy. Whoever, books the seat number first, the system shall hold the ticket for 10 minutes for them to completed the purchasing process. If not the system shall release back the ticket for anyone to purchase. 3.1.5.11. The system shall have Next button, Back button and Cancel button. 3.1.5.12. The system shall display (Review Screen) with all the following details. a) Customer details, such as First Name, Last Name, Address, Telephone and etc. b) Booking details, such as No of Adults, No of Children, Date, Time & Seating Numbers c) The system shall provide discount for ABC Priority Card holder if applicable. ABC Priority Card holder number is validate to ensure the membership is still active. d) The system shall calculate the service charges and the government tax charges. e) The total price to be paid. 3.1.5.13. The system shall have Back button, Check Out button and Cancel button. 3.1.5.14. Once customer click the Check Out button, the system shall redirect the customer to Paypal to make the payment. 3.1.5.15. The customer shall confirm the payment details and Click the Pay Now button to purchase the movie tickets. 3.1.5.16. The system shall display thank you (Thank You Screen) message for the purchase.

Software Requirements Specification for <Project>

Page 9

3.1.5.17. The system shall also send an email notification to the customer about the purchase. Confirmation number is stated in email notification. Customer need to provide the confirmation number to the counter clerk to get the movie ticket at the branch. 3.1.5.18. If the customer cancels the payment in Paypal, the system shall display the booking details back (Review Screen). 3.1.6. Purchase History 3.1.6.1. The system shall allow only customer who have login to access this record 3.1.6.2. The system shall have list of purchased movie details made by the customer.

1.8 Behaviour Requirements

1.8.1 Use Case View
<A use case defines a goal-oriented set of interactions between external actors and the system under consideration. Since sometimes we will not be able to specify completely the behaviour of the system by just State Diagrams, we use use-cases to complete what we have already started in section 3.3.1. TO DO: Provide a use case diagram which will encapsulate the entire system and all possible actors. Do not include detailed use case descriptions (these will be needed when you will be working on the Test Plan), but make sure to include a short description of what every use-case is, who are the actors in your diagram. For more information please refer to your UML guide and the MiniThermostat SRS example file.>

Software Requirements Specification for <Project>

Page 10

2 Other Non-functional Requirements

2.1 Performance Requirements
The system response time must be less than 10 seconds for both OMBS-GI and OMBS-MMI. The system must process the number of transaction based on the following calculation method.

2.2 Safety and Security Requirements

All system data must be backed up every 24 hours and the backup copies stored in another server at different building or location for disaster recovery. All access permission for the system data may only be changed by the system's administrator. All communication between OMBS-MMI server data with client shall be encrypted by using Secure Socket Layer (SSL) technology. Transaction between client and server for Guest Interface (OMBS-GI), only applicable for account creation, purchase movie and purchase history functions shall be done using Secure Socket Layer (SSL) technology to encrypt the data.

2.3 Software Quality Attributes

The source codes for the system is well documented for ease of maintenance and upgrading the system in future.

Software Requirements Specification for <Project>

Page 11

3 Other Requirements
<This section is Optional. Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>

Software Requirements Specification for <Project>

Page 12

Appendix A Data Dictionary

<Data dictionary is used to track all the different variables, states and functional requirements that you described in your document. Make sure to include the complete list of all constants, state variables (and their possible states), inputs and outputs in a table. In the table, include the description of these items as well as all related operations and requirements.>

Software Requirements Specification for <Project>

Page 13

Appendix B - Group Log

<Please include here all the minutes from your group meetings, your group activities, and any other relevant information that will assist the Teaching Assistant to determine the effort put forth to produce this document>