← CSC 311 Software Engineering
Software Process Models and Agile Methodologies
Notes
Overview of Software Process Models
Software engineering relies on disciplined development approaches known as software process models or Software Development Life Cycles (SDLC). A software process is a structured set of activities required to develop a software system, encompassing specification, design, validation, and evolution. Historically, the Waterfall model dominated the discipline. It enforces a linear, sequential flow where each phase, from feasibility study and requirements analysis to maintenance, must complete before the next begins. While Waterfall provides clear milestones and extensive documentation, it struggles with requirements volatility and delays feedback until deployment.
Agile Frameworks and Scrum
In modern software engineering, iterative and incremental methodologies dominate. The Agile Manifesto champions individuals and interactions over processes, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. Scrum is the most widely adopted Agile framework. Work is partitioned into fixed-duration iterations called sprints, typically lasting two to four weeks. Key roles include the Product Owner who curates the Product Backlog, the Scrum Master who removes impediments, and the cross-functional Development Team. Ceremonies like daily standups, sprint planning, sprint reviews, and sprint retrospectives ensure continuous adaptation and rapid defect identification.
Practical example
Consider a Nairobi-based financial technology startup developing a micro-savings platform linked to Safaricom's Daraja M-Pesa API. Using a traditional Waterfall approach would be catastrophic because regulatory requirements from the Central Bank of Kenya (CBK) frequently shift, and user behavioral patterns among informal traders (mama mbogas) require rapid adaptation.
Under Scrum, the Product Owner writes user stories such as: As a kiosk merchant in Gikomba market, I want to automatically deposit fifty shillings daily from my till number into a lock-savings account so that I can earn annual interest. During Sprint 1, the developers implement basic Daraja STK Push integration. In Sprint 2, they deploy a prototype to thirty pilot merchants in Nairobi. Feedback reveals that merchants often experience network timeouts with USSD prompts during evening peak hours. In the sprint retrospective, the engineering team pivots to implement an asynchronous queue using Redis and Celery to retry failed callbacks automatically. This rapid two-week delivery cycle allows the startup to adapt to local telecommunications latency and dynamic CBK compliance rules before running out of venture capital.
Quiz
1. In the Scrum framework, who is primarily responsible for prioritizing the product backlog?
2. Which attribute is a defining feature of the traditional Waterfall software process model?
3. Why is an iterative Agile approach preferable when integrating third-party APIs like M-Pesa Daraja in Kenya?
Sign in to submit and securely grade your quiz.