|



 



R 

 



 

˜ In general it includes several phases:-

Step1:Requirement analysis
Step2:Design
Step3:Coding
Step4:Testing
Step5:Operation & maintance

  
 All requirements has to be
defined in this step. Functional, non-functional &
requirements must be specified at this stage.
Ô   This involves designing software along with
÷ata & Architectural details have to be emphasized
in this phase. This crucial as future of s\w product
works on the basis of design.


 

3.    `odification of program to achieve required

output is essential. Selecting suitable language for the
project.
4. R  All the units & modules developed must be
ntegrated & system testing has to be performed.
Testing aims to uncover all the errors.
      Also called post installation
phase. It involves maintenance of s\w after installation.
developing software is not important, but maintaing is
very crucial.
  
Simple, systematic & easy to implement.

It is suitable for enhancement of existing model but not for new.
|
 

|
 

˜ This model was proposed by Dohem. It combines

development activities with risk management to
minimize & control risk. It accommodate any
developmental model. It consists of 4 sectors
1)    rere objective of project phase
is determined .`onstrains on product are identified &
detailed management plan is drawn. Project risk are
identified.
2)
  
or each identified
risk a detailed analysis is carried out, steps are taken
to reduce risk.
3)  
  
  After evaluation,a
development model for system is chosen. The decision
of choosing model is guided by risk factor.
 |
 

 x:If user interface risk are dominate, evolutionary

protyping might be appropriate.
4) 
   It involves reviewing the result of stage
preceding, weather to continue further loop of spiral.
If decided to cont. plans are drawn to next phase.
 It is risk driven process model.
Risk are explicitly accessed and resolved thought
the process.
 Risk assessment could cost more than
development. Applicable only to large systems.
     

     

˜ Iterative model helps to remove the demerits of

waterfall model. The phase of s/w development is
same, but construction and & delivery is done
repetitive mode.
˜ In 1st Iteration ,a less capable product are delivered
for use. This product satisfies only a subset of
requirements.
˜ In next teration, product with ncremental feature is
developed.  very Iteration consists of all waterfall
model. The complete product is divided into number
of releases. The developed product is released one
after another.
     

˜ This model repeats the activate of specification,

development & validation. nitially the system is
developed from abstract specification, which are
then refined with specification from the inputs
obtained from the customer.
     

  
It is used when less manpower is available for software
development & release deadlines are tight.
It is best suited for product development where it is
ensured that user has something to start with it.
  
Iteration may never end & the user may have endlessly
Wait for final product.
The cost estimation is also high.
R
!"#