Access over 20 million homework & study documents
search

CS 349 Waterfall Development Method Paper

Content type

User Generated

Subject

Software Development

Type

Research Paper

Rating

Showing Page:
1/3
CS349
Kodie Turner
5/24/20
Waterfall development method
Waterfall methodology is a linear project management approach, where Client requirements are
gathered at the beginning of the project, and then a finalized project plan is created to reach those
requirements. The waterfall approach was conceived in 1970, by Winston W. Royce, and it was
quickly taken in by a variety of industries due to its logical sequencing and easily implemented
into the works of projects.
Many consider the waterfall method to be the go-to traditional software development method.
The waterfall method is a linear model that primarily consists of sequential phases (requirements,
design, implementation, verification, maintenance) focusing on precise goals. Each phase must
be 100% complete before the next phase can initiate. There’s usually no process for going
backwards to readjust the project or direction.
If the waterfall model is to be executed properly, each of the above phases must execute in a
linear fashion otherwise it fails. Each phase is to be completed before the next phase can begin,
and phases can never be repeated, unless there is a failure that happens during verification or
maintenance phase.

Sign up to view the full document!

lock_open Sign Up
Showing Page:
2/3
pros:
Early stages in the software production cycle can reduce costs at later stages. For example, a
problem found in the early on is cheaper to fix than the same bug found at the end in the process.
Waterfall methodologies result in a project schedule with 2040% of the time invested for the
first couple phases, 3040% to coding, and the rest to testing and implementing. The actual
project organization needs to be highly structured. Most medium and large projects will have
detailed set of procedures and controls, which regulate everything on the project.
Another pro is that the waterfall model places emphasis on documentation as well as source
code. In less thoroughly designed and documented methodologies, knowledge is lost if members
of the time leave before the project is finished, and it would prove difficult for a project to
recover from that. If a fully working design document is present, new team members or even
entirely new teams should be able to familiarize themselves by reading the documents.
cons:

Sign up to view the full document!

lock_open Sign Up
Showing Page:
3/3

Sign up to view the full document!

lock_open Sign Up

Unformatted Attachment Preview

CS349 Kodie Turner 5/24/20 Waterfall development method Waterfall methodology is a linear project management approach, where Client requirements are gathered at the beginning of the project, and then a finalized project plan is created to reach those requirements. The waterfall approach was conceived in 1970, by Winston W. Royce, and it was quickly taken in by a variety of industries due to its logical sequencing and easily implemented into the works of projects. Many consider the waterfall method to be the go-to traditional software development method. The waterfall method is a linear model that primarily consists of sequential phases (requirements, design, implementation, verification, maintenance) focusing on precise goals. Each phase must be 100% complete before the next phase can initiate. There’s usually no process for going backwards to readjust the project or direction. If ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Anonymous
Great content here. Definitely a returning customer.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4