Software Requirements Specification

For

Ticket Booking Android Application

Version 1.0

Prepared by 10BCE013 and 10BCE016

Nirma University, Institute Of Technology

15.06.2013

Software Requirements Specification for TBAA

Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii Revision History ............................................................................... Error! Bookmark not defined. 1. Introduction ................................................................................ Error! Bookmark not defined.
1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 3.1 3.2 3.3 3.4 Purpose............................................................................................Error! Bookmark not defined. Document Conventions ...................................................................Error! Bookmark not defined. Intended Audience and Reading Suggestions .................................Error! Bookmark not defined. Product Scope .................................................................................Error! Bookmark not defined. References .......................................................................................Error! Bookmark not defined. Product Perspective.........................................................................Error! Bookmark not defined. Product Functions ...........................................................................Error! Bookmark not defined. User Classes and Characteristics ....................................................Error! Bookmark not defined. Operating Environment ...................................................................Error! Bookmark not defined. Design and Implementation Constraints .........................................Error! Bookmark not defined. User Documentation .......................................................................Error! Bookmark not defined. Assumptions and Dependencies .....................................................Error! Bookmark not defined.

2. Overall Description .................................................................... Error! Bookmark not defined.

3. External Interface Requirements ............................................. Error! Bookmark not defined.

User Interfaces ................................................................................Error! Bookmark not defined. Hardware Interfaces ........................................................................Error! Bookmark not defined. Software Interfaces .........................................................................Error! Bookmark not defined. Communications Interfaces ............................................................Error! Bookmark not defined.

4. System Features ......................................................................... Error! Bookmark not defined.

4.1 Software Process Model4 5.1 5.2 5.3 5.4 5.5

5. Other Nonfunctional Requirements .......................................................................................9

Performance Requirements .............................................................................................................. 9 Safety Requirements ........................................................................................................................ 9 Security Requirements ..................................................................................................................... 9 Software Quality Attributes ............................................................................................................. 9 Business Rules ................................................................................................................................. 9

Revision History
Name Date Reason For Changes Version

Software Requirements Specification for TBAA

Page 1

Introduction
1.1 Purpose

The purpose of this document is to present a detailed description of the Ticket Booking Android Application. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli.

1.2 1.3

Document Conventions Intended Audience and Reading Suggestions

This document is intended for developers, project managers, users, testers and documentation writers. It contains a detailed description of the application.

1.4

Product Scope

The software allows users to view movies running in Cinemas in the desired region as well as book tickets and pay via their desired method. Hence, the application promotes the sale of movie tickets by facilitating the entire process to encourage customers to purchase. The application will be intuitive and provide all relevant information to the user. Appropriate security measures will be put in place for sensitive information shared by the user.

1.5

References

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications.
IEEE Computer Society, 1998.

Software Requirements Specification for TBAA

Page 2

Overall Description
1.6 Product Perspective

The application is designed as a standalone system. This self contained product is designed to satisfy the need of services to facilitate and promote the growth of the entertainment industry.

1.7

Product Functions
The user may view currently running movies. The user may book tickets for required movies. The user may access movie information including brief summaries. The user may view Cinema listings of movies as well as other information about the Cinema. The user may pay for the ticket or generate an e-ticket. The user may view seat availability and select seats as desired.

1.8

User Classes and Characteristics

The most important user class is the regular customer who books tickets. They require relevant information as quickly as possible and due to their habituated nature will remain loyal customers. This user class generally consists of regular Cinema-goers and they may be presented further incentives for further purchases. The next user class comprises the customer who is not as frequent yet does return after undefined stretches of time. They may be encouraged to return with schemes and other incentives. The next user class comprises people who only use the application to access information but do not avail of the booking service.

1.9

Operating Environment

The application will run on Android OS Version 2.2 and above and all device that support this OS. The application requires the device to have access to the internet and the device must contain a GPS receiver.

1.10 Design and Implementation Constraints

The application database will be limited to certain popular cities. The movie timings are subject to change without warning. The payment techniques are restricted and the application does not provide all possible options of payment. The hardware limitations of some devices may not allow for proper viewing of the application.

1.11 User Documentation

The application will include help manual for users who may have any queries.

Software Requirements Specification for TBAA

Page 3

1.12 Assumptions and Dependencies

It is assumed that the application will be limited to the regions that the database can gather information about and cannot extend services to more remote areas. The Cinemas that do not support this ticketing system will not be supported by the application. Certain software components have been reused.

External Interface Requirements

1.13 User Interfaces
The user interface will consist of basic navigation options and will be designed using XML.

1.14 Hardware Interfaces

1.15 Software Interfaces

Front End: XML User friendly Low Cost Solution GUI Better designing aspects

Back End: SQL Lite Security Portability Quality

1.16 Communications Interfaces

The application will be designed to be compatible with the default android browser as well as Opera.

Software Requirements Specification for TBAA

Page 4

System Features
1.17 Software Process Model
Prototyping:
In this model we develop a working prototype with the current version of the requirements specified and collect feedback from customers to add further requirements and develop the final product. The prototype is a trimmed version of the actual application with limited features, functionality and a lower level of reliability.

The Prototyping Model

Requirement Design Implementation

Improve the Specification

Evaluation

Design Implement

Testing

Operation and Maintenance

Software Requirements Specification for TBAA

Page 5

Project Modules
Login Module: This module is for both type of users (customers and administrator). In this module according to the type of user (customer or administrator) the website will display appropriate information and access to data. User Module: As soon as a visitor registers himself as a customer or administrator, the customer can book movie tickets and pay for them online by any of the available methods whereas the administrator may evaluate and customize the application as required. Hall Module: This module deals with the information about the various Cinema halls. There are several multiplexes and each of them has more than just one hall. Hence, the application displays accurate information about each halls seat availability. Booking Module: This module allows for the actual booking of the ticket. This module contains all the information related to different orders. As soon as the customer request is complete, all the booking details are displayed to him/her. Payment Module: The most important module because it deals with the payment of the tickets booked in the booking module. The customer can pay for the tickets before the show by cash payment and if he wants to pay online, he can pay for the tickets by credit card.

System Design
The design of the system is the most critical factor affecting the quality of the software; it has major impact on the later phases, particularly testing and maintenance. The output of this phase is the design document. This document is similar to blueprint or plan for the solution. The design activity is often divided into two phases. System design: Aims to identify the modules that should be in the system, the specifications of these modules and how they interact with each other to produce the desired results. At the end of system design all the major data structures, file formats and the major modules in the system and their specifications are decided. Legend = Source or destination of data

= =

Data flow Process that transforms data

Software Requirements Specification for TBAA

Page 6

Or

Data store

Physical Design

Database Design A database may be thought of as a set of related files. Related files mean that record of one file may be associated with the records in another file. The conventional file based systems emphasized that the application and files were built around it. The database environment emphasizes the data independently of the applications that use the data. The applications are allowed to evolve around a database design such that it can adapt to changing needs. Data becomes the central resource in the database environment. Information systems are built around this central resource to give flexible access to data.

Design of Database Table The data to be used in the system are stored in various tables. The number of tables used and their structure are decided upon keeping in mind the logical relation in the data available. The database design specifies: The various tables to be used Data to store in each table Format of the fields and their types

Data Structure Tables in the database: Credit information: Attributes Num of credit card Type Data type Number Varchar

Software Requirements Specification for TBAA

Page 7

Name User Id ExpDate Ticket Movie User Information: Attributes First Name Last Name User Id Password Contact Hint Question Hint Answer E_mail Id Booking: Attributes Movie Id Name of movie Show Time Screen Id Location: Attributes ZipCode State City Street Address Country Cinema Id Movie:

Varchar Varchar Varchar Number Varchar

Data type Varchar Varchar Varchar Varchar Numeric Varchar Varchar Varchar

Data type Varchar Varchar Varchar Varchar

Data type Number Varchar Varchar Varchar Varchar Number

Software Requirements Specification for TBAA

Page 8

Attributes Movie Id Name of movie Detail Screen: Attributes Movie Id Screen Id Cinema Id Cinema: Attributes Cinema Id Number of screen Name of Cinema Show time: Attributes Time Movie Id Screen Id Cinema Id

Data type Varchar Varchar Varchar

Data type Varchar Varchar Varchar

Data type Varchar Number Varchar

Data type Number Varchar Varchar Varchar

Testing

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design, coding. The purpose of product testing is to verify and validate the various work products viz. units, integrated unit, final product to ensure that they meet their requirements.

Software Requirements Specification for TBAA

Page 9

Other Nonfunctional Requirements

1.18 Performance Requirements
Reliability: The system will consistently perform its intended function. For e.g. crucial and sensitive information must be validated. Efficiency: Unnecessary data will not be transmitted on the network and the database server will be connected properly. Integrity: Only the System Administrator has rights to access the database, not every user can access all the information. Each user will have individual rights to access the various modules.

1.19 Safety Requirements

The application is of no harm to the device it shall be operated on or the user.

1.20 Security Requirements

Sensitive information shared with the application by the user will be encrypted. Measures will be put in place to ensure complete security. The user will also be provided the option to register and create a unique log-in id.

1.21 Software Quality Attributes

The software that is developed will be developed in accordance with the following attributes: availability, correctness, flexibility, portability, reliability, testability, and usability.

1.22 Business Rules

Appropriate understanding will be developed between the money transfer application and the various cinemas as to the payment mechanism.