optional · CSS study notes
21. Web Application Development Methodologies
CSS Optional — Paper-II, Section-B · P-II.VI.21 · CSS 2018 asked to discuss Agile and Waterfall in the context of web application development — model answer in section 4.
1. What Is a Development Methodology?
A structured framework defining how development activities (requirements, design, coding, testing, deployment) are organized, sequenced, managed and communicated. Web projects favour methodologies that handle changing requirements and short release cycles.
2. Main Methodologies
| Methodology | Idea | Suits web projects when… |
|---|---|---|
| Waterfall | Sequential phases; each finishes before the next | Small, fixed-scope sites (brochure site) with clear requirements |
| Incremental | Deliver the system in functional increments | Core features first, extras later |
| Prototyping | Build quick prototypes to clarify requirements | UI/UX is uncertain; clients need to "see it" |
| Spiral (Boehm) | Iterative cycles with explicit risk analysis | Large, high-risk web systems |
| RAD | Rapid prototyping, reusable components, short timebox | Tight deadlines, available users |
| RUP | Iterative, use-case driven; phases Inception, Elaboration, Construction, Transition | Large enterprise web apps needing documentation |
| Agile (Scrum, XP, Kanban) | Short iterations, working software, customer collaboration, embrace change | Most modern web apps with evolving requirements |
| DevOps | Development + operations; CI/CD, automation, monitoring | Continuously deployed web services |
| Lean | Eliminate waste; MVP; build-measure-learn | Start-ups testing a web product idea |
Web-specific process models and design methods: Pressman's WebE process (communication → planning → modeling → construction → deployment, iterated incrementally); design methods such as OOHDM, WebML, UWE plug into these processes for modeling.
3. Agile in Detail
Agile Manifesto (2001) — we value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
(Backed by 12 principles, e.g. deliver working software frequently, welcome changing requirements.)
Scrum
- Roles: Product Owner (prioritizes backlog), Scrum Master (removes impediments, coaches process), Development Team.
- Events: Sprint (1–4 weeks), Sprint Planning, Daily Scrum (15 min), Sprint Review (demo), Sprint Retrospective.
- Artifacts: Product Backlog, Sprint Backlog, Increment (potentially shippable).
XP (Extreme Programming): pair programming, test-driven development, continuous integration, small releases, refactoring, on-site customer.
Kanban: visual board (To Do → Doing → Done), work-in-progress limits, continuous flow.
4. Model Answer — Agile vs Waterfall for Web Application Development (CSS 2018)
| Point | Waterfall | Agile |
|---|---|---|
| Structure | Linear, sequential phases | Iterative, incremental sprints |
| Requirements | Fixed upfront | Evolve; changes welcomed |
| Customer involvement | Start (requirements) and end (acceptance) | Continuous — review every sprint |
| Delivery | One release at the end | Working increments every 1–4 weeks |
| Testing | Separate phase after coding | Continuous, within each sprint |
| Documentation | Heavy | Lightweight, just enough |
| Risk | Problems discovered late | Problems surface early |
| Cost of change | High late in project | Low |
| Best for | Fixed-scope, regulated, well-understood sites | Evolving, market-driven web apps |
Why Agile usually fits web development: web requirements are volatile; users give feedback on a live product; competition demands fast releases; content and features evolve continuously; working increments (e.g. launch with registration and payment first, add chat later) deliver value early.
When Waterfall is still reasonable: a small informational site or a government portal with fixed legal requirements, fixed budget and formal sign-offs.
Conclusion: for most web applications Agile (often with DevOps) is preferred; many organizations use a hybrid — upfront planning and architecture, then agile sprints.
5. Choosing a Methodology — Factors
Requirement stability, project size and risk, client availability, team experience, deadline pressure, regulatory/documentation needs, budget type (fixed-price vs time-and-material).
🎯 CSS Exam Angle
For comparison questions use the table + a web-specific justification + conclusion. For "explain Agile/Scrum", list the 4 manifesto values and Scrum's roles, events and artifacts. Mentioning a hybrid approach shows maturity.
📌 Past CSS Paper Frequency
| Year | Question |
|---|---|
| 2018 | Discuss Agile and Waterfall methodologies in the context of web application development |
⚠️ MCQ Traps
- Agile values working software over documentation — it does not forbid documentation.
- The Product Owner manages the backlog; the Scrum Master is not a project manager.
- A Scrum sprint is typically 1–4 weeks; daily scrum is 15 minutes.
- Spiral is the risk-driven model; RUP phases are Inception, Elaboration, Construction, Transition.
- Pair programming and TDD belong to XP.
✅ Self-Check (with Answers)
Q1. State the four values of the Agile Manifesto.
Ans: Individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan.
Q2. Which methodology would you choose for a startup's new e-commerce app with unclear requirements, and why?
Ans: Agile (Scrum) with Lean MVP thinking: release a minimum viable product quickly, gather user feedback, and iterate in short sprints as requirements become clear.
Q3. Name the Scrum roles, events and artifacts.
Ans: Roles — Product Owner, Scrum Master, Development Team. Events — Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective. Artifacts — Product Backlog, Sprint Backlog, Increment.
Q4. Give one situation where Waterfall suits a web project.
Ans: A small informational website for a government department with fixed, legally defined content, fixed budget and formal approval stages.
Q5. What does DevOps add to Agile?
Ans: It extends agility to deployment and operations: CI/CD automation, infrastructure as code, monitoring and shared responsibility between developers and operations, enabling frequent reliable releases.
📜 Past-Paper Questions & MCQs (CSS 2016–2026)
2018 · Paper-II · Q8(C) · 6 marks
Q. Discuss Agile and Waterfall methodologies in the context of web application development.
Ans.
| Basis | Waterfall | Agile |
|---|---|---|
| Process | Linear phases: requirements → design → code → test → deploy | Short iterations (sprints) that each deliver working software |
| Requirements | Fixed up front | Evolve with customer feedback |
| Customer involvement | At the start and the end | Continuous |
| Change | Costly and difficult | Welcomed |
| Delivery | One release at the end | Frequent releases |
| Risk | Found late | Found early |
| Documentation | Heavy | Light |
- For web applications: requirements change fast, users are unknown and time-to-market is short, so Agile (Scrum, Kanban) usually suits better, with early releases and feedback. Waterfall fits small, stable sites or projects with fixed contracts, such as a static brochure site or regulated systems.