Software Development Life Cycle

SOFTWARE DEVELOPMENT

LIFE CYCLE MODEL

By:
MANISH KUMAR SAHOO
[email protected]
DM08047
Introduction
 Software life cycle models describe
phases of the software cycle and the
order in which those phases are
executed. There are tons of models,
and many companies adopt their own,
but all have very similar patterns.
General Life Cycle Model


REQUIREMNTS DESIGN IMPLEMENTATION TESTING

 Each phase produces deliverables required by the next phase

in the life cycle. Requirements are translated into design.
Code is produced during implementation that is driven by
the design. Testing verifies the deliverable of the
implementation phase against requirements.


 Requirements

Business requirements are gathered in this phase. This
phase is the main focus of the project managers and stake
holders. Meetings with managers, stake holders and users
are held in order to determine the requirements. Who is
going to use the system? How will they use the system?
What data should be input into the system? What data
should be output by the system? The overall result is the
system as a whole and how it performs, not how it is
actually going to do it.

 Design

The software system design is produced from the results
of the requirements phase. Architects have the ball in their
court during this phase and this is the phase in which their
focus lies.


 Implementation
 Code is produced from the deliverables of the design
phase during implementation, and this is the longest phase
of the software development life cycle. For a developer,
this is the main focus of the life cycle because this is where
the code is produced

 Testing
 During testing, the implementation is tested against
the requirements to make sure that the product is actually
solving the needs addressed and gathered during the
requirements phase. Unit tests and system/acceptance
tests are done during this phase

 So in a nutshell, that is a very basic overview of the general

software development life cycle model. Now lets delve into
some of the traditional and widely used variations.

Waterfall Model
 This is the most common and classic of life cycle models,

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 in its entirety
before the next phase can begin. At the end of each
phase, a review takes place to determine if the project
is on the right path and whether or not to continue or
discard the project. Unlike what I mentioned in the
general model, phases do not overlap in a waterfall
model.

Advantages

 Simple and easy to 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.
Disadvantages

 Adjusting scope during the life cycle can kill a

project
 No working software is produced until late during
the life cycle.
 High amounts of risk and uncertainty.
 Poor model for complex and object-oriented
projects.
Code-and-Fix
This model starts with an informal general
product idea and just develops code until a
product is ”ready” (or money or time runs
out). Work is in random order.

Advantages

 No administrative overhead
 Signs of progress (code) early.
 Low expertise, anyone can use it!
 Useful for small “proof of concept” projects,
e.g. as part of risk reduction

Disadvantages

 No visibility/control
 No resource planning
 No deadlines
 Mistakes hard to detect/correct
 Impossible for large projects,
 communication breakdown, chaos.

V-Shaped Model
 Just like the waterfall model, the V-Shaped life
cycle is a sequential path of execution of
processes. Each phase must be completed
before the next phase begins. Testing is
emphasized in this model more so than the
waterfall model though.
 Requirements begin the life cycle model just like
the waterfall model. Before development is
started, a system test plan is created
 The high-level design phase focuses on system
architecture and design.
 The low-level design phase is where the actual
software components are designed, and unit
tests are created in this phase as well.
 The implementation phase is, again, where all
coding takes place
Advantages

 Simple and easy to use.

 Each phase has specific deliverables.
 Higher chance of success over the waterfall model
due to the development of test plans early on
during the life cycle.
 Works well for small projects where requirements are
easily understood.

Disadvantages

 Very rigid, like the waterfall model.

 Little flexibility and adjusting scope is difficult and
expensive.
 Software is developed during the implementation
phase, so no early prototypes of the software are
produced.
 Model doesn’t provide a clear path for problems
found during testing phases.

Incremental Model
 The incremental model is an intuitive approach to the
waterfall model. Multiple development cycles take
place here, making the life cycle a “multi-
waterfall” cycle. Cycles are divided up into
smaller, more easily managed iterations
 A working version of software is produced during the
first iteration, so you have working software early
on during the software life cycle.
 It is a popular model software evolution used many
commercial software companies and system
vendor.
Incremental software development model may be
applicable to projects where:
- Software Requirements are well defined, but
realization may be delayed.
- The basic software functionality are required
Advantages

 Generates working software quickly and early

during the software life cycle.
 More flexible – less costly to change scope and
requirements.
 Easier to test and debug during a smaller
iteration.
 Easier to manage risk because risky pieces are
identified and handled during its iteration.
 Each iteration is an easily managed milestone.

Disadvantages

 Each phase of an iteration is rigid and do not

overlap each other.
 Problems may arise pertaining to system
architecture because not all requirements are
gathered up front for the entire software life
cycle.
Spiral Model
 The spiral model is similar to the incremental
model, with more emphases placed on risk
analysis.
 The spiral model has four phases: Planning,
Risk Analysis, Engineering and
Evaluation.

 Requirements are gathered during the planning
phase.
 In the risk analysis phase, a process is
undertaken to identify risk and alternate
solutions. A prototype is produced at the end
of the risk analysis phase.
 Software is produced in the engineering phase,
along with testing at the end of the phase.
 The evaluation phase allows the customer to
 Advantages
 High amount of risk analysis
 Good for large and mission-critical projects.
 Software is produced early in the software life
cycle.

 Disadvantages
 Can be a costly model to use.
 Risk analysis requires highly specific expertise.
 Project’s success is highly dependent on the risk
analysis phase.
 Doesn’t work well for smaller projects.


Software Development Life Cycle

Uploaded by

Copyright:

Available Formats

Software Development Life Cycle

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Development Life Cycle

Uploaded by

Copyright:

Available Formats

SOFTWARE DEVELOPMENT

LIFE CYCLE MODEL

 Each phase produces deliverables required by the next phase

 So in a nutshell, that is a very basic overview of the general

 This is the most common and classic of life cycle models,

 Simple and easy to use.

 Adjusting scope during the life cycle can kill a

product is ”ready” (or money or time runs

out). Work is in random order.

 Simple and easy to use.

 Very rigid, like the waterfall model.

 Generates working software quickly and early

 Each phase of an iteration is rigid and do not

You might also like