The answersDownload the PDF
Worksheet

A14.2 Development methodologies

Software development, law and ethics · A level · OCR H446 1.2.3, AQA 7517 4.13.1.1, Eduqas A500QS 1.5 · about 45 min

BugBotLab
NameClassDate

What this lesson is about

Waterfall, spiral, agile, extreme programming and rapid application development: how each works, when to use it, and planning agile sprints.

Questions 6 marks in all

  1. [1 mark]Which methodology is driven by identifying and reducing risk on each loop, often by building prototypes?

    1. AThe spiral model
    2. BWaterfall
    3. CExtreme programming
    4. DRapid application development

  2. [1 mark]A hospital commissions software to control drug doses. The requirements are fixed by regulations and must be fully documented. Which methodology suits best?

    1. AWaterfall
    2. BExtreme programming
    3. CRapid application development
    4. DAgile with two-week sprints

  3. [1 mark]Which of these are practices of extreme programming?

    Tick every answer that is true.

    1. APair programming
    2. BTest-driven development
    3. CContinuous integration
    4. DSigning off each stage before the next begins
    5. EHeavy upfront documentation

  4. [1 mark]What is a drawback of rapid application development?

    1. APrototypes built quickly can lead to poorly structured, inefficient code
    2. BThe users never see the system until it is finished
    3. CIt cannot use prototypes
    4. DRequirements must be fixed before any work starts

  5. [1 mark]In agile, what name is given to the number of story points a team completes in one iteration?

  6. [1 mark]Why does waterfall cope badly with changing requirements?

    1. AA change found late means going back through stages that were already completed and signed off
    2. BIt does not have a testing stage
    3. CThe client is involved in every iteration
    4. DIt uses pair programming

The task: plan the sprints

Plan the delivery robot's sprints. VELOCITY is the whole number of story points the team finishes in one sprint. backlog is a list of (story, points) tuples in priority order: story is a string, and points is a whole number of 1 or more. 1. Go through the backlog in order. Any story with more points than VELOCITY cannot fit in a sprint: print too big, split it: <story> and leave it out of the plan. 2. Put the remaining stories into sprints, in order. Add each story to the current sprint while the sprint's total stays at or below VELOCITY. When the next story would take the total over VELOCITY, that sprint is finished and the story starts a new sprint. 3. Print each sprint as sprint <n>: <stories> (<total> points), numbering from 1, with the stories separated by , . 4. Finally print sprints needed: <n>. Compare with VELOCITY in your code, not the number 8. The robot stays still.

# the two lines every program starts with: the commands, then the robot
from bugbot import *
connect()

VELOCITY = 8
backlog = [("drive to a bay", 5), ("stop at the wall", 3), ("beep when blocked", 2), ("map the room", 13),
           ("report battery", 1), ("follow a line", 8), ("avoid people", 5), ("log each delivery", 3)]

Plan your program here, then type it in and press Run.

QR code
Do it on the robot
www.bugbotlab.com/learn/a14-2-development-methodologies/
The simulator checks it and tells you when it passes. Nothing to install, no account.

Challenges

  1. Sprint 2 has only 3 points in it. Change the rule so a sprint keeps looking further down the backlog for stories that fit. What does this gain, and what does it cost the client's priorities?
  2. A hospital wants software to control the dose from an infusion pump. Recommend a methodology and give three reasons linked to the hospital.
  3. Explain why test-driven development makes refactoring safer.