srs panakja

8/2/2019 SRS Panakja

1/12

~ 1 ~

SOFTWARE REQUIREMENTSSPECIFICATIONFOR

ONLINE OFFICEAUTOMATION

NIIT LTD

Residency Road, Bangalore

Guided By : - Prepared By : -

Vamsi Priya Pankaj Kr. Dhir

Faculty of NIIT LTD. Amrita Mishra

Sanjeev Sir Sahul Faisal

Project manager Lohit

(Aproksha)


2/12

~ 2 ~

TABLE OF CONTENTS:-

1.INTRODUCTION1.1 Purpose.. 3

1.2 Scope.. 3

1.3 References..... 3

1.4 Overview... 4

2.OVERALL DESCRIPTION

2.1 Product Perspective... 4

2.2 Operations.. 4

2.3 User Characteristics... 4

2.4 Constraints. 5

3.SPECIFIC REQUIREMENTS

3.1 Functional Requirements.. 8

3.2Nonfunctional Requirements 9

3.3System Requirements.... 9


3/12

~ 3 ~

INTRODUCTION

1.1PURPOSE

SRS of Office Automation Web Application is designed to allow a quick and easy set personal andcorporate office in one, both for the individual user's needs, but also to meet the needs of corporateusers of office. This document specifies all employee of the office according to the modern era ofsoftware evolution. This SRS describes all the scope, specification, attributes, functionalities,requirements and capabilities of this project.

SCOPE

Manage Employee details Attendance maintain Send Mail to HR Feedback facility. Regular updates. 24x7 availability. Advertisement space.1.3REFERENCES

IEEE SRS Format

1.4OVERVIEW

This document gives you overall view of the office automation, design constraints,requirements, assumptions and dependencies and system attributes.


4/12

~ 4 ~

2.THE OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

Office Automation system is aimed towards the company who want tomanage their employee and common people who can be potential customer. Itshould be user-friendly, quick to learn and reliable software for the abovepurpose. It is intended to be a stand-alone product and should not depend onthe availability of other software. It should run on any operating system.

2.2OPERATIONS

User: Company Employee

Functions: The Mall Administrator is the super user and has complete controlover all the activities that can be performed. The administrator also managesthe list of available product categories. The administrator can also view anddelete entries in the guestbook.

User: Mall Customer/GuestsFunctions: A Mall Customer can browse through the shops and chooseproducts to place in a virtual shopping cart. The shopping cart details can beviewed and items can be removed from the cart. To proceed with thepurchase, the customer is prompted to login. The person can also change hislogin id or password.The customer can also view the status of any previousorders, and cancel any order that has not been shipped yet.

2.3USER CHARACTERISTICS

The user should be employee of that company. The user should be familiar with the Internet.

2.4 CONSTRAINTS There is no maintainability of back up so availability will get affected. Limited to HTTP/HTTPS. No multilingual support


5/12

~ 5 ~

3.SPECIFIC REQUIREMENTS

3.1FUNCTIONAL REQUIREMENT

R1: REQUIREMENT OF ADMINISTRATOR

R1.1 admin account

Input: login id and passwordOutput: provide functionality to admin

Description: This is for new admin of site. Ask to admin to enter name andpassword to open the new account.

R1.2 Employees Details

Input: insert employee id, name and its features

Output: overall description of the product

Description: admin can see the entire employee by entering product id

R1.3 update information

R1.3.1 update details & prize of products.

Input: info of product

Output: product details

Description: admin can update products and prize

R1.3.2 updates details of employee

Input: member id and/or name

Output: member details


6/12

~ 6 ~

Description: admin can also update member information

R1.3.3 updates details of admin

Input: admin id

Output: admin details

Description: admin can also change details

R1.3.4 updates invoice & transaction

Input: transaction id

Description: admin updates invoice and also transaction

R1.4 print invoice & report

Input: shopping cart details

Output: print bill

Description: enter shopping cart details and according to that print bill

R1.5 declare new offers

Input: product id and/or name

Output: display new offers

Description: admin can also put new product offers for customer

R 1.6 provides safely shopping

R 1.7 transaction facilities and transaction

Input: transaction id


7/12

~ 7 ~

Output: admin manage transaction

Description: admin uses transaction facilities

R 1.8 product searching techniques

R 1.8.1 using product name and models

Input: product name

Output: required products will be displayed

Description: admin can search products according to productname/models

R 1.8.2 using prize ranges

Input: product prize

Output: required products will be displayed

Description: admin can search products according to prize

R 1.9 change password

Input: enter new password

Output: password changed

Description: admin can also change password by entering old password thennew password

R 1.10 manages shipping costs.

Description: admin handle all shopping cart functionality


8/12

~ 8 ~

R2: REQUIREMENTS OF CUSTOMERS

R2.1 searching different products.

Input: enter name/id of product

Output: product

Description: This is for new user of site. Ask to user to enter name andpassword to open the new account.

R2.2 searching different products.

Input: enter name/id of product

Output: product

Description: customer can product by different ways by entering productname/id

R2.3 View shopping history

Input: shopping id

Output: shopping details

Description: customer can see history by entering shopping id

R2.4 Receive invoice

Description: customer can also get invoice

R2.5 different techniques for payments.

R2.5.1 credit card

R2.5.2 vpp (value paid parcel)


9/12

~ 9 ~

Description: customer can pay by different ways

R2.6 shopping carts.

R2.6.1customer can buy multiple products

Description: customer can add multiple items in cart

R2.7 cancelling order.

Input: customer id and product idOutput: order cancel

Description: customer can cancel order by entering customer id and productid

3.2NON FUNCTIONAL REQUIREMENTS

24 X 7 availability The system can be viewed by Microsoft Internet Explorer. Advertisement space where it will effectively catch the customers

attention and as a source of revenue.

Dynamic price model by which prices can be changed based on demandand supply.

3.3SOFTWARE SYSTEMREQUIREMENTS

These aresoftware system attributes known as non-functional requirements orquality attributes.

These are characteristics the system must possess. These requirements have tobe testable just like the functional requirements.


10/12

~ 10 ~

3.3.1RELIABILITY

It runs in any web browsers.

It runs in all operating system.

3.3.2 AVAILABILITY

Systems have to run 24/7. The system shall have an availability of 99.99%. The system shall allow users to restart the application after failure with

minimum

Loss.

3.3.3SECURITY

Specify the factors that would protect the software from accidental ormalicious

Access, use, modification, destruction, or disclosure. Utilize certain cryptographic techniques Keep specific log or history data sets Restrict communications between some areas of the program Check data integrity for critical variables

3.3.4MAINTAINABILITY

The system shall utilize interchangeable plug ins.


11/12

~ 11 ~

The system shall be easily updatable for fixes and patches.

The system shall create logs of all changes, updates, or fixes that aredone to the site.

The system shall be easy to upgrade.

3.3.5EFFICIENCY

The system shall perform searches via shortest path algorithm. For returning customers, the system shall validate 'existing' credit card

in system after each log in.

The system shall automatically compress image files that are too large insize.

The system will employ on demand asynchronous loading for fasterexecution of pages.

The system shall validate email address existence.

3.3.6USABILITY

The system shall be easy to use The system shall be easy to learn The system shall utilize help bubbles to assist managers, customers, and administrators The system shall employ easy to locate buttons The system shall prompt customer with friend easy to read error

messages

The system shall utilize consistent symbols and colors for clearnotifications.


12/12

3.3.7 PORTABILITYIt runs anywhere. Anytime and anywhere we can use it.

srs panakja

Documents