Categories

A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Problems with waterfall development model

Other software development models were developed (such as the Agile model) because it was felt that the sequential process defined in the Waterfall model was something that was not actually mapping what happens in practice, with the stated principle about one phase of the software lifecycle being completed before the next phase is initiated is not something that can happen in the real software development world. mainly because of their belief that it is impossible to get one phase of a software product’s lifecycle in a complete form before the next step is started. As an example, clients are almost never confident of their requirements being in a final form; once they see the prototype created by the software company that shows some of the workflows in action, that is when they can actually visualize their requirements; what this leads to is that on seeing these prototypes in action, the client may end up changing their requirements more than once, and this realizes in an impact to the next in line – people such as the requirements refiners and the designers may have to end up changing their output on a regular basis (or atleast more than once). In many cases, the clients end up changing their requirements after the design has been completed by the software company (with this change varying from small changes to large changes). If this happens, the design created by the software company must be modified to fit these new requirements, which can mean new effort and time, and also mean that quite a bit of effort that has already been put in could be wasted or may need to be modified, which would mean extra effort. In addition, designers cannot anticipate technical difficulties with their design, and typically these difficulties become clear during development, at which time it is expensive to change design.
Summary of problems:
– Client requirements are never complete at the time of requirement specification. They change, and it is realistic to anticipate that such change would occur
– Each phase needs information from the following phases to be fully complete. For example, requirements phase needs information from design phase as to what is feasible; design phase needs feedback from coding phase as to which design has the best chances of succeeding
– Builds in a waterfall model are typically available much later, but there is a need to have builds much earlier so as to build confidence
– Each phase has people who are specialised for that phase. It is a hard task to get people specialized for each phase, as well as make sure that they are connecting with each other for proper information transfer

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>