Waterfall Method

waterfall-model-sdlc1

The waterfall method is a way of producing new code, it is a sequential design process. This methodology has eight steps or tasks. Those are onception, initiation, analysis, design, construction, testing, implementation, and maintenance. Obviously, this methodology has advantages and disadvantages.

Advantages:

  • One of the biggest advantages regarding the methodology is that it is possible to have a well-programmed schedule. Each progress is recorded so it is the possibility to improve the way we  work.
  • It is a great tool to costumers. They can have an idea regarding the time, size, and cost of the project.
  • It’s a great way of having a complete documentation.

Disadvantages:

  • If a step or task is completed, there is no way back to it.
  • The methodology requieres a lot of time just for trying to reach it.
  • If a mistake in the methodology is found, all the project must start from the beginning.
  • The methodology doesn’t take into account the customer once the waterfall method starts.

Retrieved from http://www.base36.com/2012/12/agile-waterfall-methodologies-a-side-by-side-comparison/.

 

 


Method came in like a Waterfall

Is a linear sequential Life Cycle Model, in which each phase is completed in order, there is no overlapping, and at the end of each a review is done.

The process consists of stateting requirements, analyze them, designing a solution or approach, architect a software framework for that solution, develop code, test, deploy, and maintaining.

This kind of method allows departmentalization and is very helpful for small projects without uncertain requirements.

RESOURCES:

TutorialsPoint

imagen1
Image from HubSpot

Waterfall Method

13966371577_1e545704a8_n
Retrieved from: http://www.flickr.com

Also known as Linear Sequential Life Cycle Model, is a popular version of the Systems Development Life Cycle Model. Is often considered as the traditional model for software development. In the Waterfall Model, each phase must be completed in order t move to the next step. Usually applied to small projects with o uncertain requirements; there is no overlapping between the phases. At the end of each phase, a review takes place to determine if the project is in the right path.

These are the steps of the Waterfall Method:

  1. Requirements: requirement are gathered and documented
  2. Analysis: Analyzed whether the requirements are valid or not
  3. Design: Determines the architecture of the software
  4. Implementation: Coding
  5. Testing: Testing each component for making sure it works as expected
  6. Deployment: Sending the program to the users
  7. Maintenance: Fix the problems found in the future

 

The advantages of using the Waterfall Method are:

  • Is easy to comprehend
  • Allows for departmentalization and control
  • Each stage can have a predetermined due time

 

 

Although, it has the disadvantage of being unable to go back if one of the steps has a mistake that was discovered in the next stages.

 

References:

ISTQB Exam Certification. (2016). What is Waterfall model- advantages, disadvantages and when to use it? August 8th, 2016, from ISTQB Exam Certification Website: http://istqbexamcertification.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/

Naveen. (2016). What is Waterfall Model in software testing and what are advantages and disadvantages of Waterfall Model. August 8th, 2016, from Testing Freak. Website: http://testingfreak.com/waterfall-model-software-testing-advantages-disadvantages-waterfall-model/

Tech Target. (2016). waterfall model. August 8th, 2016, from Tech Target Website: http://searchsoftwarequality.techtarget.com/definition/waterfall-model

Tutorials Point. (2016). SDLC – Waterfall Model. August 8th, 2016, from Tutorials Point Website: http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm

 


Software Lifecycle – Waterfall Method

If you remember last week's Software Lifecycle post, at the end I wrote that there are methodologies to follow the steps defined in the SDLC.

Today in this TC1019's express blog post, I will write about the Waterfall Model (WM), a software development methodology. This is a very simple topic.

The WM is called like that because each step is executed lineally and individually, with the output of one step being the input of the other, if you put it in a diagram, it would look like this:
Source
Hence the name waterfall method, it is the most basic and widely used model, also the first one to appear. Its application is recommended when the software requirements are well defined, the project is short and customer input is not usually required. The software definition must be stable.

Here are the advantages and disadvantages of this model:

Advantages
Disadvantages
  • Simple and easy
  • Well-defined stages and deliverables
  • Non-overlapping phases
  • Good for small and well-understood projects.
  • Once finished, the application cannot be changed easily.
  • The product is delivered at the end, no minimum viable product to test.
  • Not good for complex and long-running projects.
  • Specification changes are not easily incorporated.

Hope you learned something today :) 

Sources:
http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm
http://istqbexamcertification.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/




Software Lifecycle – Waterfall Method

If you remember last week's Software Lifecycle post, at the end I wrote that there are methodologies to follow the steps defined in the SDLC.

Today in this TC1019's express blog post, I will write about the Waterfall Model (WM), a software development methodology. This is a very simple topic.

The WM is called like that because each step is executed lineally and individually, with the output of one step being the input of the other, if you put it in a diagram, it would look like this:
Source
Hence the name waterfall method, it is the most basic and widely used model, also the first one to appear. Its application is recommended when the software requirements are well defined, the project is short and customer input is not usually required. The software definition must be stable.

Here are the advantages and disadvantages of this model:

Advantages
Disadvantages
  • Simple and easy
  • Well-defined stages and deliverables
  • Non-overlapping phases
  • Good for small and well-understood projects.
  • Once finished, the application cannot be changed easily.
  • The product is delivered at the end, no minimum viable product to test.
  • Not good for complex and long-running projects.
  • Specification changes are not easily incorporated.

Hope you learned something today :) 

Sources:
http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm
http://istqbexamcertification.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/




Waterfall model

http://www.rootsitservices.com/pictures/waterfall%20copy.jpg
Original at: http://www.rootsitservices.com/pictures/waterfall%20copy.jpg

This methodology of software development was one of the first to be implemented in order to have well made software.

In this model, all of the development of software is sliced in different steps, implemented one followed by another, always focused in different phases of the software development process. This phases are seperated to follow a sequential line. In other words, the process of Software development is sequantially.

Each of the phases means one different step:

  • Requirement and analysis: All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification doc.
  • Design: The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture.
  • Coding: With inputs from system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality which is referred to as Unit Testing.
  • Testing: All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.
  • Maintenance: There are some issues which come up in the client environment. To fix those issues patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

 

The following table lists out the pros and cons of Waterfall model:

Pros Cons
  • Simple and easy to understand and use
  • Easy to manage due to the rigidity of the model . each phase has specific deliverables and a review process.
  • Phases are processed and completed one at a time.
  • Continue reading "Waterfall model"