The Lifecycle at a Glance

One loop, not a straight line

Every piece of software passes through the same activities. Someone understands a need. Someone designs an answer. Developers build it. The team verifies it. The team releases it. Then people operate and support it in production. What users say and what the monitoring shows then becomes the next need. The software development lifecycle (SDLC) is the name for this loop.

The loop matters because each activity depends on the quality of the one before it. A vague need produces a vague design. A design that ignores operations produces a system that is hard to run. A team that understands the whole loop makes better decisions in each part of it.

This course covers the loop at an intermediate level. You will choose between options, diagnose problems in real cases and adapt the lifecycle to a project, rather than only name its parts.

Worked example: a leave request system

A human resources (HR) team asks for an online leave request form. In the understand activity, the analyst learns that managers also need to see team calendars, and that some staff work in two countries with different public holidays. In design, the team decides to store holidays per country as data, not in the code. In build and verify, tests cover an employee who changes country in the middle of the year. In release, the form goes live for one department first. In operate, the logs show that many requests fail on one browser. That finding becomes a new item for the next cycle.

Worked example: a payment change

A finance system must support a new bank file format by a fixed date. The need is clear and stable, but the testing must be strict, because an error sends money to the wrong account. The same six activities happen. The team simply spends more effort on verification and on a careful release plan with a parallel run, where the old and new files are produced side by side and compared.