Software Development Life Cycle (SDLC)

70,876 views

Published on

This is a presentation on the Software Development Life Cycle (SDLC)

Published in: Technology
1 Comment
87 Likes
Statistics
Notes
  • More than 5000 IT Certified ( SAP,Oracle,Mainframe,Microsoft and IBM Technologies etc...)Consultants registered. Register for IT courses at http://www.todaycourses.com Most of our companies will help you in processing H1B Visa, Work Permit and Job Placements
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
70,876
On SlideShare
0
From Embeds
0
Number of Embeds
239
Actions
Shares
0
Downloads
6,080
Comments
1
Likes
87
Embeds 0
No embeds

No notes for slide

Software Development Life Cycle (SDLC)

  1. 1. ByAngelin
  2. 2. SDLC A framework that describes theactivities performed at each stage of asoftware development project.
  3. 3. SDLC PHASESRequirements Gathering and AnalysisDesignDevelopmentTestingImplementationMaintenance
  4. 4. SDLC PHASES
  5. 5. SDLC MODELS To help understand andimplement the SDLC phases variousSDLC models have been created bysoftware development experts,universities, and standardsorganizations.
  6. 6. Reasons for Using SDLC ModelsProvides basis for project planning, estimating& schedulingProvides framework for standard set ofterminologies, activities & deliverablesProvides mechanism for project tracking &controlIncreases visibility of project progress to allstakeholders
  7. 7. Advantages of Choosing an Appropriate SDLC Increased development speed Increased product quality Improved tracking & control Improved client relations Decreased project risk Decreased project management overhead
  8. 8. Common Life Cycle ModelsWaterfallSpiral/IterativeAgile
  9. 9. Waterfall Model Analysis Design Development Testing Deployment Maintenance
  10. 10. Waterfall ModelOldest and most well-known SDLC modelFollows a sequential step-by-step process fromrequirements analysis to maintenance.Systems that have well-defined and understoodrequirements are a good fit for the WaterfallModel
  11. 11. Waterfall Model StrengthsEasy to understand, easy to useProvides structure to inexperienced staffMilestones are well understoodSets requirements stabilityGood for management control (plan, staff,track)Works well when quality is more importantthan cost or schedule
  12. 12. Waterfall Model WeaknessesAll requirements must be fully specifiedupfrontDeliverables created for each phase areconsidered frozen – inhibits flexibilityCan give a false impression of progressDoes not reflect problem-solving nature ofsoftware development – iterations of phasesIntegration is one big bang at the endLittle opportunity for customer to previewthe system (until it may be too late)
  13. 13. When to use the Waterfall ModelRequirements are very well knownProduct definition is stableTechnology is understoodNew version of an existing productPorting an existing product to a newplatform.
  14. 14. Spiral/Iterative Model Requirements Analysis Requirements Design GatheringRepeat Enhancement Maintenance Iterative Development Quality Deployment Assurance
  15. 15. Spiral ModelSpiral Model is a “risk-driven” iterative modelDivides a project into iterationsEach iteration deals with 1 or more risksEach iteration starts with small set ofrequirements and goes through developmentphase (except Installation and Maintenance)for those set of requirements.
  16. 16. Spiral ModelIterate until all major risks addressed and theapplication is ready for the Installation andMaintenance phase (production)Each of the iterations prior to the productionversion is a prototype of the application.Last iteration is a waterfall process
  17. 17. Spiral Model Strengths Provides early indication of insurmountable risks, without much cost Critical high-risk functions are developed first The design does not have to be perfect Users see the system early because of rapid prototyping tools Users can be closely tied to all lifecycle steps Early and frequent feedback from users
  18. 18. Spiral Model Weaknesses Time spent for evaluating risks too large for small or low-risk projects Time spent planning, resetting objectives, doing risk analysis and prototyping may be excessive The model is complex Risk assessment expertise is required Spiral may continue indefinitely May be hard to define objective, verifiable milestones that indicate readiness to proceed through the next iteration
  19. 19. When to use Spiral ModelWhen creation of a prototype is appropriateWhen costs and risk evaluation is importantFor medium to high-risk projectsUsers are unsure of their needsRequirements are complexNew product lineSignificant changes are expected (researchand exploration)
  20. 20. Agile Model Discover Test Design DiscoverDevelop Test Design Discover Develop Test Design Develop
  21. 21. Agile ModelSpeed up or bypass one or more life cyclephasesUsually less formal and reduced scopeUsed for time-critical applicationsUsed in organizations that employdisciplined methods
  22. 22. Some Agile MethodsRapid Application Development (RAD)ScrumExtreme Programming (XP)Adaptive Software Development (ASD)Feature Driven Development (FDD)Crystal ClearDynamic Software Development Method (DSDM)Rational Unify Process (RUP)
  23. 23. Agile Model StrengthsDeliver a working product faster thanconventional linear development modelCustomer feedback at every stage ensuresthat the end deliverable satisfies theirexpectationsNo guesswork between the developmentteam and the customer, as there is face toface communication and continuous inputsfrom the client
  24. 24. Agile Model Weaknesses For larger projects, it is difficult to judge the efforts and the time required for the project in the SDLC. Since the requirements are ever changing, there is hardly any emphasis, which is laid on designing and documentation. Therefore, chances of the project going off the track easily are much more
  25. 25. Thank You! Angelin

×