Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

Online Catalog V1.2

Software Requirements Specification Document

For

By

Netsmartz, LLC

Page 1 of 13

Netsmartz LLC Title: Software Requirements Specification REVISION HISTORY

Doc. No: Version No.: 2.0

Date Nov. 26

Author

Change Details Added New points suggested by Shalom. Added Section 1.10 (H) Updated section 2.1.1.3 Updated 2.1.1.5 Case 3 added in 2.1.2.1 Note updated in 2.1.2.3 Browser Compatibility updated in section 1.7 and 3.3

Reference as Email from XXXX as on Nov 26

Nov 29

Updated section 1.7 for Sql Email from XXXX as on Server 2005 compatability Nov 28 Updated section 2.1.1.6 for admin right to override payment

Page 2 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

Table of Content
1 Introduction....................................................................................................4 1.1 Application Overview, Scope & Objectives........................................................4 1.2 Application Objectives....................................................................................4 1.3 Need for the Application.................................................................................4 1.4 Purpose of the Document...............................................................................4 1.5 Vision / Views of the Technology Head / Project Sponsor ..................................4 1.6 References ..................................................................................................4 1.7 Application Environment................................................................................5 1.8 Security System............................................................................................5 1.9 External Interfaces .......................................................................................6 1.10 User Interface.............................................................................................6 2 Functional Description......................................................................................7 2.1 Process/Function Description..........................................................................7 2.1.1 Administrator section .............................................................................................7 2.1.2 Publishers Section .................................................................................................8 2.1.3 Subscriber Section ...............................................................................................11 3 Issues & Concerns..........................................................................................12 3.1 Assumptions and dependencies-....................................................................12 3.2 Transaction Volumes (Current and Anticipated)-..............................................12 3.3 Design and implementation constraints-.........................................................12 3.4 Deliverables-..............................................................................................12 4 Standards.....................................................................................................12

Page 3 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

1
1.1

Introduction
Application Overview, Scope & Objectives

Online Catalog site provide online space for publishers for marketing their products and browsing features for the subscribers to analyze and provide feedback for products.
1.2 Application Objectives

1. To provide online Space per catalog for publishers for their product. 2. Browsing feature for subscriber to browse the products posted by publisher 3. To provide feature to Subscribers to list the favorite products and post the comments
1.3 Need for the Application

Online Catalog will provide the easy and user friendly web portal for product marketing and browsing the posted products.
1.4 Purpose of the Document

The purpose of this document is to lay out in detail the functional and other requirements. This document contains the necessary information to meet the requirements set forth for the completion of this application. The target audience of this document is Project Sponsor, Project Managers, Developers, Designers, and QA Engineers. Now onwards, this document will act as a portal of information during the whole development cycle and any change in the functional or other requirements will be communicated through this document.
1.5 Vision / Views of the Technology Head / Project Sponsor

Vision here is to develop a web application which establishes the client (Online Catalog) as a leading provider of the proposed system. Online Item Catalog Users Following will be the users of the Online Item Catalog website 1. Publisher(Multiple Users) 2. Subscriber(Multiple Users) 3. Administrator (Single User)
1.6 References

Netsmartz Agreement - signed.pdf

Page 4 of 13

Netsmartz LLC Title: Software Requirements Specification 1.7 Application Environment

Doc. No: Version No.: 2.0

Hardware Environment (Deployment Server)

Operating System Processor RAM HDD

Windows server 2003 Intel based 2 GHz min.(Core2Duo or Xeon) 2 GB As per DB and Files size

Software Environment (Deployment Server) Operating System Other Software Web Server Browser Windows .net 3.5, Sql Server 2005 IIS 6.0 or higher IE 7.0 or higher

Software Environment (End User) Operating System Browser Development Environment Operating System Technologies Database Windows XP .net 4.0, Ajax SQL Server 2005 Windows XP , 2000, Vista, 7 IE 7.0 or higher, Fire fox 3.0 or higher, Chrome, Safari, Opera

1.8

Security System

Many of pages will be available to any anonymous user but to perform any action, user will have to enter username and password.

Page 5 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

1.9

Data will be validated on client as well as on server before any processing starts on it. Website will run on the http. Hardware Interfaces - No non-standards hardware devices are required.

External Interfaces

1.10 User Interface General Elements: (available to anonymous user) A) Home Page:

Home page will be the main page of the website and will be displayed by default. Home page will contain the brief description about the services provided to publishers and subscribers.

Note: The Content of description of service for publisher and subscriber will be provided by client. However, CMS will be given to administrator for editing content. B) Login Page: User will be asked for username and password. After login,

authenticated user will be redirected to respected webpage according to users role. There will also be a link for forgot password.
C) Forgot Password:

There will be forgot password link with login panel, on clicking on this link the users/brokers/admin will be redirected to the forgot password page. This page will accept login name as parameters and will send password into an email to the users. us content will be managed in Admin Section under Manage CMS section.

D) About Us: About us will be static Content provided by client. However the about E) Term Of use: Term Of use will be static Content provided by client. However the

about us content will be managed in Admin Section under Manage CMS section.
F) Contact Us: There will be a panel on contact us page using which, user can

post their comments/request to the admin of website. Some text part of contact us page will be managed under Manage CMS in admin section.
G) Privacy policy: Privacy policy will be static Content provided by Admin. However the Privacy policy content will be managed in Admin Section under Manage

CMS section.
H) How It works: How It works will be static Content provided by Admin. However the How It works content will be managed in Admin Section under Manage

CMS section. There are three types of Roles for users:

Page 6 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

1. Admin: The Administrator will be able to view all the activities of the website.

Such as catalog list, publisher list and description, Subscriber list and description.
2. Publisher: The publisher account on the website is paid and payment will be

done via pay pal. Publisher will receive feedback on his products from subscribers of website.
3. Subscriber: Subscriber can browse the detail of any product available on the

website and can post his feedback. Subscriber can add products into their favorites.

2
2.1

Functional Description
Process/Function Description

The online item catalog website shall have three major sections. These sections are: Administrator Section: Publishers Section Subscribers Section The detailed description of each section is given as under:
2.1.1

Administrator section The Administrator will be able to view all the activities of the website. Such as catalog list, publisher list and description, Subscriber list and description. The administrator will not be able to add/edit/delete Products. Administrator can create users and deactivate users. Goal: Give the Administrator a bird-eye view of all activity moving through the website. These activities are listed below.

2.1.1.1 Home Page:

The goal of the Home Page is to give the user quick access to his data as it flows through the site. Such as quick links to the Manage Subscribers, Manage Publishers, Manage Catalog, Manage CMS page, Manage Payment.
2.1.1.2 Manage Subscribers:

Administrator will be able to create/edit/delete/activate/ deactivate Subscribers from their panel. Note: Admin can deactivate/reactivate users without Subscribers/Publishers knowledge or permission.

Page 7 of 13

Netsmartz LLC Title: Software Requirements Specification 2.1.1.3 Manage Publishers:

Doc. No: Version No.: 2.0

Administrator will be able to create/edit/delete/activate/ deactivate Publishers from their panel. Admin can create Publishers account on website with/without payment. He can also add free subscriptions to users.
2.1.1.4 Manage Categories:

Administrator will be able to create/edit/delete/activate/ deactivate Categories (Categories could be up to N level and will be under the catalog) from there section. If Administrator will deactivate a category, the Products under that category will not be displayed to subscribers.
2.1.1.5 Manage Catalog:

Administrator will be able to create/edit/delete/activate/ deactivate Catalogs. If Administrator will deactivate a catalog, the users under that Catalog will remain active . Ex: User1 is registered under catalog1. If Admin deactivates the Catalog1 then User1 will still remain active.
2.1.1.6 Manage Payment: Admin will manage the Payment for publishers on the website. Admin can create Publishers account on website with/without payment. He can also add free subscriptions to users. 2.1.1.7 Manage CMS: Administrator will be able to Manage CMS pages Contact us, privacy policy, FAQ, Terms of use, how it works and some part of the home page body (subscribers and publishers service description content). 2.1.2 Publishers Section

Publishers will get registered on website and can post Products under his account. The publisher account on the website is paid and payment will be done via pay pal. Publisher will receive feedback on his products from subscribers of website.

2.1.2.1 Registration Page:

This webpage will be used by user to register as publishers. User need to fill the following fields while registering as publishers: First Name* Last Name * Email Address*(User name) Textbox Textbox Textbox

Page 8 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

Password* Confirm Password* Company Name* Address1* Address2 City* State* Country* Zip Code* Phone* Fax URL Contact Email* Support Email* Product inquiry Email*

Textbox(Password mode) Textbox(Password mode) Textbox Textbox(Multiline) Textbox(Multiline) Textbox Dropdown Dropdown Textbox Textbox Textbox Textbox Textbox Textbox Textbox

User will be asked for payment by pay pal to register as publisher. After successful payment of charges for publisher registration, an email will be sent to user for registration information along with login credentials details. If the mentioned catalog already exists in the database, then user will be registered to existing catalog. However the same user cant register for same Catalog. Also user can register under one catalog only. User can invite other user under his own catalog to create a publisher account. For ex: Case 1: If user1 is registered for Catalog1, then user1 cant register under Catalog1 again. Also user1 can register under Catalog1 only. Case 2: if Catalog1 already exists in database and user2 mention Catalog1 in company name then user2 will registered under Catalog1.

Page 9 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

Case 3: User1 Can Invite User2 to access User1s catalog only. User2 can create a publishers account without the purchase of a catalog as a response to an invite email from User1.
Note: Above fields mentioned with * are mandatory. Pay pal will be used for the payment

on the website. Publisher can register to website by selecting only one catalog per registration.
2.1.2.2 Create Categories/Brands:

Publisher can add/edit the categories using this webpage under his login. Publisher need to fill following detail to post categories: Category Name Category Description Category URL Textbox Textbox (Multiline) Textbox

2.1.2.3 Post Product:

Publisher can add/edit the Products on website using this webpage. Publisher need to fill following detail to post the Product: SKU/Item Number* UPC code* Description Item Name* Image* Extended description Product dimensions URL Item category* Textbox Textbox Textbox Textbox File uploader Textbox (Multiline) Textbox Textbox Dropdown

Note: The Product image will be restricted with image dimensions and image size.

All internet formats like jpg, png, gif etc will be supported.
2.1.2.4 Change password: Publisher will be able to change his password anytime. 2.1.2.5 Edit Personal details:

Publisher will be able to update their personal details anytime.

Page 10 of 13

Netsmartz LLC Title: Software Requirements Specification 2.1.3 Subscriber Section

Doc. No: Version No.: 2.0

Subscriber is the user of website who can view the list of products under different catalogs. Subscriber can browse the detail of any product available on the website and can post his feedback.
2.1.3.1 Registration Page

Using this webpage user will be registered as Subscriber. User need to fill following detail to register as subscriber: First Name* Textbox Last Name* Textbox Address1* Textbox (multiline) Address2 Textbox (multiline) City* Textbox State* Dropdown Country* Dropdown Zip* Textbox email Address*(User name) Textbox Password* Textbox(Password mode) After successful submission of page user will registered as Subscriber and an email will be sent to mentioned email id along with login credentials. User will automatically login the website after successful registration. Note: There no charges for users to register as Subscriber. Mandatory fields are marked as *.
2.1.3.2 View Products

Subscribers can browse the list of available products. He can browse the detail of Item and can post feedback for the particular Products. Subscribers can also add the selected Products to their My favorite section.
2.1.3.3 View Product Detail This webpage will display the full detail of selected product. There will be a panel provided on this webpage using which subscriber can post the feedback. 2.1.3.4 View Subscribed products Subscribed products are those which subscriber has added in my favorite section. Subscribers can add/edit/delete the subscribed list of products. 2.1.3.5 Change password: Publisher will be able to change his password anytime.

Page 11 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

2.1.3.6 Edit Personal details: Publisher will be able to update their personal details

anytime.

3
3.1 3.2 3.3

Issues & Concerns

Assumptions and dependenciesNo assumptions. Transaction Volumes (Current and Anticipated)TBD Design and implementation constraintsBrowser Compatibility-

The website would be tested for compatibility with the following web browsers: Internet Explorer 7.0 onwards Mozilla Firefox 3.0 onwards Google Chrome Safari Opera
Design

CSS format for global control GUI should limit client side scripting unless using AJAX to meet above browser requirements. 30 minutes automatic logout. OOPS Extensive Error reporting as detailed in Web modules. OOPS Data layer which calls stored procedures which Netsmartz writes.

Middle Tier

Data Tier Netsmartz will create all stored procedures and tables 3.4 Deliverables-

The Project would have the following deliverables: FTP uploads to our server of complete source code deletion of source after delivered and accepted. Development and Project management documents One time Installation on clients server

Standards
All CMMI level 3 standards of Netsmartz will be implemented.

Page 12 of 13

Netsmartz LLC Title: Software Requirements Specification

Doc. No: Version No.: 2.0

Page 13 of 13