Software
testing also helps to identify errors, gaps or missing requirements in contrary
to the actual requirements. It can be either done manually or using automated
tools. Some say software testing as white box and black box testing. Want to
learn concepts from professionals see QA testing training by Learn IT Training.
The Waterfall model is the earliest SDLC approach that was
used for software development.
The waterfall Model illustrates the software development
process in a linear sequential flow. This means that any phase in the
development process begins only if the previous phase is complete. In this
waterfall model, the phases do not overlap.
Waterfall Model –
Design
Waterfall approach was first SDLC Model to be used widely in
Software Engineering to ensure success of the project. In "The
Waterfall" approach, the whole process of software development is divided
into separate phases. In this Waterfall model, typically, the outcome of one
phase acts as the input for the next phase sequentially.
Also
alternatively, if the Enterprise focused mainly on Java or C++ (Learn JAVA
scripting from JAVA training) in
development frameworks then one will be expected to possess a knowledge of
testing tools such as Selenium (Selenium online training by professionals), Cucumber and even other tools such as
SmartBear and TestNG, Ranorex and other available automation test suites. The primary skills that companies look for are if professionals can code and automate test scripts.
The following illustration is a representation of the different phases of the Waterfall Model.
The
sequential phases in waterfall model are:
Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement
specification document.
System Design −
The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying hardware
and system requirements and helps in defining the overall system architecture.
Implementation − with
inputs from the 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.
Integration and 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.
Deployment of system −
Once the functional and non-functional testing is done; the product is deployed
in the customer environment or released into the market.
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.
All these phases are cascaded to each other in which progress
is seen as flowing steadily downwards (like a waterfall) through the phases.
The next phase is started only after the defined set of goals are achieved for
previous phase and it is signed off, so the name "Waterfall Model".
In this model, phases do not overlap.
Waterfall model
application
Every software developed is different and requires a suitable
SDLC approach to be followed based on the internal and external factors. Some
situations where the use of Waterfall model is most appropriate are:
- Requirements are very well documented, clear and fixed.
- Product definition is stable.
- Technology is understood and is not dynamic.
- There are no ambiguous requirements.
- Ample resources with required expertise are available to support the product.
The advantages of waterfall development are that it allows
for departmentalization and control. A schedule can be set with deadlines for
each stage of development and a product can proceed through the development
process model phases one by one.
Development moves from concept, through design,
implementation, testing, installation, troubleshooting, and ends up at
operation and maintenance. Each phase of development proceeds in strict order.
Some of the advantages of waterfall model are as follows:
- Simple to use and easy to understand
- 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.
- Works well for smaller projects where requirements are very well understood.
- Clearly defined stages
- Well understood milestones
- Easy to arrange tasks
- Process and results are well documented
The disadvantage of waterfall development is that it does not
allow much reflection or revision. Once an application is in the testing stage,
it is very difficult to go back and change something that was not
well-documented or thought upon in the concept stage.
The major disadvantages of waterfall model as follows:
- No working software is produced until late during the life cycle.
- High amounts of risk and uncertainty.
- Not a good model for complex and object-oriented projects.
- Poor model for long and ongoing projects.
- Not suitable for the projects where requirements are at a moderate to high risk of changing. So, risk and uncertainty is high with this process model.
- It is difficult to measure progress within stages.
- Adjusting scope during the life cycle can end a project.
Learn
IT Training is a comprehensive repository for online and offline courses
offering high quality state-of-the-art IT and Business related e-learning trainings
and courses apart from SAP training
modules. It is one of the best global online training portals for the students.
We provide trainings throughout USA, UK,
Australia, UAE, Canada, Saudi Arabia, New Zealand, India and Many other
Countries with industry experts.
Want
to join with us to establish a testing career, Take a free demo today at: Click Here
For more details contact us:
VISIT: www.learnittraining.com
INDIA: +91 9912989639
USA: +12108585008
Contact@learnittraining.com
Skype:Learn IT Training
WhatsApp: +91 9912989639
No comments:
Post a Comment