Define

 

•

•

Defne (That is project setup, project plan) Analyze (That is understand unctional requirement, unctional specifcation document)

•

Design (Database, U, documents)

•

!oding " Unit testing (#an at $or%)

•

&erifcation and &alidation (ntegration and system testing)

'ach phase has enoled some documentation to $or% on *

Defne+ roject is aailable to us -e chec% i statement o $or% is aailable to us Defne+ .o, Statement o Work (SOW) document (SOW) document $ould be the frst document receied rom client /nce project in, $e may 0initiate0 and do an o1cial %ic% o2 o the project .o, $e may create Project Initiation Note document Note document That may be created by 3usiness #anager as $ell as the attendants o this meeting Team $ould start on Project Plan (by Plan (by roject #anager) document, Quality Plan " Plan " Test Plan (by Plan (by 4A #anager) document -e also identiy quantifable ris% $hich are inoled in project at this leel and create roject 5is% #anagement lan (by roject #anager) document 6 Analyze++ The most important documents at this stage are7 e!uirement Analyze S"ecifcation Document S"ecifcation  Document (.5.)7 that is a joint e2ort by client and team and second is the #inutes o #eetin$ (#/#) #eetin$ (#/#) document created on each discussion8interaction8communication This phase also may include %se discussion8interaction8communication &ase document &ase  document based on .5. document (joint e2ort o client, programmers and 4A) as $ell as e!uirement Trace'ility #atri document #atri document (by progammers) arallelly arallelly 4A may $or% on reised Test Plan Plan document  document $hich may hae change based on analysis 9 Desi$n++ mportant document is7 Desi$n ocument (joint e2ort o Team head, Desi$n solution architect) that specifes use o design pattern, code or design guidelines, U guidelines and standard to maintain may also consider to add screen prototypes prototypes  reports are inoled then $e may also create e"ort Desi$n document Desi$n document At this stage .olution architect or Team may reie$ these documents and prepare a reised e!uirement Tracea'ility #atri document #atri document $hich may change based on design 4A may update Test Plan Plan document  document  mean to say, each document $hich are created earlier may tend to change and get updated in incremented $ay $ay : &oin$++ mportant documents are7 !ode itsel &oin$ itsel -ell, o course only i you consider it as a document as $ell This is the part most a$aited by deelopers, $e maintain code guideline in this phase A parellel code reie$ might be going on the $ay, $hich produces &oe e*ie+document e*ie+document At the same time 4A may be $or%ing on Test case S"ecifcation (by S"ecifcation (by 4A head) document Deelopers may create %nit Test "lan,etaile document "lan,etaile document i require 4A e;ecutes their Test case specifcation on actual unctions and prepate Test esult document esult document At this stage as $ell, the e!uirement Trace'ility #atri document #atri document $ill be haing most updation 3ecause, $e may ace this situation $here actual problem8issue8challenges problem8issue8challenges $e ace only at this stage $hich $e may not hae anticipated < -eriy+ts -eriy +ts a testing stage7 $here $e gie importance to Test &ase. Test esult documents esult  documents -e, deelopers7 receie Deli*ery notes (by notes (by 4A head) ater a test cycle or Test Test case e;ecution on modules and integrated modules to delieer as a milestone  This may be less or more more based on the organization structure, structure, project project requirement or methodology you adhere

 

SD/& •

•

•

5oles and 5esponsibilities =lossary and Acronyms  T  Templates emplates

•

Alternate #ethodologies

•

>A4s

Tem"lates 01 Initiation P2ase •

!oncept roposal

•

ro roje ject ct !h !har arte terr

31 &once"t De*elo"ment P2ase •

roject .cope .tateme .tatement nt

41 Plannin$ P2ase •

roject #anagement lan

•

5is% #anagement lan

•

!hange #anagement lan

•

!ommunication #anagement lan

•

.ta1ng #anagement lan

•

.ta%eholder #anagement lan

51 e!uirements Analysis P2ase •

•

>unctional 5equir >unctional 5equirements ements Document  T  Test est #aster lan

61 Desi$n P2ase •

.ystem Design Document  Document 

•

!onersion lan

•

mplementation lan

•

/perations #anual

 

•

.ystem Administration #anual

•

#aintenance #anual

•

 T  Training raining lan

•

User #anual

71 De*elo"ment P2ase •

.ot$are Deelopment Document

•

ntegration Document

•

 T  Test est Analysis 5eport 5eport

81 Test Test P2ase •

 Test Analysis Approal  Test Approal Determination

•

 T  Test est roblem 5eport 5eport

91 Im"lementation P2ase •

&ersion Descri Description ption Documen Documentt

•

ost?mplementation 5eie$ 5eport

:1 O"erations an #aintenance #aintenance P2ase •

Disposition lan