System Life Cycle
SDLC phases (Analysis/Design/Development/Testing/Implementation/Maintenance/Evaluation/Documentation), Development methods (Waterfall/Agile/Iterative/Incremental/RAD), Implementation methods (Direct/Parallel/Phased/Pilot), Testing (Alpha/Beta/White-box/Black-box), Maintenance types.
Danh sách bài học
26 bài📖 Nội dung lý thuyết — T16: System Life Cycle
Xem bài học chi tiết trong tab Bài học phía trên. Mỗi bài giảng bao gồm:
- ✅ Định nghĩa thuật ngữ chuẩn Cambridge
- ✅ Bảng so sánh & ví dụ minh hoạ
- ✅ Exam tips — cách trả lời câu hỏi Paper 1/3
- ✅ Các lỗi thường gặp cần tránh
- ✅ Sơ đồ & diagram khi cần thiết
Kho đề thi Cambridge theo chương này. Chọn đề để luyện tập có đếm giờ.
Chưa có tài liệu. Giáo viên sẽ bổ sung.
Mnemonic học thuộc: SDLC analysis phase
Cornell Notes: SDLC design phase
Kỹ thuật Feynman: SDLC development phase
Kết nối với thực tế: SDLC maintenance phase
Teach Back (dạy lại): Waterfall development model
Active Recall: Direct changeover implementation
Peer Teaching: Parallel running implementation
Ví dụ cụ thể: White-box testing
Flashcard kỹ thuật số: SDLC testing phase
Mind map từ trí nhớ: SDLC implementation phase
Vẽ sơ đồ từ trí nhớ: Beta testing
Spaced Repetition: Black-box testing
DFD Questions — How to Score Every Mark
📊 DFD Completion Strategy
DFD questions (e.g. FM2026 Q9, MJ2025/32 Q5) are typically 5–6 marks. Each mark targets one correct element:
| Element | Symbol | Common Mistakes |
|---|---|---|
| External Entity | Plain rectangle (square corners) | Using rounded corners — that is a Process |
| Process | Rounded-corner rectangle or circle | Not labelling with a verb/action phrase |
| Data Store | Open-ended rectangle (open on right side) | Closing the right end — loses the mark |
| Data Flow | Arrow (→) with a descriptive label | Unlabelled arrows — labels are always required |
Pre-submission checklist:
- ✅ Every arrow has an arrowhead showing direction
- ✅ Every arrow has a label (what data flows)
- ✅ At least one flow goes TO and FROM each data store
- ✅ External entities use plain rectangles only
Software Maintenance — 4 Types for 8-Mark Analyse Questions
🔧 Four Types of Software Maintenance
| Type | Definition | Banking App Example |
|---|---|---|
| Corrective | Fix bugs found after deployment | Fixing a calculation error in interest rates |
| Adaptive | Update for changed environment or regulations | Updating for new iOS version or PCI-DSS compliance rules |
| Perfective | Add new features requested by users | Adding biometric login or cryptocurrency support |
| Preventive | Refactor code to prevent future problems | Rewriting legacy modules to reduce technical debt |
8-mark Analyse technique: Do not just define each type — explain HOW it extends the lifespan. Example: "Without adaptive maintenance, the banking app would become legally non-compliant with new regulations, forcing early retirement and shortening its commercial lifespan dramatically." That causal explanation is the analysis mark.