Boosting Online Business through SNS

August 8

2012
SRS

This document contains SRS (Software Requirement Model) for our project.

Introduction
1.1 Purpose and Scope Relating and promoting the brands which can be trusted , with one of the basic needs of human life today i.e social networking sites.

1.2 Product and Environment The product will take the user's social database as raw input and will display the products purchased by the user to the people who are related to the user based on the likes and tags in descending order.

1.3 Definition, Acronyms and Abbreviations User = Person making purchase at customers site SNS = Social Networking Site

1.4

References -

Online Social Networks Research @

The Max Planck Institute for Software Systems

http://socialnetworks.mpi-sws.org/
1.5 Overview Digging the database for user's basic information , and finding people most closely related to the user and promoting the products based on user's purchasing.

2. General Description
2.1 Product Perspective The purpose of creating this product is to implement a new method of promotion of products through people closely related to each other.

2.2 Product Functions The functioning of the software will be solely based on extracting the basic information of a particular user and finding a list of people closely related to the user based on the likes , tags etc in descending order and posting the details of the purchased product on their personal profiles.

2.3 User Characteristics The requirements will be users account details such as 1. Email id 2. Friend list 3. Details of comments , likes and posts related to users a/c.

2.4 General Constraints 1. Social networking site used in the given context will be facebook. 2. Number of people to be considered in the users related list will be atmost equal to the number of friends the user has. 3. The notifications of these promotions will have a different icon from simple notification.

2.5 Assumptions And Dependencies The email ids provided by the user in the softwares database as login id should be same as that of SNS(social networking site).

3. Data and Database

3.1 Contents of Information Basically, all user data including contact details, ID of the friend list and frequencies will be stored in the database.

3.1.1 Data Element User_id, Name, Address, Phone, Frequency, Friend list ID.

3.2 Intensity of Use It will be accessed every time a friend likes a post or user make a

purchase.

3.3 Capacity It will depend on number of target users and their number of connections.

4. Functions
4.1 General To predict probable buyer for the product.

4.2 Program The product will take the user social database as raw data. Persons related to the user will be segregated on the basis of number of likes on user activity. Now these sorted persons will be shown an advertisement if the user make purchases.

5.Interfaces
5.1 Hardware No direct hardware interface needed for the product. Simple OS controlled disk and memory operations will be sufficient. But for large scale systems, dedicated dns servers with high network bandwidth (>50mbps) along with high rpm disks(7200rpm) are required.

5.2 Software -

Prime software requirements will include a Internet browser, a good operating system for effective resource management.

5.3 Communication Standard HTTP (hypertext transfer protocol) and XMTP(XML MIME Transformation Protocol) will be needed for exchange of information between various servers

6.Other Requirements
6.1 Performance and response Time It is totally dependent on users friend connection. 6.2 Security, Recovery and Usability We will deploy RSA 128 bit encryption for information exchange. There would be a backup server which will store the user data when the load on the main server is low. 6.3 Maintainability As this is a web based programme it has to be updated with newer versions of online languages. 6.4 Portability This software is platform independent and can be applied to any system base windows/linux/max with ease.

7. Design Constraints
7.1 Standards We try to follow standard IEEE conventions throughout. 7.2 Hardware Small scale processors and small servers can make the implementation inefficient. Also there is a need of large chunk of storage since our product works on the past data. 7.3 Software the backend of the product mainly makes use of java or php in comparison to C/C++ as they are more versatile but one thing they lack is speed. Also implementing out project using java is also cumbersom job since it is quite vast and complex. 7.4 Other Constraints Have not been identified yet.

8 Ideas for Further Development

There is always a scope for improvement. We will try to optimize query time, security of user data and better customer experience.

Under the guidance of Dr. Sonali Agarwal Submitted By Siddharth Prakhar Pulkit IIT2010173 IIT2010185 IIT2010128