{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

SWEN_Week1 (1).docx - Running Head CRITIQUE OF THE...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
Running Head: CRITIQUE OF THE WATERFALL MODEL 1 Critique of the Waterfall Model University of Maryland University College
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CRITIQUE OF THE WATERFALL MODEL 2 The use of the Waterfall methodology is beginning to gain some reputation as being "old-fashioned" in comparison to other newer methodologies being used such as the Agile Methodologies. Waterfall is carried out in a steady, logical and sequential manner. There are several advantages and disadvantages to the old-fashioned method that will be reviewed in the following paragraphs. Waterfall method, like with all methodologies, are not necessarily meant for a specific type of project, therefore, examining each method and project is critical to ensuring that the specific approach is being used properly.
Background image of page 2
CRITIQUE OF THE WATERFALL MODEL 3 Figure 1. Depicts the waterfall model, the requirement information is first gathered which allows for the team to gain an understanding of what kind of software needs to be developed and the kind of things it needs to be able to do. Next, the design phase is where the requirements from the first stage are examined and the designed is being prepared. During the implementation phase the system is being developed in units and those are then combined in the next phase. Each unit is then tested and placed into the system which is then tested to ensure there are no errors. Once the system is tested the system is then deployed to the
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}