CE343 Software Engineering 20DCE051 - Dipak Karmur

Practical 1
Aim: List & draw at least 7 various Software Development Life Cycle (SDLC) modelsand
preparing the detailed case study on “Definition A” that which SDLC model is suitable to
develop the “Definition A”?

Theory:

SDLC Models
Software Development life cycle (SDLC) is a spiritual model used in project management
that defines the stages include in an information system development project, from an initial
feasibility study to the maintenance of the completed application.
There are different software development life cycle models specify and design, which are
followed during the software development phase. These models are also called "Software
Development Process Models." Each process model follows a series of phase unique to its
type to ensure success in the step of software development.

Fig.1 SDLC model

A software life cycle model (also termed process model) is a pictorial and diagrammatic
representation of the software life cycle. A life cycle model represents all the methods
required to make a software product transit through its life cycle stages. It also captures the
structure in which these methods are to be undertaken.
Need of SDLC
The development team must determine a suitable life cycle model for a particular plan and
then observe to it.

DEPSTAR 5CE1 1
CE343 Software Engineering 20DCE051 - Dipak Karmur

Without using an exact life cycle model, the development of a software product would not be
in a systematic and disciplined manner. When a team is developing a software product, there
must be a clear understanding among team representative about when and what to do.
Otherwise, it would point to chaos and project failure. This problem can be defined by using
an example. Suppose a software development issue is divided into various parts and the parts
are assigned to the team members. From then on, suppose the team representative is allowed
the freedom to develop the roles assigned to them in whatever way they like. It is possible
that one representative might start writing the code for his part, another might choose to
prepare the test documents first, and some other engineer might begin with the design phase
of the roles assigned to him. This would be one of the perfect methods for project failure.

SOFTWARE MODEL TYPE

 Waterfall model
 Iterative model
 Incremental model
 RAD model
 Spiral model
 Prototype model
 Evolutionary model
 V model
 Agile model

Waterfall Model
Waterfall approach was first SDLC Model to be used widely in Software Engineering to
ensure success of the project. In "The Waterfall" approach, the whole process of software
development is divided into separate phases. In this Waterfall model, typically, the outcome
of one phase acts as the input for the next phase sequentially.
The Waterfall Model was the first Process Model to be introduced. It is also referred to as
a linear-sequential life cycle model. 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.

Application of Waterfall Model

Every software developed is different and requires a suitable SDLC approach to be followed
based on the internal and external factors. Some situations where the use of Waterfall model
is most appropriate are −
 Requirements are very well documented, clear and fixed.
 Product definition is stable.
 Technology is understood and is not dynamic.

DEPSTAR 5CE1 2
CE343 Software Engineering 20DCE051 - Dipak Karmur

 There are no ambiguous requirements.

 Ample resources with required expertise are available to support the product.
 The project is short.

Fig.2 waterfall model

Some of the major advantages of the Waterfall Model are as follows −

 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has specific deliverables
and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.

The major disadvantages of the Waterfall Model are as follows −

 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.

Iterative Model

In the Iterative model, iterative process starts with a simple implementation of a small set of
the software requirements and iteratively enhances the evolving versions until the complete
system is implemented and ready to be deployed.

DEPSTAR 5CE1 3
CE343 Software Engineering 20DCE051 - Dipak Karmur

An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part of the
software, which is then reviewed to identify further requirements. This process is then
repeated, producing a new version of the software at the end of each iteration of the model.

Fig.3 Iterative model

Application of Iterative Model

Like other SDLC models, Iterative and incremental development has some specific
applications in the software industry. This model is most often used in the following
scenarios −
 Requirements of the complete system are clearly defined and understood.
 Major requirements must be defined; however, some functionalities or requested
enhancements may evolve with time.
 There is a time to the market constraint.
 A new technology is being used and is being learnt by the development team while
working on the project.
The advantages of the Iterative and Incremental SDLC Model are as follows −
 Some working functionality can be developed quickly and early in the life cycle.
 Results are obtained early and periodically.
 Parallel development can be planned.
 Progress can be measured.
 Less costly to change the scope/requirements.

DEPSTAR 5CE1 4
CE343 Software Engineering 20DCE051 - Dipak Karmur

The disadvantages of the Iterative and Incremental SDLC Model are as follows −
 More resources may be required.
 Although cost of change is lesser, but it is not very suitable for changing
requirements.
 More management attention is required.
 System architecture or design issues may arise because not all requirements are
gathered in the beginning of the entire life cycle.
 Defining increments may require definition of the complete system.

Incremental Model
Incremental Model is a process of software development where requirements divided into
multiple standalone modules of the software development cycle. In this model, each module
goes through the requirements, design, implementation and testing phases. Every subsequent
release of the module adds function to the previous release. The process continues until the
complete system achieved.

Fig.4 Incremental model

Application of Incremental Model:

 When the requirements are superior.
 A project has a lengthy development schedule.
 When Software team are not very well skilled or trained.
 When the customer demands a quick release of the product.
 You can develop prioritized requirements first.
Advantage of Incremental Model
 Errors are easy to be recognized.
 Easier to test and debug
 More flexible.

DEPSTAR 5CE1 5
CE343 Software Engineering 20DCE051 - Dipak Karmur

 Simple to manage risk because it handled during its iteration.

 The Client gets important functionality early.

Disadvantage of Incremental Model

 Need for good planning
 Total Cost is high.
 Well defined module interfaces are needed.

RAD Model
Rapid application development is a software development methodology that uses minimal
planning in favor of rapid prototyping. A prototype is a working model that is functionally
equivalent to a component of the product.
In the RAD model, the functional modules are developed in parallel as prototypes and are
integrated to make the complete product for faster product delivery. Since there is no detailed
preplanning, it makes it easier to incorporate the changes within the development process.
RAD projects follow iterative and incremental model and have small teams comprising of
developers, domain experts, customer representatives and other IT resources working
progressively on their component or prototype.

Fig.5 RAD model

The advantages of the RAD Model are as follows −

 Changing requirements can be accommodated.

DEPSTAR 5CE1 6
CE343 Software Engineering 20DCE051 - Dipak Karmur

 Progress can be measured.

 Iteration time can be short with use of powerful RAD tools.
 Productivity with fewer people in a short time.
 Reduced development time.
 Increases reusability of components.
 Quick initial reviews occur.
 Encourages customer feedback.
 Integration from very beginning solves a lot of integration issues.

The disadvantages of the RAD Model are as follows −

 Dependency on technically strong team members for identifying business
requirements.
 Only system that can be modularized can be built using RAD.
 Requires highly skilled developers/designers.
 High dependency on Modelling skills.

Spiral Model 
Spiral model is one of the most important Software Development Life Cycle models, which
provides support for Risk Handling. In its diagrammatic representation, it looks like a spiral
with many loops. The exact number of loops of the spiral is unknown and can vary from
project to project. Each loop of the spiral is called a Phase of the software development
process. The exact number of phases needed to develop the product can be varied by the
project manager depending upon the project risks. As the project manager dynamically
determines the number of phases, so the project manager has an important role to develop a
product using the spiral model. 
The Radius of the spiral at any point represents the expenses(cost) of the project so far, and
the angular dimension represents the progress made so far in the current phase. 

The advantages of the Spiral SDLC Model are as follows −

 Changing requirements can be accommodated.
 Allows extensive use of prototypes.
 Requirements can be captured more accurately.
 Users see the system early.
 Development can be divided into smaller parts and the risky parts can be developed
earlier which helps in better risk management.

DEPSTAR 5CE1 7
CE343 Software Engineering 20DCE051 - Dipak Karmur

Fig.6 Spiral model

The disadvantages of the Spiral SDLC Model are as follows −

 Management is more complex.
 End of the project may not be known early.
 Not suitable for small or low risk projects and could be expensive for small projects.
 Process is complex
 Spiral may go on indefinitely.
 Large number of intermediate stages requires excessive documentation.

Prototype Model
The prototype model requires that before carrying out the development of actual software, a
working prototype of the system should be built. A prototype is a toy implementation of the
system. A prototype usually turns out to be a very crude version of the actual system, possible
exhibiting limited functional capabilities, low reliability, and inefficient performance as
compared to actual software.

Advantage of Prototype Model

 Reduce the risk of incorrect user requirement
 Good where requirement are changing/uncommitted
 Regular visible process aids management
 Support early product marketing

DEPSTAR 5CE1 8
CE343 Software Engineering 20DCE051 - Dipak Karmur

Fig.7 Prototype model

Disadvantage of Prototype Model

 An unstable/badly implemented prototype often becomes the final product.
 Require extensive customer collaboration
 Costs customer money
 Needs committed customer
 Difficult to know how long the project will last.
 Easy to fall back into the code and fix without proper requirement analysis, design,
customer evaluation, and feedback.

Evolutionary model
Evolutionary model is a combination of Iterative and Incremental model of software
development life cycle. Delivering your system in a big bang release, delivering it in
incremental process over time is the action done in this model. Some initial requirements and
architecture envisioning need to be done.

DEPSTAR 5CE1 9
CE343 Software Engineering 20DCE051 - Dipak Karmur

Fig.8.Evolutionary model

Advantages of Evolutionary Model

 The big advantage of the evolutionary model is that the user has checked every
stage during the development and it is helpful in achieving customer confidence.
 There are fewer chances of errors because all the modules are well seen.
 It helps to reduce the risk of software projects.
 It also reduces the cost of development.
 Minimize serious problems during testing.

Disadvantages of  Evolutionary Model

 The delivery of full software can be late due to different changes by customers during
development.
 It is difficult to divide the problem into several parts, that would be acceptable to the
customer which can be incrementally implemented and delivered.

V-Model 
The V-model is an SDLC model where execution of processes happens in a sequential
manner in a V-shape. It is also known as Verification and Validation model.
The V-Model is an extension of the waterfall model and is based on the association of a
testing phase for each corresponding development stage. This means that for every single
phase in the development cycle, there is a directly associated testing phase. This is a highly-
disciplined model and the next phase starts only after completion of the previous phase.

Fig.9 V model

DEPSTAR 5CE1 10
CE343 Software Engineering 20DCE051 - Dipak Karmur

The advantages of the V-Model method are as follows −

 This is a highly-disciplined model and Phases are completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Simple and easy to understand and use.
 Easy to manage due to the rigidity of the model. Each phase has specific deliverables
and a review process.

The disadvantages of the V-Model method are as follows −

 High risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of
changing.

Agile model
Agile SDLC model is a combination of iterative and incremental process models with focus
on process adaptability and customer satisfaction by rapid delivery of working software
product. Agile Methods break the product into small incremental builds. These builds are
provided in iterations. Each iteration typically lasts from about one to three weeks. 
Every iteration involves cross functional teams working simultaneously on various areas like
 Planning
 Requirements Analysis
 Design
 Coding
 Unit Testing and
 Acceptance Testing.

DEPSTAR 5CE1 11
CE343 Software Engineering 20DCE051 - Dipak Karmur

Fig.10 Agile model

The advantages of the Agile Model are as follows −
 Is a very realistic approach to software development.
 Promotes teamwork and cross training.
 Functionality can be developed rapidly and demonstrated.
 Resource requirements are minimum.
 Suitable for fixed or changing requirements
 Delivers early partial working solutions.

The disadvantages of the Agile Model are as follows −

 Not suitable for handling complex dependencies.
 More risk of sustainability, maintainability and extensibility.
 An overall plan, an agile leader and agile PM practice is a must without which it will
not work.
 Strict delivery management dictates the scope, functionality to be delivered, and
adjustments to meet the deadlines.

DEPSTAR 5CE1 12