REALLY NEW

8/7/2019 REALLY NEW

1/14

SRS Template As on 31/1/2003

Internal Use Only i

8/7/2019 REALLY NEW

2/14

PRAVEEN ELECTRONICS PVT LTD

kERALA

web applications

Software Requirements SpecificationsVersion 1.0

03/2011

8/7/2019 REALLY NEW

3/14

WarningThis is a hard copy of a document maintained on electronic media. It may not be the latestversion. Kindly ascertain the latest version from the Document Master List available with the

Project Leader .

8/7/2019 REALLY NEW

4/14

Web World Software Requirements Specifications ver. 1.0

DOCUMENT RELEASE NOTICE

Document Details:

Name Version No. DescriptionSoftware RequirementsSpecifications

1.0 SRS document for WebWorld of Domain WOrld

Revision Details

Action taken(Add/Del/Change)

Preceding Page No. New Page No. RevisionDescription

This document and any revised pages are subject to document control. Please keep them up-to-date using the release notices from the distributor of the document.

Approved by: Date:

Authorised by: Date:

Internal Use Only i

8/7/2019 REALLY NEW

5/14


PREFACE

Purpose of this Document

This document describes the System Requirements Specifications of the web application .This document lays down the software requirements for the application that have beencaptured through a detailed study of the business workflow and functions .

Intended Audience

This document is intended for use by the designers of the system, and for those who may berequired to maintain it. The document will enable them to understand all aspects of thesystem in detail. It will enable the praveen electronics pvt ltd to know that TCS has

captured all the requirements. The document will also be used by praveen electronics pvtltd for carrying out the acceptance testing for which it will form the.

Related Documents / References

The following documents have been referred to for the preparation of this SRS document:

1. Technical Proposal for the study2. Contract and associated relevant document

Acronyms and Abbreviations

Abbreviation/Acronym Description

Organization of this Document

This document consists of sections and appendices.

Section 1Section 2

Internal Use Only ii

8/7/2019 REALLY NEW

6/14


TABLE OF CONTENTS

1. INTRODUCTION..................................................................................................................1

1.1 B ACKGROUND .......................................................................................................................11.2 S COPE ...............................................................................................................................11.3 K EY ASSUMPTIONS , D EPENDENCIES , C ONSTRAINTS AND OVERRIDING P RIORITIES .................................11.4 S ITE ADAPTATION .................................................................................................................21.5 A PPLICATION S ECURITY ..........................................................................................................21.6 M IGRATION REQUIREMENTS ....................................................................................................2

2. FUNCTIONAL REQUIREMENTS.........................................................................................3

2.1 S ELECTING THE SERVICE :........................................................................................................32.2 L ISTING THE COST OF SERVICE :.................................................................................................3

3. USER INTERFACE SPECIFICATIONS................................................................................4

............................................................................................................................................4

4. OTHER REQUIREMENTS....................................................................................................5

4.1 G ENERIC REQUIREMENTS ........................................................................................................54.2 U SER ACCESS CONTROL AND S ECURITY ....................................................................................54.3 A RCHIVING AND HOUSEKEEPING ................................................................................................54.4 P ERFORMANCE REQUIREMENTS ................................................................................................6

5. APPENDIX A: ANALYSIS OBJECT MODEL......................................................................7

6. GLOSSARY OF TERMS......................................................................................................8

Internal Use Only iii

8/7/2019 REALLY NEW

7/14


1. Introduction

1.1 BackgroundThis document outlines the software requirement specification for the Web ApplicationSystem. It is the outcome of the Analysis Phase during which discussions were held with theusers. The objective of this Analysis Phase was to:

Define the scope for the web application Serve as the baseline for the design of the web application

Any changes to requirements after acceptance of this document will be through appropriateChange Management procedure, as detailed in the contract.

Both the user and designer should go through the document carefully in order to ensure that : All the user requirements which need to be supported by the system have been identified

and detailed. The document is a clear and unambiguous statement of functionality required from the

system for the design and development team. The document can be used as a basis for development of the System Test data.

It is essential to identify the problems, if any, with the basic structure of the proposed systemat this stage. If these are not taken care of at this stage, it may be difficult to incorporate thedesired modifications to overcome the shortcomings at a later stage.

Client details: praveen electronics pvt ltd ,ambattur chennai,

project details: package deals

1.2 Scopecreation of web application , the scope of this project is corporate and regoinal

provided for regional and corporate levels.No areas that are excluded from this service.Industrial websites,social networking sites,company websitesGlobal as well as localweb services,under which web design , web application,web redesign and content

development are the sub services provided. It also providesdesign services under which logo design, illustrations, corporate profile ,brochuredesign

1.3 Key Assumptions, Dependencies, Constraints andOverriding Priorities

The successful execution of the assignment will depend on the following factors

AssumptionsInternet connection should be always available

Internal Use Only 1

8/7/2019 REALLY NEW

8/14


Dependencies Availability of System Software from the client for development. Availability of installed hardware/System software for implementation. Feedback on this report will be provided as per the agreemnent in the contract. Any delay

in the feedback will have impact on the schedule and cost of the project.

Constraints

None

1.4 Site AdaptationNot applicable

1.5 Application SecurityNot applicable

1.6 Migration RequirementsNot applicable

Internal Use Only 2

8/7/2019 REALLY NEW

9/14


2. Functional Requirements

2.1 Selecting the service:The customers can find the various services provided by the company listed out.The services can be selected by the customer.

2.2 Listing the cost of service:The e-quote for a service is sent to the customer.The cost of service consists of the three packages available to the customer.

1.1 Accepting the service: The customer can select the required service.

The customer can also introduce a buddy and avail discount for further consignments.

Internal Use Only 3

8/7/2019 REALLY NEW

10/14


3. User Interface Specifications

< External Interface Specifications

Internal Use Only 4

8/7/2019 REALLY NEW

11/14


4. Other Requirements

4.1 Generic Requirements

4.2 User Access Control and Security

4.3 Archiving and Housekeeping

8/7/2019 REALLY NEW

12/14


4.4 Performance Requirements

Internal Use Only 6

8/7/2019 REALLY NEW

13/14


5. Appendix A: Analysis Object Model

AOM will be done using a tool supporting UML notation, like Rational Rose.

Internal Use Only 7

8/7/2019 REALLY NEW

14/14


6. Glossary of Terms

Internal Use Only 8