SDI1 week3_1

10/02/2010

 
 

Compare

• Waterfall Model
  
• Prototype Model
  

   
   

SDLC

• Requirements/Analysis
  
• Design
  
• Implement
  
• Testing
  
• Deployment
  
• Maintenance
  

   
   

Requirements : can do

Sys requirements

User requirements

Client requirements

 
 

Specification(Unique) : it is

 
 

Prototype Documentation

Client meeting

Supervisor meeting

Journal

 
 

Suggest Modeling

Initial Step	Prototype Model
And then	Chose Waterfall or Prototype Model
Or	Some degree changeable from Prototype to Waterfall Model

 
 

Prototype Model's Pros

• Better understanding of requirements
  
• Good starting point
  

Prototype Model's Cons

• The prototype may be used as a starting point rather than thrown away.
  
• The prototype typically have poor design and quality.
  
• Bad decisions during prototyping may propagate to the real product.
  

   
   

Waterfall Model vs Prototype Model

Prototype Strength

• No need much requirement/detail.
  
• Easy to accept changes in the middle of project.
  
• Usually get little resistance from users.
  
• Involve the user in analysis & design.
  

Waterfall Strength

• Can make a reliable system.
  
• Cost benefit & payback analysis are more clear & closed.
  
• Time & budget could estimate in front.
  

 
 

Prototype Weakness

• Cost benefit & payback analysis are not clear & only estimate.
  
• Budget & time must flexible.
  
• If goal not clear, subject requirements from user will involve.
  

Waterfall Weakness

• Need detail spec of what & how to get the target. (more req.)
  
• Need big effort & budget if something important change in the middle of project