Software Requirements Specification (Nonfunctional Requirements), Online Movie Booking System Part 5

Please note : OUM Students don't copy this SRS document, I have submitted this paper for September 2010 assignment paper on software requirements

Non functional requirements include performance, reliability, safety, security and design constraint requirements.

5.1 Performance Requirements

5.1.1 The system response time must be less than 10 seconds for both OMBS-GI  and OMBS-MMI.

5.1.2 The system must process the number of transaction based on the following calculation method.

5.2 Reliability Requirement

5.2.1 OMBS system shall have a minimum uptime of 99 % excluding time pre-scheduled for maintenance and/or upgrades.

5.3 Safety Requirements

5.3.1 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. 

5.4 Security Requirements

5.4.1 All access permission for the system data may only be changed by the system's administrator.

5.4.2 All communication between  OMBS-MMI server data with client shall be encrypted by using Secure Socket Layer (SSL) technology. 

5.4.3 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.

5.5 Design Constraint

5.5.1 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.

5.6 Software Quality Attributes

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