soft by Nantha kumar

CityGuest Daily A Deals - website Software Requirements Specification For Reebonz / ReebonzCity like Website Version 1.0 Prepared By: John (Sr. Business Development Manager) Date: 05 September 2011

TABLE OF CONTENTS Content INTRODUCTION...........................................................................................................................................4 PURPOSE OF REQUIREMENTS DOCUMENT......................................................................................4 SCOPE OF THE PROJECT........................................................................................................................4 DOCUMENT CONVENTIONS.................................................................................................................4 INTENDED AUDIENCE AND READING SUGGESTIONS...................................................................4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS..........................................................................5 GENERAL DESCRIPTION............................................................................................................................6 PRODUCT PERSPECTIVE........................................................................................................................6 DESIGN AND IMPLEMENTATION CONSTRAINTS.............................................................................7 PRODUCT FUNCTIONS...............................................................................................................................7 MEMBER CHARACTERISTICS...............................................................................................................7 CONSTRAINTS..........................................................................................................................................8 SYSTEM SPECIFICATIONS – Front End Subsystem...................................................................................9 .....................................................................................................................................................................9 SYSTEM SPECIFICATIONS: Admin Panel .................................................................................................9 Login............................................................................................................................................................9 Admin Account Settings............................................................................................................................10 Logout........................................................................................................................................................10 Content Management System....................................................................................................................10 Manage moderators...................................................................................................................................10 Manage members ......................................................................................................................................11 Manage Business (Vendors Requests).......................................................................................................11 Manage Deal (Deal List)...........................................................................................................................12 Manage referral payment (Add/Edit).........................................................................................................13 Manage payment .......................................................................................................................................13 Manage referral payment (Add/Edit)..........................................................................................................13 Reference Document ....................................................................................................................................13 Project Proposal for Group Buying Website...............................................................................................13 Appendix........................................................................................................................................................13 Build and Maintain a Secure Network .......................................................................................................14 Protect Cardholder Data.............................................................................................................................14 Maintain a Vulnerability Management Program .......................................................................................14 Implement Strong Access Control Measures .............................................................................................14 Regularly Monitor and Test Networks .......................................................................................................14 Maintain an Information Security Policy...................................................................................................14 PCI Compliance Validation .......................................................................................................................15 Quality Management Process.....................................................................................................................16 SEO / User Friendly Design and Development .........................................................................................16 Development Framework...........................................................................................................................17 DEVELOPMENT PROCESS....................................................................................................................17 Project Team ....................................................................................................................................................................18

Progress is built on ideas.

Revision History Date

Old Status

05 September, 2011

New Status

Version Author

Initial Draft

1.0

John

3/18 Page

Progress is built on ideas.

INTRODUCTION This document serves as the Software Requirements Specification (SRS), which describes the Requirements for developing Reebonz / ReebonzCity like Website. Reebonz / ReebonzCity like Website is a multilingual portal of collective buying eCommerce Site, the website shall allow Admin to sell coupons on behalf of local businesses to customers. The coupon shall give the buyer the right to buy a product or service at a discounted price for a set period of time specified by the Administrators (Country / City Moderators), Super Admin or Vendors. Super Adin, Administrators of the site and Vendors shall be able to quickly & easily create new Deals for any number of unique locations. Customers shall be able to quickly & easily view these Deals. All Deals created (by Country / City) by Vendors will be verified and approved by Country / City Administrators (Moderators), before publication on the website.

PURPOSE OF REQUIREMENTS DOCUMENT The purpose of this Software Requirements Specification (SRS) is to document the requirements for DEAL in a detailed manner. Once the requirements are documented, this SRS document shall be sent to developer for approval. The intended audience of this document includes but not limited to business analysts, project managers, designers, software developers, system customer, testers and all other parties which are related to this project.

SCOPE OF THE PROJECT The scope of the project includes designing, documenting, developing, and testing an e-commerce website as well as creating a User Manual for the specified SubSystems.

DOCUMENT CONVENTIONS This SRS is multilevel. Each level has been numbered to make it more easily readable. Every process has been divided into sub-processes keeping in mind the design and development process.

INTENDED AUDIENCE AND READING SUGGESTIONS This document is prepared for every party related to this project. SRS is distributed to the Project Managers, Business Analysts, Approvers and Reviewers, Project Steering Committee Members (who shall assign Project Manager), Designers, Testers and Developers. 4/18 Page

Progress is built on ideas.

This document should be read from top to bottom. Some of the points are interrelated so top-to-bottom approach is suggested to understand it more clearly.

DEFINITIONS, ACRONYMS AND ABBREVIATIONS Description of Actors: Visitors: Visitors can view only the public/static page information, and can view Deal’s but if they need to book any deal for purchase, they would be required to register with the website as a valuable customer. Customers: Customers are registered users who can utilize their DEAL access to book any deal for purchase. They can browse, search, various deals available at particular time and purchase by using their credit card. A registered member can also review his/her transaction history & order details. Vendors: Vendors are the users who will fill & send out a request form to Administrator to enable their deal on the website for the customers to purchase. Administrator: Administrator shall have full control over the application. She/he shall manage users, deals, payment and content management system. Administrator of the site shall be able to quickly & easily create new Deals for any number of unique locations. Glossary of Terms: B2C: Business-to-consumer DEAL: Groupon/ reebonzcity like Website (Name to be used) Fire Fox: A web browser Safari: A web browser Internet Explorer: A web browser SMTP: Simple Mail Transfer Protocol HTML: Hypertext Markup Language JavaScript: A client side language executed in browser SMTP: Simple Mail Transfer Protocol SRS: Software Requirements Specification 5/18 Page

Progress is built on ideas.

XML: Extensible Markup Language RSS: Really Simple Syndication PHP: Hypertext Preprocessor MYSQL: A Database Storage Engine AJAX: Asynchronous JavaScript and XML MVC: Model View Controller CCV: Credit Card Verification code. API: Application Programming Interface CMS: Content Management System CSV: Comma Separated Value SEO: Search Engine Optimization SSL: Secure Sockets Layer URL: Uniform Resource Locator USD: United States Dollar The Deal: The main deal for the day The Chaser: The side deal for the day

GENERAL DESCRIPTION Software requirements specification document is a specification document that concentrates only on the requirements of the System/Application. The solution that this document shall be describing is the development of an easy to use DEAL web application.

PRODUCT PERSPECTIVE DEAL is developed by Company or Vendors from scratch. The goal of the DEAL is to provide a portal of collective buying e-Commerce Site, the website shall allow 6/18 Page

Progress is built on ideas.

Admin to sell coupons on behalf of local businesses to customers. The coupon shall give the buyer the right to buy a product or service at a discounted price for a set period of time specified by the Administrator or Vendors. Administrators of the site and Vendors shall be able to quickly & easily create new Deals for any number of unique locations. Customers shall be able to quickly & easily view these Deals.

OPERATING ENVIRONMENT The System shall be developed using following technologies:Servers: Server Side Scripting: Database: Programming Style: Client Front-end: Client Side Scripting: Client/Server Side Scripting:

Apache PHP MYSQL Object Oriented, MVC MODEL HTML JavaScript Flash, AJAX

DESIGN AND IMPLEMENTATION CONSTRAINTS The application has one production front-end and one production backend. All restrictions to a web based application would apply on DEAL web application

PRODUCT FUNCTIONS MEMBER CHARACTERISTICS Visitors: Visitors can view only the public/static page information, and can view deal’s but if they need to book any deal for purchase, they would be required to register with the website as a valuable customer. Customers: Customers are registered users who can utilize their DEAL access to book any deal for purchase. They can browse, search, various deals available at particular time and purchase by using their credit card. A registered member can also review his/her transaction history & order details. Vendors: Vendors are the users who will fill & send out a request form to Administrator to enable their deal on the website for the customers to purchase. 7/18 Page

Progress is built on ideas.

Administrator: Administrator shall have full control over the application. She/he shall manage users, deals, payment and content management system . Administrator of the site shall be able to quickly & easily create new Deals for any number of unique locations.

CONSTRAINTS Regulatory Policies All the Regulatory policies of the state shall be applied to the DEAL site. The website shall be in full compliance with PCI Standards (Refer: Section 7.7 Appendix). We shall use some third party SSL certification and approval for secured payment like VeriSign.

Hardware Limitations This is designed to operate in a web environment. Therefore, there shouldn't be any hardware limitation.

Interfaces to Other Applications The application shall be integrated with more Payment Methods. Free Order Pay with Paypal Account Pay with SagePay (for Eg.) will talk about it Pay with Internet Bank Transfer Pay with Cash on the Bank Pay with your Phone Pay with Credit Card Installment Plan Purchase (the Bank partnership) Gift to a Friend

Parallel Operations This Application shall support hundreds of thousands of members into the System simultaneously. Concurrent operations shall be handled by the System. This application shall be able to handle hundreds of thousands of concurrent members. Any deadlocks shall be handled programmatically, and the member shall be notified with member-friendly error messages.

Audit Operations The application shall have certain levels of auditing capability, so that different levels of errors, debugging, and access logging information shall be stored as text files. These files can be used for auditing and debugging purposes.

8/18 Page

Progress is built on ideas.

Reliability and Performance 1. 2. 3. 4.

The System should be stable and should be available 24/7 The System must have "commit-and-rollback" features; if one of the variables has failed, then all the other variables need to fall back to their original values. The System shall be used for more than hundreds of thousands of requests. All requests should run simultaneously without affecting the performance of the System. The System should be able to support hundreds of thousands of concurrent members. The performance and number of concurrent members mainly depends on hardware. The application does not have a limitation on number of concurrent members.

SYSTEM SPECIFICATIONS – Front End Subsystem -

In progress

SYSTEM SPECIFICATIONS: Admin Panel Login This section shall enable the Administrator to login to Admin Sub-System Login shall have following functional requirements: 5.1.1. Super Admin must enter his/her User Name and Password to login to the System 5.1.2. There will be moderators on the website based on the locations the access level will be provided to them based on locations. 5.1.3. Super Admin will have full rights to manage manage the moderators account. 5.1.4. All the features of the moderators will be similar to Super Admin except they will have the rights limited to location. 5.1.5. The System must validate the User Name and Password by matching it against the value stored in database 5.1.6. Admin shall be allowed to login only if the User Name and Password match with the ones stored in the database 5.1.7. The System shall display the relevant message to the Admin if the User Name and Password are not valid 9/18 Page

Progress is built on ideas.

Admin Account Settings 5.1.8. Edit/Update Admin Password 5.1.9. Edit/Update Admin personal information and email id

Logout This section shall enable the Administrator to logout from Admin Sub-System. Logout shall have following functional requirements: 5.1.10. The System shall allow the logged in Admin of the site to logout of the System. 5.1.11. The System shall destroy all the session information of the Admin after he/ she logs out successfully. 5.1.12. The System shall redirect the logged out Admin to the Admin Login page of the website

Content Management System This section shall enable the Administrator to set content for static pages. Content Management System shall have following functional requirements: 5.1.13. System shall provide a means to Administrator to view the list of Static pages of website. 5.1.14. System shall provide a means to Administrator to add a Static page. 5.1.15. System shall provide a means to Administrator to add the content of Static pages of website. 5.1.16. System shall provide a means to Administrator to edit the content of Static pages of website. 5.1.17. System shall provide a means to Administrator to reorder Static pages. 5.1.18. System shall provide a means to Administrator to remove the Static page. 5.1.19. Systems shall allow Administrator the ability to toggle certain features on and off, specifically the following features: 5.1.19.1. Select Your Location 5.1.19.2. The Chaser 5.1.19.3. Future Deals

Manage moderators This section shall enable the Administrator to manage registered users of website Manage members shall have following functional requirements: 10/18 Page

Progress is built on ideas.

5.1.1. System shall provide a means to Administrator to view the list of moderators and details about their accounts and purchases 5.1.2. System shall allow Administrator to Moderators account. 5.1.3. Administrator will have full rights to reset the Password of any given member. 5.1.4. System shall allow Administrator to delete selected member. 5.1.5. System shall allow Admin to add new Moderator.

Manage members This section shall enable the Administrator to manage registered users of website Manage members shall have following functional requirements: 5.1.6. System shall provide a means to Administrator to view the list of members and details about their accounts and purchases 5.1.7. System shall allow Administrator to activate/deactivate member's account. 5.1.8. System shall allow Administrator to update account information of any given member. 5.1.9. System shall provide a means to Administrator to reset the Password of any given member. 5.1.10. System shall allow Administrator to delete selected member. 5.1.11. System shall allow Admin to add new member. 5.1.12. System shall allow Admin to search the member on the basis of User Name, Email.

Manage Business (Vendors Requests) 5.1.13. System shall provide a means to Administrator to view the list of members and details about their accounts and purchases 5.1.14. System shall allow Administrator to activate/deactivate member's account. 5.1.15. System shall allow Administrator to update account information of any given member. 5.1.16. System shall provide a means to Administrator to reset the Password of any given member. 5.1.17. System shall allow Administrator to delete selected member. 5.1.18. System shall allow Admin to add new member. 5.1.19. System shall allow Admin to search the member on the basis of User Name, Email. This section shall enable the Administrator to manage requests send by vendors through business page: 5.1.20. System shall provide a means to Administrator to view the list of requests 11/18 Page

Progress is built on ideas.

5.1.21. System shall allow Administrator to Approve or Deny selected requests. 5.1.22. System shall allow Administrator to search requests list on the basis of business name, email, phone no. 5.1.23. System shall allow Administrator to edit request and save it in deal list. 5.1.23.1. Edit Request(To save it in deal list) 5.1.23.1.1. Business Name(Text field auto fill) Mandatory 5.1.23.1.2. Deal Headline(Text field) Mandatory 5.1.23.1.3. Date of Deal(JavaScript calendar) Mandatory 5.1.23.1.4. Start Time of Deal(List box) Mandatory 5.1.23.1.5. End Time of Deal(List box) Mandatory 5.1.19.3.1. Price of Deal(Text field) Mandatory - Depends of published perioud accepted, Discount rate and Maximum Number of Deals Available 5.1.23.1.6. 5.1.23.1.7. Value of Deal(Text field) Mandatory 5.1.23.1.8. Minimum Number of Deals Needed(Text field) Mandatory 5.1.23.1.8.1. Maximum Number of Deals Available(Text field) Mandatory 5.1.23.1.8.1.1. If there is no maximum, allow admin to input “unlimited” or something similar 5.1.23.1.9. The Details(Text area) Mandatory 5.1.23.1.10. The Highlights(Text area) Mandatory 5.1.23.1.11. What It’s All About(Text area) Mandatory 5.1.23.1.11.1. Change the Business Name Tag for The Deal and The Chaser

Manage Deal (Deal List) This section shall enable the Administrator and Vendors to manage deals, but the Administrator will have to approve it. 5.1.24. System shall provide a means to Administrator to view the list of deals 5.1.25. System shall allow Administrator to activate/deactivate deals 5.1.26. System shall allow Administrator to update deals 5.1.27. System shall provide a means to Administrator to view report of deal which shows how many users has apply for this deal and statistics such as: 5.1.27.1. Number purchased 5.1.27.2. Total sales volume 5.1.27.3. What age / sex purchased the deal 5.1.19.4. City of transactions 12/18 Page

Progress is built on ideas.

5.1.28. System shall allow Administrator to delete selected deal. 5.1.29. System shall allow Administrator to add/remove deals to the Future Deals Section 5.1.30. System shall allow Administrator to add/remove deals to the Recent Deals Section

Manage referral payment (Add/Edit) 5.1.31. 5.1.32.

Amount (Text field) Mandatory Description(Text area) Mandatory

Manage payment This section shall enable the Administrator to view payment that users have paid for deal. 5.1.33. Database with searchable features, including: 5.1.33.1. Select location (list box) 5.1.33.1.1. Select deal(List box in chronological order) 5.1.33.1.2. User name 5.1.33.1.3. Quantity 5.1.33.1.3.1. Quantity bought 5.1.33.1.3.2. Quantity gifted 5.1.33.1.4. Amount 5.1.33.1.5. Gross amount paid 5.1.33.1.6. Referral credit used 5.1.33.1.7. Net amount paid 5.1.33.1.8. Total 5.1.34. Ability for Administrator to redeem/give back members with their money if necessary

Manage referral payment (Add/Edit)

Reference Document Project Proposal for Group Buying Website

Appendix The Basics of PCI Compliance and Validation Regulations to be followed for DEAL are as below. 13/18 Page

Progress is built on ideas.

Build and Maintain a Secure Network (This shall be done by the web hosting company) 5.1.35. Requirement 1: Install and maintain a firewall configuration to protect cardholder data 5.1.36. Requirement 2: Do not use vendor-supplied defaults for System Passwords and other security parameters Protect Cardholder Data (We required VeriSign SSL certification for 128 bits data encryption. DEAL shall provide the required VeriSign login detail) 5.1.37. Requirement 3: Protect stored cardholder data 5.1.38. Requirement 4: Encrypt transmission of cardholder data across open, public networks Maintain a Vulnerability Management Program 5.1.39. Requirement 5: Use and regularly update anti-virus software (These shall be done by the web hosting company and also DEAL shall have to purchase the McAfee Secure CERTIFICATION. It shall automatically scanned the entire website on regular basis) 5.1.40. Requirement 6: Develop and maintain secure systems and applications Implement Strong Access Control Measures (Please refer section 5.4) 5.1.41. Requirement 7: Restrict access to cardholder data by business need-to-know 5.1.42. Requirement 8: Assign a unique ID to each person with computer access 5.1.43. Requirement 9: Restrict physical access to cardholder data Regularly Monitor and Test Networks (NB: Not part of development process. If you want company to do it for you on regular basis please contact our pre-sales department) 5.1.44. Requirement 10: Track and monitor all access to network resources and cardholder data 5.1.45. Requirement 11: Regularly test security systems and processes Maintain an Information Security Policy (DEAL shall provide information for any security requirement) 14/18 Page

Progress is built on ideas.

5.1.46. Requirement 12: Maintain a policy that addresses information security PCI Compliance Validation Credit card companies validate that vendors are abiding by the PCI Compliance regulations. The volume of transactions and the risk determined by the Credit Card Company determines the validation rating for the merchants and institutions accepting credit/debit and pay cards. Along with requiring participating businesses to complete a self-assessment questionnaire, MasterCard and Visa perform the following actions to validate a participating business' security: 1. An on-site visit and 2. A network scan performed by an authorized PCI Compliance scanning vendor.

15/18 Page

Progress is built on ideas.

Quality Management Process Being an ISO certified software development Company our quality assurance department always work with programmers and designers in order to discover early errors, if any. We perform unit tests of code programming as well as individual classes are tested within each unit level to assure reliability and functionality. After getting all testing done including integration testing, scalability testing, resolution testing and cross browser compatibility testing we generate live testing of websites and applications. The Test driven Design/Development process follows the following steps: 1. 2. 3. 4. 5. 6. 7.

Client Consultation Initial Drafts and Photoshop Mock Up Finalize the Design (Test driven) Code into XHTML/CSS (Test driven) W3C Code / CSS validation PHP/MYSQL (Test driven development) Final Testing & debugging

SEO / User Friendly Design and Development We will working on the project by considering search engine and user guideline to make the website very user and search engine friendly. Our SEO/ Promotion team will be regularly in tough with design/ development team to work in effective manner. 1. 2. 3. 4. 5. 6. 7. 8.

SE friendly design /code structure Proper Content placement and Properly Navigation / Link placement Optimized XHTML Code Optimized CSS W3C compliance Web 2.0 standards Browser Compatibility

16/18 Page

Progress is built on ideas.

Development Framework Development environment and tools for PHP 1. 2. 1. 2. 3. 4. 5.

PHP/MySQL Server/HTML/AJAX (proposed technologies) Server Side scripting: PHP 5.X Database: MySQL 5.x Programming Style: Object Oriented, N Tier Client Front-end: HTML, DHTML Client side scripting: JavaScript Servers: Red Hat Linux

DEVELOPMENT PROCESS We follow waterfall model approach for developing Robust, Secure and Portable solutions. The development process follows seven distinct steps which helps us to create the best possible solutions on-time & within budget. The web designers and developers team closely work with SEO professionals to implement solutions in search engine friendly and user friendly manner achieving web branding, promotion, viable traffic, and web functionality to generate business through online web presence. The Web Design/Development process follows the following steps: 1. Client Consultation 2. Initial Drafts and Sketches 3. Photoshop Mock Up 4. Finalize the Design 5. Code into XHTML/CSS 6. W3C Code / CSS validation 7. PHP/MYSQL 8. Testing & debugging The waterfall model provides an orderly sequence of development steps and helps ensure the adequacy of documentation and design reviews to ensure the quality, reliability, and maintainability of the developed software.

17/18 Page

Progress is built on ideas.

Project Team

**The Team would be assign after awarding the project

18/18 Page