1. Waterfall Model
This is the most basic process of software development
life cycle that is widely followed in the industry. Here the developers follow
the order of the process in which the flow is getting to the final destination.
It's like a waterfall where there are a number of stages.
These phases have their own unique function and purpose.
There is, in fact, the four phases - requirements gathering and analysis phase,
software design, implementation and testing of programmed maintenance. The
fourth phase of this came one by one in the order given.
In the first stage all the system requirements are likely to
develop certain software recorded and analyzed.
Documents created that action into the next stage of the
software design phase. What needs to be emphasized here is that once you move to
the next stage will not be possible to update the requirements. So you have to
be very careful and cautious about the needs of the end user.
profit
Easy to implement and maintain.
The initial stage of requirements and a strict monitoring
system helps save time later in the development stage
minimal resource requirements and tests are carried out
after the completion of each stage.
deficiency
It is not possible to modify or update its terms
You can not make changes after you to the next stage.
Unable to start the next stage until the previous stage is
completed
2. V Model
This model is widely recognized as superior to the waterfall
model. Following the development activities and the implementation of the tests
performed on side by side in the form of downhill and uphill. In this model,
testing began at the unit level and spread toward the integration of the entire
system.
So, SDLC is divided into five stages - unit testing, integration
testing, regression testing, system testing and acceptance testing.
profit
Easy to use models since activities such as planning and
design of experiments testing is done before coding
Save time and improve your chances of success.
Defects are mostly found in the early stages and flow
downward from defects generally avoided
deficiency
It is a rigid model
Early prototypes of this product is not available for
software developed during the implementation phase
If there is a change in the middle of the road, then a test
document needs to be updated
3. The Agile Model
profit
Ensure customer satisfaction with rapid development and
continuous submission.
It is a flexible model as customers, developers and testers
constantly interact with one another
working software can be developed quickly and the product
can be adapted to changing needs on a regular basis
deficiency
In the case of software development of large and complex it
becomes difficult to assess the effort required at the beginning of the cycle
Due to constant interaction with customers, the project can
go off track if customers are not clear about the purpose
Also Read : Software Testing Company in Bay Area
4. Spiral Model
It is more like Agile models, but with a greater emphasis on
risk analysis. It has four stages - planning, risk analysis, and evaluation
techniques. Here gather requirements and risk assessment carried out on the
ground level and each spiral on build on it.
profit
chance of risk aversion increased because of the importance
of risk analysis.
Its a good model for large and complex systems.
Depending on the changed circumstances additional functionality
can be added at a later date
Software produced at the beginning of the cycle
deficiency
Its models are expensive and require highly specialized
expertise in risk analysis
It does not work well in simple projects
Also Read : Software Testing Company in San Francisco
5. Rational Unified Process
This model also consists of four phases, each arranged in a
number of separate iterations. The difference with other models is that each
iteration must separately meet the criteria set before the next step is done.
profit
With an emphasis on accurate documentation of this model is
able to resolve the risks associated with the changing needs of clients
Integration takes less time as the process throughout the
SDLC.
deficiency
The biggest disadvantage is that the team members need to be
an expert in their niche.
In large projects the continuous integration, may cause
confusion
Also Read : Software Testing Company in Boston
6. The rapid application development
This is another incremental models such as Agile models. The
following components are developed in parallel with each other. Then assembled
into product development.
profit
The development time is reduced due to the simultaneous
development of parts and components can be reused
Many integration problems solved because of the integration
of early stage
deficiency
It requires a strong team of developers is very capable with
individual success in identifying business needs
It is a model based modules, which can be modularized so
that the system can only be developed in this model
Such as high cost, this model is not suitable for projects
cheaper
Conclusion
Model testing software mentioned above is part of the SDLC
process. With the increasing awareness and demand for information technology,
has delivered more than 100+ types of tests used today in many large companies.
This process is constantly changing to suit the requirements, project and
preferences.
Also Read : Software Testing Company in USA
No comments:
Post a Comment