SDLC Model Selection
Chapter III opens with the SDLC model selection. You must name a model, justify why you chose it, and describe each of its phases as YOU applied them.
SDLC model selection + phases
What this section does
The first major section of Chapter III. You name the Software Development Life Cycle model you followed, justify why you chose it, and describe how each phase was actually applied to YOUR project.
The Agile 4-sprint cycle (Sample Bakery Shop example)
Choosing a model
| Question | Pick |
|---|---|
| Requirements stable? | Waterfall is honest |
| Need iteration with users? | Agile or Iterative |
| Limited time, UI-heavy? | RAD |
| No prior client? | Probably Agile |
Phases of the chosen SDLC (Agile example)
| Sprint | Weeks | Activities | Outputs |
|---|---|---|---|
| 1 | 1-2 | Interviews, observation, architecture | SRS, IPO, arch + ERD draft |
| 2 | 3-5 | DB schema, ordering module | Working module + unit tests |
| 3 | 6-8 | Inventory module, SMS integration | Inventory + SMS + integ tests |
| 4 | 9-12 | Acceptance survey, bug fixes, documentation | Score + manuscript + deploy pkg |
Mentor's tip
The phase descriptions should match the Gantt chart in Section 6 (Feasibility Schedule). If your sprints add up to 12 weeks here but the Gantt chart shows 8, the panel will catch it.
Panel defense checklist
- [ ] SDLC model named and justified.
- [ ] Justification ties to your project specifics, not generic theory.
- [ ] Every phase described with activities, outputs, tools, duration.
- [ ] Durations sum to what the Gantt chart shows.
- [ ] Outputs reappear in Chapter IV.
- [ ] Diagram of the SDLC included as a figure (e.g. Figure 3.0).
Mentor’s tip: Name the model, justify it for YOUR project, then describe each phase with activities, outputs, tools, and weeks. Make sure durations match your Gantt chart.
Discussion
Loading…