Manage system life cycle phases (analysis, design, testing)
16 System Life Cycle
In this lesson we’ll explore the three main phases of the system life cycle: Analysis, Design, and Testing. Think of it like building a LEGO set: you first plan, then build, and finally check that everything works.
We can represent the life cycle as $SLC = Analysis + Design + Testing$.
1. Analysis 🧐
During analysis you ask who will use the system, what they need, and why the system is required. This is the “blueprint” stage.
- Identify stakeholders (users, managers, etc.)
- Define system requirements (functional & non‑functional)
- Document use cases and user stories
Exam Tip: Remember to differentiate between functional and non‑functional requirements.
2. Design 🎨
In design you turn the analysis into a concrete plan. Think of it as drawing a detailed map before you start building.
- Architectural design – choose the overall structure (client‑server, microservices, etc.)
- Data design – create ER diagrams and database schemas
- Interface design – mock‑ups, wireframes, and user flows
Exam Tip: Be able to explain the purpose of an ER diagram and how it relates to database tables.
3. Testing 🔬
Testing checks that the system works as intended. It’s like a final quality check before the product goes to market.
| Test Type | Purpose |
|---|---|
| Unit Testing | Verify individual components |
| Integration Testing | Check interactions between components |
| System Testing | Validate the complete system |
| Acceptance Testing | Confirm user requirements are met |
Exam Tip: Know the difference between unit and system testing.
Putting It All Together 📦
The life cycle is iterative: after testing, you may go back to analysis or design to fix issues. This loop continues until the system meets all requirements.
Remember the V‑Model diagram: each development phase has a corresponding testing phase.
Good luck with your studies! 🚀
Revision
Log in to practice.