SOFTWARE DEVELOPMENT

LIFE CYCLE with AGILE TESTING

By B V Ramana Test Lea ! CSTE an IST"B Ce#ti$ie ! S%#&m %e#ti$ie P#'$essi'na(! T#aine a#'&n )*** +#'$essi'na(s 'n A,i(e! Di#e%t'# '$ "&a(ity Th'&,h Te%hn'(',ies! F'# C'nta%t- qtramana@gmail.com

TABLE OF CONTENTS

Software Development Models ....1 Importan e of SDLC.....! "aterfall Model....# $ Model....% Iterat&on Model.....11 A'&le Met(odolo')......1! S r*m Framewor+....1, E-treme .ro'ramm&n'..1/ Interv&ew 0*est&ons..!1

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Software Development Models:

T(e Software Development l&fe ) le 1SDLC2 model &s3 1. An approa ( to (ave a se4*en e of steps to s)stem or Software prod* t 2. To e-e *te t(e pro ess from start to f&ns&( w&t(o*t rev&s&t&n' an) prev&o*s step

Why we need SDLC:

To E-e *te pro5e ts w&t( proven frame wor+ To def&ne and fo *s roles and respons&6&l&t&es To enfor e plann&n' and ontrol To (ave ons&sten ) amon' del&vera6les To In rease prod* t&v&t) 6) e-e *t&n' t(e pro5e t &n s)stemat& manner To red* e t(e rewor+ effort d*r&n' pro5e t

SDLC Activities or Phases:

Project Initiation Phase: T(&s &s 1st .(ase &n t(e pro5e t l&fe ) le7 as &t &nvolves start&n' *p a new pro5e t. A pro5e t &s started 6) def&n&n' &ts3 O65e t&ves S ope .*rpose

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Del&vera6les

Also &n t(&s p(ase we (&re t(e pro5e t team7 set*p t(e pro5e t off& e and rev&ew t(e pro5e t7 to 'a&n approval to 6e'&n t(e ne-t p(ase. T(e .*rpose of t(e In&t&at&on p(ase &s to start t(e pro5e t.

Concepts Development Phase: T(e Con ept Development .(ase ma) 6e'&n after t(e approval of t(e omplet&on of t(e &n&t&at&on pro5e t stat*s rev&ew and t(e approval to pro eed to t(e Con ept Development .(ase. The foc s of the phase is two!fold: 1. Eval*ate feas&6&l&t) of alternat&ve and 2. Clearl) def&ne and approve pro5e t s ope7 &n l*d&n' t(e s)stem7 all del&vera6les and all re4*&red a t&v&t&es.

Plannin": .ro5e t .lann&n' 8 Determ&nes t(e pro5e t9s 'oals and res*lts &n a (&'(:level v&ew of t(e potent&al pro5e t. .roper Compre(ens&ve pro5e t plann&n' &s essent&al to a s* essf*l IT pro5e t7 and &n omplete pro5e t plann&n' and anal)s&s are fre4*entl) root a*ses o pro5e t fa&l*re. T(e p*rpose o t(e plann&n' p(ase &s to plan all pro5e t pro esses and a t&v&t&es re4*&red to ens*re pro5e t s* ess and to reate a ompre(ens&ve set of plans7 +nown as t(e pro5e t Mana'ement .lan 1.M.27 to mana'e t(e pro5e t from t(&s p(ase *nt&l pro5e t term&nat&on.

#e$ irement Analysis: T(e ;e4*&rement Anal)s&s .(ase 6e'&ns w(en t(e prev&o*s p(ase o65e t&ves (ave 6een a (&eved. Do *mentat&on related to *ser re4*&rements from t(e Con ept Development .(ase and t(e plann&n' p(ase s(all 6e *sed as t(e 6as&s for f*rt(er *ser needs anal)s&s and t(e development of deta&led re4*&rements. T(e .*rpose of t(e ;e4*&rements Anal)s&s .(ase &s to transform t(e needs and (&'( level re4*&rements spe &f&ed &n earl&er p(ases &nto *nam6&'*o*s 1meas*ra6le and lesta6le27 tra ea6le7 omplete7 ons&stent and sta+e(older 8 approved re4*&rements. QUALITY THOUGHT qt o!g t""@gmail.com * qttfacebook@gmail.com * Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Desi"n: D*r&n' t(e Des&'n .(ase t(e s)stem &s des&'ned t& sat&sf) t(e re4*&rements &dent&f&ed &n t(e prev&o*s p(ases. T(e ;e4*&rements Ident&f&ed &n t(e ;e4*&rements Anal)s&s .(ase are transformat&on &nto a s)stem des&'n do *ment t(at a *ratel) des r&6es t(e des&'n of t(e s)stem and t(at an 6e *sed as an &np*t to s)stem development &n t(e ne-t p(ase. T(e p*rpose of t(e des&'n p(ase &s to transform t(e re4*&rements &nto omplete and deta&led s)stem des&'n spe &f& at&ons. On e t(e des&'n &s approved7 t(e Development Team 6e'&ns t(e Development .(ase.

Development:

T(e Development p(ase feat*res a +e) step &n t(e pro5e t S)stem onstr* t&on. T(e prev&o*s p(ases la) t(e fo*ndat&on for s)stem development t(e follow&n' p(ases ens*re t(at t(e prod* t f*n t&ons as re4*&red. To omplete t(e development p(ase s* essf*ll)7 two elements are re4*&red. 1. A omplete set of des&'n spe &f& at&ons 2. .roper pro esses standards and tools. T(e p*rpose of t(e development p(ase &s to onvert t(e s)stem des&'n protot)ped &n t(e des&'n p(ase &nto a wor+&n' &nformat&on s)stem t(at addresses all do *mented s)stem re4*&rements. At t(e end of t(&s p(ase7 t(e wor+&n' s)stem w&ll enter t(e test p(ase. Testin": T(e test p(ase fo *ses on an emp&r& al &nvest&'at&on &n w(& ( t(e res*lts des r&6e t(e 4*al&t) of t(e s)stem test&n' annot onf&rm a s)stem f*n t&ons propert) *nder all ond&t&ons 6*t an esta6l&s( t(at &t fa&ls *nder spe &f& ond&t&ons. In t(e test p(ase7 test&n' of t(e s)stem proves t(at t(e s)stem meets all re4*&rements7 &n l*d&n' t(ose for performan e and se *r&t).

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

T(e p*rpose of t(e test p(ase &s to '*arantee t(at t(e s)stem s* essf*ll) 6*&lt and tested &n t(e development p(ase meets all re4*&rements and des&'n parameters. After 6e&n' tested and a epted t(e s)stem moves to t(e &mplementat&on p(ase.

Implementation: The Implementation Phase has one %ey activity: Develop&n' t(e new s)stem &n &ts tar'et env&ronment. S*pport&n' a t&ons &n l*de tra&n&n' end *sers and prepar&n' to t*rn t(e s)stem over to ma&ntenan e personnel. T(e p*rpose of t(e &mplementat&on p(ase &s to deplo) and ena6le operat&ons of t(e new &nformat&on s)stem &n t(e prod* t&on env&ronment.

&peration and maintenance D*r&n' t(e operat&ons and ma&ntenan e p(ase7 t(e &nformat&on s)stem9s ava&la6&l&t) and .erforman e &n e-e *t&n' t(e wor+ for w(& ( &t was des&'ned &s ma&nta&ned. S)stem operat&ons ont&n*e *nt&l t(e s)stem9s term&nat&on date7 w(en t(e ne-t p(ase7 d&spos&t&on7 6e'&ns. T(e p*rpose of t(e operat&ons and ma&ntenan e p(ase &s to ens*re t(e &nformat&on s)stem &s f*ll) f*n t&onal and performs opt&mall) *nt&l t(e s)stem rea (es &ts end of l&fe.

Waterfall methodolo"y:
'efore we act ally di" into the (ea ty of a"ile) lets dnerstand what is water fall in reality: "ater fall never sa)s we s(o*ld not 'o 6a + to se ond p(ase7 on e we are done w&t( &t and we are &n ,rd p(ase. If t(at &s so7 t(ere &s no 6*'f&- &n water fall7 6e a*se development omes 6efore test&n' and )o* an not develop &f )o* 'et a 6*'.

What is waterfall then*

"ater fall sa)s t(at7 one an not v&s&t t(e ! nd p(ase *nless (e < s(e &s a t*all) on se ond p(ase. Sa)7 a tester an not start test&n' *nless t(e pro5e t &s moved from dev p(ase to test&n' p(ase. Bas& all) one an not feel an)t(&n' earl).

+istory:
QUALITY THOUGHT qt o!g t""@gmail.com * qttfacebook@gmail.com * Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

"&nston ;o) e sa&d &n 1=%> t(at3 snea+ pea+ test&n' T(&s means7 a tester s(o*ld feel t(e test&n' &n a pro5e t even 6efore we start w&t( test&n' p(ase.

Waterfall Model main feat res are:

"(ole pro ess of software development &s dev&ded &nto separate p(ases Der&ves from &ts name7 '&v&n' as ad&n' effe t from one p(ase to anot(er p(ase Ea ( o(ase (as well def&ned start&n' and end&n' po&nt w&t( &dent&f&a6le del&ver&es to t(e ne-t p(ase. Most ommonl) *sed model

'loc% Dia"ram:

Waterfall Model Disadvanta"es:

No wor+&n' software &s prod* ed *nt&l late d*r&n' t(e l&fe ) le. QUALITY THOUGHT qt o!g t""@gmail.com * qttfacebook@gmail.com * Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

?&'( amo*nts of r&s+ and *n erta&nt). .oor model for omple- and o65e t:or&ented pro5e ts. .oor model for lon' and on'o&n' pro5e ts. "or+s well for smaller pro5e ts w(ere re4*&rements are ver) well *nderstood. .oor model w(ere re4*&rements are at a moderate to (&'( r&s+ of (an'&n'. ;ewor+ wo*ld 6e more.

Waterfall vs, A"ile:

"aterfall ?eav) do *mentat&on Ded& ated teams Def&ned ontra ts of wor+ Man'ed 6) separate teams Ever) p(ase m&'(t not onta&n a del&ver) A'&le Effe t&ve do *mentat&on M*lt& f*n t&onal teams Fle-&6le s ope of wor+ Self mana'e6le All p(ases are 'o&n' to (ave l&ve prod* t as end res*lt.

- Mode.:
T(e $:Model for Test&n' prov&des a str* t*red development framewor+7 emp(as&@&n' 6*&ld&n' 4*al&t) &n from t(e &n&t&al re4*&rements sta'e t(ro*'( t(e f&nal test&n' sta'e.

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

-!Model Desription:
A A A A A A A A Development effort 6e'&ns on t(e left:(and s&de of t(e $:Model w&t( anal)s&s and des&'n a t&v&t&es .ro5e t &s spe &f&ed top down7 ma+&n' de &s&ons and add&n' more deta&l at ea ( new spe &f& at&on sta'e D*r&n' ea ( anal)s&s or des&'n sta'e on t(e left7 a test plan &s developed7 w(& ( do *ments t(e test ases and e-pe ted res*lts re4*&red to test t(e &mplementat&on of t(e spe &f& at&on &n t(e orrespond&n' test&n' a t&v&t) on t(e r&'(t s&de "(en t(e des&'n &s omplete7 t(e 6*&ld pro ess 6e'&ns On e development &s omplete7 t(e appl& at&on moves t(ro*'( t(e test&n' a t&v&t&es on t(e r&'(t (and s&de of t(e $ Test&n' done on t(e r&'(t s&de of t(en $:Model tests t(at t(e related spe &f& at&on on t(e left s&de &s properl) &mplemented D*r&n' t(e earl&er sta'es of test&n'7 t(e fo *s &s on &nd&v&d*al omponents As test&n' pro'resses7 t(e fo *s &n on f*n t&onal&t) and a (&evement of t(e 6*s&ness ase

T(e $ Model demonstrates t(e relat&ons(&ps 6etween ea ( p(ase of development l&fe ) le and &ts asso &ated p(ase of test&n' .T(e $ Model Ill*strates (ow test&n' a t&v&t&es an 6e &nte'rated &nto ea ( p(ase of t(e software development L&fe ) le.

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Iterative Development Model

M*lt&ple ) les ta+e pla e (ere7 C) les are d&v&ded *p &nto smaller7 more eas&l) mana'ed &terat&ons. Ea ( &terat&on passes t(ro*'( t(e re4*&rements7 des&'n7 &mplementat&on and test&n' p(ases. Eas&er to test and de6*' d*r&n' a smaller &terat&on. More fle-&6le 8 less ostl) to (an'e s ope and re4*&rements. A wor+&n' vers&on of software &s prod* ed d*r&n' t(e f&rst &terat&on7 so )o* (ave wor+&n' software earl) on d*r&n' t(e software l&fe ) le. Iterat&ve or In remental Development .ro esses

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Why A"ile process is Important: A'&le &s a software development pro ess. In toda)9s rap&d world7 .ro5e t sta+e (olders want &mmed&ate ret*rn on t(e&r &nvestment. T(e) don9t want to wa&t lon'er to 'et t(e f*ll feat*res prod* t. As a res*lt7 now a da)9s new software development and test&n' framewor+s are at (&n' moment*m A'&le approa (. In A'&le pro5e ts are d&v&ded &n top small feat*res t(at are &n t*rn developed and tested &n spe &f& t&me 8 frames alled as spr&nt 1small ) les2.T(e ma&n &dea 6e&n' 8 feat*res s(o*ld 6e developed and tested &n spe &f&ed small t&me:frames.

Introd ction of A"ile process:

A'&le met(ods 6rea+ tas+s &nto small &n rements w&t( m&n&mal plann&n'7 and do not d&re tl) &nvolve lon':term plann&n'. Iterat&ons are s(ort t&me frames 1Bt&me 6o-esB2 t(at t)p& all) last from one to fo*r wee+s. Ea ( &terat&on &nvolves a team wor+&n' t(ro*'( a f*ll software development ) le &n l*d&n' plann&n'7 re4*&rements anal)s&s7 des&'n7 od&n'7 *n&t test&n'7 and a eptan e test&n' w(en a wor+&n' prod* t &s demonstrated to sta+e(olders. Team ompos&t&on &n an a'&le pro5e t &s *s*all) ross:f*n t&onal and self:or'an&@&n'. Team mem6ers normall) ta+e respons&6&l&t) for tas+s t(at del&ver t(e f*n t&onal&t) an &terat&on re4*&res. T(e) de &de &nd&v&d*all) (ow to meet an &terat&onCs re4*&rements.. Most a'&le &mplementat&ons *se a ro*t&ne and formal da&l) fa e:to:fa e omm*n& at&on amon' team mem6ers.

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Principles of a"ile methods:

C*stomer sat&sfa t&on 6) rap&d7 ont&n*o*s del&ver) of *sef*l software "or+&n' software &s del&vered fre4*entl) 1wee+s rat(er t(an mont(s2 "or+&n' software &s t(e pr&n &pal meas*re of pro'ress Even late (an'es &n re4*&rements are wel omed Close7 da&l) ooperat&on 6etween 6*s&ness people and developers Fa e:to:fa e onversat&on &s t(e 6est form of omm*n& at&on 1 o:lo at&on2 .ro5e ts are 6*&lt aro*nd mot&vated &nd&v&d*als7 w(o s(o*ld 6e tr*sted Cont&n*o*s attent&on to te (n& al e- ellen e and 'ood des&'n S&mpl& &t) Self:or'an&@&n' teams

Practical Implementations of A"ile Methods: A'&le Model&n' A'&le *n&f&ed .ro ess Essent&al Dn&f&ed .ro ess 1EssD.2 E-treme .ro'ramm&n'1E.2 Feat*re Dr&ven Development 1FDD2 Open Dn&f&ed .ro ess S r*m L&near development

Scr m Characteristics:
S r*m &s a Fpro ess s+eletonG w(& ( onta&ns sets of pra t& es and predef&ned roles. S r*m &s an &terat&ve7 &n remental framewor+ for pro5e ts and prod* t or appl& at&on development. S r*m (as QUALITY THOUGHT qt o!g t""@gmail.com * qttfacebook@gmail.com * Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

6e ome more and more pop*lar software development and test&n' framewor+ amon' or'an&@at&ons &n t(e re ent past. Man) small to lar'e s&@ed &t or'an&@at&ons (ave started to em6ra e s r*m framewor+7 as t(&s an reate e- ellent 4*al&t) prod* ts &n s(orter and more 4*ant&f&a6le t&meframes t(an an) ot(er trad&t&onal software development met(odolo'&es. T(&s framewor+ an save ompan&es 6ot( t&me and mone).

The main roles in Scr m are:

T(e name s r*m &s &nsp&red from r*'6) 'ame w(ere team wor+ &s ma&n +e) for t(e s* ess. An a'&le pro5e t mana'ement framewor+ and development pro ess w(ere a team of # to 1> people prod* e &n rements of prod* ts ever) 1H to ,> da)s &terat&on 6ased *pon t(e pr&or&t) of wor+ set 6) t(e *stomer. .rod* ts &s des&'ned and 6*&lt &terat&vel) and &n rementall) *s&n' t(e prod* t development l&fe ) le &n ! to H wee+s d*rat&on. At t(e end of &terat&ons7 prod* t &s del&vered 6ased *pon t(e 6*s&ness val*e of t(e feat*res as pr&or&t&@ed 6) t(e *stomers. C*stomer rev&ews t(e prod* t and prov&des feed6a + to t(e team.

T(e FProd ct &wnerG7 w(o represents t(e sta+e(olders and t(e 6*s&ness .rod* t owner &s t(e one w(o de &des on pr&or&t&es of t(e re4*&rements .rod* t owner &s not t(e person w(o allo ates tas+s to team mem6ers .rod* t owner ma) < ma) not 6e l&ent:6*t ma&nta&ns (ara ter&st& s .rod *t owner w&ll not '&ve te (n& al s*''et&ons to team mem6ers 6*t de &des on 6*s*&ness

T(e FScr m MasterG7 w(o ma&nta&ns t(e pro esses 1t)p& all) &n l&e* of a pro5e t mana'er2 S r*m master &s t(e one w(o a ts as 6r&d'e 6etween 6*s&ness and team7 means a ts as 6r&d'e 6etween prod* t owner and team 1dev7 test et 2 S r*m master s(o*ld 6e &n a pos&t&on to (elp an) team mem6er to a ompl&s( t(e&r tas+s 6) remov&n' &mped&ments &n t(e&r wa).

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

S r*m master s(o*ld (elp ever)one &n t(e team7 from t(e 6e'&nn&n' to t(e release of ever) s r*m. S r*m master s(o*ld not allo ate tas+s 6*t (elps &n *nderstand&n' 6*s&ness pr&or&t&es. S r*m master oord&nates w&t( 0A and DAT team &n 'ett&n' s&'noffs for t(e releases. Or'an&@es t(e s r*m alls < stand:*p alls.

T(e FTeamG7 a ross:f*n t&onal 'ro*p of a6o*t % people w(o do t(e a t*al anal)s&s7 des&'n7 &mplementat&on7 test&n'7 et . ?ere7 t(e ross:f*n t&onal means7 t(ere &s no separate ta' l&+e tester<developer or 6*s&ness *ser 7 rat(er ever) one &s part of ever) 'ro*p. T(e a6ove statement lar&f&es t(at7 ever) one s(o*ld 6e (av&n' e-pos*re &nto m*lt&ple doma&ns and te (nolo'). Team mem6ers &n a'&le are self or'an&@ed and self mana'e6le.

T(e FMana"ementG fol+s are someone w(o &s not respons&6le for an) del&ver&es or someone w(o &s not part of t(e 'ro*p 6*t someone w(o &s &nterested &n t(e pro5e t. In A'&le team7 mana'ement doesnot &nvlove &n t(e allo at&on of t(e tas+s or pr&or&t) def&nat&on of an) a t&v&t&es. Mana'ement &s not allowed to spea+ &n s r*m alls.

Stand! p Calls
A'&le 6ele&ves t(at7 people an spea+ (o*rs to 'et(er &n meet&n's 6*t t(e o*tp*t &s val*a6le of 1#m&ns wort( a da)7 (en e all meet&n's &n a'&le met(odolo') are stand *p meet&n's7 w(ere people s(o*ld stand and spea+7 (en e t(e) won9t spea+ more t(an 1#m&ns:w(& ( &s a t*all) re4*&red for t(e pro5e t. /ote: Stand *p all 'enerall) (appens ever) da) at t(e morn&n'. 0enerally) in a call (elow thin"s are disc ssed: "(at d&d )o* do )esterda)I "(at are )o* 'o&n' to do toda)I * qttfacebook@gmail.com * Email:

QUALITY THOUGHT qt o!g t""@gmail.com

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Are t(ere an) o6sta les &n )o*r wa)I Str& tl)7 no resol*t&ons &n t(e meet&n's 8 resol*t&ons offl&ne.

Terminolo"ies sed in A"ile

Stor&es Iterat&ons Comple-&t) po&nts Iterat&on $elo &t) .rod* t Ba +lo' < Iterat&on Ba +lo' S r*m < Da&l) Stand Dp Meet&n' Iterat&on .lann&n' Meet&n' 1I.M2 Iterat&on ;ev&ew Meet&n' S(ow ase and ;etrospe t&ve Meet&n' B*rn Dp and B*rn:Down C(art

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

The Scr m 1ramewor%

SC#2M P#&C3SS:
Stpe13 In A'&le met(odolo') all re4*&rements are d&v&ded &nto stor&es. Step !3 A'&le met(odolo') "or+s &n Iterat&ons. Iterat&on means t&me l&ne f&-ed to del&ver t(e Stor&es w&t(o*t defe ts. In 'eneral Iterat&on d*rat&ons are 1 wee+7 ! wee+s or 1mont( Step ,3 B*s&ness Anal)sts w&ll send stor&es to t(e team &n t(e start&n' da) of &terat&on. Step H3 "(en Iterat&on starts Developers start wor+&n' on od&n' at t(e same t&me Testers wor+ on des&'n&n' of test ases. "(en t(e Stor&es are read) for test&n' Testers w&ll e-e *te all t(e test ases. Step #3 S r*m Master Coord&nates t(e A'&le pro5e t and &n S r*m meet&n's w&t( all teams 1BA9s7 Modelers7 Developers7 Test&n' team2 d&s *ss a6o*t t(e stat*s on t(e stor) Step #3 B) t(e end of &terat&on all t(e stor&es test&n' s(o*ld 6e ompleted w&t(o*t an) defe ts Step J3 .rod* t Owners &.e. C*stomers w&ll test t(e prod* t. S* ess r&ter&a for Iterat&on3 1.No r&t& al defe ts 6) end of t(e Iterat&on7 No (&'( defe ts 6) end of t(e &terat&on * qttfacebook@gmail.com * Email:

QUALITY THOUGHT qt o!g t""@gmail.com

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

What testers can e4pect:

New feat*res are added to t(e software &n ea ( of t(e Iterat&on. Test Teams s(o*ld e-pe t to r*n one or more omplete test ) le &n ea ( &terat&on of t(e pro5e t7 &n l*d&n' re'ress&on test&n' prev&o*sl) del&vered feat*res as well as t(e *rrent feat*re. Testers7 B*s&ness Anal)sts7 and Developers w&ll wor+ to'et(er as an &nte'rated team to def&ne7 6*&ld7 and test software. Test&n' spans t(e &terat&on 1t&me2 and spans a ross t(e team 1roles2. ;e4*&rements and ode ont&n*e to (an'e d*r&n' test ) les. Env&ronments and test data m*st 6e read) earl&er and more losel) mana'ed.

+ow testers will (enefit from an a"ile approach

More feat*res are f*ll) ompleted earl&er &n t(e pro5e t7 remov&n' t(e need for a lon'7 (&'(: press*re test&n' ) le r&'(t 6efore t(e prod* t moves to prod* t&on. B*s&ness Anal)sts and Testers (ave more opport*n&t) to prov&de and re e&ve feed6a + on t(e software earl&er &n t(e pro5e t7 lead&n' to fewer ma5or (an'es late &n t(e effort. More Developer test&n' red* es t(e n*m6er of B ommonB defe ts t(at t(e testers need to worr) a6o*t and red* es t(e amo*nt of t&me spent mana'&n' lar'e amo*nts of defe ts. T(e defe t report<f&- ) le &s dramat& all) s(ortened. An A'&le approa ( an more eas&l) a ept (an'es &n *stomer re4*ests.

Challen"es for testers:

Tests m*st 6e a6le to r*n 4*& +l) and repeatedl). Iterat&ons last !:J wee+s. Ea ( &terat&on s(o*ld &n l*de one to man) f*ll test&n' ) les. T(&s &s a (*'e (allen'e for efforts t(at rel) on mostl) man*al test&n'. Test ase reat&on s(o*ld 6e'&n on *rrentl) w&t( t(e ela6orat&on of t(e feat*re.

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Test e-e *t&on m*st start as soon as feat*res are read)7 re4*&r&n' env&ronments and data to 6e set *p d*r&n' t(e f&rst &terat&on. .erforman e Test&n' ma) need to o *r earl&er t(an trad&t&onal waterfall efforts. ;e4*&rements and ode are (an'ed d*r&n' test ) les7 re4*&r&n' more fle-&6le test s (ed*les7 and more re'ress&on test&n'. Inte'rat&n' w&t( non:a'&le pro5e ts7 an present a t&m&n' (allen'e7 as ot(er pro5e ts m&'(t not (ave t(e&r s&de of &nte'rat&on po&nts 6*&lt earl) eno*'( to do e-tens&ve test&n'. Mana'&n' test data and env&ronments on s(orter t&me frames.

Chec%points
A'&le Development &s a part of w(& ( software Development modelI "(at &s $elo &t)I A *ser stor) &s developed 6) aI

' rn Down Chart

T(e p*rpose of t(e 6*rn down (art &s to (ave a v&s*al representat&on of t(e amo*nt of wor+ left to omplete &n t(e *rrent &terat&on. It '&ves a s&mple v&ew of t(e spr&nt pro'ress. Ideall) s(o*ld 6*rn down to @ero to t(e end of t(e Spr&nt T(e o*tstand&n' wor+ 1or 6a +lo'2 &s often on t(e vert& al a-&s7 w&t( t&me alon' t(e (or&@ontal

' rn Down Chart

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

' rn p Chart
T(e pro6lem &s t(at 6*rn down (arts la + two essent&al p&e es of &nformat&on. F&rst7 (ow m* ( wor+ was a t*all) a ompl&s(ed d*r&n' a '&ven &terat&on 1as opposed to (ow m* ( wor+ rema&ns to 6e ompleted2 Se ond (ow m* ( total wor+ t(e pro5e t onta&ns 1or &f )o* prefer (ow m* ( s ope (as &n reased ea ( &terat&on2.

' rn p Chart

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

34treme Pro"rammin" 56P7

One of t(e most well:+nown a'&le development l&fe ) le models. T(e met(odolo') la&ms to 6e more (*man fr&endl) t(an trad&t&onal development met(ods. Some (ara ter&st& s of E. are3 It promotes t(e 'enerat&on of 6*s&ness stor&es to def&ne t(e f*n t&onal&t). It demands an on:s&te *stomer for ont&n*al feed6a + and to def&ne and arr) o*t f*n t&onal a eptan e test&n'. It promotes pa&r pro'ramm&n' and s(ared ode owners(&p amon'st t(e developers.

It states t(at omponent test s r&pts s(all 6e wr&tten 6efore t(e ode &s wr&tten and t(at t(ose tests s(o*ld 6e a*tomated. It states t(at &nte'rat&on and test&n' of t(e ode s(all (appen several t&mes a da). It states t(at we alwa)s &mplement t(e s&mplest sol*t&on to meet toda)Cs pro6lems.

Differences (8w 6P 9 Scr m

S r*m teams t)p& all) wor+ &n &terat&ons 1 alled spr&nts2 t(at are from two wee+s to one mont( lon' w(&le E. one or two wee+s lon'. S r*m teams do not allow (an'es &nto t(e&r spr&nts. E. teams are m* ( more amena6le to (an'e w&t(&n t(e&r &terat&ons. E-treme .ro'ramm&n' teams wor+ &n a str& t pr&or&t) order. Feat*res to 6e developed are pr&or&t&@ed 6) t(e *stomer and t(e team &s re4*&red to wor+ on t(em &n t(at order. B) * qttfacebook@gmail.com * Email:

QUALITY THOUGHT qt o!g t""@gmail.com

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

ontrast7 t(e S r*m prod* t owner pr&or&t&@es t(e prod* t 6a +lo' 6*t t(e team determ&nes t(e se4*en e &n w(& ( t(e) w&ll develop t(e 6a +lo' &tems.

Pro(lems with a"ile methods

A'&le sa)s avo&d do *mentat&on7 and &t &s d&ff& *lt to (ave a pro5e t w(& ( &s do *ment free. It an 6e d&ff& *lt to +eep t(e &nterest of C*stomers w(o are &nvolved &n t(e pro ess. Team mem6ers ma) 6e *ns*&ted to t(e &ntense &nvolvement t(at (ara ter&@es a'&le met(ods. .r&or&t&@&n' (an'es an 6e d&ff& *lt w(ere t(ere are m*lt&ple sta+e(olders. Ma&nta&n&n' s&mpl& &t) re4*&res e-tra wor+. ;e4*&rement w&ll not 6e free@e7 w(& ( a*ses more rewor+.

+ow to overcome the challen"es

A'&le allows do *mentat&on 6*t one s(o*ld tr) to avo&d &t7 meas 8 one s(o*ld not (ave len't() do *mentat&on for an) re4*&rements. Follow 6etter do *mentat&on approa (es s* ( as:spe &f& at&on 6) e-ample7 w(& ( sa)s t(ere &s no separate do *ment for re4*&rements and separate for test&n' < *at. ;at(er (ave one do *ment w(& ( an 6e *sed 6) all. ;e4*&rements s(o*ld 6e pr&orot&@ed alwa)s &n a wa) t(at7 one s(o*ld 'et o*tp*t alwa)s for ever) release as a l&ve prod* t. Sa)7 t(ere &s a offee vend&n' ma (&ne pro5e t7 one s(o*ld not prepare a draft plan and sa) t(at t(&s &s t(e o*tp*t of m) f&rst spr&nt as &am &n plann&n' p(ase. B*t7 t(e e-pe tat&on from a'&le &s7 one s(o*ld ome *p w&t( a offee vend&n' ma (&ne &tself7 ma) 6e o*t of 1>7 onl) ! opt&ons are &n wor+&n' ond&t&on w(& ( '&ves some *se to l&ent.

'est Practices 8 Lesson Learnt

Iterat&on Tra +er Stand Dp meet&n's

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Defe t 0*er) Lo' ;etrospe t&ve Defe t ;emoval Eff& &en ) S(eet1D;E2 "&t(drawn Defe ts Anal)s&s ;eport Ma&nta&n proper 6a +*p plan for ever) reso*r e &n t(e team A*tomate w(at ever and w(ere ever Cont&no*s &nte'rat&on 8 t(ere are tools ava&la6le &n mar+et S r&pt less a*tomat&on 8 for t(e *se of 6*s&ness *sers Spe &f& at&on 6) e-ample 8 6est do *mentat&on approa (

Differences yo felt in -!model and A"ile Model* $:Model 1.$er&f& at&on and val&dat&on !.;e4*&rements are free@ed A'&le Model 0*& + mov&n' pro ess ;e4*&rements (an'e d)nam& all) so t(e) are not free@ed.

,. It9s ver) r&'&d and least fle-&6le an) (an'es B*s&ness re4*&rements are des&'ned &n t(e (appen m&d wa)7 not onl) t(e re4*&rements form of &terat&ons7 w(& ( ma+es t(e do *ments 6*t also t(e test do *mentat&on needs re4*&rements *pdate pro ess to 6e fle-&6le. to 6e *pdated. H.T(e e-e *t&on of operat&on 7ma&ntenan e repa&r E-,e *t&on7 ;epa&r and Ma&ntenan e are and d&sposal of t(e s)stem are not overed 6) t(e overed &n A'&le model.

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

v:Model

#. Involve more do *mentat&on. Do *ment Less do *mentat&on 6e a*se t(ere &s &nvolves deta&ls of operat&ons performed &n 6efore fre4*ent omm*n& at&on 6etween team sta'e. mem6ers of d&fferent sta'e

When to "o for A"ile methodolo"y*

"(en t(e re4*&rements (an'e d)nam& all). Cont&n*es mon&tor&n' of pro5e t 6) l&ent.

When not to "o for a"ile methodolo"y*

"(en t(ere are dependen &es. "(en t(ere &s omm*n& at&on 6arr&er 6etween team mem6ers or l&ent t(&s ma+es no 4*& + response from t(em. For pro5e ts w(ere re4*&rements doesn9t (an'e d)nam& all).

+i"hli"hts:
Several s*rve)s sa)7 a'&le met(odolo') w&ll 6e *sed &n =>KL of t(e pro5e ts 6) all software &nd*str&es. T(e p*rest form of a'&le w&ll )e&ld t(e 6etter res*lts7 means3 o A'&le K 6est pra t& es K S r*m :M S ra'&le o A'&le : 6est pra t& es K S r*m :M Fra'&le

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

Interview : estions
34pected : estions: 1. "(at &s SDLCI Can )o* e-pla&n me &n deta&lI "() do we need SDLCI 2. Def&ne var&o*s SDLC p(asesI 3. Des r&6e 6elow models w&t( l&fe ) le7 Advanta'eo*s7 d&sadvanta'eo*sI "aterfall Model $ Model .rotot)pe Model Iterat&ve Model Sp&ral Model ;AD Model 4. Can )o* e-pla&n waterfall model &n Man*al Test&n'I 5. Can )o* e-pla&n $ Model &n Man*al Test&n' w&t( )o*r real T&me e-per&en eI 6. E-pla&n t(e d&fferen e 6etween "aterfall and $ ModelI 7. E-pla&n d&fferen es 6etween $ Model and A'&le Met(odolo')I 8. E-pla&n t(e SC;DM Framewor+ pro ess &n )o*r .ro5e tI 9. E-pla&n $er&f& at&on $al&dat&on Model w&t( ea ( level of Test&n'I 10. "(at are t(e d&fferent a'&le met(odolo'&es Implementat&onsI E-pla&n t(e d&fferen e 6etween a'&le met(odolo') and S r*m Frame wor+I 11. For w(& ( t)pe of pro5e ts SC;DM Framewor+ &s s*&ta6leI 12. "(at are t(e a'&le met(odolo'&es .r&n &plesI 13. ?ow testers w&ll 6enef&t from an a'&le approa (I 14. "(at are t(e (allen'es for testers &n a'&le met(odolo')I

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com

15. For w(& ( t)pe of .ro5e ts A'&le Met(odolo') &s not s*&ta6leI 16. ?ow )o* de &de Iterat&on Ba +lo' &n )o*r .ro5e tI 17. "(at &s Iterat&on .lann&n' Meet&n'7 ;etrospe t&ve Do *ment &n A'&le Met(odolo')I 18. L&st few d&fferen es 6etween A'&le7 $ model &n terms of a. Do *ments preparat&on b. Test&n' L&fe C) le 19. ?ow )o* are a6le to omplete all t(e a t&v&t&es &n Test&n' &n s(ort l&fe ) leI 20. "(at are t(e roles and respons&6&l&t&es of SC;DM MasterI

QUALITY THOUGHT qt o!g t""@gmail.com

qttfacebook@gmail.com

Email:

# one: ""$%&'$(')* )&)+&))(,&(% ---.Q!alit.T o!g tTec nologie/.com