1 / 20

SDLC – Beyond the Waterfall

SDLC – Beyond the Waterfall. Systems Development Life Cycle (SDLC). Many approaches to systems development Sequential versus Iterative Development Understanding the difference between these two approaches is essential Traditional Approach – Waterfall Model.

sereno
Download Presentation

SDLC – Beyond the Waterfall

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SDLC – Beyond the Waterfall

  2. Systems Development Life Cycle (SDLC) • Many approaches to systems development • Sequential versus Iterative Development • Understanding the difference between these two approaches is essential • Traditional Approach – Waterfall Model

  3. Systems Development Life Cycle (SDLC) • Traditional Approach is sequential • Waterfall Model is a common example of a sequential approach

  4. SDLC - Waterfall Model Initiation Investigation Analysis Design Implementation Maintenance

  5. SDLC - Waterfall Model • What are the limitations of this approach? • Cannot correct defects from previous stages • No Feedback • Expensive

  6. Example • Existing System – Analysis stage • Extensive problem analysis and Requirements gathered • Move to next stage – Design stage • Create design based on previous analysis stage • What happens if something changes!!

  7. SDLC - Waterfall Model Initiation Investigation Analysis Design Implementation Maintenance

  8. SDLC – Waterfall Model • Limitations of sequential approach has lead to the emergence of a more iterative approach

  9. Traditional vs Agile Traditional Methods • Waterfall Model • Spiral Model • V-Model Agile Methods • Extreme Programming (XP) • Scrum • Adaptive Software Development • Dynamic Systems Development Method (DSDM) • Feature Driven Development

  10. Why Agile? • Instead of the traditional approach

  11. Why Agile? • A more effective method?

  12. A Possible Solution… • Agile software development • Each of these iterations can be seen as miniature software projects

  13. The Agile Software Development Manifesto On February 11-13, 2001 Agile Alliance, (formed of software practitioners and consultants), formed and produced a Manifesto for Agile Software Development Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over rigid contracts Responding to change over following a plan

  14. People over Process • Human interactions are more important than the company’s processes and tools • Close team relationships • Close working environment

  15. Working Software • Frequent output of working, tested software • Keep It Simple Stupid (KISS)

  16. Relationship With Customer • Reduce the risk of not meeting the terms of contract

  17. Responding to Change • Contracts must be worded so as to allow change

  18. So what makes an agile method? • Incremental • Cooperative

  19. So what makes an agile method? • Straightforward • Adaptive

  20. Agile Methods • Extreme Programming (XP) • Scrum • Adaptive Software Development (ASD) • Crystal Clear and Other Crystal Methodologies • Dynamic Systems Development Method (DSDM) • Feature Driven Development

More Related