FOCUS QUESTION

What are the phases of building and shipping software, and how do they connect?

The map breaks this topic into its core concepts, connected by labeled relationships. Each link is written so it can be read as a complete statement — not just an unlabeled line between boxes.

Concepts and relationships

  • Requirements Gathering → Feasible?.
  • Feasible? Yes System Design.
  • Feasible? No Revise Requirements.
  • Revise Requirements retry Requirements Gathering.
  • System Design → Design Approved?.
  • Design Approved? Yes Implementation.
  • Design Approved? No Revise Design.
  • Revise Design retry System Design.
  • Implementation → Testing & QA.
  • Testing & QA → Tests Pass?.
  • Tests Pass? Yes Deployment.
  • Tests Pass? No Fix Bugs.
  • Fix Bugs retry Implementation.
  • Deployment → Maintenance.
  • Maintenance new cycle Requirements Gathering.

How to read this map

Follow the phases in order, reading each connection. Notice that later phases feed back into earlier ones — the lifecycle is iterative, not strictly linear.

Learning objectives

  • Order the main phases of the software lifecycle.
  • Explain what each phase produces.
  • Describe how testing and feedback loop back into design.
  • Use the map to plan a small project end to end.
Review standard: The phases reflect widely taught SDLC models and are updated whenever the template changes. Sources: Standard software-engineering lifecycle models.