srs detail explaination

7/25/2019 SRS Detail Explaination

1/14

Software Requirements Specification

Version 1.0

Group Id:

Supervisor Name :< >


2/14

Revision Histor

!ate

"dd#mm#$

Version !escription %ut&or

04/08/2015 1.0 Software RequirementsSpecification Document

MC

Name..


3/14

'a()e of *ontents

1. Scope of t!e pro"ect#

2. $unctiona% Requirements Non $unctiona% requirements

&. 'se Case Dia(ram

4. 'sa(e Scenarios

5. )*opte* Met!o*o%o(+

,. -or %an 'se MS ro"ect to create Sc!e*u%e/-or %an#

1. Scope "of t&e pro+ect$

ro"ect scope is t!e part of pro"ect p%annin( t!at ino%es *eterminin( an* *ocumentin( a %ist of

specific pro"ect (oa%s *e%iera%es tass an* *ea*%ines.

ro"ect Scope. 3!e wor t!at nee*s to e accomp%is!e* to *e%ier a pro*uct serice or resu%twit! t!e specifie* features an* functions.3


4/14

!e wor an* resources t!at (o into t!e creation of t!e pro*uct or serice are essentia%%+ t!et!in(s t!at frame t!e scope of t!e pro"ect. !e scope of t!e pro"ect out%ines t!e o"ecties of t!epro"ect an* t!e (oa%s t!at nee* to e met to ac!iee a satisfactor+ resu%t. er+ pro"ect mana(ers!ou%* un*erstan* !ow to *efine t!e pro"ect scope an* t!ere are some steps t!at can e fo%%owe*w!en *oin( t!is.

o *efine a pro"ect scope +ou must first i*entif+ t!e fo%%owin( t!in(s6

1. ro"ect o"ecties

2. Su7p!ases

&. ass

4. Resources


5/14

2. $unctiona% Requirements Non $unctiona% requirement

.

!e officia% *efinition of a functiona% requirement9 is t!at it essentia%%+ specifies somet!in( t!e

s+stem s!ou%* *o.

+pica%%+ functiona% requirements wi%% specif+ a e!aior or function for e:amp%e6

;Disp%a+ t!e name tota% si


6/14

Non7functiona% requirements

Non7functiona% Requirements6 specif+ t!e qua%it+ of t!e s+stem is most%+ re%ate* to t!e

satisfiai%it+ of t!e user.

Non7functiona% requirements *escrie !ow t!e s+stem wors w!i%e functiona% requirements

*escrie w!at t!e s+stem s!ou%* *o.

!e *efinition for a non7functiona% requirement is t!at it essentia%%+ specifies !ow t!e s+stem

s!ou%* e!ae an* t!at it is a constraint upon t!e s+stems e!aior.

Some t+pica% non7functiona% requirements are6

erformance A for e:amp%e Response ime !rou(!put 'ti%i


7/14

Maintainai%it+

Sericeai%it+

Securit+

Re(u%ator+

Mana(eai%it+

nironmenta%

Data nte(rit+

Non7$unctiona% Requirements are as fo%%ows6

,sa(i)it:

!is app%ication can e use* + a sin(%e user at a time

-erformance:)pp%ication s!ou%* perform a%% of its functions e:ce%%ent%+ an* effectie%+wit!out an+ inconenience.

%vai)a(i)it:

!is app%ication wi%% e aai%a%e free for eer+one-orta(i)it:

'&e app)ication can easi) porta()e from one destop app)ication to

anot&er

,ser /riend):

)pp%ication wi%% !ae a user frien*%+ interface.Sca)a(i)it:

!is app%ication s!ou%* e more sca%a%e an* a%%ow mana(ement

to a** more functiona%it+.


8/14

&. 'se Case Dia(ram

) use case *ia(ram at its simp%est is a representation of a user@s interaction wit! t!e s+stem t!at

s!ows t!e re%ations!ip etween t!e user an* t!e *ifferent use cases in w!ic! t!e user is ino%e*.
http://en.wikipedia.org/wiki/Use_Casehttp://en.wikipedia.org/wiki/Use_Case


9/14

'se cases can e emp%o+e* *urin( seera% sta(es of software *ee%opment suc! as p%annin(

s+stem requirements a%i*atin( *esi(n testin( software an* creatin( an out%ine for on%ine !e%p

an* user manua%s

4. 'sa(e Scenarios

) usa(e scenario or scenario for s!ort *escries a rea%7wor%* e:amp%e of !ow one or morepeop%e or or(ani


10/14

i(!7Eee% :amp%e

Scenario6 )M anin( for t!e wee.1. )%i !an p%aces !er an car* into t!e )M.2. )%i successfu%%+ %o(s into t!e )M usin( !er persona% i*entification numer.&. )%i *eposits !er wee%+ pa+c!ec of F&50 into !er sain(s account.4. )%i pa+s !er p!one i%% of FG5 !er e%ectric i%% of F145 !er ca%e i%% of F55 an* !er water

i%% of F85 from !er sain(s account5. )%i attempts to wit!*raw F100 from !er sain(s account for t!e weeen* ut *iscoers

t!at s!e !as insufficient fun*s

,. )%i wit!*raws F40 an* (ets !er car* ac

. %dopted et&odo)o2

t is *eci*e* to se%ect B' process Mo*e% t!at is a Comination of -ater $a%% mo*e% an* Spira%

Mo*e%.


11/14

Reasons for C!oosin( B' process Mo*e%.

1. !e main i*ea to c!oose is to (et t!e enefits of ot! t!ese mo*e%s.2. t is sequentia% mo*e% wit! acwar* repetition.&. -e want to ac!iee t!e %inear nature of waterfa%% an* iteratie p%us ris re*uction nature

of spira% mo*e%.4. n u process mo*e% we wi%% e wor in p!ases to comp%ete t!e (ien pro"ect.5. )%% t!e actiities are performe* in a sequence in B' rocess Mo*e%.,. f we want to *o correction or etterment at an+ sta(e an* repetition w!eneer necessar+

t!en we can c!oose B' process mo*e%.


12/14

!e waterfa%% mo*e% is a sequentia% *esi(n process use* in software *ee%opment processes in

w!ic! pro(ress is seen as f%owin( stea*i%+ *ownwar*s %ie a waterfa%%# t!rou(! t!e p!ases ofConception nitiation )na%+sis Desi(n Construction estin( ro*uction/mp%ementation an*

Maintenance.

!e spira% mo*e% a%so nown as t!e spira% %ifec+c%e mo*e% is a s+stems *ee%opment met!o*

SDM# use* in information tec!no%o(+ #. !is mo*e% of *ee%opment comines t!e features

of t!e protot+pin( mo*e% an* t!e s+stems *ee%opment %ife c+c%e SDEC#.


13/14

3. 4or -)an ",se S -ro+ect to create Sc&edu)e#4or -)an$

!e wor p%an is a *ocument t!at consu%tin( firms use to or(ani


14/14

srs detail explaination

Documents