Scribd
Upload
60 views13 pages

4 Models of SDLC's

The document describes several software development models: - Waterfall model is a sequential design process with distinct phases like requirements, design, coding, testing, etc. with no backtracking. - Spiral model builds software incrementally in loops/cycles called spirals with each spiral addressing a portion of the requirements and allowing revisions. - V-Model incorporates verification and validation activities throughout the development phases for early testing. - Prototype model develops an initial prototype to get early customer feedback before full development. - Hybrid models combine elements of different models like Spiral and Prototype to suit specific project needs.

Uploaded by

Dhruva Shirsale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
60 views13 pages

4 Models of SDLC's

The document describes several software development models: - Waterfall model is a sequential design process with distinct phases like requirements, design, coding, testing, etc. with no backtracking. - Spiral model builds software incrementally in loops/cycles called spirals with each spiral addressing a portion of the requirements and allowing revisions. - V-Model incorporates verification and validation activities throughout the development phases for early testing. - Prototype model develops an initial prototype to get early customer feedback before full development. - Hybrid models combine elements of different models like Spiral and Prototype to suit specific project needs.

Uploaded by

Dhruva Shirsale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Waterfall model

l It is a traditional model

It is a sequential design process, often used in SDLC, in which the


progress is seen as flowing steadily downwards (like a waterfall),
through the different phases
Requirements Collection :-

- done by Business Analysts and Product Analysts

- gathering requirements

- translates business language into software language For ex, let us


consider the example of a banking software.

Feasibility Study :-

- done by software team consisting of project managers, business


analysts, architects, finance, HR, developers but not testers

- architect – is the person who tells whether the product can be


developed and if yes, then which technology is best suited to develop it.

- here we check for,

- technical feasibility
- financial feasibility
- resource feasibility

Design :-

There are 2 stages in design,

HLD – High Level Design


LLD – Low Level Design

HLD
– gives the architecture of the software product to be developed and is
done by architects and senior developers

LLD
– done by senior developers. It describes how each and every feature in
the product should work and how every component should work.

Here, only the design will be there and not the code.

For ex, let us consider the example of building a house

Coding / Programming :-

- done by all developers – seniors, juniors, freshers

- this is the process where we start building the software and start
writing the code for the product

Testing :-

- done by test engineers

- it is the process of checking for all defects and rectifying it.

Installation / Deployment :-

- done by installation engineers

- to install the product at a client’s place for using after the software has
been developed and tested.

For ex, consider the example of a software to be developed and installed


at Reliance petrol bunk.

Maintenance:-

- here as the customer uses the product, he finds certain bugs and
defects and sends the product back for error correction and bug fixing.

- bug fixing takes place


- minor changes like adding, deleting or modifying any small feature in
the software product

100 % testing is not possible – because, the way testers test the
product is different from the way customers use the product

Drawbacks of Waterfall Model :


- backtracking is not possible i.e, we cannot back and change
requirements once the design stage is reached. Thus the
requirements are freezed once the design of the software product is
started.

– testing is a small phase which is done after coding. Requirement is not


tested, design is not tested, if there is a bug in the requirement, it goes
on till the end and leads to lot of re work

Advantages of waterfall model –


requirements do not change nor does design and code, so we get a
stable product.

Applications of waterfall model :-


Used in – developing a simple application
- for short term projects
- whenever we are sure that the requirements will not change

For ex, waterfall model can be used in developing a simple calculator as


the functions of addition, subtraction etc and the numbers will not
change for a long time.
Spiral Model

The module A – requirements of the module is collected first and then the
module is designed. The coding of module A is done after which it is tested for
defects and bugs.
The module B – once module A has been built, we start the same process for
module B. But while testing module B, we test for 3 conditions – a)test module
B b)test integration of module B with A c)test module A.
The module C – after building module A,B, we start the same process for
module C. Here we test for the following conditions – 1) test module c, b, a 2)
test for integration of C and B, C and A, A and B.
And thus the cycle continues for different modules. Thus in the above example,
module B can be built only after module A has been built correctly and
similarly for module C
Advantages of Spiral Model :-
1) Requirement changes are allowed.
2) After we develop one feature / module of the product, then and only then
we can go on to develop the next module of the product.

Drawbacks of Spiral Model –


Traditional model and thus developers only did testing job as well.

Applications of Spiral Model


- whenever there is dependency in building the different modules of the
software, then we use Spiral Model.
- whenever the customer gives the requirements in stages, we develop the
product in stages.
V – MODEL / V & V MODEL (Verification and
Validation Model )
This model came up in order to overcome the drawback of waterfall model –
here testing starts from the requirement stage itself.
1) In the first stage, the client send the CRS both to developers and testers.
The developers translate the CRS to the SRS.
The testers do the following tests on CRS,
1. Review CRS
a. conflicts in the requirements
b. missing requirements
c. wrong requirements
2. Write Acceptance Test plan
3. Write Acceptance Test cases
The testing team reviews the CRS and identifies mistakes and defects and send
it to the development team for correcting the bugs. The development updates
the CRS and continues developing SRS simultaneously.

2 ) In the next stage, the SRS is sent to the testing team for review and the
developers start building the HLD of the product. The testers do the following
tests on SRS,
1. Review SRS against CRS
a. every CRS is converted to SRS
b. CRS not converted properly to SRS
2. Write System Test plan
3. Write System Test case The testing team reviews every detail of the SRS if
the CRS has been converted properly to SRS.

3 ) In the next stage, the developers start building the LLD of the product.
The testers do the following tests on HLD,
1. Review HLD
2. Write Integration test plan
3. Write Integration test case
4 ) In the next stage, the developers start with the coding of the product.
The testing team carries out the following tasks,
1. Review LLD
2. Write Functional test plan
3. Write Functional Test case
After coding, the developers themselves carry out unit testing or also known as
white box testing. Here the developers check each and every line of code and if
the code is correct. After white-box testing, the s/w product is sent to the
testing team which tests the s/w product and carries out functional testing,
integration testing, system testing and acceptance testing and finally deliver
the product to the client

Advantages of V&V model


1) Testing starts in very early stages of product development which avoids
downward flow of defects which in turn reduces lot of rework
2) Testing is involved in every stage of product development
3) Deliverables are parallel/simultaneous – as developers are building SRS,
testers are testing CRS and also writing ATP and ATC and so on. Thus as the
developers give the finished product to testing team, the testing team is ready
with all the test plans and test cases and thus the project is completed fast.
4) Total investment is less – as there is no downward flow of defects. Thus
there is less or no re-work

Drawbacks of V&V model


1) Initial investment is more – because right from the beginning testing team is
needed
2) More documentation work – because of the test plans and test cases and all
other documents

Applications of V&V model


We go for V&V model in the following cases,
1) for long term projects
2) for complex applications
3) when customer is expecting a very high quality product within stipulated
time frame because every stage is tested and developers & testing team are
working in parallel

PROTOTYPE DEVELOPMENT MODEL


Advantages of Prototype model
1) In the beginning itself, we set the expectation of the client.
2) There is clear communication b/w development team and client as to the
requirements and the final outcome of the project
3) Major advantage is – customer gets the opportunity in the beginning itself
to ask for changes in requirements as it is easy to do requirement changes in
prototype rather than real applications. Thus costs are less and expectations
are met.
Drawbacks of Prototype model
1) There is delay in starting the real project
2) To improve the communication, there is an investment needed in building
the prototype.
Applications
We use this model when,
1) Customer is new to the s/w
2) When developers are new to the domain
3) When customer is not clear about his own requirement
HYBRID MODEL
It combines 2 or more models and modify them as per business requirements.
Hybrid model of Spiral and Prototype development models

We go for this model when,


1) Whenever there is dependency, we go for this hybrid model
2) When the customer gives requirement in stages, we develop the product in
stages using this hybrid model.
3) When the customer is new to the s/w domain
4) When developers are new to the domain
5) When customer is not clear about his own requirements

You might also like