Follow a school club's event sign-up app from idea to retirement. Requirements: the club leaders say sign-ups must stop at 30, with a waiting list after that. Design: sketch the screens and decide how the waiting list works. Implementation: write the code. Testing: sign up 30 people, then a 31st, and check that the 31st lands on the waiting list. Deployment: put it online for the whole school. Maintenance: a year later, fix a time-zone bug and add a new kind of event. Each phase produces something the next phase depends on.
The phases are kinds of work, not always a fixed timetable. In the waterfall model you finish each phase before starting the next, which suits projects whose requirements are set by law or contract. In agile, a two-week sprint contains a little of every phase: plan a few features, build them, test them, show them to users and adjust. Agile still has structure, with sprint planning, reviews and retrospectives; what it drops is the single plan made up front.
Not every development story is the SDLC. Fixing one typo on a live website is a single maintenance task, not a pass through six phases, and debugging is an activity inside testing and maintenance, not a life cycle of its own. You are dealing with the SDLC when the question is about the order of phases, what moves between them, or which model to choose for a whole project.
Think of it like this. Developing software resembles launching a new dish at a restaurant: ask diners what they want, write the recipe, cook a test batch, let staff taste it, add it to the menu, then tweak it from comments. Waterfall perfects the dish before serving anyone; agile serves small tasting plates every week. Unlike a dish, released software reaches every user at once, mistakes included.
Core idea. The SDLC provides structure so that complex software can be built reliably. Different models (waterfall, agile, spiral) emphasize different approaches.