Computer Science › Section H · Software engineering › Topic H.3
Software engineering methodologies
Every software project analyses requirements, designs, implements and tests, but teams arrange those activities in very different ways. Choosing the arrangement, from a strict waterfall to two-week agile sprints, is one of the biggest decisions a project makes.
Same stages, different arrangements
The topic "The software life cycle" listed the activities of development: requirements analysis, design, implementation and testing. A methodology, also called a process model, says how to arrange them: in what order, how often to repeat them, how much to write down and when users see working software. No single arrangement suits every project. Software for a heart pacemaker and a phone game for a music festival face very different risks, deadlines and regulators. The models below range from the most rigid to the most flexible, and most real teams mix ideas from several of them.
The waterfall model
Early approaches insisted that the stages happen strictly in sequence: the whole requirements specification is completed and approved before design starts, and the design is finished before any code is written. Because work flows in one direction only, like water down a series of steps, this became known as the waterfall model. A 1970 paper by Winston Royce is often cited as its origin, though Royce himself warned that a single one-way pass was risky. Its strengths are clear milestones, thorough documents and easy progress tracking, which suit stable requirements and heavily regulated work. Its weakness is late feedback: users may see nothing working until the end, when changes are most expensive.
Incremental and iterative models
The incremental model builds the system in pieces. The first increment is a simplified version with limited features; once it is tested and tried by users, more features are added, one increment at a time. A homework portal might first only let students view assignments, then add submission, then marking. The iterative model instead repeats the cycle to refine each version, improving what exists rather than only adding to it. The two are often combined. Barry Boehm's spiral model, from the late 1980s, adds risk analysis to each loop: tackle the riskiest unknowns first. The Unified Process, popularised commercially by Rational Software, now part of IBM, organises iterations into inception, elaboration, construction and transition phases.
Prototyping
A prototype is an incomplete version of a system built to learn something. In evolutionary prototyping, the prototype is improved step by step until it becomes the final product, which fits the incremental model. In throwaway prototyping, it is discarded once it has answered its question, and the real system is built fresh. A rapid prototype is a throwaway kind built very early, sometimes just a few clickable screen images with nothing behind them. Its job is communication: showing users what the system might look like often reveals misunderstood requirements far faster than reading a specification. It can also help sell an idea to a potential client.
Open-source development
Open-source development applies incremental ideas on a huge, informal scale. Someone publishes a program's source code, often written for their own needs, and anyone may download, use and study it. Users who fix errors or add features submit their changes, and the maintainers review them and merge the good ones into the shared version, which others then extend in turn. Today this usually happens through hosted version-control services, where a proposed change is reviewed before it is accepted. The Linux kernel, started by Linus Torvalds in 1991, is the best-known example; thousands of programmers now contribute to it. Who may use and change such code is set by its licence.
Agile methods
The sharpest break from the waterfall is the family of agile methods. In 2001 seventeen developers met in Utah and wrote the Manifesto for Agile Software Development. In paraphrase, it values people and their interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan, while still seeing value in the second item of each pair. Extreme programming (XP), developed by Kent Beck and others in the late 1990s, is one agile method: small teams, short release cycles, pair programming, in which two people share one keyboard, one typing and one reviewing, writing tests before code, and integrating everyone's work many times a day.
Scrum
Scrum is, in industry surveys, the most widely used agile framework. Work happens in sprints, fixed periods of one month or less, often two weeks. The product owner keeps the product backlog, an ordered list of everything the product might need. At sprint planning, the developers choose items they can finish and turn them into a sprint backlog. Each day they hold a short daily scrum of about 15 minutes to check progress and adjust the plan. At the end, a sprint review shows the working increment to stakeholders, and a retrospective asks how the team can work better. A scrum master coaches the team and removes obstacles. Many teams estimate items in story points and track velocity, the points completed per sprint.
Worked example: forecasting with velocity
A Scrum team uses two-week sprints. In its last four sprints it completed 20, 26, 24 and 22 story points, and 132 points remain in the product backlog. Estimate the finish. 1. Average velocity: \(\frac{20 + 26 + 24 + 22}{4} = \frac{92}{4} = 23\) points per sprint. 2. Sprints needed: \(\frac{132}{23} \approx 5.7\), so round up to 6, because a partial sprint still takes a whole sprint. 3. Time: \(6 \times 2 = 12\) weeks. 4. Caveats: story points are the team's own relative estimates, velocity varies, and the backlog will change as stakeholders react to each increment. Agile teams therefore update the forecast after every sprint rather than promising a fixed date at the start.
Worked example: choosing a methodology
Compare two projects. A: control software for an insulin pump, which regulators must approve and whose requirements are set by medical science. B: an app for a three-day music festival next summer, whose organisers keep changing their minds. 1. A's requirements are stable and its errors could harm patients, so it needs complete, approved specifications, careful design and full records: a plan-driven, waterfall-like or spiral process. 2. B's requirements are unclear and the deadline is fixed, so it needs early working versions and fast feedback: an agile approach such as Scrum, with rapid prototypes of the main screens. 3. Conclusion: the right model follows from the project's risks, stability and regulation, not from fashion.
Common mistakes to avoid
First, treating agile as "no planning and no documents"; agile teams plan every sprint and write what is useful. Second, confusing incremental, which adds features, with iterative, which refines what exists. Third, letting a throwaway prototype quietly become the product, with all its shortcuts. Fourth, rounding sprint forecasts down: 5.7 sprints means 6. Fifth, assuming the waterfall is always wrong; stable, regulated projects can suit it.
Key takeaways
A methodology arranges the development activities. The waterfall model runs them once, strictly in order, giving clear milestones but late feedback. Incremental models add features piece by piece; iterative models refine each version; the spiral model puts risk first; the Unified Process organises iterations into phases. Prototypes are evolutionary or throwaway, and rapid prototypes clarify requirements. Open-source development spreads improvement across a community. Agile methods, guided by the 2001 Manifesto, favour working software, collaboration and change; XP and Scrum, with its sprints, backlogs and velocity, are leading examples.
Flashcards
Flashcard
A way of arranging requirements, design, implementation and testing
Test your understanding
Question 1 of 5
A team builds a booking app that first only shows available rooms; later versions add booking, then payment, then cancellations. Which model is this?
Question 2 of 5
A Scrum team averages 20 story points per three-week sprint, and 90 points remain. About how long until the backlog is done?
Question 3 of 5
Designers show users a few clickable screen pictures with no working code behind them, then discard them. What is this?
Question 4 of 5
Which statement matches the Agile Manifesto?
Question 5 of 5
Software for a medical device must be approved by regulators, and its requirements are stable. Which approach fits best?
