pixelworld srs

7/29/2019 PixelWorld SRS

1/26

PixelWorldA project work being carried out at

Adroit Infoactive Pvt Ltd.

Software Requirement

Specification

Submitted by

Kiran N (Reg. No: 100919069)

Under the guidance of

Mr. SSS Shameem Mr Satyabrat MishraAsst. Professor IT Manager

Department of M C A Adroit Infoactive Pvt Ltd.,M.I.T, Manipal 576 104 Palace Colony Basheerbagh,

Hyderabad-500 063

January 2013


2/26

Contents

1 Introduction 1

1.1 Document Purpose . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Product Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.3 Intended Audience and Document Overview . . . . . . . . . . 2

1.4 Definitions, Acronyms and Abbreviations . . . . . . . . . . . . 2

1.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Overall Description 4

2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 Product Functionality . . . . . . . . . . . . . . . . . . . . . . 4

2.3 Users and Characteristics . . . . . . . . . . . . . . . . . . . . . 7

2.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . 7

2.5 Design and Implementation Constraints . . . . . . . . . . . . . 9

2.6 User Documentation . . . . . . . . . . . . . . . . . . . . . . . 9

2.7 Assumptions and Dependencies . . . . . . . . . . . . . . . . . 9

3 Specific Requirements 11

3.1 External Interface Requirements . . . . . . . . . . . . . . . . . 11

3.2 Functional Requirements . . . . . . . . . . . . . . . . . . . . . 15

3.3 Behaviour Requirements . . . . . . . . . . . . . . . . . . . . . 17

i


3/26

PixelWorld

4 Other Non-Functional Requirements 20

4.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . 20

4.2 Safety and Security requirements . . . . . . . . . . . . . . . . 21

4.3 Software Quality Attribute . . . . . . . . . . . . . . . . . . . . 21

Bibliography i

Department of M.C.A ii M.I.T, Manipal


4/26

Chapter 1

Introduction

This document is meant to delineate the features of PixelWorld - A place for

buying best photographs, so as to serve as a guide to the developers on one

hand and a software validation document for the prospective client on the

other. The Online Shopping System for photograph gallery web application

is intended to provide complete solutions for vendors as well as customers

through a single get way using the internet. It will enable vendors to sell their

photographs online, customer to browse through the gallery and download

them online. The administration module will be able upload the photographs,

approve and reject requests for new vendors and maintain various lists of

photographs category.

1.1 Document Purpose

Defining and describing the functions and specifications of the pixelworld is the

primary goal of this Software Requirements Specification (SRS). This Software

Requirements Specification illustrates, in clear terms, the systems primary use

and required functionality as specified by our customer.

1


5/26

PixelWorld

1.2 Product Scope

Initial functional requirements will be: -

Secure registration and profile management facilities for Customers.

Browsing through the e-gallery to see the photographs that are there in

each categories like landscape, potrait, wedding, wildlife, etc.

Adequate searching mechanisms for easy and quick access to particular

photograph.

Creating a lightbox(wishlist) for downloading the photographs over the

internet.

1.3 Intended Audience and Document Overview

Describe the different types of reader that the document is intended for, such

as developers, project managers, marketing staff, users, testers, and documen-

tation writers. Suggest a sequence for reading the document, beginning with

the overview sections and proceeding through the sections that are most per-

tinent to each reader type. Uploading Most Popular photographs in each

category of photographs.

1.4 Definitions, Acronyms and Abbreviations

GUI- Graphical User Interface

HTTP: Hypertext Transfer Protocol is a transaction oriented client/server

between a web browser and a Web Server.

Department of M.C.A 2 M.I.T, Manipal


6/26

PixelWorld

HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure

socket layer).

OSS- Online shopping System (for photograph shop)

SRS- Software Requirement Specification

Stockholder- The person who will participate in system Ex. Vendor,

Administrator, Subscribers/customers, etc.

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of

communication protocols used to connect hosts on the Internet. TCP/IP

uses several protocols, the two main ones being TCP and IP.

1.5 References

IEEE SRS Format



7/26

Chapter 2

Overall Description

2.1 Product Perspective

PixelWorld is a online photo gallery which supports number of functions for

both consumer and administrator management. This website must be com-

pletely independent and dynamic available to anyone who are connected to

internet. Only the admin is allowed to manage all the vendors, photos and

subscription plans.

2.2 Product Functionality

PixelWorld will provide a number of functions, each is listed below.

Maintain data associated with photos

A photograph has a code, image of 3 different sizes, a value related

to each size and the copyrights.

Each photographs can be categorised into several categories like

landscape, potrait, wildlife, etc.

The record of photograph downloaded.

4


8/26

PixelWorld

Maintain packages available for subscription

Each Subscription packages has a name(unique) and Status which

specifies whether its available for subscription or not.

Above packages will have a several plans containing charges(price),

validity and points.

Maintain records for many customers

Customer are the subscribed members categorised based on their

subscription plans.

A customer has a username(unique across all users), password(no

restrictions), address(no restrictions) and a postal address(unverified).

Anyone can subscribe for customer account.

Maintain records for several suppliers

Supplier record is created by admin.

Supplier are categorised to contract basis supplier, personally hired,

photographers, etc...

Each supplier has a username(unique accross all suppliers), pass-

word(no restrictions).

Supplier can upload photos and can view download summary report

of the photos uploaded.

Gallery

Shows all the available photos in the gallery.

Photos can also display based on the selected category.

Option is available to download the photo and to add it to lightbox.



9/26

PixelWorld

Available sizes of the photos for downloading is also displayed.

Allow users and suppliers to login and logout of the system.

Users and suppliers should be logged out if inactive for 15mins.

Lightbox(wishlist)

Lightbox is only available to logged-in customers. A user that is

not logged in as a customer is given a chance to log in.

Provide Personalized profile

Provide a download history of downloaded photographs of a mem-

ber user.

Provide Customer Support

Provides online help, FAQs customer support, and site-map options

for customer support.

Provides Search Facility

Users can be able to enter search text on the screen, select multi-

ple search option on the screen to search, display all the matching

results on the current screen

Offer online promotions and rewards

The website shall display all the available promotions to the users.

And should allow users to select the available promotion.

Administrator

Can upload photos.



10/26

PixelWorld

Can add/update categories, subscription packages and plans.

Can to manage all the vendor records.

Data Flow Diagram

The purpose of this diagram is to show how the data will flow

inside the system.

Fig 2.1 shows the Data flow in the system.

2.3 Users and Characteristics

Admin, member/non-member user and supplier are the various

kind of users who has access to the internet to use this system.

Non-member user is simply anyone who has access to the internet

and the browser. Member user is a person who has subscribedSupplier is a photographer who uploads the photos to the sys-

tem. Admin is a employee of the company, who has authority to

manage all the objects related to the photographs.

2.4 Operating Environment

The website needs to be designed in a user-friendly manner to

ensure its competiveness and effectiveness. Internet connection

is required to access this website and a browser which supports

the javascript. A server with a constant internet connection is



11/26

PixelWorld

Figure 2.1: PixelWorld Data Flow Diagram



12/26

PixelWorld

required for the availability of the website.

2.5 Design and Implementation Constraints

Security for photographs is the main constraint and authorization

for the management pages is required. Password shouldnt be

stored as plain text in the database.

2.6 User Documentation

List the user documentation components (such as user manuals,

on-line help, and tutorials) that will be delivered along with the

software. Identify any known user documentation delivery for-

mats or standards. TO DO: You will not actually develop any

user-manuals, but you need to describe what kind of manuals and

what kind of help is needed for the software you will be develop-

ing. One paragraph should be sufficient for this section.

2.7 Assumptions and Dependencies

Client:

We have assumed that the users computer system is in proper

working condition with internet connection and that the user is

capable of operating the systems basic functions like operating



13/26

PixelWorld

computer, browsing to the address of pixelworld website.

Provider:

We have assumed that the PixelWorld will be running on a

properly working web server and database system with an Inter-

net connection that allows this system to perform all communi-

cations with clients.

Assumptions:

The admin cannot be a user/supplier.

The supplier can only be able upload photos and view the

download report.

The admin cannot edit the member information.

The freely subscribed user cannot be able to download pho-

tos.



14/26

Chapter 3

Specific Requirements

3.1 External Interface Requirements

3.1.1 User Interfaces

1. Login Page: Fig 3.1 shows template format of the login page.

2. Registration/Subscription Plans: Fig 3.2 shows the template

of subsciption page.

3. Personal Details: Fig 3.3 show the template of the Personal

Details page used during registration.

4. Gallery Page: Fig 3.4 shows the template of the gallery page.

5. Lightbox/Wishlist: Fig 3.5 shows the template of the wish-

list page.

6. Administrator Page: Fig 3.6 shows the template for the ad-

ministrator/vendor page

11


15/26

PixelWorld

Figure 3.1: Login Page

Figure 3.2: Subscription Plans



16/26

PixelWorld

Figure 3.3: Personal Information

Figure 3.4: Photo Gallery Page



17/26

PixelWorld

Figure 3.5: Lightbox/Wishlist

Figure 3.6: PixelWorld Administrator



18/26

PixelWorld

3.1.2 Hardware Interafaces

The System must run over the internet, hence all the hardware

shall require to connect internet will be hardware interface for the

system. As for e.g. Modem, WAN LAN, Ethernet Cross-Cable.

3.1.3 Software Interfaces

The system is on server so it requires the any scripting language

like PHP. The system require Data Base also for the store the any

transaction of the system like MYSQL etc. system also require

DNS(name space) for the naming on the internet. At the last

user need web browser for domain interact with the system.

3.1.4 Communication Interfaces

HTTP/HTTPS

TCP/IP

3.2 Functional Requirements

Login Function:

In this function the username and password of the user is

verified with the database.



19/26

PixelWorld

User registration:

This module deals with the registration of users

Input:

The user should first select the subscription plan and must

enter all the details related to him like name, email, address,

etc.. And has to make an online payment for selected sub-

scripion plan. Output:

A email containing the password is sent to the email-id pro-

vided during registration.

Photo Lightbox:

A option is provided for adding the photo into the lightbox.

If the user who selected this option is not a member then he

is redirected to the subscribe/registration page.

Photo Download:

When user tries to download the photo two function are

done viz. Check whether the user still has required number

of points for downloading the photo. If yes then photo is

downloaded on to his local harddisk, if not then the user is

redirected to the subscription plan page for subscribing.

Photo Category Display:

In this function all the main categories of photo are dis-



20/26

PixelWorld

played. From this point user can select any category and

they can proceed to select the view/download photos in this

category.

Photo search: This function shows all the photos under

the search criteria. If there are no photos under these search

criteria then system will give the message that there are no

photos found under this category. If there are photos under

ther search criteria photos are displayed.

Venor Membership Request:

The user has to submit his email-id, contact details and a

message requesting for the vendor membership.

3.3 Behaviour Requirements

Fig 3.1 shows the state diagram and all the actors in participate

in the system.

User

Are the registered members who are subscribed with the

application.

Payment Processor

Is a 3rd party system which provides a payment gateway.



21/26

PixelWorld

Customer Support

Are the employees of the company who resolves the problems

of customers.

Vedor

Are the photographers who uploads the photos.

Admin

Are the application administrator, who creates the vendor

records and also uploads the photos and manage all the other

functions of the website.



22/26

PixelWorld

heightheight

Figure 3.7: PixelWorld State Diagram



23/26

Chapter 4

Other Non-Functional

Requirements

4.1 Performance Requirements

If there are performance requirements for the product under var-

ious circumstances, state them here and explain. Make such re-

quirements as specific as possible. You may need to state perfor-

mance requirements for individual functional requirements or fea-

tures. TODO: Provide different performance requirements based

on the information you collected from the client. For example you

can say 1. Any transaction will not take more than 10 seconds,

etc...

20


24/26

PixelWorld

4.2 Safety and Security requirements

The system uses SSL (secured socket layer) in all transac-

tions that include any confidential customer information.

The system must automatically log out all customers after

a period of inactivity.

The system should not leave any cookies/session variables

on the customers computer containing the users password.

The systems back-end servers shall only be accessible to

authenticated administrators.

Sensitive data will be encrypted before being sent over inse-

cure connections like the internet.

4.3 Software Quality Attribute

4.3.1 Availability

The system should be available at all times, meaning the user can

access it using a web browser, only restricted by the down time of

the server on which the system runs. In case of a of a hardware

failure or database corruption, a replacement page will be shown.

Also in case of a hardware failure or database corruption, backups

of the database should be retrieved from the server and saved by



25/26

PixelWorld

the administrator. Then the service will be restarted. It means

24 X 7 availability.

4.3.2 Maintainability

A commercial database is used for maintaining the database and

the application server takes care of the site. In case of a failure,

a re-initialization of the program will be done. Also the software

design is being done with modularity in mind so that maintain-

ability can be done efficiently.

4.3.3 Portability

The application is HTML and scripting language based. So The

end-user part is fully portable and any system using any web

browser should be able to use the features of the system, including

any hardware platform that is available or will be available in the

future.

An end-user is use this system on any OS; either it is Windows

or Linux.

The system shall run on PC and Laptops. l



26/26

Bibliography

[1] Tim Converse, PHP5 and MySql Bible, Wiley Publications

Inc..

[2] PHP, www.w3school.com

[3] PHP PDO, http://php.net/manual/en/index.php

i

pixelworld srs

Documents