c
c

  
 

It contains 6 phases.

’@ @
@
c@
c
’ 
c@cc
’ c@ c
’ @ c
’
c
@ c
’ 
@ @
  c

@  !

!"  Interacting with the customer and gathering the requirements.
 !  BA (Business Annalist)
EM (Engagement Manager)

!!
First of all the business analyst will take an appointment from the customer, collects the
templates from the company meets the customer on the appointed date gathers the
requirements with the support of the templates and comeback to the company with a
requirements documents.

 
It is defined as a pre-defined format with pre-defined fields used for preparing a
document perfectly.


The proof of this phase is requirements document which is also called with the following
name
FRS - (Functional Requirement Specification)
BRS - (Business Requirement Specification)
CRS - (Client/Customer Requirement Specification.

 !! !

!"  Feasibility study.
Tentative planning.
Technology selection.
Requirement A\analysis.

 !  System Annalist (SA)
Project Manager (PM)
Team Manager (TM)

!!
@ # !$ !%& It is detailed study of the requirements in order to check whether all the
requirements are possible are not.
@@
  ' The resource planning and time planning is temporary done in this section.
|@@@
  '!  The lists of all the technologies that are to be used to accomplish the
project successfully will be analyzed listed out hear in this section.
@(%
  !!
The list of all the requirements like human resources, hardware, software required to
accomplish this project successfully will be clearly analyzed and listed out hear in this
section.


 The proof of this phase is SRC (Software Requirement Specification).

!' !

!"! HLD (High Level Designing) LLD (Low Level Designing)

 ! HLD is done by the CA (Chief Architect). LLD is done by the TL

(Technical Lead).

!!
The chief architect will divided the whole project into modules by drawing some
diagrams and technical lead will divided each module into sub modules by drawing some
diagrams using UML (Unified Modeling Language).
The technical lead will also prepare the PSEUDO Code.


 The proof of this phase is technical design document (TDD).
!%&& It is a set of English instructions used for guiding the developer to develop the actual
code easily.
&% 
Module is defined as a group of related functionalities to perform a major task.

&' !

!"  Programming / Coding.
 !  Developers / Programmers.

!!
Developers will develop the actual source code by using the PSUEDO Code and
following the coding standards like proper indentation, color-coding, proper commenting
and etc«


 The proof of this phase is SCD (Source Code Document).


!' !

!" Testing.
 !  Test Engineer.

!!

r First of all the Test Engineer will receive the requirement documents and review it for under
studying the requirements.

r If at all they get any doubts while understanding the requirements they will prepare the
Review Report (RR) with all the list of doubts.

r Once the clarifications are given and after understanding the requirements clearly they will
take the test case template and write the test cases.

r Once the build is released they will execute the test cases.

r After executions if at all find any defects then they will list out them in a defect profile
document.

r Then they will send defect profile to the developers and wait for the next build.
 r Once the next build is released they will once again execute the test cases

r If they find any defects they will follow the above procedure again and again till the product
is defect free.

r Once they feel product is defect free they will stop the process.


 The proof of this phase is Quality Product.

! !
Test case is an idea of a Test Engineer based on the requirement to test a particular
feature.
 
 &   !
 


!" Installing application in the client environment.
 ! Senior Test Engineers / Deployment Engineer.

!!
The senior test engineers are deployment engineer will go to the client place and install
the application into the client environment with the help of guidelines provided in the
deployment document.
  
After the delivery if at all any problem occur then that will become a task based on the
problem the corresponding roll will be appointed. Based on the problem role will define
the process and solve the problem.