c



    



The  is a sequential design process, often used in software development processes, in
which progress is seen as flowing steadily downwards (like a waterfall) through the phases of
Conception, Initiation, Analysis, Design, Construction, Testing and Maintenance

á
i
  

 


 
 

 

 






  






 
    
 



 






 






 
á
 

 



  





   
 
 




 




 










     



 
á

 
  



   



 


 



  

   

!
 


 


á 

 



   
 

  
 
 


 






"





 

 


# 
$ 

  
 
 
%  


Advantages of 

The waterfall model provides a clear and easy to follow sequence of activities; it is simple and can be
understood without many complications. Furthermore, particular issues on quality management are
addressed through the Justification and Confirmation section that is being followed in each phase of the
model, and in addition to this, this model will facilitate project management and control by the need to
complete each stage before moving to the succeeding phase.

1. Clear project objectives.

2. Stable project requirements.
Ñ. Progress of system is measurable.
4. Strict sign-off requirements.

Disadvantages of Waterfall Model

The waterfall model lacks prescribed technique of implementing management control over a project;
planning, controlling, and risk management are not enveloped within the model itself. Moreover,
forecasting the estimated time and cost are complicated for each stage. The life cycle can take long as
the original requirements may no longer be valid, with little possibility for prototyping.

1. Time consuming
2. Never backward (Traditional)
Ñ. Little room for iteration
4. Difficulty responding to changes

c

The  is a software development process combining elements of both design and
prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. Also
known as the spiral lifecycle model (or spiral development), it is a systems development method (SDM)
used in information technology (IT). This model of development combines the features of the
prototyping model and the waterfall model. The spiral model is intended for large, expensive and
complicated projects

Advantages of c

1. Avoidance of Risk is enhanced.
2. Strong approval and documentation control.
Ñ. Implementation has priority over functionality.
4. Additional Functionality can be added at a later date.

Disadvantages of Spiral Model

1. Highly customized limiting re-usability
2. Applied differently for each application
Ñ. Risk of not meeting budget or schedule
4. Possibility to end up implemented as the Waterfall framework

è

A prototype is a working model that is functionally equivalent to a component of the product.

In many instances the client only has a general view of what is expected from the software product. In
such a scenario where there is an absence of detailed information regarding the input to the system, the
processing needs and the output requirements, the prototyping model may be employed.

This model reflects an attempt to increase the flexibility of the development process by allowing the
client to interact and experiment with a working representation of the product. The developmental
process only continues once the client is satisfied with the functioning of the prototype. At that stage
the developer determines the specifications of the client͛s real needs.

Advantages of è
1. Strong Dialogue between users and developers
2. Missing functionality can be identified easily
Ñ. Confusing or difficult functions can be identified
4. Requirements validation, Quick implementation of, incomplete, but
functional, application
5. May generate specifications for a production application
6. Environment to resolve unclear objectives
7. Encourages innovation and flexible designs

Disadvantages of Prototype model

1. Contract may be awarded without rigorous evaluation of Prototype
2. Identifying non-functional elements difficult to document
Ñ. Incomplete application may cause application not to be used as the
full system was designed
4. Incomplete or inadequate problem analysis
5. Client may be unknowledgeable
6. Approval process and requirement is not strict
7. Requirements may frequently change significantly
0


  



 




 

   


 




 
     
& 


   


 


 
 
& 
 '

   
 
 



 
 





 

0


  




0 

  
  




 

 
 


    á
  




#()


  
 
 
 á
! 






  
 


  

!
 

  




 

( 
 
#()

 *

1. Flexible and adaptable to changes.

2. Prototyping applications gives users a tangible description from which to judge whether critical
system requirements are being met by the system. Report output can be compared with existing
reports. Data entry forms can be reviewed for completeness of all fields, navigation, data access
(drop down lists,checkboxes, radio buttons, etc.).
Ñ. RAD generally incorporates short development cycles - users see the RAD product quickly.
4. RAD involves user participation thereby increasing chances of early user community acceptance.
5. RAD realizes an overall reduction in project risk.
6. Pareto's 80 - 20 Rule usually results in reducing the costs to create a custom system.

) 
 #()

 *

1. Anknown cost of product. As mentioned above, this problem can be alleviated by the customer
agreeing to a limited amount of rework in the RAD process.
2. It may be difficult for many important users to commit the time required for success of the RAD
process.

 

 

&


 


  
 

á
 













 


 & 

 

 


 

 



 



&


  




 


 

 %
 

*
˜+ 
#



 



 
, 
 



˜á
 
   



 
  


-.


! 
! 
 
 

 

-/
 

0
    





 
-'
 
 



 
-'
 

!

! 



  
 
 
 
-' 
 
 



 


   


-'  
 
  

 

-1


 

   

 
 


 



 



   

 
 

 



  
 

This is an adaptation of the spiral model which emphasis is explicitly placed on the involvement of
the client in a negotiation process at the genesis of the product development. Ideally, the developer
would simply ask the customer what is required and the customer would provide sufficient detail to
proceed. Anfortunately this rarely happens and significant negotiations between both parties are
required to balance functionality, performance, etc͙ with cost and time-to-market considerations.

á


 
 




 
    

  



 
 






 




 
%
 

á



 £2
3 
4%
 
2340)


 %
 
 
 
% 

  

 %
 

 

   

 




 

52
3 
( 
 
23(0' 

%
 
  

 





 
 
 




6& 4
 3 &430


 
 %
 

 


  
 
   7  

  
   


  
  
 
 


  


˜ 
 
   
   



  


 
 !
 

˜ 3

 

!



 


á    

The concurrent development model, sometimes called concurrent engineering

The concurrent process model can be represented schematically as a series of major

technical activities, tasks, and their associated states. For example, the engineering
activity defined for the spiral model is accomplished by invoking the
following tasks: prototyping and/or analysis modeling, requirements specification,
and design.

The activity-analysis-may be in any one of the states noted

at any given time. Similarly, other activities (e.g., design or customer communication)
can be represented in an analogous manner. All activities exist concurrently but
reside in different states. For example, early in a project the customer communication
activity has completed its first iteration and exists in the awaiting changes state. The analysis activity
(which existed in the none state while initial customer communication was completed) now makes a
transition into the under development state. If, however, the customer indicates that changes in
requirements must be made, the analysis activity moves from the under development state into the
awaiting changes state.
The concurrent process model defines a series of events that will trigger transitions
from state to state for each of the software engineering activities.

  

ù It͛s flexible ʹ the number incremental releases can be determined by the project team

ù Immediate feedback from testing

ù New features can be added late in the project

ù No surprises during formal validation because testing has been continuous

   

ù The SRS must be continually updated to reflect changes

ù It requires discipline to avoid adding too many new features too late in the project

Ê
  



Ê

 
 



 Ê
!


 





Ê    



  

 ,


  



  

   
   
 

 

á  

  
 



 

  

  




 
 
 
  ,    
 
á


 




  
 
  



& 
   



 
  

  

 
"




 




 



  


!
 


 


+ 






   
   
 


  
3

   
 



+





  +

4


( 
 
+4(

 

 

8ë i
9
  

  

  
 
 
    

 

á


 

    
á


  

 



   

 


!
 

( 
 3


 :
/
*

˜ The component based development model leads to software re-used and re-usability provides a
number of tangible benefits.
˜ It leads to reduction in development cycle time.
˜ It leads to significant reduction in project cost.
˜ It leads to significant increase in productivity.

   

˜ á
 








(

    






  



 


 


 


 

 86;9
˜ A 
  


&





 



 

  

 





 
 
%
 

 



 




 



 4
 

%

 
 




 



 






 
 



 
  #



 
 
  




  

   
 

!




 
    


á 
      




 á 
!
 

   
  




 
 


 


 
  8<=9
˜ Ê 


  

 á

 



 
 

 
  


 







 




 




 
 

 





 
(



  
 
 
 




 
  





  

  
 
 
 

   




 86;9
˜ Ê

  

 
 


 





 


 

   



 
 
 



 



  

  

 


  


 
 



 
 


 

 



 869
˜ 0
  
 
(

   




 


 ! 



 



!  

 
 


   
 



  
     
 

 
  ! 
 



  


 

 
 
  
  


 
 


  

 

!  
 

 

 

 
8>9

c   

+




   







 
' 
  
 $ 




 

  

 

 
%
 +





  



 


 


 
 


/ 
*
 



á

 

 






  

 

*

£ #



 
  #



  
5 + 
)

6 &
 
 ; á
 ? 
< )


 &  
= /



&  
 




  
 
 

 

 
#


 



 

  
   
   
  
 

 
 
 
#


 



 

  

 





@
 








 
  

%
 
    

 

  

 

 

  

 $


á  
 

 

 



  
 
 


 







 


/ 
*+



á
!
 
  +


!



  
 





 
 
&£

: :


 
 
 





 


  



!

  

 

  



 


 !


 
  




 



*




 
!   
 



 



á
+,

  



 
  
 
 



  
 
   
*

£ 

 *
   
 



 



 

 

%
 



 
  @
5 #! * 


  



 
  
  



!@
6




   
%
 *




    




 

  @
#!




 ,
     
 
  


 
 

 
  
 




 "




 


  
  *

£ 



 ,
!  

 

 
 


  

    
!



 

 
 


 




 


 




 
5 & 




   ! 
  
 
   
%
 

! 







  
 


 
%
 
6 . 



 ! 
!
  !


 
 

!

  
 





 
 
 
 

%
 
 
  
 



 
 ! 




  
 
 
 



 !





   

  
  
 
  
& 

! 

 

 



 

  





  

 
 
 
  
 


 


  



 
  

 





/ 
*&
 


 



 

&
 




 8£9


     
 


  
 
%
  
 

 

  

 




 
 
 
&
 






8

  9
 







 
  
 

  


 
 !  

  
 

 






/ 
*(
 




 
(
 




 

 




  







 
    
(





!




  

 
á


!
 

 



 

 


á



   


*

˜ &' 


1

A1
 


 
 

 

 


 

  

á

  



    


  !
 

!
 


 
 
 





 

 

 



  


 



 B
   


  





 


$  !
  


   



)
 
 




  
 



)

 




 
4 
 

 






  




á





    





 
 


 


 
 
   




 

(   
  

   
  

 
 
    
 



˜ +