levo
Log inStart

Systems Analysis and Development Approaches

Rapid application development and Agile

  • 3 things to know
  • AS Unit 1

Overview

Rapid Application Development with timeboxing and MoSCoW prioritisation, the Agile approach with sprints, user stories and the product backlog, and how each handles a change of requirement compared with the waterfall model.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Evaluation

Give two advantages of Rapid Application Development.

Evaluation

Give two disadvantages of Rapid Application Development.

Key term

Describe the Agile approach to systems development.

Questions from this subtopic

Each one with the model answer underneath.

  1. 1

    Describe Rapid Application Development.

    Model answer

    Rapid Application Development builds a system through a series of quickly produced working versions that users try and comment on, with the design refined at each cycle instead of being settled in advance.

  2. 2

    What is timeboxing in Rapid Application Development?

    Model answer

    Timeboxing sets a short fixed period for each cycle, and any requirement that cannot be finished within it is moved to a later cycle rather than the deadline being extended.

  3. 3

    Why are Rapid Application Development teams kept small?

    Model answer

    A small team can take decisions and change direction without formal meetings and paperwork, and that speed is what makes a short cycle possible.

  4. 4

    Give two advantages of Rapid Application Development.

    Model answer

    Users see working software within weeks and can correct misunderstandings early, and the finished system usually fits the way people really work.

  5. 5

    Give two disadvantages of Rapid Application Development.

    Model answer

    Rapid Application Development produces little formal documentation, which makes later maintenance harder, and it needs users available continuously, which many organisations cannot provide.

  6. 6

    Why is Rapid Application Development unsuitable for a very large system built by many teams?

    Model answer

    Coordinating many teams needs agreed interfaces and written specifications, and a fast-changing informal design makes it hard to keep separate teams building to the same plan.

See the rest and revise

Other ways to work this

The same content, four other ways.

What is inside Levo

Six ways to work the same material.

1Closed book
2Open book
3Closed book

The 3-step method, run for you

Answer cold, learn it, then prove it stuck. Levo tracks the jump between your first attempt and your last.

Systems Analysis and Development Approaches
Design, Development and Testing
Implementation and System Security
Programming

Cram a whole paper in one sitting

Sort every topic into what you know and what you do not, then drill only the weak ones.

A check requires a value.
presencerangeformat

Blank Blitz makes facts automatic

Rapid timed gap-fills on the terms and numbers you need to recall without thinking.

ANormal data is 12, which should be accepted.
BBoundary data is 1 and 50, which should be accepted.
C0 and 51, just outside the limits, should be rejected.

Build It gets the exam shape right

Assemble a full-mark answer from its marking points, in the order an examiner wants them.

One byte is made up of 8 bits.
TrueFalse

Test It catches misconceptions

Spot the fault in a statement. The traps are the mistakes students actually make.

721941163128510

Brain Breaks between sessions

Short focus games to reset attention, so the next set lands better than the last.

Every question in Systems Analysis and Development Approaches, on a schedule.

Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.

Start revising, £5 a monthSee how the method works

Or £46 a year, about £3.83 a month. Cancel anytime.