Software Development Process

By: KUMAR NISHANT (090101096) KUNAL JINDAL (090101097)

What is Software development process

A software development process, also known as a software development life cycle (SDLC), is a structure imposed on the development of a software product. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process.

Software development models

Several models exist to streamline the development process. Each one has its pros and cons, and it's up to the development team to adopt the most appropriate one for the project. Sometimes a combination of the models may be more suitable.

Waterfall model

The waterfall model shows a process, where developers are to follow these phases in order:

1.Requirements specification 2.System design 3.Implementation and Integration 4.Testing (or Validation) 5.Deployment (or Installation) 6.Maintenance

Advantages of waterfall model

Oldest and most widely used Systematic and sequential approach. Requirements are well understood Explicit recognition of phases. Errors can be identified at early stages

Disadvantages of waterfall

Complete set of user requirement Time consuming Doesnt incorporate risk assessment Real projects rarely follow sequential flow Not for new software projects

What is Wicked Problem

Problems we cant really understand until weve developed a solution.

That is not what I want ... but now I know what I do want!

Prototyping Model
Put together a team of Smart Guys from multiple disciplines Develop the GUI on Paper

Listen To Customer

Code the GUI in a fast language (Make it look like its working)
Show it to the USERS Get Feedback Customer Test Drives Mockup

Build/Revise Mockup

Problems With Prototyping

No Current Documents.
Prototype is not baseline functionality Startup costs for building a prototype may be high

Developing team may compromise during prototype implementation

Advantage
Faster development
Improved communication b/w user & team Easy requirement analysis User involvement during development More errors can be identified at each prototype

Iterative model
The iterative model is also called increment model because we increment the requirement in each cycle. This model has the same phases as the waterfall model , but with fewer restrictions.

Spiral model
Combining elements of both design and prototyping-in-stages. An effort to combine advantages of top-down and bottomup concepts. The features of the prototyping model and the waterfall model.

Operational Prototype

Prototype 1

Prototype 2

Prototype 3

14

Spiral Model Strength and Weaknesses

o Strengths
Introduces risk management Prototyping controls costs Evolutionary development flexible design Release builds for beta testing No need to define all requirements in detail at early stage

o Weaknesses
Lack of risk management experience Doesn't work well for smaller projects Can be a costly & complex model to use

THANK YOU