Scribd
Upload
16 views

Classical Waterfall Model2

Uploaded by

chatterjee.shrijata
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

Classical Waterfall Model2

Uploaded by

chatterjee.shrijata
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Software Engineering

CLASSICAL WATERFALL MODEL

1
INTRODUCTION
3

WHEN TO USE WATERFALL MODEL?


4

WATERFALL MODEL PHASES


5
WATERFALL MODEL DIAGRAM
10

ADVANTAGES OF WATERFALL
MODEL
11
DISADVANTAGES OF WATERFALL
MODEL
INTRODUCTION
• Winston Royce introduced Waterfall Model
in 1970.

• Also called as Linear Sequential


Development
Model.

• Waterfall model approach was first SDLC


Model,used widely in Software Engineering
to ensure success of project.

• Each phase must be completed before the


next phase can begin.Output of one phase
will be input of next phase.

• This model is named “Waterfall Model”,


because its diagrammatic representation of
cascading waterfalls.
When to use classical waterfall model?

1. When the requirements are constant and not


changed regularly.

2. Application is not complicated and big.

3. A project is short and simple.

4. Where the tools and technology used is


consistent and is not changing.

5. When the resources sre well prepared and


are available to use.
Waterfall Model Phases
1. Requirement Analysis :-

• The aim of this phase is to understand the exact requirements of the customer and to document them
properly.

• They discuss functions, performance and interfacing requirement of the software.

• In this phase, Software Requirement Specification (SRS) document is created.

• It contained a detail description of what the system will do in the common language.

• SRS document serves as a contract between the development team and customers.

5
Waterfall Model Phases
2. Design Phase :-
• All gathered requirements are converted into suitable design.

• It defines the overall software architechture together with high level and detailed design.

• High level design include Algorithm, Flow charts, Decision tree, Database design etc.

• Low level design include Rough paper design, User interface components etc.

• Also finalized programming languages, Database or other Hardware & Software


requirements.

• All this work is documented as a Software Design Document (SSD).

6
Waterfall Model Phases
3. Development Phase :-
• In this phase software design is translated into source code using any suitable
programming language.

• The developer first developed in small programs called units after that integrated it.

• Unit testing is done in this phase to check weather each module is working properly
or not.

7
Waterfall Model Phases
4. Testing phase :-
• In this phase, Tester perform all the testing activities to make sure that the system
meets the client requirements or not.

• After combining all the unit modules, Integration testing is done for any faults and
failures.

• In case of any anomaly, report it.

• It generates Test cases & Test reports.

8
Waterfall Model Phases
5. Deployment & Maintenance phase :-

• The product is deployed in the customer enviorment or released into the market.

• In maintenance phase, There are some issues which come up in the client environment.

• To fixed those issues, patches are released.

• Also to enhance the product some better versions are released.

• Maintenance is done to deliver these changes in the customer environment.

9
Diagram of Classical Waterfall Model

10
Advantages of classical waterfall model

1. Simple and easy to understand and use.

2. Before the next phase of development , each phase must be completed.

3. Works well for smaller projects.

4. Requirements are very well understood & fixed.

5. Any changes in software is made during the process of development.

6. Process and results are well documented.

11
Disadvantages of classical waterfall model
1. High amount of risk and uncertainty.

2. Error can be fixed by only during the phase.

3. Not suitable for the projects where requirements are changing.

4. It becomes very difficult to move back to phase.

5. Not a good model for complex and object oriented projects.

6. Clients valuable feedback cannot be included with ongoing development phase.

12
thank you

You might also like