PROCESS MODEL

Def:

A process is a collection of activities, tasks and actions that are performed when some work
product is to be created. It is a rigid prescription for how to build computer software.

Waterfall model:
The waterfall model was first process model to be introduced. Because of the cascade from one phase
to another, this model is known as the ‘waterfall model’ or software life cycle.

In a waterfall model, each phase must be completed fully before the next phase can begin. This type of
software development model is basically used for the project which is small and there are no uncertain
requirements.

Diagram of waterfall model:

• Communication: communicate with customer to understand objectives and gather

requirements
• Planning: creates a “map” defines the work by describing the tasks, risks and resources, work
products and work schedule.
• Modeling: Create a “sketch”, what it looks like architecturally, how the constituent parts fit
together and other characteristics.
• Construction: This activity combines code generation and testing that is required to uncover
errors in the code
• Deployment: Delivered to the customer who evaluates the products and provides feedback
based on the evaluation.
Advantages :

 This model is simple and easy to understand and use.

 Easy to manage due to rigidity of the model.
 Phases are processed and completed one at a time.

Disadvantages:
 Poor model for long and ongoing projects.
 High amounts of risk and uncertainty.
 Not a good model for complex and object—oriented projects
When to use the waterfall model:
 This model is used only when the requirements are very well known, clear and fixed.
 When the project is short.
 There are no ambiguous requirements.

V-model
Def:

The v-model is a type of SDLC model where process executes in a sequential manner in V-shape. It is
also known as verification and validation model.

Development of each step directly associated with the testing phase. The next phase starts only after
completion of the previous phase.

Advantages:

 This model is simple and easy to understand and use.

 V-model is used for small projects where project requirements are clear.
 Utility of resources is high.
 In v-model, each phase has specific deliverables.

Disadvantages:

 Very rigid, like the waterfall model.

 High risk and uncertainty
 It is not good for complex and object-oriented projects.

Limits of v-model:

 The placing of contracts for service is not regulated.

 The v-model addresses software development within a project rather than a whole organization.

When to use the waterfall model:

 The v-shaped model should be used for small to medium sized projects where
requirements are clearly defined and fixed.
 The v-model should be chosen when ample technical resources are available with
needed technical expertise.