1.

Predictive Model

► This approach is generally referred to as the ‘Traditional Model’ since it has been in
practice for quite some time now. In the field of Information Technology it is generally
referred to as the (Waterfall, Prototyping, RAD).
► It would be ideal to choose the Predictive Model of Software Development when we
exactly know what we are building. When there is no ambiguity(doubt, uncertainty) in
requirement Waterfall Model would be the most ideal method for Software Development
because of the considerable amount of control it gives one the cost and time of the
project.
► In a Predictive Model, the exact number of resources required to build the project, the
amount of time they will have to work to complete the project and the exact amount of
cost that would be required to take the project live to production can be calculated even
before the start of the project.
► This greatly helps in planning the finances and resource allocation of the project. This
also helps the stakeholders be on top of the expected time of completion of the project.
► Let’s assume that a large corporation is trying to clean its employee portal. The ideal
development model for this would be the Predictive Model (Water-Fall Model) because
the requirements are already known and could be frozen.
i. Waterfall Model
The Waterfall Model was first Process Model to be introduced. It is very simple to
understand and use. In a Waterfall model, each phase must be completed before the
next phase can begin and there is no overlapping in the phases. Waterfall model is the
earliest SDLC approach that was used for software development.

In “The Waterfall” approach, the whole process of software development is divided into
separate phases. The outcome of one phase acts as the input for the next phase
sequentially. This means that any phase in the development process begins only if the
previous phase is complete. The waterfall model is a sequential design process in
which progress is seen as flowing steadily downwards (like a waterfall) through the
phases of Conception, Initiation, Analysis, Design, Construction, Testing,
Production/Implementation and Maintenance.
As the Waterfall Model illustrates the software development process in a linear
sequential flow; hence it is also referred to as a Linear-Sequential Life Cycle Model.
 Advantages
Basic model
Simple to use
Disadvantages
No feedback customer involved at last
No experiment no rigid
No parallelism
High Risk
60% effort on maintainance
ii. Prototyping Model

A prototype is an early sample, model, or release of a product

built to test a concept or process or to act as a thing to be
replicated or learned from. It is a term used in a variety of
contexts, including semantics, design, electronics, and software
programming. A prototype is generally used to evaluate a new
design to enhance precision by system analysts and users.
Prototyping serves to provide specifications for a real, working
system rather than a theoretical one. In some design workflow
models, creating a prototype (a process sometimes called
materialization) is the step between the formalization and the
evaluation of an idea.
For example Marvelapp, Pencil, In vision etc.
Prototype for Mobile
iii. RAD (Rapid Application Development)

The RAD (Rapid Application Development) model is based on

prototyping and iterative development with no specific planning
involved. The process of writing the software itself involves the
planning required for developing the product.
Rapid Application Development focuses on gathering customer
requirements through workshops or focus groups, early testing
of the prototypes by the customer using iterative concept, reuse
of the existing prototypes (components), continuous integration
and rapid delivery.
Advantage of RAD Model

○ This model is flexible for change.

○ In this model, changes are adoptable.
○ Each phase in RAD brings highest priority functionality to the customer.
○ It reduced development time.
○ It increases the reusability of features.

Disadvantage of RAD Model

○ It required highly skilled designers.

○ All application is not compatible with RAD.
○ For smaller projects, we cannot use the RAD model.
○ On the high technical risk, it's not suitable.
○ Required user involvement.