SDLC

1. Reported by: Honey Mae Llanto

2. It is a model which was
developed for software
development; that is to create
software. This was first put forth
by Winston Royce in 1970 in one of
his articles.

4.  Analysis
 Design
 Technical Design/ Detailed Design
 Implementation and Coding
 Testing
 Integration
 Acceptance Test
 Management and Maintenance

5.  The project requires the fulfillment of one
phase, before proceeding to the next.
 Provides structure to inexperienced staff
 Works well when quality is more important
than cost or schedule

6.  Many software projects are dependent upon
external factors.
 A huge amount of time is also wasted.
 Little opportunity for customer to preview
the system.
 All requirements must be known upfront

7.  Requirements are very well known
 Product definition is stable
 Technology is understood
 New version of an existing product

8.  This model is preferred for large, expensive
and complicated projects. It combines the
features of Prototyping and Waterfall
models.

10.  Envisioning Phase
 Planning Phase
 Developing Phase
 Stabilizing Phase
 Deploying Phase

11.  Early and frequent feedback from users
 Users see the system early because of rapid
prototyping tools
 Provides early indication of risks.
 Users can be closely tied to all lifecycle
steps

12.  Time spent for evaluating risks too large
 The model is complex
 Risk assessment expertise is required
 May be hard to define objective, verifiable
milestones that indicate readiness to
proceed through the next iteration

13.  When creation of a prototype is
appropriate
 Requirements are complex
 Significant changes are expected
 Users are unsure of their needs

14. End ^-_^