You are on page 1of 24

Software Requirements Specification

For

MOVIE MANAGEMENT SYSTEM


Version 1.0 approved

Prepared by: Abhinav Bhargava Divya Arora Harshit Jain Kriti Sharma

Vivekananda Institute of Technology (CS)

28th Aug, 2011

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page ii

Table of Contents
Table of Contents ...................................................................................................................... ii Revision History ....................................................................................................................... iii 1. Introduction......................................................................................................................... 1
1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.6 Purpose ................................................................................................................................... 1 Document Conventions ........................................................................................................... 1 Intended Audience .................................................................................................................. 2 Project Scope .......................................................................................................................... 3 References .............................................................................................................................. 4 Project Perspective .................................................................................................................. 5 Project Features Summary....................................................................................................... 5 Operating Environment ........................................................................................................... 8 Design and Implementation Constraints .................................................................................. 8 User Documentation ............................................................................................................... 9 Assumptions and Dependencies .............................................................................................. 9

2. Overall Description of Project ............................................................................................ 5

3. Functional Requirements .................................................................................................... 9 4. Technology Information ................................................................................................... 19


4.1 4.2 4.3 5.1 5.2 5.3 User Interfaces details ........................................................................................................... 19 Software Interfaces ............................................................................................................... 19 Communications Interfaces ................................................................................................... 20 Performance Requirements ................................................................................................... 20 Security Requirements .......................................................................................................... 20 Scalability ............................................................................................................................. 20

5. Other Nonfunctional Requirements ................................................................................. 20

6. Other Requirements .......................................................................................................... 21 Appendix A: Glossary ............................................................................................................. 21

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page iii

Revision History
Name of team member Date Reason For Changes Version

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 1

1. Introduction
1.1 Purpose
This Software Requirements Specification (SRS) will provide detail description of requirements for ABC (ABC) Movie Management System. This SRS helps end users, project managers and software engineers to have clear understanding of the Movie Management System and it's functionality that allows correct software to be developed. This SRS provides the foundation for the project. From this SRS, the system will be developed and tested. This SRS will be used by software engineers as guideline to develop the Movie Management System. ABC's 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 to their expectations and software engineer will change this SRS to conform to the end users and project managers need.

1.2 Document Conventions


The following are list of conventions and acronym used in this document and the project. * Customer: ABC's customer who have created an account. * ABC: ABC * Interface: Something used to communicate across different mediums. * MMS: Movie Management System * MMS-MMI: Movie Management Interface * MMS-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 MOVIE MANAGEMENT SYSTEM

Page 2

Font

Style

Size

Heading

Times New Roman

Bold

18

Sub-Heading

Times New Roman

Bold

14

Others

Arial

Regular

10.5

1.3 Intended Audience


We are developing our project Movie Management System for the ABCs user. But this project can be deployed in any organization. This SRS is mainly developed for the project development team. In this team there are the project manager, developer, coder, tester and documentation writer and the user of the project also.

User (Customer)
This document is intended to user and customer to make them ensure that this document is well meeting the need of the users.

Project Manager
This SRS document is also very important for the project manager to ensure that can estimate the cost easily by referring to the SRS document and that it contains all the information require planning the project.

Project Developer
The project developer will refer to the SRS document to make sure that they developed exactly what the customer requires.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 3

Tester
The tester will read this SRS document and he will ensure that the requirements are understandable from functionality point of view so that he can test the software and validate its working.

Document Writer
The document writer is reading the SRS document is to ensure that they understand the document well enough to be able to write the users manuals.

Maintenance
The SRS document helps the maintenance engineers to understand functionality of the system, a clear knowledge of the functionality can help them to understand design and code.

Suggestions
1. The user can read the whole SRS document but for him Introduction, Overall description and System features is much required the software performance. 2. For the project manager the system features is very important. 3. The developer must go through the whole SRS for understanding the requirement and functioning of software. 4. The designer and coder must see the class and object diagram and state transmission diagram for coding the modules. 5. A tester must be aware of coding language and visit through the code section and check the required output. 6. The document writer should write the qualitative document so that it becomes easy and understand to every one.

1.4 Project Scope


The software product to be produced is the Movie Management System which will provide online movie management system and reviews to ABC customers to purchase the movie ticket easily from ABC website portal and also get the reviews of the movies and trailers of the upcoming movies. This will help ABC to add a new sales channel, minimize operational cost and improve sales. MMS will have two user interface layers, first one is Guest Interface (MMS) and the second one is Movie Management Interface (MMS).

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 4

Customer can purchase the movie ticket from ABC website portal which is actually Guest Interface (MMS). MMS-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 and also read and write reviews for a particular movie. MMS system shall use PayPal system to process customer payment using Credit Card, Debit Card or PayPal Balance. To automate the process ABC staff will update and maintain the MMS using Movie Management Interface (MMS). Movie Management Interface (MMS) 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 * Review Module * Trailers Module Access to the module determined by staff account type and branch/head office location. By managing the MMS via Movie Management Interface (MMS), ABC can provide facility for customers to purchase movie ticket online.

1.5 References
* http://www.uml-diagrams.org/ * http://argouml.tigris.org/ * http://www.agilemodeling.com/artifacts/useCaseDiagram.htm * http://www.gatherspace.com/static/use_case_example.html * http://www.visual-paradigm.com/VPGallery/diagrams/Sequence.html * http://www.fridayrelease.com

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 5

2. Overall Description of Project


This SRS is organized into two main sections. The first is The Overall Description and the second is the Specific Requirements. The Overall Description will describe the requirements of the MMS from a general high level perspective. The Specific Requirements section will describe in detail the requirements of the system.

2.1 Project Perspective


The MMS is an independent standalone system. It is totally self contained.

2.2 Project Features Summary


MMS will have two user interface layers, first one is Guest Interface (MMS-GI) and the second one is Movie Management Interface (MMS-MMI). Guest Interface (MMS-GI) Guest Interface (MMS-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. Movie Management Interface (MMS-MMI) Movie Management Interface (MMS-MMI) is used to update and maintain the MMS by ABC staff. It will have its own url which only known by ABC staff and they could access the website securely through the Internet. Movie Management Interface (MMS-MMI) will have the following functions and modules in the system.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 6

Login Function * Provides access to MMS-MMI Staff Module * Allows new staff data to be added * Allow staff data to be updated * Allow staff data to be deleted * Has search facility to search staff Only accessible by system administrator Reservation Module * Allow ABC staff to reserve and issue the movie ticket Only accessible by counter clerk, branch manager and branch supervisor. Access is limited to their branch level only. Ticket Module * Allow ABC staff to issue the movie ticket Only accessible by counter clerk, branch manager and branch supervisor. Access is limited to their branch level only. Membership Module * Allows new membership data to be added * Allow membership data to be updated * Allow membership data to be deleted * Allow membership data to be renewed * Has search facility to search membership data Only accessible by counter clerk, branch manager and branch supervisor. Access is limited to their branch level only. Movie Module * Allows new movie data to be added * Allow movie data to be updated * Has search facility to search movie data Only accessible by head office personnel.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 7

Pricing Module * Allows new pricing table to be added * Allow pricing table to be updated * Allow pricing table to be deleted Only accessible by branch manager and branch supervisor. Access is limited to their branch level only. Availability Module * Allows new availability data to be added * Allow availability data to be updated * Allow availability data to be deleted Only accessible by branch manager and branch supervisor. Access is limited to their branch level only. Branch Module * Allows new branch data to be added * Allow branch data to be updated * Allows new hall data to be added * Allow hall data to be updated Only accessible by system administrator. Report Module Provides the following reports to the respective user. * Branch Report (Only accessible by Branch Manager or Branch Supervisor) * Head Office Report (Only accessible by Head Office Personnel) * Customer Refund List (Only accessible by Credit Unit Personnel) Review Module Provides the following functions to the users. * Read the reviews. * Write reviews. * Comment on the reviews from other users. Trailers Module Provides the users and visitors to watch the trailers of the upcoming new releases.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 8

Access Type Access to the modules is determined by staff account type and branch/head office location. Types of account type are as follows: * Counter Clerk * Branch Manager * Branch Supervisor * Head Office Personnel * Credit Unit Personnel * System Administrator

By managing the MMS via Movie Management Interface (MMS-MMI), ABC can provide facility for customers to purchase movie ticket online. Customer can purchase the movie ticket from ABC website portal which is actually Guest Interface (MMS-GI).

2.3 Operating Environment


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 Firefox or Google Chrome. * Memory: 1 GB

2.4 Design and Implementation Constraints


The MMS 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 programming languages. The system shall run using Apache Server and MySql Database Server.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 9

2.5 User Documentation


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

2.6 Assumptions and Dependencies


MMS will use PayPal payment gateway to process customer payment using Credit card, Debit card or PayPal Balance.

3. Functional Requirements
Functional requirements define the fundamental actions that system must perform. ABC Movie Management System (MMS) could be dividing into two interfaces that work together seamlessly. The first interface is only accessible to the customers and visitors called Guest Interface (MMS-GI) . And the second interface is only accessible by ABC staff called Movie Management Interface (MMSMMI) Guest Interface (MMS-GI) Functional Requirements Guest Interface (MMS-GI) will have the following functional requirements. Accessible via ABC main website portal. 3.1. View Movie Details. 3.1.1. The system shall enable customer or visitor to view list of movies showcased at each venue by date and time. 3.2. Search Movie 3.2.1. The system shall have search function. Customer or visitor can search movies based on movie name, date, time and venue 3.3. Create Account 3.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.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 10

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.3.2. The system shall send activation link via email to customer to activate the account. 3.4. Customer Login 3.4.1. The system shall have customer login function. Once activated, customer can login using username and password. 3.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.5. Purchase Movie Ticket 3.5.1. The system shall enable customer to purchase the movie ticket from Guest Interface (MMS-GI). 3.5.2. The system shall display list of movies showcased at each venue. 3.5.3. The system shall display for each movie at the venue the following details a) Date b) Time c) Price

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 11

3.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.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.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.5.7. The system shall have Next button and Cancel button. 3.5.8. The system shall display the seating position (Seating Screen) still available for the movie based on time and date. 3.5.9. The system shall record the seatings selected by the customer. 3.5.10. The system shall have lock function. MMS 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.5.11. The system shall have Next button, Back button and Cancel button. 3.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.5.13. The system shall have Back button, Check Out button and Cancel button. 3.5.14. Once customer click the Check Out button, the system shall redirect the customer to Paypal to make the payment. 3.5.15. The customer shall confirm the payment details and Click the Pay Now button to purchase the movie tickets. 3.5.16. The system shall display thank you (Thank You Screen) message for the purchase.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 12

3.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.5.18. If the customer cancels the payment in Paypal, the system shall display the booking details back (Review Screen). 3.6. Purchase History 3.6.1. The system shall allow only customer who have login to access this record 3.6.2. The system shall have list of purchased movie details made by the customer.

Movie Management Interface(MMS-MMI) Functional Requirements Only ABC staff can access Movie Management Interface(MMS-MMI) via dedicated website url. The Movie Management Interface(MMS-MMI) is divide into into nine main module : Staff Module, Reservation Module, Ticketing Module, Membership Module, Movie Module, Availability module, Pricing Module, Branch Module and Report Module. Permission to each module depends on staff account type.

The functional requirements of Movie Management Interface(MMS-MMI) are as follows: 3.7. Login Function. 3.7.1. The system shall allow only staff with staff username and password to access the system. 3.7.2. Access to the modules determined by account type and Branch / Headoffice Location. 3.8. Staff Module 3.8.1. The system shall allow system administrator only to access this module. System administrator shall login first to access this module. 3.8.2. The system shall allow the system administrator to add staff , update staff and delete staff . 3.8.3. The system shall record all the following details, except the optional fields. a) Staff Username b) Password c) Account Type, determines which modules accessible to staff. d) First Name e) Last Name f) Street Address 1,

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 13

g) Street Address 2, (Optional) h) Zip Code, i) City/Town j) State k) Country l) Telephone Number m) Fax Number (Optional) n) Branch / Head office Location 3.8.4. System administrator will email to the staff username and password to access the system. 3.8.5. The system shall provide permission to the modules for each staff based on Account Type and Branch / Head Office Location. 3.8.6. The system shall have search function. 3.9. Reservation Module 3.9.1. The system shall allow counter clerk, branch manager and branch supervisor of the cinema branch to access the module. They shall to login first to access this module. 3.9.2. The system shall limit the access to branch level only. 3.9.3. The system shall display list of movies showcased at the branch. 3.9.4. The system shall allow the counter clerk to select the movie based the following criteria. a) Date b) Time 3.9.5. The system shall record the following details from the customer a) Number of adult b) Number of children 3.9.6. The system shall display the Seating Screen for customer to select their seat location 3.9.7. The system shall allow the counter clerk to book the seats for the customer. 3.9.8. The system shall have lock function. MMS will prevent customers or counter clerk from booking the same ticket based on 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.9.9. The system shall display the total amount to be paid. 3.9.10. The system shall allow the counter clerk to print the movie ticket.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 14

3.10. Ticket Module. For customer who bought the ticket on-line, they need to get the movie ticket from the branch. To get the movie ticket they need to provide the confirmation number that was generate when they book the ticket online. 3.10.1. The system shall allow counter clerk, branch manager and branch supervisor of the cinema branch to access the module. They shall to login first to access the module. 3.10.2. The system shall limit the access to branch level only. 3.10.3. The system shall allow counter clerk to search the movie reservation by using the confirmation number. 3.10.4. The system shall allow the counter clerk to print movie ticket for valid confirmation number. 3.10.5. The system shall report invalid confirmation number. 3.11. Membership Module. This module is used to register ABC priority card holder. 3.11.1. The system shall allow counter clerk, branch manager and branch supervisor of the cinema branch to access the module. They shall to login first to access this module. 3.11.2. The system shall limit the access to branch level only. 3.11.3. The system shall allow counter clerk to add member, update member and delete member. 3.11.4. The system shall record the following data for the customer. a) First Name b) Last Name c) Street Address 1, d) Street Address 2, (Optional) e) Zip Code, f) City/Town g) State h) Country i) Telephone Number j) Fax Number (Optional) k) ABC Priority Card No. The system shall automatically generate the card no. 3.11.5. The system shall display the total amount to paid for the membership. 3.11.6. The system shall allow the counter clerk to print the membership card.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 15

3.11.7. The system shall have search function to search membership record easily using the following search criteria. a) First Name b) Last Name c) Identity Card Number d) ABC Priority Card Number 3.11.8. The system shall have membership renewal function. 3.12. Movie Module. 3.12.1. The system shall allow head office personnel only to add and update new movie details in the system. Head office personnel shall login first to access this module 3.12.2. The system shall allow head office personnel to add movie and update movie. 3.12.3. The system shall record the following details for each movies. a) Movie Title b) Movie Summary c) Movie Description d) Movie Duration e) Movie Cast List f) Movie Director g) Movie Photos 3.12.4. The system shall allow the movie details to be publish or not publish. 3.12.5. The system shall not have delete function to remove added movie. Head office personal can only make the movie not publish. 3.12.6. The system shall have search function to find the movie record using the following criteria. a) Movie Title b) Movie Cast List c) Movie Director d) Date

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 16

3.13. Pricing Module 3.13.1. The system shall allow branch manager and branch supervisor of the branch only to access this module. Branch manager or branch supervisor shall login first to access this module. 3.13.2. The system shall limit the access to branch level only. 3.13.3. The system shall allow each branch to have their own pricing table. 3.13.4. The system shall allow the branch manager or supervisor to add pricing table, update pricing table and delete pricing table. 3.13.5. The system shall have the flexibility to create pricing table based on the following pricing parameter. a) Weekday pricing b) Weekend pricing c) Public Holiday pricing d) Based on Adult or children. e) Eligible discount for ABC priority card holder. 3.14. Availability module 3.14.1. The system shall allow branch manager and branch supervisor of the branch only to access this module. Branch manager or branch supervisor shall login first to access this module. 3.14.2. The system shall limit the access to branch level only. 3.14.3. The system shall allow the branch manager or supervisor to add availability, update availability and delete availability. 3.14.4. The system shall allow each branch to manage the availability of the movie showcased at their cinema. The branch manager or supervisor can make the movie available or not available at their branch. 3.14.5. The system shall make the movie available with the following steps a) Add the new movie. b) Select the pricing table. c) Enter the Start Date d) Enter the End Date e) Select the halls involved. f) Select the time slot for the movie. g) Enter how many hour or day the system shall stop selling the movie ticket via Guest Interface (MMSGI) system

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 17

3.14.6. The system shall allow many availability for each movie. This allows different hall and time slot to be selected. 3.14.7. The system shall not have date overlapping between the movie availabilities. 3.14.8. The system shall display the movie details at Guest Interface (MMS-GI) when it is made available. The system shall display the following details for each movie a) Movie Title b) Movie Summary c) Movie Description d) Movie Duration e) Movie Cast List f) Movie Director g) Movie Photos h) Time Slot i) Plus, the capability to book the movie ticket online. 3.14.9. The system shall allow the branch manager or supervisor to delete availability based on date and time for unforeseen reason. 3.14.10. The system shall generate list of customer that ABC need to refund for customer who have already purchased the ticket online, to be handled by ABC Credit Unit. Customer who bought the ticket from the counter can get the refund from the counter clerk. 3.15. Branch Module 3.15.1. The system shall allow system administrator only to access this module. System administrator shall login first to access this module. 3.15.2. The system shall allow system administrator to add branch and update branch. 3.15.3. The system shall record the following details for each branch a) Branch Overview b) Branch Description c) Branch Address & Contact Details d) Branch Location Map e) Branch Photos 3.15.4. The system shall not have delete function to remove the branch details. This is to prevent accidental error by the system administrator. The system shall only allow to make the branch details to be publish or not publish.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 18

3.15.5. The system shall allow system administrator to add hall and update hall for each branch. 3.15.6. The system shall not have delete function to remove the hall details. This is to prevent accidental error by the system administrator. The system shall only allow to make the hall details to be publish or not publish. 3.15.7. The system shall allow to set the seating configuration of each hall in the branch. a) The system shall record the number of rows in the hall. b) The system shall record the number of columns in the hall. 3.16. Report Module. 3.16.1. The system shall generate report based account types. 3.16.2. The system shall generate the following reports for each branch manager or branch supervisor. Branch manager or branch supervisor shall login first to access the reports. Report generated for the respective branch only. a) Branch Sales Report b) Branch Occupancy Report 3.16.3. The system shall generate the following reports for head office personnels. Head office personnel shall login first to access the reports. Report based on each branch or summarization of the total ABC branches. a) Head Office Sales Report b) Head Office Occupancy Report 3.16.4. The system shall generate the following report for ABC Credit Unit. This report is used to refund customers back for cancellation of show by branch. Applicable only to customer who purchased the ticket online via Guest Interface (MMS-GI). a) Customer Refund List

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 19

4. Technology Information
4.1 User Interfaces details
y y y y y The design or layout of every form will be very clear and very interactive to the user. When the user open the software the welcome window will appear. In the login window the user can easily entered the desired password and login name. Then it will give the successfully login message. From each and every window the user can easily go to any desired window that is there is will be a absolute and relative linking. y y y In every window & Mac there is help and support option is present for the ease of user. There will be a proper collection of GUI interface, which will provide better look and feel. In the screen layout the background color is very light and the graphics and font style will be in proper manner and well organized. y y y If the user will print any error statement then it will give the proper error message display. In each and every window there will be alert, confirm etc message box for displaying message. The user will be able to search any data from the record by using proper guideline shown in the window & Mac. y In the opening of the software there will be a menu window where the overall table contents of the software will be present through which the user can move to any desired window & Mac. y This will provide the better security data because the menu window will be displaying according to the login (admin or normal user). y User can easily save its data in to the database and keep track of the records of purchase, vendor and inventory etc. y This software will be easily understandable and operable by the user.

4.2 Software Interfaces


Database * MySql Server version 5 or above. Web Server * Apache Server version 2.2.6

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 20

Programming Languages * JavaScript * Java

4.3 Communications Interfaces


* Dial Up Modem * Broadband Internet * All transaction between client and server for Movie Management Interface (MMS-MMI) must be done using Secure Socket Layer (SSL) technology to encrypt the data. * Transaction between client and server for Guest Interface (MMS-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.

5. Other Nonfunctional Requirements


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

5.2 Security Requirements


5.2.1 All access permission for the system data may only be changed by the system's administrator. 5.2.2 All communication between MMS-MMI server data with client shall be encrypted by using Secure Socket Layer (SSL) technology. 5.2.3 Transaction between client and server for Guest Interface (MMS-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.

5.3 Scalability
The source codes for the system are well documented for ease of maintenance and upgrading the system in future. MMS system shall have a minimum uptime of 99 % excluding time pre-scheduled for maintenance and/or upgrades. 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.

Software Requirements Specification for MOVIE MANAGEMENT SYSTEM

Page 21

6. Other Requirements
<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.>

Appendix A: Glossary
 JSP (Java Server Pages): It is used to create dynamic web content.  J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications.  WASCE (Web Sphere Application Server Community Edition): It is an application server that runs and supports the J2EE and the web service applications.  DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong "on demand" business applications.  XML (Extensible Markup Language): It is a mark-up language that was designed to transport and store data.  Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create dynamic web pages.  Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability, user-cantered design and collaboration on the World Wide Web.