PROCESS MODELS

By Ravi Varma Asst Professor (REC)

Process model

They define a distinct set of activities that are required to engineer high-quality software workflow

DIFFERENT TYPES OF PROCESS MODELS

a. b. a. b.

Waterfall model Incremental process model Incremental model Rapid process development(RAD) model Evolutionary process model Prototype model Spiral model Unified process

WATERFALL

MODEL

It is developed by Royce in 1970. It is oldest Paradigm for software engineering It is also known as linear sequential model or Classical life cycle It is a systematic, sequential approach to software development

WATERFALL MODEL

Begin with customer specification of requirements and progresses through planning ,modeling, construction and deployment .

PROS AND CONS OF WATERFALL MODEL

Advantages
It is simple , step-by-step , focused and easy to follow. It is straightforward and divides the large task into a series of cleanly divided phases , each phase dealing with a logic concern

PROS AND CONS OF WATERFALL MODEL

Disadvantages
It is difficult state all requirements at the beginning of a project. This model is not suitable for accomaating any change. A working version of system is not seen until late in the projects life. It does not scale up to large projects. Real projects are rarely sequential.

INCREMENTAL PROCESS MODEL

These are used when initial requirement are reasonably well-defined but the over all scope precludes a purely linear process . To provide software functionality to user quickly.

There are two types of incremental process models. 1. Incremental model 2. Rapid application development model

INCREMENTAL MODEL

It combines elements of the waterfall model applied in an iterative fashion It delivers a series of releases, called increments, that provide progressively more functionality for customer as each increment is delivered When it is used, the first increment is often a core product. That is, basic requirements are addressed. supplementary features can be delivered in further increments. The core product is used by customer. As a result, a plan is developed for next increment Unlike prototyping, the incremental model focuses on the delivery of an operational product with each increment.

INCREMENTAL MODEL

INCREMENTAL MODEL

Advantages
Incremental development is particularly useful when staffing is unavailable. Early increments can be implemented with fewer people, and additional staff can be added to later increments Increments can be planned to manage technical risks

RAD MODEL

RAD is an incremental SW process model that emphasizes a short development cycle RAD model is a high-speed adaptation of the waterfall model. Rapid development is achieved by using a componentbased construction approach If requirements are well understood and project scope is constrained, the RAD process enables a development team to create a fully functional system within a very short time period If a business application can be modularized in a way that enables each major function to be completed in less than 3 months, it is a candidate for RAD Each major function can be addressed by a separate RAD team and then integrated to form a whole

RAD MODEL

DRAW BACKS OF RAD MODEL

For large, but scalable projects, RAD requires sufficient human resources to create right number of RAD teams. If developers and customers are not committed to the rapid-fire activities necessary, RAD projects will fail If a system cannot be properly modularized, building the components necessary for RAD will be problematic. RAD may not be appropriate when technical risks are high. Highly specialized & skilled developers are required and such developers are not easily available.

EVOLUTIONARY PROCESS MODELS

Evolutionary models are iterative. They are characterized in a manner that enables SW engineers to develop increasingly more complete versions of the software. These are useful especially when requirements are not clear.

There are two types of evolutionary models Prototype model Spiral model

PROTOTYPE MODEL
Customers often define a set of general objectives for Software, but doesnt specify detailed input requirements. prototyping paradigm assists the SW engineer and the customer to better understand what is to be built when requirements are fuzzy. When developer becomes unsure about efficiency of algorithms ,adaptability of OS and so on to solve this problem prototype is used.

PROTOTYPE MODEL
It begins with communication(objectives). A quick analysis take place. A quick design than occurs. Build a prototype. Deploy a prototype then evaluated by customer. Iteration of prototype continues till needs of customer satisfies.

PROTOTYPE MODEL

SPIRAL MODEL
It is evolutionary software process model . It couples the iterative nature of prototype and controlled and systematic nature of waterfall model . In this model risk analysis is carried out during planning activity approach . In this software is developed in a series of evolutionary releases. Unlike other models that ends when software delivered , but it can apply through out life of a software

SPIRAL MODEL
The first spiral might represent a Concept Development Project. the latter represents new product development and Product enhancement .

SPIRAL MODEL

Problems with spiral

It is difficult to convince the customer