Scribd
Upload
20 views20 pages

SOftware Dev Models

Software modules

Uploaded by

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

SOftware Dev Models

Software modules

Uploaded by

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

Software Development Models

Mr. Cheng’asia Josephat



Formal SDLC models can be very detailed, with
1. specific practices,
2. procedures,
3. documentation,

but many organizations choose the elements of one or more
models that best fit their organizational style, workflow, and
requirements.
WATERFALL

The Waterfall methodology is a sequential
model in which each phase is followed by the
next phase.

Phases do not overlap, and each logically leads
to the next.

In Phase 1, requirements are gathered and
documented.

Phase 2 involves analysis intended to build
business rules and models.

Phase 3, a software architecture is designed,
and coding and integration of the software
occurs in

Phase 4. Once the software is complete,

Phase 5: occurs, with testing and debugging
being completed in this phase.

Finally the software enters an operational
phase, with support, maintenance, and other
operational activities happening on an ongoing
basis.


Waterfall has been replaced in many
organizations because it is seen as relatively
inflexible, but it remains in use for complex
systems.
THE WATERFALL SDLC MODEL
Identification, or requirements gathering, which
initially gathers business requirements, system
requirements, and more detailed requirements
for subsystems or modules as the process
continues.
Design, conceptual, architectural, logical, and
sometimes physical or final design.
Build, which produces an initial proof of
concept and then further development releases

Evaluation, which involves risk analysis for the
development project intended to monitor the
feasibility of delivering the software from a
technical and managerial viewpoint.


As the development cycle continues, this phase
also involves customer testing and feedback to
ensure customer acceptance.
SPIRAL

The Spiral model uses the linear development
concepts from the Waterfall model and adds an
iterative process that revisits four phases
multiple times during the development life cycle
to gather more detailed requirements, design
functionality guided by the requirements, and
build based on the design. I
AGILE

Agile software development is an iterative and
incremental process, rather than the linear
processes that Waterfall and Spiral use.

Agile is rooted in the Manifesto for Agile
Software Development, a document that has
four basic premises:

Individuals and interactions are more important
than processes and tools.

Working software is preferable to
comprehensive documentation.

Customer collaboration replaces contract
negotiation.

Responding to change is key, rather than
following a plan.
The Agile methodology is based on
12 principles:

Ensure customer satisfaction via early and
continuous delivery of the software.

Welcome changing requirements, even late in
the development process.

Deliver working software frequently (in weeks
rather than months).

Ensure daily cooperation between developers

Projects should be built around motivated
individuals who get the support, trust, and
environment they need to succeed.

Face-to-face conversations are the most
efficient way to convey information inside the
development team.

Progress is measured by having working
software.

Development should be done at a sustainable
pace that can be maintained on an ongoing
basis.

ay continuous attention to technical excellence
and good design. Simplicity—the art of

maximizing the amount of work not done is
essential.

The best architectures, requirements, and
designs emerge from self-organizing teams.

Teams should reflect on how to become more
ASSIGNMENT
With the aid of a well labeled
diagrams, Describe the Waterfall and
Spiral software development models
(20 marks)

You might also like