QMS-MINFY-T-<Project ID>-SRS(W)

Software Requiremet! S"ecificatio

For
DeccaT#
Version No 1.1 Prepared by
Date
Name
Signature
Copy No
Approved by
Issued to
Name
Signature
$ffecti%e Date& '' Dec ()'* #er!io No+ '+) i
QMS-MINFY-T-<Project ID>-SRS(W)
Documet ,me-met Recor-
, . ,--e-/ M . Mo-ifie-/ D . De0ete-
#er!io
No+
Date Pa1e No 23a1e
Mo-e
(,4M4D)
23a1e
Reque!t
Num5er
6rief De!cri"tio of 23a1e
$ffecti%e Date& '' Dec ()'* #er!io No+ '+) ii
QMS-MINFY-T-<Project ID>-SRS(W)
Ta50e 7f 2otet!
'+) INTR7D82TI7N+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
1.1 PURPOSE................................................................................................................................
1. SCOPE..................................................................................................................................
1.! DE"INI#IONS$ ACRON%&S AND A''REVIA#IONS...................................................................................
1.( RE"ERENCES...........................................................................................................................
(+) 7#$R#I$W++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
.1 CURREN# PRODUC#...................................................................................................................
. PROPOSED S%S#E&....................................................................................................................
*+) M7D89$S 7F T:$ PR7D82T++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
;+) 7#$R#I$W 7F T:$ M7D89$S 7F T:$ PR7D82T+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
<+) S8MM,RY 7F T:$ F$,T8R$S 7F T:$ M7D89$S+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
=+) D$T,I9$D F8N2TI7N,9 R$Q8IR$M$NTS+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
>+) P,?$ T$MP9,T$++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
@+) 7P$R,TIN? $N#IR7NM$NT+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
).1 *ARD+ARE.............................................................................................................................
). SO"#+ARE..............................................................................................................................
).! NE#+OR,...............................................................................................................................
).( CO&&UNICA#ION......................................................................................................................
A+) P$RF7RM,N2$ R$Q8IR$M$NTS++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
')+) ST,ND,RDS+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
''+) SP$2I,9 8S$R R$Q8IR$M$NTS++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
'(+) 8S$R 2:,R,2T$RISTI2S++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
'*+) 7T:$RS++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++(
$ffecti%e Date& '' Dec ()'* #er!io No+ '+) iii
QMS-MINFY-T-<Project ID>-SRS(W)
'+) Itro-uctio
-In this section the introduction about the software requirements analysis phase is done to analyze customer
problem domain and produce a set of software requirements as complete, consistent and correct as possible.
These guidelines are to be used in the preparation of Software Requirements Specification (SRS-!" based#.
$ro%ect &eader will prepare the SRS based on the study and'or discussions with the customer or mar(eting.
The study team should include users, software engineers, hardware engineers, and business domain e)perts
and operations personnel. $ro%ect management should ensure that customer and all interested parties are
consulted to acquire complete information on user requirements.
'+' Pur"o!e
-In t/is sub se0tion 1rite 1/o is t/e 0ustomer and t/e purpose o2 t/e SRS t/at 1i33 be deve3oped. E45
6Purpose o2 t/is SRS is to 2orma33y de2ine and do0ument 0ustomer re7uirements to enab3e t/e deve3opment
team design and deve3op produ0t to meet t/e 0ustomer re7uirements.8
*dditionally the user problem or bac(ground to the product effort may also be discussed+
'+( Sco"e
, In this sub section, briefly describe the software - the need for it, what it will do, who it is intended for. *im
to gi-e the reader a quic( o-er-iew. !). /The scope of the SRS is to document all the functional requirements
of the customer for the product ordered.0+
'+* Defiitio!/ ,croBm! a- ,55re%iatio!
, In this sub section list all the 1efinitions, *cronyms and *bbre-iations that are used in the preparation of
SRS of the software proposed to be de-eloped+
'+; Referece!
-In this sub section pro-ide a complete list of all documents referenced elsewhere in the SRS, Identify each
document by Report no ' Title' 1ate ' 2rganization 3ame.
(+) 7%er%iew
-In this section pro-ide complete o-er-iew of the product that is de-eloped and the o-er-iew of the proposed
product respecti-ely.
(+' 2urret Pro-uct
, In this sub section pro-ide a complete o-er-iew of the product briefly along with the limitations of the
product+
(+( Pro"o!e- SB!tem
, In this sub section pro-ide a complete o-er-iew of the proposed product briefly+
*+) Mo-u0e! 7f T3e Pro-uct
,In this section identify how the product will be constructed using modular approach and list the -arious
modules of the product+
$ffecti%e Date& '' Dec ())'* #er!io No+ '+) Pa1e ' of ;
QMS-MINFY-T-<Project ID>-SRS(W)
;+) 7%er%iew 7f T3e Mo-u0e! 7f T3e Pro-uct
,In this section, list all the modules mentioning the o-er-iew of indi-idual modules in the product. 4ill up the
tabular form+
S+No Mo-u0e Name 7%er%iew 7f T3e Mo-u0e
<+) SummarB 7f T3e Feature! 7f T3e Mo-u0e!
, 4or each module, list all the functional requirements, based on the study of customer requirements or the
general mar(et requirements. 4ill in the tabular form li(e sno, module name, function no, functional
requirements of the module+
Mo-u0e <Name>
S+No Feature 2otet RemarC!
=+) Detai0e- Fuctioa0 Requiremet!
-In this section describe the process flow and the requirements of each feature of all the modules. 4ill in the
tabular form as gi-en in the template. 1escribe about the module name, 4unction no, Inputs, $rocesses,
2utputs for all the modules in detail.
Mo-u0e Name& <Name> Feature No<N>
Item De!cri"tio
"eature
Ob9e0tives
Des0ription o2 t/e
0ontents
Pro0ess
Nature o2 0ontents
Data inputs
Data outputs
Is sear0/ re7uired
Privi3eges:
Se0urity 3eve3s
Any e;0ommer0e 0ontent
"uture updates
"re7uen0y o2 updates
Comments
Note& Repeat the abo-e for all the features and for all modules of the product
$ffecti%e Date& '' Dec ())'* #er!io No+ '+) Pa1e ( of ;
QMS-MINFY-T-<Project ID>-SRS(W)
>+) Pa1e Tem"0ate
,$ro-ide a sample page template+
@+) 7"erati1 $%iromet
@+' :ar-ware
,Identify hardware requirements for the implementation+
@+( Software
,Identify software requirements for the implementation+
@+* NetworC
,Identify networ( requirements within the customer premises for the implementation+
@+; 2ommuicatio
,Identify communication requirements for the implementation. !.g 3etwor(, *3+
A+) Performace Requiremet!
, Identify quality indices (quantifiable if possible# for the measurable and -erifiable performance of the
product. The performance of the product can be measured against the following details.
3umber of optimum users
Response time+
')+) Sta-ar-!
,Identify customer specific standards to be followed during de-elopment+
$ffecti%e Date& '' Dec ())'* #er!io No+ '+) Pa1e * of ;
QMS-MINFY-T-<Project ID>-SRS(W)
''+) S"ecia0 8!er Requiremet!
, Identify any special user requirements such as
Security
"ac( up and reco-ery
1ata migration
5ser training
Statutory and regulatory requirements
&egal requirements
#/ese are 0ustomer spe0i2i0 and are identi2ied 2or ea0/ 0ustomer.
'(+) 8!er 23aracteri!tic!
-Identify the characteristics of the users, any bac(ground (nowledge and training needed for the usage of the
product.
'*+) 7t3er!
,$ro-ide any other information, which may be useful in the product de-elopment. +
3ote. This template may be appropriately modified depending on the pro%ect+
<Note: This template may be appropriately modified depending on the project. The Requirement
Traceability Matrix Form !M"#M$NF%#F#RTM& may be referred during the preparation of this
'ocument. The information gi(en )ithin the *<+, needs to be deleted. -hiche(er section is not
applicable. it should not be deleted/ *N01, is to be gi(en instead+
$ffecti%e Date& '' Dec ())'* #er!io No+ '+) Pa1e ; of ;