Software Development Life Cycle(SDLC) * Overview (— Se * Objective * Development Phases : * Life cycle Model ’ + Agile SDLC « Strength & weakness * conclusion1.Overview * It is a process used to develop information systems and user ownership « A framework that describes the activities performed at each stage of a software development project * High quality system * Reaches completion with cost and time * Have various model like Waterfall,spiral,RAD,Agile2.Objective Sdlc has Three primary objectives: -Ensure the delivery of high quality systems -Provide strong management control -Maximize productivity3.Development Phase The development phase in SDLC are # Requirement analysis # Design # Coding 20% 100% # Testing # Operation & MaintainanceRequirement Analysis * It invovles ‘breaking down’ the system for * analysis of situation * analysis of project goals * It can be done by individuals or team membersDesign * It takes the initial input * For each requirements design elements will be produced ¢ It describes the software features and includes hierarchy diagrams,screen layout diagrams * The output of ths stage describe the new system as a collection of modules or subsytemsCoding * Modular & subsystem programming code will be accomplished during this stage * It is interlinked with the testing stage * Here overall coding will be testedTesting * Here the code are tested at various levels ¢ Most common testing are unit,system and user acceptance. * Types of testing are # White box testing # Black box testing # Regression testingTesting(cont.) # Performance testing # Integration testing # Data set testingOperation & Maintenance * The deployment includes changes and enhancements * Maintaining is the important aspect of SDLC4.Life cycle models Different types of life cycle model available are * Waterfall model * Prototyping model * Rapid Application Development(RAD) * Spiral model5.Waterfall model It is the classical system development model Requirements-defines needed information, function, behaviour,performance and interface Design-data structures,software architedtures, interface representations,algorithmic details Implementation-source code,database,documentation,testingwaterfall(cont.) Various stages of waterfall modelWaterfall(cont.) Strength Weakness * Minimizes planning * Inflexible overhaed * Only final stage ¢ Structure minimizes produces wasted effort documentation * Works well for * Backing up to address technically weak or mistake is difficult inexperinced staff6.Prototyping Model * It uses multiple iterations or requirement,analysis,design ¢ After each iteration,the result is evaluted by the customer ¢ When the user is satisfied,the prototype code is brought up to the standards needed for afinal product.Prototype(cont.) Prote Typit = | ene . Evaluation Xe / Updation =| pe Maintain: Test Proto Type Model Tnitial Design | Customer CustomerPrototyping(cont.) Strength Weakness * Customers can see * It is impossible to steady progress know how long it will * This is useful when faKe requirements are * There is no way to changing rapidly know the no.of iterations will be required7.Spiral Model It is risk-reduction oriented model It breaks the whole projects into mini projects For projects with risky elements, its beneficial. Each cycle invovles the same sequence as the steps as the waterfall process modelSpiral(cont.) Strength Weakness * Early iterations of the * Complicated project are cheapset * Require attentive & * Risk decreases knowledgable + All iterations meets management the project needs8.RAD model * RAD is a concept that products can be developed faster and higher quality through: - Gathering requirements using workshops - Prototyping and early,reiterative user testing of designs - the re-use of software components