Wednesday, April 6, 2011

Facebook Advertising Costs, Daily Budget & Pricing

Facebook is a good advertising platform for your business. You don’t need have a specific budget amount to start a campaign. I have started mycampaign for less than 10 USD.


There costs for Facebook advertising depends whether you select Pay for Impression (Cost Per Thousand Impression - CPM) orPay for Click (Cost per Click - CPC).
The minimum cost that the system allows you to set in the ad campaign is USD 0.02 for CPM and USD 0.01 forCPC. The system will suggest the bid amount, but you could set it lower. For my campaign, I put USD 0.02 the minimum amount for 1000 impressions and still manage to run my campaign as I want.
If you want to create awareness for your new portal, product or service but you don’t care whether the people actually click the advertisement than you should choose Pay per impression pricing for your campaign. Or else use CPC pricing for your campaign.
The minimum daily budget for CPC and CPM is USD 1.00 and Facebook advertising will not charge you more than the minimum budget you have set. In addition, your daily budget must be 2 times the CPC or CPM amount that you set. If you set 10 USD for the CPC, then your minimum daily budget must be set as 20 USD.
Facebook will charge your Paypal or credit card for the campaign on a specific billable date or earlier if you have stopped/completed your campaign.
Facebook Advertising Costs, Daily Budget & Pricing
Facebook Advertising Costs, Daily Budget & Pricing

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.  

Software Requirements Specification (Functional Requirements), Online Movie Booking System Part 3

Please note : OUM Students don't copy this SRS document, I have submitted this paper for September 2010 assignment paper on software requirements
3. System Requirements
This section contains all the software requirements at a very detail level, combined with the use case diagram, use case description and the sequence diagram will enable software engineers to design the OMBS according to end users requirements, and test engineers to test the system.
For the use case diagrams and the descriptions,please refer to  Appendix A.
For the sequence diagrams, please refer to Appendix B.

3.1 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(OMBS-MMI)
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
 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 (OMBS-GI).
 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.
 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.

Movie Management Interface(OMBS-MMI) Functional Requirements
Only ABC staff can access Movie Management Interface(OMBS-MMI) via dedicated website url.  
The Movie Management Interface(OMBS-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(OMBS-MMI)  are as follows:
 3.1.7. Login Function.
  3.1.7.1. The system shall allow only staff with staff username and password to access the system.
  3.1.7.2. Access to the modules determined by account type and Branch / Headoffice Location.

 3.1.8. Staff Module
  3.1.8.1. The system shall allow system administrator only to access this module. System administrator shall login first to access this module.
  3.1.8.2. The system shall allow the system administrator to add staff , update staff and delete staff .  
  3.1.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,
 g) Street Address 2, (Optional)
 h) Zip Code,
 i) City/Town
 j) State
 k) Country
 l) Telephone Number 
 m) Fax Number (Optional)
 n) Branch / Headoffice  Location
  3.1.8.4. System administrator will email to the staff username and password to access the system.
  3.1.8.5. The system shall provide permission to the modules for each staff based on Account Type and Branch / Head Office  Location.
  3.1.8.6. The system shall have search function.

 3.1.9. Reservation Module
  3.1.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.1.9.2. The system shall limit the access to branch level only.
  3.1.9.3. The system shall display list of movies showcased at the branch.
  3.1.9.4. The system shall allow the counter clerk to select the movie based the following criteria.
 a) Date
 b) Time
  3.1.9.5. The system shall record the following details from the customer
 a) Number of adult
 b) Number of children
  3.1.9.6. The system shall display the Seating Screen for customer to select their seat location
  3.1.9.7. The system shall allow the counter clerk to book the seats for the customer.
  3.1.9.8. The system shall have lock function. OMBS 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.1.9.9. The system shall display the total amount to be paid.
  3.1.9.10. The system shall allow the counter clerk to print the movie ticket.

 3.1.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.1.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.1.10.2. The system shall limit the access to branch level only.
  3.1.10.3. The system shall allow counter clerk to search the movie reservation by using the confirmation number.
  3.1.10.4. The system shall allow the counter clerk to print movie ticket for valid confirmation number.
  3.1.10.5. The system shall report invalid confirmation number.

 3.1.11. Membership Module. This module is used to register ABC priority card holder.
  3.1.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.1.11.2. The system shall limit the access to branch level only.
  3.1.11.3. The system shall allow counter clerk to add member, update member and delete member.
  3.1.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.1.11.5. The system shall display the total amount to paid for the membership.
  3.1.11.6. The system shall allow the counter clerk to print the membership card.
  3.1.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.1.11.8. The system shall have membership renewal function.

 3.1.12. Movie Module.
  3.1.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.1.12.2. The system shall allow head office personnel to add movie and update movie.
  3.1.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.1.12.4. The system shall allow the movie details to be publish or not publish.
  3.1.12.5. The system shall not have delete function to remove added movie. Head office personal can only make the movie not publish.
  3.1.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

 3.1.13. Pricing Module
  3.1.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.1.13.2. The system shall limit the access to branch level only.
  3.1.13.3. The system shall allow each branch to have their own pricing table.
  3.1.13.4. The system shall allow the branch manager or supervisor to add pricing table, update  pricing table and delete  pricing table.
  3.1.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.1.14. Availability module
  3.1.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.1.14.2. The system shall limit the access to branch level only.
  3.1.14.3. The system shall allow the branch manager or supervisor to add availability, update  availability and delete  availability.
  3.1.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.1.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 (OMBS-GI) system
  3.1.14.6. The system shall allow many availability for each movie. This allow different hall and time slot to be selected.
  3.1.14.7. The system shall not have date overlapping between the movie availabilities.
  3.1.14.8. The system shall display the movie details at Guest Interface (OMBS-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.1.14.9. The system shall allow the branch manager or supervisor to delete availability based on date and time for unforeseen reason.  
  3.1.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.1.15. Branch Module
  3.1.15.1. The system shall allow system administrator only to access this module. System administrator shall login first to access this module.
  3.1.15.2. The system shall allow system administrator to add branch and update branch.
  3.1.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.1.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.
  3.1.15.5. The system shall allow system administrator to add hall and update hall for each branch.
  3.1.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.1.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.1.16. Report Module.
  3.1.16.1. The system shall generate report based account types.
  3.1.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.1.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.1.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 (OMBS-GI).
 a) Customer Refund List
Related Posts Plugin for WordPress, Blogger...

ShareThis