Course contentsShow
← Software Engineering
Lesson 11 of 1,9331. Foundations of Software EngineeringFree lesson

SDLC Phases: Testing, Deployment, Maintenance

Understanding verification through testing, release to production, and ongoing support and evolution of software.

SDLC Phases: Testing, Deployment, Maintenance

What you'll learn: How software moves from "built" to "proven," then into users' hands, and continues evolving long after launch.

Testing: Proving Your Software Works

After implementation, you must verify that your software actually does what it's supposed to do. Testing is like a restaurant taste-testing every dish before serving customers—you're checking for bugs (defects) and ensuring requirements are met.

Testing isn't just clicking around randomly. Engineers write specific test cases: "When a user enters an invalid password, the system should display an error message." You systematically check expected behavior against actual behavior. Finding bugs now is far cheaper than discovering them after users are affected.

Deployment: Release to Production

Once testing confirms the software works, it's time for deployment—moving your software from the development environment to the real world where actual users can access it. Think of this like opening day at that restaurant: you're no longer cooking for yourself, but for paying customers.

Deployment involves installing software on servers, configuring databases, and making everything accessible. It requires careful planning because you're often replacing or updating an existing system that people depend on.

Maintenance: The Longest Phase

Here's the surprise: maintenance isn't just fixing broken things—it's the ongoing evolution of software. Remember our earlier lesson: most time is spent maintaining software, not building it initially.

Maintenance includes:

  • Fixing bugs users discover in real-world conditions
  • Adding new features as needs change
  • Updating for security patches or compatibility
  • Optimizing performance based on usage patterns

Your restaurant doesn't stop improving after opening day—you adjust the menu, fix equipment, respond to feedback. Software is the same, just constantly evolving.

Key Takeaway: Testing verifies quality before release, deployment puts software into users' hands, and maintenance keeps it valuable and working throughout its lifetime—often spanning years or decades.