Sdlc framework


Published on

Published in: Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Sdlc framework

  1. 1. SDLCFramework
  2. 2. IntroductionRisksRewardsGoalsLifecycle comparisonsFramework and Methodology comparisonsHow to implementCase study examplesQ&A 2
  3. 3. Why do Large Projects Fail?Requirements Unrealistic or unarticulated project goals Badly defined system requirementsRisk Unidentified and unmanaged risks Use of immature technology Project team not able to handle the projects complexity Sloppy development practicesCommunication Poor communication among customers, developers, and users Poor reporting of the projects status Stakeholder politicsPlanning Inaccurate estimates of needed resources Commercial pressures Poor project management 3
  4. 4. What is SDLC – Simplified Version What and Why and When And How and Where and Who. 4
  5. 5. What is SDLC – WhoWho wants it?Who will benefit?Who is going to do it?Who is going to pay for it? 5
  6. 6. What is SDLC – WhatWhat do you want?What will it do?What will it impact?What benefit do you expect? 6
  7. 7. What is SDLC – WhenWhen do you want it?When is the contractual deadline?When is regulatoryimplementation?When is the market window ofopportunity? 7
  8. 8. What built?Where will it be is SDLC – Where In house Vendor Contractor On-shore or off-shoreWhere will it run? In house Vendor Local implementation National or global implementation 8
  9. 9. What is SDLC – WhyWhy do you want it?Why do you think it will benefit us?Why do our clients, customers,beneficiaries want or need it? 9
  10. 10. What is SDLC – HowHow will you do it?Be very, verydetailed. 10
  11. 11. Life Cycle ComparisonsWaterfallFountainSpiral(螺旋)RAD/JADRapid Prototyping 11
  12. 12. WaterfallAdvantages Planning Linear and sequential Simplifies task scheduling Analysis – no overlapping steps Ensures points of review Logical Design PhysicalDisadvantages Design Slow Implementation Does not adapt to changing requirements Maintenance Minimal user input Higher error rates 12
  13. 13. FountainBased on the waterfall modelBut observes that the sequence alwayscontains cyclesReflects the fact that some phasescannot begin before others and thatsome phases are poorly delineatedA mental image to help visualize whatactually happens in many real softwaredevelopment projects 13
  14. 14. Spiral 14
  15. 15. Spiral Categorizes the many (and repeated) phases of software development into a number of cyclically repeated sectors System complexity and size grows with increasing radius, as do investment and riskDisadvantages Difficult to convince some customers process is controllable Needs considerable risk assessment If risk not discovered, problems will occur Risk analysis effort wasted for simple, easy projects. 15
  16. 16. Rapid Application Development (RAD) Joint Application Development (JAD)Advantages Heavy user involvement More accurate requirements Higher user satisfaction Rapid Application Development (RAD) is a methodology for compressing the analysis, design, build and test phases into a series of short, iterative development cycles. This has a number of distinct advantages over the traditional sequential development model. One of the principles of RAD is to start developing as early as possible in the project,Disadvantages 16 Hard to decide when its done
  17. 17. Rapid Prototypingrapid prototyping (RP) refers to a class of technologies that can automatically construct physical models from Computer-Aided Design (CAD) data. The steps are: Create a CAD model of the design Convert the CAD model to STL format Slice the STL file into thin cross- sectional layers Construct the model one layer atop another Clean and finish the model 17
  18. 18. Rapid PrototypingAdvantages Iterative process Involves user in analysis and design Captures requirements in concrete(具體的) form Higher user satisfactionDisadvantages Harder to estimate manpower time Premature(過早的) launch of prototype 18