0% found this document useful (0 votes)
10 views5 pages

Understanding Software Requirements Specification

The Software Requirements Specification (SRS) document outlines the detailed requirements for a software system, including both functional and non-functional requirements. It serves as a communication tool between stakeholders and the development team, ensuring clarity and completeness in understanding user needs. Key components of an SRS include an introduction, overall description, functional requirements, non-functional requirements, and system models.

Uploaded by

Parshant Jangra
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views5 pages

Understanding Software Requirements Specification

The Software Requirements Specification (SRS) document outlines the detailed requirements for a software system, including both functional and non-functional requirements. It serves as a communication tool between stakeholders and the development team, ensuring clarity and completeness in understanding user needs. Key components of an SRS include an introduction, overall description, functional requirements, non-functional requirements, and system models.

Uploaded by

Parshant Jangra
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SRS

’ Ses
SRS Standls for Sodhoaie Regqu'semeut Analys's|speu'si catien
7 3+ is aDetau'led desciohem o the So hoate syien
De developed with its fuM chonal and non funcien al
Requisem euts . The SRS iS Developed Based on Agsee meut
B)w cousmes t onra ctor.

client use needs

Problem Analysish

Broduct Desoniphemk
Validahen

Vali'dated sRS

# Nee d to Ses ;
C4) Clea Undeustondinq o Reg
usemets sRS Pso'des a complete
and cleay Descip hen wh at the coustmes wauts.
(8) Act as a coract- sts
woks like
ogseemeut Blw te
coustmeh and e deuel op meut team
(3) Helps in Planning and 9+ Helhs in Esihimahing
Esimaien
hime and

Resouces needed for ko Projects


(4) Qudes Desiaqn aud Deuelopmeut - Dev lopes use Sks as a

ke euce le desiguing and coding tee Syslean


Helps in teshing Testes Psrepae a tcst Case Based on sRs e
TE SRS is wronq 4ew findI Pouoduct win Be

(6) Redyce Reok - clea Regu'smeuts


ed uce Eps amd
change latey in u Psoject
( Impoves CommuicaheM SRS Enswes Bete ord'nah'e
Blw Pooject team Membes
# Chasa ctushes sRs Agood SRS Nust. Have tolouDing
Impotaut pual'hies -

Co91ect. hl kequseyets ügitley in tee SRS


Must
the Real
Be accuate and Must Rereset
needs the uset
(1)
Complete - The sRS MUst Cowtain A funchen ap and wen
Aunck•nal Requrenets . Nothing impostant
Should Be Misaing.
clea Staemets in sRs should Be casy to ondeustaut
and Should mot kaue Double Meonig
u) Congisteut - ND toD kegusemet in teu SRs Should corathct
r conit oita Each ete

() ) Veifiabe - Ea ch equemeut should Be esta ble we


Must Be oble to check hey e4 g+'s implemete
Co9TecHy
(U) Modi fable SRS Should Be well shruced Bo gt can
Easiiy
Upd ated steu chanqes ate Requ's ed
9 Ui) TQ ceable - Each Requseneut Shouid
Be linked
Code, eshing steps gt Should to Desigu
Be Easy to hr
hene Each Requu'emeit is
sed.
# Compon euts a SRS :- An S&s Documet Mainly 5 impostaut pasts

|. lnhodu chien
Ths Sech'en gines a Bas'c Oveuieo at he Sofhare
Systen
9t Explans :
" PupoSe - Pupose a the
Sothoae (ohy 9t is Bee Hode)
" Stope What he Se toae oill Do and what It in Mt Do
Deinaien Impottaut tems ae used.
" lnteuted uee. qt Sho who wfll use tt Soth ae

. Oveall DesciphÇ u's Sechiem Des couibes te Eviomet


Qnd Back ground t the Syste
94 inclu des:

means hat use Erpect rom the systen:


Sstem Gnvironmeut. ch it
HadO asue aud Sofhase in hih

Conshrauuts . Rules limtah ens like legal Sules, Pertomace lim


Assumph'ens. Things cansidened tue whi'e repasaing
equsemeds

3 Punchenal Regu'sement These c e he maun Feahue or operat


tau Systewy Must Petom:

coe Aunchen

J
ovdes.
allou Coustey to Ploce
Exomple - 4e System Shall

bow
3 Detines not
t Nem funchenal Reauisyenes- These
System Peogm
3’ hey Descibe 4&e Qua0' Stondnd of the Sysewm Sucl as

Peito91imance ;- Speed of Syslam


Eq Paqe Must load in les than 28ec.

Secuiy Psotechen o Data.


Eg- mly authD4i2ed usH cou Acces hle
Reltablity i `ysten Stablity - Sysen Should ook 24x7
ojtt ot faulue.

5. System Models Cophiema) - This Secien uses Diagranwy


Diaqta to
&plaun ao

commen
Dlagam includes
Wse case Diagram (use Ach'en)
Pata Flouw Di'agram (Plo Data)
ER Diagrqm (Database Design)
Plo chast ( sep By Step wookylow)

You might also like