Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


A Comparison Between Five Models Of Software Engineering

No description

fuqiang Zhang

on 5 May 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of A Comparison Between Five Models Of Software Engineering

Software Process Models

Five Models
Iterative Development
Extreme Programming
A Comparison Between Five Models Of Software Engineering
Nabil Mohammed Ali Munassar
A. Govardhan
General Software Process Models
Waterfall model

Prototype model

RAD (Rapid application development model)

Evolutionary development

Incremental model

Iterative model

Spiral model
Waterfall model needs planning early and ensures design flaws before develop.
Easy to understand and implement.
Reinforces good habits: define-before- design, design-before-code.
Identifies deliverables and milestones.
Works well on mature products and weak teams.
Idealized, doesn’t match reality well.
Difficult to integrate risk management.
Difficult and expensive to make changes to documents.
Costly for small teams and projects
Iterative Development
It is a way of breaking down the software development of a large application into smaller chunks.
Iterative Development
V-Shaped Model
V-Shaped life cycle is a sequential path of execution of processes. Each phase must be completed before the next phase begins.
V-Shaped Model
Simple and easy to use.
Each phase has specific deliverables.
Higher chance of success over the waterfall model.
Works well for small projects where requirements are easily understood.

Very rigid like the waterfall model.
Little flexibility and adjusting scope is difficult and expensive.
No early prototypes of the software are produced.
This Model does not provide a clear path for problems found during testing phases
Spiral Model
The spiral model is similar to the incremental model, with
more emphases placed on risk analysis.
High amount of risk analysis.
Good for large and mission-critical projects.
Software is produced early inthe software life cycle.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk analysis phase.
Doesn’t work well for smaller projects
Spiral Model
Extreme Programming
An approach to development, based on the development and delivery of very small increments of functionality.
Lightweight methods suit small-medium size projects.
Produces good team cohesion.
Emphasises final product.
Test based approach to requirements and quality assurance.
Difficult to scale up to large projects where documentation is essential.
Needs experience and skill .
Programming pairs is costly.
There are many existing models for developing systems for different sizes of projects and requirements.
Waterfall model and spiral model are used commonly in developing systems.
Each model has advantages and disadvantages for the development of systems , so each model tries to eliminate the disadvantages of the previous model
Thank You
--Fuqiang Zhang
Full transcript