Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Waterfall Model Presentation

A computer studies assignment-about the waterfall process, used to make a software program
by

Matt Roden

on 2 June 2011

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Waterfall Model Presentation

Waterfall Model A sequential design process used in software development, whose progress can be recorded in a flowing downward pattern, like a... The Creation The Phases Conclusion The waterfall development model originates from: By: Matt Roden Waterfall!! Winston Royce was the first one to describe the
Waterfall Model back in 1970.

He described it as innovative, yet flawed. the manufacturing and construction industries. Like Software Development, they are highly structured physical environments in which any changes are costly, if not impossible. Conception/Initiation Production Analysis Design Construction Testing Maintenance Waterfall Model - Phases There have also been many Modified Models,
that are based on the original. Requirements Design Implementation Verification Maintenance The Requirements Phase is
a complete description of the behavior
of a system to be developed. SRS is implemented. Software Requirements Specification. Included in this Phase are:
Set of Use Cases that describe user interactions
Non-functional requirements The Design Phase is
a process of problem solving and planning
for a specific software solution. Included in this Phase are:
Low-Level Component issues
Algorithm Implementation issues
Architectural View The Implementation Phase is
coming to a realization of the application
and attempting to execute the plan. Included in this Phase are:
Requirements Analysis
Scope Analysis
Customizations
User Policies
Training and Delivery The Verification Phase is
the actual final debugging and installation of
a computer system so it can be executed. Included in this Phase are:
Interactive Debugging
Control Flow
Integration Testing
Logging
Monitoring
Profiling The Maintenance Phase is
the modification of the software after the
initial delivery to correct faults and improve
performance. There are many different Modified Models. Any Questions?? Conclusion about Waterfall Model In my opinion, the Waterfall Model
(especially the Modified Models) can be helpful in the implementation of System Software.

It was originally used as a way to provide structure to a cluttered, often confusing, uneffective, and outdated system.

While the original was very flawed, some of the Modified Models are still used today. References http://www.waterfall-model.com/

http://withfriendship.com/user/boss/waterfall-model.php

http://www.selectbs.com/analysis-and-design/what-is-the-waterfall-model

Video: http://www.youtube.com/watch?v=X1c2--sP3o0

http://en.wikipedia.org/wiki/Waterfall_model (Checked all information with other sources) Pros and Cons Less Effort
Less Time
Less Money
Less Documentation
Well Known (Now)
Better for Large Projects Dependant
Client is External Factor
Changing Requirements
Phases are difficult to put in time frame
Usually Large Phases
Time Wasted waiting for next Phase
Design Modifications can be timely Included in this Phase are:
Correct Faults
Fix Bugs
Implement Upgrades
Align with Customer Priorities
Late Testing
Full transcript