Software Development Lifecycle SS3 Digital Technologies Lesson Note

What is SDLC? (The “Game Plan”)

Have you ever tried to cook a complex meal or build a piece of furniture without looking at the instructions? Usually, it ends in a mess.

In professional programming, we don’t just sit down and start typing code. We use a “Game Plan” called the Software Development Life Cycle (SDLC). It is a step-by-step process that teams follow to build high-quality software that actually works and makes the customer happy.

Think of it as a map. It tells us:

1. Where to start.
2. What to do next.
3. How to know when we are finished.

Without SDLC, software would be full of bugs, over budget, and late.

The 6 Phases of the Life Cycle

Every piece of software, from WhatsApp to TikTok, goes through these six stages:

1. Planning: “What are we building and why?” We define the goal and see if we have the money and time to do it.
2. Analysis: We talk to the users. “What buttons do you need? What problem are we solving for you?”
3. Design: This is the blueprint phase. We don’t code yet; we draw how the screens look and how the data flows.
4. Implementation (Coding): This is where the programmers finally write the actual code based on the design.
5. Testing: We try to “break” the software. We look for bugs and fix them before the public sees the app.
6. Deployment & Maintenance: We release the app to the world. If users find new bugs or want new features later, we update it.

The Waterfall Model (The “One-Way Street”)

The Waterfall Model is the oldest way of building software. Just like a real waterfall, the water only flows down. You cannot move to the next stage until the current one is 100% finished.

• How it works: You plan everything at the start, design everything, then code everything.
• The Good: It is very disciplined and easy to manage because everyone knows exactly what phase they are in.
• The Bad: It’s very “stiff.” If you realize you made a mistake in the planning phase while you are already coding, it is very expensive and difficult to go back up the waterfall.

Best for: Small projects where you know exactly what you want from Day 1.

The Agile Model (The “Building Blocks”)

In the modern world, things change fast. Agile was created because the Waterfall model was too slow. Instead of building the whole app at once, Agile breaks the project into tiny pieces called Sprints (usually 2–4 weeks long).

• How it works: You build a small, working part of the app, show it to the customer, get their feedback, and then move to the next part.
• The “Cycle”: Every two weeks, you Plan, Design, Code, and Test. It’s like a mini-SDLC happening over and over again.

The Main Advantage: If the customer changes their mind halfway through, it’s easy to pivot because you haven’t built the whole thing yet. It’s all about flexibility.

Waterfall vs. Agile (Which one to pick?)

Choosing a model is like choosing a vehicle. You wouldn’t take a bicycle on a highway, and you wouldn’t take a semi-truck to buy a loaf of bread.

Summary:  SDLC is the roadmap.

• Waterfall is a straight line from start to finish.

Agile is a series of small circles (loops) that get you to the finish line faster with fewer mistakes.