Professional Documents
Culture Documents
Process Mode1
Process Mode1
Process Mode1
1) Waterfall model: -
Waterfall model is an example of sequential model. In this model, the
software development activity is divided into different phases and
each phase consists of a series of task and has different objectives.
The waterfall Model shows the software development process in a
linear sequential flow.
In the waterfall, development of phases starts only when the previous
phase is completed.
PROS: -
Timescales are kept
No financial surprises
Testing is made easy
The outcome is crystal clear
Deal with issues in the design
What you plan is what you get
CONS: -
Needs can be difficult to define
Potential lack of flexibility
Longer delivery time
2) Prototype model: -
In the prototype model after taken the initial requirement of
developing software there are multiple iteration are there and it’s
depended on user.
Prototype model should be used when the desired system needs to
have a lot of interaction with the end users or we can say when the
user is changing the requirement of software rapidly then it’s better
that we should use prototype model.
Typically, online systems, web interfaces have a very high amount of
interaction with end users, are best suited for Prototype model.
PROS: -
3) Spiral model: -
Planning:
This phase starts with the gathering of business requirements. In the
subsequent spirals as the product matures, identification of system
requirements and unit requirements are done in this phase.This also includes
understanding of system requirements by continual communication between
the customer and the analyst. At the end of the spiral the product is deployed.
Design:
Design phase starts with the design in the baseline spiral and involves
architectural, logical design of modules, physical product design and final
design in the successive spirals.
Construct:
Construct phase refers to development of the final software product at every
spiral.
In the spiral when the product is just thought and the design is being
developed, a Proof of Concept (POC) is developed in this phase to get the
users’ feedback.
Then in the successive spirals with higher clarity on requirements and design
a working model of the software called build is developed with a version
number.
These versions are sent to the users for feedback.
Strengths
Introduces risk management
Prototyping controls costs
Evolutionary development
Release builds for beta testing
Marketing advantage
Weaknesses
Lack of risk management experience
Lack of milestones
Management is dubious of spiral process
Change in Management
Prototype Vs Production
4) Agile model: -
agile model is combination of iterative and incremental process
model.
Team will gather some information initial requirement for
software development.
Now team will take core requirement and implement the initial
increment, now this step will repeat again in this increment after
observing feedback from stack holder some new feature added.
PROS: -
Flexible.
Embracing uncertainty
Immediate feedback
Less Defective
CONS: -
Lack of documentation
Scope creep
Time
Lack of Predictability
Which Model to choose?