1. Fall 2009 1 Systems Development Life Cycle Systems Development Life Cycle SDLC framework for describing phases in developing & maintaining information systems Typical SDLC phases include planning, analysis, design, implementation & support

2. Fall 2009 2 Systems Development Life Cycle Traditional (heavyweight) RAD (Rapid Application Development) Agile (Lightweight)

3. Fall 2009 3 Sample SDLC Models Waterfall model well-defined, linear stages of systems development of support Spiral model software developed using iterative or spiral approach rather than linear approach

4. Fall 2009 4 Sample SDLC Models (cont.) Incremental release model progressive development of operational software RAD model produces systems quickly without sacrificing quality (!) Prototyping model develops prototypes to clarify user requirements

5. Systems Development Life Cycle

6. Structured Approaches:Waterfall Method

7. Spiral Model of Software Development (Boehm, 1988)

8. RAD -- Prototyping

9. Fall 2009 9 Sandra DewitzSystems Analysis & Design (1996) Traditional systems development ill-suited for online, real time systems development ill-suited for leading edge development does not foster customer-designer communication inflexible as freezes requirements (tries to!) Three popular strategies joint application development (JAD) phased development rapid application development (RAD)

10. Fall 2009 10 JAD Overcomes customer-designer communications gap Reduce time/effort documenting, approving requirements/design JAD sessions bring users/designers together to focus on project development Employs prototyping as integral part of process

11. Fall 2009 11 JPP Joint Project Planning (JPP) session Objective: develop a project plan that meets conditions negotiated between requester & provider Wysocki chapter 8

12. Fall 2009 12 Phased Development Partitions large system into subsystem based on major processes Performs traditional cycle iteratively till full system implemented

13. Fall 2009 13 RAD Similar to both JAD & phased development Segments system into subsystem Iteratively performs model-critique-refine process till users approve prototype What sets RAD apart is addition of TIMEBOX sets time limit on prototyping phase Goal is having working system of limited functionality quickly

14. Fall 2009 14 RAD (continued) Incremental delivery reduces time from requirements to system delivery Limited time and expense at risk for organization RAD approach not appropriate for all projects

15. RAD Process

16. Fall 2009 16 Other SDLC Models Scrum model Rational Unified Process (RUP) model Agile methodologies e.g. eXtreme Programming XP) model