You are on page 1of 27

Larkut.

com
Page i

Software Requirements Specification
For
Larkut.com
SociaI Networking Website
Version 1.0
Prepared by Trupti JaiswaI
Guided by Prof. Robert Zhu
Herguan University
06/11/2010
Larkut.com
Page ii

Table of Contents
Table of Contents ...................................................................................................................... ii
#evision History ........................................................................................................................ ii
1. MILESTONE 1 ................................................................................................................... 1
1.1 Introduction ............................................................................................................................ 1
1.1.1 Purpose ............................................................................................................................... 1
1.1.2 Document Conventions ....................................................................................................... 1
1.2 Business Requirement ............................................................................................................. 1
1.2.1 Business Opportunity .......................................................................................................... 1
1.3 Intended Audience .................................................................................................................. 1
1.4 Project Scope .......................................................................................................................... 1
1.5 ReIerences .............................................................................................................................. 2
. MILESTONE ...................................................................................................................
2.1 Product Perspective ................................................................................................................. 2
2.2 Product Functions ................................................................................................................... 2
2.3 Operating Environment ........................................................................................................... 3
2.4 Design and Implementation Constraints .................................................................................. 3
2.5 Assumptions and Dependencies .............................................................................................. 3
2.6 External InterIace Requirements.............................................................................................. 4
2.6.1 Flow Diagram ..................................................................................................................... 4
2.6.2 Activity Chart Ior Social Networking Website .................................................................... 5
2.6.3 Communications InterIaces ................................................................................................. 5
2.7 System Features ...................................................................................................................... 6
Main Features.................................................................................................................................. 6
2.8 System Feature ....................................................................................................................... 6
2.9 NonIunctional Requirements ................................................................................................... 7
2.9.1 PerIormance Requirements ................................................................................................. 7
2.10 Security Requirements ............................................................................................................ 7
. Other #equirements ............................................................................................................ 8
3.1 System Development Requirements ........................................................................................ 8
3.1.1 Description ......................................................................................................................... 8
3.1.2 Requirements ...................................................................................................................... 8
. MILESTONE ................................................................................................................. 10
4.1 Design Phase ........................................................................................................................ 10
4.1.1 Use case diagrams............................................................................................................ 10
4.1.2 Sequence Diagram ............................................................................................................ 15
. Database #elationship .......................................................................................................


#evision History
Name Date #eason For Changes Version
%rupti Jaiswal 07/01/2010 First DraIt V0.1
%rupti Jaiswal 07/03/2010 First Revision V0.2
%rupti Jaiswal 07/15/2010 Final Revision V1.0


Larkut.com
Page 1

1. MILESTONE 1
1.1 Introduction
1.1.1 Purpose
%his soItware requirement speciIication (SRS) document describes the Iunctional and nonIunctional
requirements oI the Larkut.com, a social networking system. Business opportunity and objectives is brieIly
summarized Iollowed by detailed description oI the system`s scope, vision, use case, Ieatures, Iunctionality,
Ieasibility and other related requirement issues. In the project`s later phases, such as system design, database
design, implementation and testing, this document should be reIerred as Iunctional model oI the system.
1.1. Document Conventions
All system development activities should Iollow the Iinal version oI this document. Any discrepancy that
Iound during in later phases should be modiIied subject to SRS. However, this document may be subject to
change dependent on the decision oI Guide ProI. Robert Zhu.
1. usiness #equirement
1..1 usiness Opportunity
Product intends to provide a well established web-based social networking system. As Internet and Web-
based applications become more and more crucial and widely adapted in today`s society, people have Iound
that most everyday businesses can be carried out online in a more Ilexible and convenient way. Social
network got a great place to communicate make people closer at particular place. It has all things which
makes social networking site more enjoying and impressive to people who are using it.

1. Intended Audience
1. SoItware developer
2. Administrator
3. Security Analysts
4. Users oI the system
5. Maintenance %eam

1. Project Scope
%he social networking website is an online community designed to make social liIe more active and
stimulating. %he social network can help you maintain existing relationships with people and share pictures
and messages, and establish new ones by reaching out to people you've never met beIore.
Larkut.com
Page 2

%his website also provides the Ieatures oI blogging. %he main idea behind blogging is to share your thoughts
with all your Iriends which can be read by all the users using the website. %his blog can be handled by the
user as he wants .It also provides the Ieatures oI adding videos and photos. %his website includes buying and
selling oI products Ieature. People using this website can market to buy and sell products. %he main purpose
behind this classiIied Iunctionality will help people to buy products in trusted circle.
1. #eferences
Larkut.com project speciIication
http://www.google.com
http://www.orkut.com
http://www.Iacebook.com
http://craigslist.org

. MILESTONE
.1 Product Perspective

%his social networking website challenges to give a better socializing and classiIied System at the same
place. %his website helps buying and selling oI products in trusted Iriend circle

. Product Functions
OAuthorization: Entire authority oI the system is to the Iounder / administrator oI the system.

O&80r auth0ntication: A newly created user is authenticated against the given email address.

O&80r form%he system oIIers a simple, attractive, user Iriendly user interIace easily understandable by the
users oI the system. Entries oI the user Iorm are under the authority oI the administrator only. Some oI the
entries in the Iorm are mandatory in order to authenticate the user, describe the user thoroughly etc.

OAdmini8trator Function8

1. Authentication oI the users aIter registration.
2. Mails to the users regarding the approval as a registered user, disapproval
3. Mentioning the appropriate reasons.
4. Updating the account details on the request oI the users.
5. NotiIication to the end users regarding proposals.
6. Mentioning the security measures Ior the system`s saIety.
7. Deleting an account/user Irom the system`s databases on request oI the user.

Larkut.com
Page 3

O0-8it0 Information:

1. i85aying Hi8tory: Mentions the history about the system such as Iounder oI the system.
2. ontact d0tai8: Contact details.
3. Adv0rti80m0nt8: Website will contain advertisements related to all various products present Ior
selling.

. Operating Environment
OInt0rn0t Brow80r Su55ort:
1. Internet Explorer 6/7/8
2. Mozilla FireIox
3. Google Chrome
4. Opera
5. SaIari

O50rating Sy8t0m Su55ort:


1. WINDOWS 98/XP/VIS%A/7
2. Mac OS

OInt0rn0t onn0ctivity R06uir0d

. Design and Implementation Constraints

1. S0curity: %he system should take care oI hacks like SQL injection. It should also not expose any
sensitive inIormation to normal users.

2. Faut To0ranc0: Data should not become corrupted in case oI system crash or power Iailure.

. Assumptions and Dependencies


1. Central server oI the system must be able to handle all the incoming requests simultaneously.
2. Back up oI the databases in case oI hardware Iailure, disaster, natural calamities.
No data loss in case oI handling oI the system by the administrators or the system related personnel

Larkut.com
Page 4

.6 External Interface #equirements
.6.1 Flow Diagram



llg 1 llow ulagram



Larkut.com
Page 5

.6. Activity Chart for Social Networking Website




.6. Communications Interfaces

%o use the social networking system eIIiciently user need to have an internet connection with a personal
computer running with any well established Operating System like Windows or Linux. User needs to have
installed Internet browser and email client on his machine Ior the same.

Larkut.com
Page

.7 System Features
%he social networking website is Ior people to get connected, there is also a Ieature Ior them to post
classiIieds to buy and sell products in a trusted Iriend circle. In addition to this Ieature the users have the
Iacility to add videos and photos. %his website gives a lot oI Ieatures all at one place.
Main Features
FE-1: Create/Delete ProIile
FE-2: Update account
FE-3: Get Iorgotten password through Email
FE-4: Message system (write on others wall/Delete own message Irom others wall/delete message Irom
own wall)
FE-5: Search members /add as member/delete member
FE-6: Blog system (add/modiIy/delete posts)
FE-7: Add comment on others blog post
FE-8: Post and search classiIieds.
FE-9: Add comments on classiIieds.
FE-10: User login/Logout
*FE-11
1
: Add/ Delete/ModiIy Photo Galleries
*FE-12
2
: Add/ Delete/ModiIy Video Galleries
*FE-13
3
: Update/add/delete company inIormation, Site administration to manage site content like Admin
Users Members, Pictures, Videos, Music, Blog, Categories, Blog ,Posts, classiIieds Categories, block users
(by administrator)


.8 System Feature
Creating a new account
1. User is allowed to create his own proIile.
2. According to the speciIications required by the administrator, the user creates his own proIile and
submits it to the system.

00ting th0 account
1. %he user can delete his/her account.

&pdating the account
1. %he user is allowed to update his/her account.
2. %he administrator updates the proIile accordingly.
3. %he user is not allowed to keep any mandatory Iields blank while updating. e.g. Name, Last name, email
Id etc.


1
Features with an asterisk (*) means this Ieather will be implemented iI time permits.
2
Features with an asterisk (*) means this Ieather will be implemented iI time permits.
3
Features with an asterisk (*) means this Ieather will be implemented iI time permits.
Larkut.com
Page 7

Forget password through Email
User can request Ior new password. Existing password will be sent to the registered email Id oI the user.

Message system
User can send and get message to his message box.

Search members /add as member/delete member

User can search, add and delete members in his list to widen his network

O&ploading Photographs
%he user has a Iacility to upload and share his photographs.
OAdding YouTube videos
%he user can add videos Irom you tube and share with people.
Ologging
%he user has the right to write his blog and publish it.
O Post and search classifieds.
%he users can place their items they need to sell on this website. %he users can also search items to buy Irom
this website. As this is a social network website one can trust on the quality oI the items begin posted.

.9 Nonfunctional #equirements
.9.1 Performance #equirements

OScalability: System should be able to handle around thousand users at the same time.
O&sability: Simple user interIaces that a layman can understand.
OSpeed: Speed oI the system should be responsive i.e. response to a particular action should be available in
short period oI time. For e.g. on registering as a new user the notiIication about the approval is sent
immediately to the respective user through email. Updating the account takes Iew seconds Ior the changes iI
the entry is not starred.

.10 Security #equirements
1. %he new proIile Iormed is validated against the given email address.
2. %he system or the system databases should not be manipulated by the normal users.


Larkut.com
Page 8

. Other #equirements
.1 System Development #equirements
.1.1 Description
%his section describes what resources will be utilized in the development and use oI the soItware.
.1. #equirements
#eq # Description
#EQ-S#1 %he database backend system in use will be MYSQL5.1.
#EQ-S#
%he Front-end and middle logic tools and technology will be
written using Java2EE, Spring, Hibernate, AJAX, JSP, Javascript,
JQuery, Servlets, H%ML, CSS
#EQ-S# Code will be stored on the Google Code SVN repository.
#EQ-S# Development environment will be the Eclipse Integrated
Development Environment.
#EQ-S# I will use %omcat as a web server.
#EQ-S#6 I will use Iterative model and Agile Methodology.
#EQ-S#7 Bugzilla Ior bug tracking

#EQ-S#8 I may make changes to any oI the above system requirement at
anytime and Ior any reason.

.1..1 Agile Methodology

Larkut.com
Page 9

.1.. Iterative Model




.1.. Scrum Framework

Larkut.com
Page 1

. MILESTONE
.1 Design Phase
.1.1 &se case diagrams

4.1.1.1 Login/Registration







User
Regester for login
Login
Request for forgetted passward
Cet email to confirm registration
<<include>>
Cet password email
<<include>>
<<include>>
validate user
<<include>>
Larkut.com
Page 11

4.1.1.2 Home Page




User
Nessage
Blog
Search to buy item
Post to sell item
Photo
videos
Profile
Logout
Search friends
Friend List
Accept/Reject Friend Request
Add HomePage Photo
Send Email To Add Friend
Larkut.com
Page 12

4.1.1.3 Wall Page




4.1.1.4 Blog Page


4.1.1.5 Profile Page



User
Delete message from own wall
Reply to Nessage
User
Add/Delete comment on blog post
Add/Nodify/Delete Post to blog
User
Add/Nodify/delete profile info
Larkut.com
Page 13

4.1.1. Search Friend Page

4.1.1.7 Friend List Page


User
Cet List of Searched Friend
Add friend
Write message on friends wall
Delete own message from friendrs wall
User
Write message on friends wall
Delete own message from friendrs wall
Delete friends
Add/Delete comment on blog post
view Profile !nfo
Larkut.com
Page 14

4.1.1.8 Buy Item Page

4.1.1.9 Sell Item Page

4.1.1.1 Photo Page



4.1.1.11 'ideo Page



User
Search to buy item
Add/Delete Comment on Searched !tem
User
Add !tem Details
Nodify !tem Details
Delete !tem Details
User
Add/Delete photo
User
Add/Delete video Link
Larkut.com
Page 15

.1. Sequence Diagram
4.1.2.1 'alidate User





lt
Opt
Opt
User Login !nterface Larkut Controler
User Table
1 : Enter Login Details()
2 : Submit()
3 : Check Login !nfo()
4 : Redirect to Home Page()
S : Display Error Nessage()
6 : Enter Registration Details()
7 : Submit()
8 : Save Data()
3 : Send Email To Confirm Registration()
10 : Confirm Registration()
11 : Save Data of Confirmation()
12 : Request for Forget Password()
13 : Submit()
14 : Cet Password()
1S : Post Password()
16 : Send Email with Password !nfo()
Larkut.com
Page 1

4.1.2.2 Home

Opt
User Home !nterface Larkut Controler User Table Friend Table Email Controler
1 : click on Edit Profile()
2 : Submit()
3 : Redirect to profile Page()
4 : Click On Wall()
S : Submit()
6 : Redirect to Wall Page()
7 : Click on Blog()
8 : Submit()
3 : Redirect to Blog Page()
10 : Click on Search to buy !tem()
11 : Submit()
12 : Redirect to Buy Page()
13 : Click on Post to Sell !tem()
14 : Submit()
1S : Redirect To Sell Page()
16 : Click On Photo()
17 : Submit()
18 : Redirect to Photo Page()
13 : Click on video Page()
20 : Submit()
21 : Redirect to video Page()
22 : Click on Nanage Friend List()
23 : Submit()
24 : Redirect to FriendList Page()
2S : Click on Search friend()
26 : Submit()
27 : Redirect to Search Frend Page()
28 : Click on ccept Friend Request()
23 : Submit()
30 : Update()
31 : Update()
32 : Click on Reject Friend Request()
33 : Submit()
34 : Update()
3S : Send Email To dd Friend()
36 : Submit()
37 : Submit()
38 : Update()
33 : Update()
40 : Click On Logout()
41 : Submit()
42 : Redirect to Login Page()
Larkut.com
Page 17

4.1.2.3 Wall

4.1.2.4 Blog


Opt
User
Nessage !nterface
Larkut Controler Wall Table
1 : Display Nessage()
2 : Enter Nessage to Reply()
3 : Submit()
4 : Save()
S : Delete Nessage()
6 : Submt()
7 : Delete()
Opt
User Blog !nterface Friends Blog !nterface Larkut Controler Blog Table BlogComment Table
1 : Enter Blog Post()
2 : Submt()
3 : Save()
4 : Delete Blog Request()
S : Submit()
6 : Delete()
7 : Nodify Blog Request()
8 : Submit()
3 : Nodify()
10 : dd Comment()
11 : Submit()
12 : Svae()
13 : Delete Comment()
14 : Submit()
1S : Delete()
Larkut.com
Page 18


4.1.2.5 Profile

4.1.2. Search Friends

User Profile !nterface
Larkut Controler
UserTable ddress Country
1 : Nodify Profile info()
2 : Submit()
3 : Update()
4 : Update()
S : Update()
lt
Opt
User HomePage !nterface
Search Friend List !nterface Larkut Controler User Table Friend Table
1 : Enter Friend Name in search Box()
2 : Submit()
3 : Cet List of Corresponding Names()
4 : Display List()
S : Display Blank Page with message()
6 : Click on Friend link()
7 : Click on add Button()
8 : Submit()
3 : Save()
10 : Save()
Larkut.com
Page 19

4.1.2.7 Friend List

Opt
User Friend List !nterfase Friends Profile !nterface Larkut Controler Friend Table Nessage !nterface Blog !nterface Wall Table BlogComment Table
1 : Display Friend List()
2 : Select Friend to Delete()
3 : Submit()
4 : Delete Friend()
S : Click on some Friend Link()
6 : Submit()
7 : Display Friend Profile()
8 : Click on Wall()
3 : Submit()
10 : Display Wall Nessages()
11 : Write and send Nessage()
12 : Submit()
13 : Save()
14 : Select own message to delete()
1S : Submit()
16 : Delete()
17 : Click on Blog()
18 : Submit()
13 : Display Blog()
20 : Write Comment to Blog()
21 : Submit()
22 : Save()
23 : Select own blog comment to delete()
24 : Submit()
2S : Delete()
Larkut.com
Page 2

4.1.2.8 Buy Item

Opt
User SearchToBuy !nterface
Larkut !nterface
ProductList !nterface Product Table Product Cimment Table
1 : Enter !tem Name to Buy()
2 : Submit()
3 : Cet Data()
4 : Display !tem To Sell()
S : dd Comment()
6 : Submit()
7 : Save()
8 : Delete Own Comment()
3 : Submit()
10 : Delete()
Larkut.com
Page 21

4.1.2.9 Sell Item

Opt
User
Product !nterface
ProductList !nterface Larkut Controler
Product Table
1 : dd !tem !nfo()
2 : Submit()
3 : Save()
4 : Select Own Product to Nodify()
S : Submit()
6 : Display !tem !nfo()
7 : Nodify !tem !nfo()
8 : Submit()
3 : Update()
10 : Select Own Product to Delete()
11 : Submit()
12 : Display Product !nfo()
13 : Delete !tem()
14 : Submit()
1S : Delete()
Larkut.com
Page 22

4.1.2.1 Photo

Opt
User
Photo Table
Larkut Controler
Photo !nterface
1 : Display List of photo()
2 : Browse and Select Photo()
3 : Submit dd Request()
4 : Save()
S : Delete Request()
6 : Submit()
7 : Delete()
Larkut.com
Page 23

4.1.2.11 'ideo

Opt
User video !nterface
Larkut Controler video Table
1 : Display video list()
2 : browse video from You tube()
3 : Submit dd Request()
4 : Save()
S : Request to Delete video()
6 : Submit()
7 : Delete()
Larkut.com
Page 24


. Database #elationship





. Programmer`s Point of View

%he earlier section covers the schema oI the project with the design oI the tables being created.
For all pages we are going to use JSP as Irontend and MySQL as backend.

Login Pag0:
We are going to veriIy the login credentials Irom user table. II user enters valid inIormation he/she will get
logged in and home page will get displayed. II person is new user he will select register page option.

Larkut.com
Page 25

%his 5,0 will take basic user details and aIter checking all the values (eg. Empty values, Invalid Password
etc.) It will insert all the values in the register table. AIter successIul inserts, user will get directed to login
page.

Hom0 Pag0:
On the home page, we will have Iriends list displayed in html table on the right side oI page and all these
values will be retrieved Irom Iriends table. %his page will also have links to pages like videos, blogs etc. %he
middle part oI home page will have entries displayed Irom user table.

Edit 5rofi0 5ag0:
Once the user has logged on, he can change the proIile details by using the edit proIile page. When the user
reaches this page, data will be obtained Irom the user table and displayed in the respective text boxes. %he
user could change these details iI he wishes to do so. AIter he Iinishes editing the details he can click the
update button. When this button is clicked the new details will be updated in the user table. %hese new
details will be selected Irom the user table during Iuture reIerences.

Vid0o Pag0:
For video page we are going to use You%ube API. We will have search video option. AIter searching the
videos, option will be provided to user Ior adding the video to his/her proIile. For this Iunctionality will add
the Embed` details Ior that video will get added to video tables. All the proIile videos will get displayed on
the right hand side oI the page.

Photo Pag0:
On the image page we will have browse button. User will select the image Iile Irom his local machine and
click on add Image. AIter adding the image, the image will be stored in the images Iolder on the server. And
the URL oI that image will be stored in the images tables. Below the browse button, all the images added Ior
the current user will get displayed Irom images table.

S0 5ag0:
%his page will allow the user to add the image oI the product he wishes to. %he uploaded image would be
stored on the server and the image link would be saved in the table. Along with the product image the
description oI the product and the start price is entered in the table. %he page would also have the option oI
adding more products iI the user wishes to. In this scenario the entries would be added in the table. II the
user wishes to see all the items which are up Ior sale, the user can click on the link 'List oI All Items .All
the inIormation about the products would be retrieved Irom the product table.

Buy Pag0:
%his page shows the InterIace through which the user can Bid Ior the products available Ior the user. %his
page requires some validations like Ior example, the product owner must provide with an initial price. User
who wants to buy product can comment on the product detail page and contact the owner.

Bogging Pag0:
%he blogging page would give you create new blog post Iorm. %he user will enter the title oI the blog post
and the contents oI the blog post in the respective text boxes. AIter entering the user will click the create
button. When the create button is clicked the title oI the blog post and the contents oI the blog post will be
saved in the blog table. All previously stored blog posts will be retrieved Irom the blog table and displayed
below to create new blog Iorm.

You might also like