CASE STUDY

TUMBLR
BY:- YOGESH KUMAR
Functional Requirements

For

Tumblr

Introduction

1.1 Purpose
The purpose of this document is to present a detailed
description of Tumblr. It describes the software requirements
and specifications to Tumblr which is a microblogging and
social networking website founded by David Karp in New
York City in 2007, and is presently owned by Yahoo!
 Functional Requirements
General
Functional Requirement 1:
Administrator Menu: In this module we can do the following:

 Admin should be able to access any account according to

policies .
 Can accept or Reject an user according to the policies.
 Should be able to change or modify the application when
ever needed.
 Can make records of user.

Functional Requirement 2:
 Account Creation: In this module we create a new
account and store it.
Input: Input the user name.
Process: The process is done by the main server of tumblr.
Output: Successful creation of an account.
Functional Requirements 3:
 Search: In this module the user can search for a person,
page or a blog according to his requirement.
Input: enter the person , page or blogs name.
Process: The processing is done by the main server of
the Tumblr.
Output: The required profile of the user, page or blog.
Functional Requirement 4:
 Update: In this module the user can upload any data,
image, file or video on his interface and it is visible to
all the following users.
Process: The processing is done my Tumblr’s main
server.
Output: The users wall or profile or interface showing
the updated data.
Functional Requirement 5:
 Message: In this module the user can send any form of
data in the form of a message to any othe user on tumblr.
Process: Processing done by Tumblr’s main server.
Output: The users message is sent to another user and it
is displayed on the screen.
Functional Requirement 6:
 Inbox: In this module the user has an option to see all the
messages he has got from the other users.
Process: done by the Tumblr’s main server.
Output: It displays the messages received by the user.