SE Chapter 4

Software Engineering
SE
Contents
o What is SDLC Models
o Waterfall Model
o RAD Model
o Spiral Model
o Agile Model
o Iterative Model
o Big bang Model ( H W )
o V Model ( H W )
o Incremental Model ( H W )
What is 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.

 The software development paradigm helps developer to select a strategy to develop the software.

 A software development paradigm has its own set of tools, methods and procedures, which are expressed
clearly and defines software development life cycle
SDLC Models
What is Waterfall Model?
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.

 The Waterfall model is the earliest SDLC approach that was used for software development.
 The waterfall Model illustrates the software development process in a linear sequential flow. This means

that any phase in the development process begins only if the previous phase is complete.
 Waterfall Model - Design

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.
Waterfall Model – Application
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.
• There are no ambiguous requirements.
• Ample resources with required expertise are available to support the product.
• The project is short.
Waterfall Model – Advantages
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.
Waterfall Model – Disadvantages
• 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.
• Not suitable for the projects where requirements are at a moderate to high risk of changing.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.
• Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological or
business bottleneck or challenges early.
What is 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.

 The most important aspect for this model to be successful is to make sure that the prototypes developed are
reusable.
RAD Model Design
RAD model distributes the analysis, design, build and test phases into a series of short, iterative development
cycles.

Following are the various phases

of the RAD Model

• Business Modelling
• Data Modelling
• Process Modelling
• Application Generation
• Testing and Turnover
RAD Model – Application
RAD model can be applied successfully to the projects in which clear modularization is possible. If the project
cannot be broken into modules, RAD may fail.

The following pointers describe the typical scenarios where RAD can be used −

• RAD should be used only when a system can be modularized to be delivered in an incremental manner.
• It should be used if there is a high availability of designers for Modelling.
• It should be used only if the budget permits use of automated code generating tools.
• RAD SDLC model should be chosen only if domain experts are available with relevant business
knowledge.
• Should be used where the requirements change during the project and working prototypes are to be
presented to customer in small iterations of 2-3 months.
The Advantages of the RAD Model

• Changing requirements can be accommodated.

• 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 Mode

• 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.
• Inapplicable to cheaper projects as cost of Modelling and automated code generation is very high.
• Management complexity is more.
• Suitable for systems that are component based and scalable.
• Requires user involvement throughout the life cycle.
• Suitable for project requiring shorter development times.
What is Spiral Model?
This Spiral model is a combination of iterative development process model and sequential linear development
model i.e. the Spiral model with a very high emphasis on risk analysis.

It allows incremental releases of the product or incremental refinement through each iteration around the
spiral.

Spiral Model – Design

The spiral model has four phases. A software project repeatedly passes through these phases in iterations called
Spirals.
• Identification
• Design
• Construct or Build
• Evaluation and Risk Analysis
Con…

Based on the customer evaluation,

the software development process
enters the next iteration and
subsequently follows the linear
approach to implement the feedback
suggested by the customer.
The process of iterations along the
spiral continues throughout the life
of the software.
Spiral Model Application
The Spiral Model is widely used in the software industry as it is in sync with the natural development process of
any product, i.e. learning with maturity which involves minimum risk for the customer as well as the development
firms.

The following pointers explain the typical uses of a Spiral Model:

• When there is a budget constraint and risk evaluation is important.

• For medium to high-risk projects.
• Long-term project commitment because of potential changes to economic priorities as the requirements
change with time.
• Customer is not sure of their requirements which is usually the case.
• Requirements are complex and need evaluation to get clarity.
• New product line which should be released in phases to get enough customer feedback.
• Significant changes are expected in the product during the development cycle.
The Advantages of the Spiral SDLC Model
• 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.
The Disadvantages of the Spiral SDLC Model
• 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.
What is Agile?
Agile model believes that every project needs to be handled differently and the existing methods need to be tailored to
best suit the project requirements.

 In Agile, the tasks are divided to time boxes (small time frames) to deliver specific features for a release.
 Iterative approach is taken and working software build is delivered after each iteration.
 Each build is incremental in terms of features; the final build holds all the features required by the customer.
 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

Here is a graphical illustration of the Agile Model:

The Agile thought process had started early in the software development and started becoming popular with time
due to its flexibility and adaptability.

The most popular Agile methods include

• Rational Unified Process (1994)
• Scrum (1995)
• Crystal Clear
• Extreme Programming (1996)
• Adaptive Software Development
• Feature Driven Development
• Dynamic Systems Development Method (DSDM) (1995).

These are now collectively referred to as Agile Methodologies, after the Agile Manifesto was published in 2001.

Following are the Agile Manifesto principles:

• Individuals and interactions
• Working software
• Customer collaboration
• Responding to change
The Advantages of the Agile Model
• 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.
• Good model for environments that change steadily.
• Minimal rules, documentation easily employed.
• Enables concurrent development and delivery within an overall planned context.
• Little or no planning required.
• Easy to manage.
• Gives flexibility to developers.
The Disadvantages of the Agile Model
• Not suitable for handling complex dependencies.
• More risk of sustainability, maintainability and extensibility.
• Strict delivery management dictates the scope, functionality to be delivered, and adjustments to meet the
deadlines.
• Depends heavily on customer interaction, so if customer is not clear, team can be driven in the wrong
direction.
• There is a very high individual dependency, since there is minimum documentation generated.
• Transfer of technology to new team members may be quite challenging due to lack of documentation.
SDLC 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.

Iterative Model – Design

At each iteration, design modifications are made and new functional capabilities are added. The basic idea behind
this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time
(incremental).
The following illustration is a representation of the Iterative and Incremental model:
Iterative Model – Application
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.
• Resources with needed skill sets are not available and are planned to be used on contract basis for specific
iterations.
• There are some high-risk features and goals which may change in the future.
The Advantages of the Iterative and Incremental SDLC Model
• 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.
• Testing and debugging during smaller iteration is easy.
• Risks are identified and resolved during iteration; and each iteration is an easily managed milestone.
• Easier to manage risk - High risk part is done first.
• With every increment, operational product is delivered.
• Issues, challenges and risks identified from each increment can be utilized/applied to the next increment.
• Risk analysis is better.
• It supports changing requirements.
• Initial Operating time is less.
• Better suited for large and mission-critical projects.
• During the life cycle, software is produced early which facilitates customer evaluation and feedback.
The Disadvantages of the Iterative and Incremental SDLC Model
• 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.
• Not suitable for smaller projects.
• Management complexity is more.
• End of project may not be known which is a risk.
• Highly skilled resources are required for risk analysis.
• Projects progress is highly dependent upon the risk analysis phase.
End Chapter 4
Reference : Ian Somerville, Advanced Software engineering 10th edition &
Google Search.