Assignment 1 – Software Process Models
1. Pros and Cons of Different Software Process Models
Model Pros Cons Why Use It
Waterfall Simple, structured, easy to follow. Works for fixed
Rigid,requirements.
no going back, testing is late. Best when requirements are clear and stable.
V-Model Strong testing at every stage, defects found early,
Rigid,high
costly
quality.
for changes, heavy documentation.
Good for safety-critical systems (banking, medical).
Incremental Delivers in parts, easier testing, early usable product.
Needs planning, integration issues possible. Best for phased delivery projects.
Iterative Early version available, adapts to changes, continuous
Resource-heavy,
improvement.
risk of scope creep. Good when requirements are unclear.
Prototype Clarifies requirements, early models reduce misunderstandings.
Can increase cost, not for very large [Link] for student projects, startups.
Spiral Strong risk analysis, combines iterative + waterfall.
Complex, expensive, needs experts. Best for large, high-risk projects.
Extreme Programming
Continuous
(XP) testing, flexible, high customer satisfaction.
Needs skilled team, stressful, not for big teams.
Good for small-medium projects with changing needs.
Big Bang Very simple, minimal planning, flexible for small
Hightests.
risk of failure, not for large projects. Good for academic projects, experiments.
RAD Very fast delivery, strong user involvement, quick
Needsprototypes.
skilled devs, not for complex projects. Best when time is short.
Agile Flexible, frequent releases, strong customer involvement.
Needs experienced team, unpredictable cost/time.
Best for modern projects (apps, web).
Scrum Strong teamwork, fast sprints, adapts [Link] meetings, requires discipline. Best for teamwork and fast delivery.
Kanban Visual workflow, simple, good for ongoing work.
Not ideal for strict deadlines. Good for continuous delivery.
Lean Efficient, reduces waste, faster delivery. Hard to scale, needs discipline. Best for startups needing speed.
DevOps Continuous delivery, faster deployment, dev +Needs
ops collaboration.
infrastructure and tools, not for small teams.
Best for cloud-based systems with frequent updates.
2. Which Model Would I Adopt and Why?
If I were working with a small student team with limited resources, I would choose the Prototype Model.
This is because as students, we often don’t have clear or fixed requirements at the start. Clients (like teachers or end-users) may change their minds after
seeing the first version. Prototypes let us show an early working model, which helps refine the requirements. It reduces misunderstandings and ensures
the final system matches user needs.
■ In short: Prototype Model is best for student projects because it allows changes, ensures better communication, and is cost-friendly for small
projects.
