software project management->Waterfall model

1. Software Project Management
Waterfall model
By : Mohammad umair khan

2.  The waterfall model is a model which was developed for
software development; that is to create software. It is called
as such because the model develops systematically from one
phase to other in a downward fashion, like a waterfall.

3. The history of the Waterfall model is somewhat disrupted. It
is often said or believed that the model was first put forth by
Winston Royce in 1970 in one of his articles; whereas he did
not even used the word “waterfall.” In fact Royce later
presented this model to depict a failure or a flaw in a non-
working model. So later on, this term was mostly used in
writing about something that is often wrongly done in the
process of software development – like a common
malpractice.

5. Phases of waterfall
• Definition Study/Analysis
• Basic Design
• Technical Design/Detailed Design
• Construction
• Testing
• Integration
• Management and
• Maintenance.

6. Phases of waterfall
• Definition Study / Analysis:
During this phase research is being conducted which includes
brainstorming about the software, what it is going to be and
what purpose is it going to fulfill.
• Basic Design:
If the first phase gets successfully completed and a well
thought out plan for the software development has been laid
then the next step involves formulating the basic design of the
software on paper.
• Technical Design / Detail Design:
After the basic design gets approved, then a more elaborated
technical design can be planned. Here the functions of each of
the part are decided and the engineering units are placed for
example modules, programs etc.

7. • Construction / Implementation:
In this phase the source code of the programs is written.
• Testing:
At this phase, the whole design and its construction is put
under a test to check its functionality. If there are any errors
then they will surface at this point of the process.
• Integration:
in the phase of Integration, the company puts it in use after the
system has been successfully tested.
• Management and Maintenance:
Maintenance and management is needed to ensure that the
system will continue to perform as desired.

8.  Requirements will be set and these wouldn't be changed.
 As everything is documented a new team member can easily
understand what's to be done.
 Implementers have to follow the design accurately.
 A waterfall model helps find problems earlier on which can cost a
business less than if it was found later on.
 reduces the risk of schedule slippage, or of customer
expectations not being met.

9.  If requirements may change the Waterfall model may not work.
 Many believe it is impossible to make one stage of the projects
life cycle perfect.
 Difficult to estimate time and cost for each stage of the
development process.
 Constant testing of the design is needed. It does not allow for
much reflection or revision.
 Designs that look feasible on paper turn out to be expensive or
difficult in practice.

10.  Whether you should use it or not depends largely on
 how well you believe you understand your customer's needs
 The model is recommended for use only in projects which are
relatively stable and where customer needs can be clearly
identified at an early stage.

11.  Managing the Development of Large
Software Systems.
 Waterfall model considered harmful
 Understanding the pros and cons of the
Waterfall Model of software development
 Waterfall Model

12. Thanks
Please any question...