SDLC - Software Development Life Cycle SDLC

Learn the software development life cycle (SDLC) as a seven-stage framework, from analysis and planning to maintenance, including requirements, design, development, testing, deployment, and updates.

The SDLC provides a systematic plan with concrete steps to define goals, enable progress tracking for stakeholders, ensure quality via stage-specific quality control, and reduce cost, risk, and deployment time.

Explore how the sdlc framework guides automating hiring workflows at DailyNeeds, from onboarding and it procurement to finance, project deployment, and security access via an employee portal.

Initiate analysis and planning to align the project with company vision, assess resources, tools, scheduling, estimate costs, consult security and operations, and produce a high-level scope of work.

Explore a high-level SDLC schedule for a daily needs employee portal project, detailing analysis, planning, requirements, design, development, QA, deployment, hypercare, and hotfix cycles with monthly timelines.

Gather and document requirements from business users through meetings and workshops, identify use cases, and define functional and non-functional needs in the SRS as the single source of truth.

Explore a sample SRS document for the daily needs employee portal, highlighting purpose, scope, functional and nonfunctional requirements, external interfaces, use cases, diagrams, and version control.

Convert the SRS into wireframes and prototypes using figma and Invision, enabling high-level and low-level designs and setting up dev, qa, stage, and prod environments for next-phase coding.

Explore high level and low level diagrams, a data flow diagram, and a database schema with a login prototype within an SDLC-based employee portal, detailing UI, APIs, and data interactions.

Showcases a sample low level diagram of the UI module in a React-based frontend, featuring a login and multi-section new employee form with database saving and HR submission.

Explore how a data flow diagram shows how a new joinee's data moves through personal, academic, finance, and skill set sections into the database and to HR for verification.

Explore how a sample database schema models entities, attributes, and relationships, and learn how normalization forms 1NF, 2NF, and 3NF reduce redundancy and enforce data integrity.

Explore a sample login page wireframe prototype, showing a two-input username and password UI with a login button, designed using Draw.io and used by developers to code the UI.

Explore the fourth phase of the SDLC, coding to deliver a scalable application per the S-R-S document, guided by a developer manual, object-oriented design patterns, peer reviews, and change logs.

Coordinate comprehensive testing across functional, integration, performance, load, and penetration tests, log and fix bugs, obtain QA and UAT sign-off, and prepare for deployment.

Learn how production deployment moves packaged code from development through QA and UAT to production servers, guided by RFCs, Change Manager approvals, and backout plans, with hypercare and hot fixes.

Teams adapt SDLC guidelines to fit unique projects, creating models like waterfall, incremental, iterative, V-shaped, spiral, and agile. These models share SDLC steps but vary in execution and values.

Explore the waterfall model, the first linear sequential SDLC, where planning, requirement gathering, design, implementation, testing, deployment, and maintenance proceed in strict sequence with sign-off before the next phase.

Learn when to apply the waterfall model for projects with clear, fixed requirements, ample resources, and mission critical needs, with explicit validation at each stage.

Explore the pros and cons of the waterfall model: simple, well-defined phases with fixed deliverables and progress, versus no working software or mvp, and poor handling of changing requirements.

Identify waterfall drawbacks and adopt the incremental model, delivering the system in increments through design, development, testing, and build, with final delivery for feedback.

Identify when to apply the incremental model by assessing clear requirements, resource constraints, and variable project scope.

The iterative model addresses late customer feedback by delivering a minimum viable product through repeated planning, design, development, testing, and deployment, with ongoing customer feedback guiding each iteration.

Apply the iterative model for startup projects or product-based companies that must deliver basic working software early, when requirements are unclear and resources are limited.

The iterative model delivers early working software for customer review and rapid feedback, but faces risks from changing requirements, tech shifts, and higher management effort, especially for startups.

The lecture explains the V-model, a waterfall extension, with strict verification and validation at each phase, linking requirement gathering, system and architecture design, coding, and unit to acceptance testing.

Identify when the V-Model fits small to medium projects with fixed requirements, including medical devices software, where verification, validation, and regulatory compliance are paramount.

Examine the pros and cons of the V-Model, highlighting its disciplined, phase-by-phase approach and suitability for small, well-understood projects. Note its limitations for changing requirements and complex or long-duration efforts.

The spiral model emphasizes early risk assessment and iterative development. It integrates planning, risk analysis, product development, and customer feedback through cycles, accommodating new requirements and prototypes.

Identify when the spiral model fits best for medium to high risk projects, emphasizing risk assessment, cost evaluation, and flexible, incremental releases in IT settings.

Assess risks early with the spiral model, enabling user feedback and easier cost estimation through prototypes, while noting expert analysis is needed and it may risk budget for small projects.

The lecture contrasts traditional predictive SDLC models with agile adaptive SDLC models, showing rigidity in planning and openness to change through feature-driven development and frequent customer feedback.

Adopt agile by breaking requirements into small tasks and building the product iteratively and incrementally with planning, requirements, design, development, and testing phases, plus customer feedback and product owner collaboration.

Use the agile model when requirements change and scope is not fixed. Tolerate bugs, fixed in the next iteration, while customers review progress frequently for startup companies and small teams.

Explore the agile model's pros—frequent customer collaboration, faster delivery, flexible scope, early reviews—and its cons, including time and cost estimation challenges and fragmented output.

Explore how the Agile Manifesto prioritizes individuals and interactions over process and tools, working software over documentation, customer collaboration over contracts, and change over plan.

Explore the 12 agile principles from the Agile Manifesto, including delivering valuable software early and welcoming changing requirements through daily collaboration.

Learn how lean startup uses hypothesis-driven experiments and iterative releases to validate a business model, via a minimum viable product that delivers validated learning by observing customer behavior.

Learn how agile requirements use user stories and invest criteria, with role-action-benefit templates, acceptance criteria, and formulas like triple c and give-when-then, aided by Jira and Azure DevOps.

Explore burndown charts as a visual tool in agile and Scrum, tracking work remaining over time, modeling ideal versus actual progress and predicting timely completion.