levo
Log inStart

Design, Development and Testing

The development stage: turning a design into working code

  • 3 things to know
  • AS Unit 1

Overview

Done during the development stage of a project, purpose of commenting code during development and code walkthrough.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Process

What is done during the development stage of a project?

Key term

Why are coding standards agreed before development starts?

Key term

What is the purpose of commenting code during development?

Questions from this subtopic

Each one with the model answer underneath.

  1. 1

    What is done during the development stage of a project?

    Model answer

    During development each module of the design is coded, checked on its own and then joined to the others until the whole system runs.

  2. 2

    Why are coding standards agreed before development starts?

    Model answer

    Agreed rules on naming, layout and commenting mean any developer can read and change another's work, which matters most once the original author has moved on.

  3. 3

    What is the purpose of commenting code during development?

    Model answer

    Comments record why a section of code does what it does, so a later maintainer understands the intention instead of having to work it out from the statements.

  4. 4

    What is a code walkthrough?

    Model answer

    A code walkthrough is a meeting in which a developer takes colleagues through their code line by line, so that faults and misunderstandings are found by inspection rather than by running it.

  5. 5

    Give two advantages of reviewing code by inspection rather than only by running it.

    Model answer

    Inspection finds faults on paths that testing may never execute, and it spreads knowledge of the code across the team.

  6. 6

    What is a dry run?

    Model answer

    A dry run is a manual trace of a piece of code in which the developer works through the statements by hand and records the value of each variable at every step.

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 Design, Development and Testing, 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.