• Home
  • Testing
  • SAP
  • Web
  • Must Learn!
  • Big Data
  • Live Projects
  • Blog

To manage the level of complexity during the software development cycle, various SDLC model is implemented by the software companies. Their aim is to deliver a quality software product, however each model is unique in terms of their software development approach. Here we will see how each model differs from other in terms of cost, time duration, requirements, maintenance etc.

Properties of ModelWater-Fall ModelIncremental ModelSpiral ModelRad Model
Planning in early stageYesYesYesNo
Returning to an earlier phaseNoYes YesYes
Handle Large-ProjectNot AppropriateNot AppropriateAppropriateNot Appropriate
Detailed DocumentationNecessaryYes but not muchYesLimited
Requirement SpecificationsBeginning BeginningBeginningTime boxed release
Flexibility to changeDifficultEasy EasyEasy
User InvolvementOnly at beginningIntermediateHighOnly at the beginning
MaintenanceLeastPromotes MaintainabilityTypical Easily Maintained
DurationLongVery longLong Short
Risk InvolvementHighLowMedium to high riskLow
Framework TypeLinearLinear + IterativeLinear + IterativeLinear
TestingAfter completion of coding phaseAfter every iterationAt the end of the engineering phaseAfter completion of coding
Overlapping PhasesNoYes (As parallel development is there)NoYes
MaintenanceLeast MaintainableMaintainableYesEasily Maintainable
Re-usabilityLeast possibleTo some extent To some extentYes
Time-FrameVery LongLong LongShort
Working software availabilityAt the end of the life-cycleAt the end of every iterationAt the end of every iterationAt the end of the life cycle
ObjectiveHigh AssuranceRapid Development High AssuranceRapid development
Team sizeLarge TeamNot Large TeamLarge TeamSmall Team
Customer control over administratorVery LowYesYesYes