levo

The Development Project: Build, Testing and Evaluation

  • 10 subtopics
  • 30 things to know
  • A2 Unit 2

What The Development Project: Build, Testing and Evaluation covers

The Development Project: Build, Testing and Evaluation is examined in Unit A2 2, Application Development — an internally assessed coursework portfolio. It covers choosing software to develop the solution, building the solution, test data and the types of testing, carrying out and recording the testing, Documenting a strategy for system implementation, Evaluating the solution against the user requirements, identifying extensions to the system, the electronic user guide, Bringing the system into use and supporting it and documentation for the completed system.

Where it is assessed

A2 Unit 2

Application Development — an internally assessed portfolio.

Check the CCEA specification ↗

The 10 subtopics

Each one has its own page.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Key term

What is a prototype, and why is one built?

Key term

Why does the maintainability of the chosen software matter as much as its capability?

Key term

How is the choice of software justified in the documentation?

Key term

Why should the design be updated when the build departs from it?

Key term

What are internal comments in code, and what should they explain?

Key term

What should be done about a requirement that proves impossible during the build?

Key term

Why are both white box and black box testing needed?

Key term

Give normal, boundary and erroneous test data for a field holding a quantity ordered between one and fifty.

Key term

How is the test log used after the project is finished?

Key term

What is an implementation strategy?

Key term

Why must the strategy be documented rather than agreed verbally?

Key term

What should the installation section of the strategy cover?

Key term

What is evaluation in a development project?

Key term

How should the evaluation be structured?

Key term

How does the test log support the evaluation?

Key term

Why does a development project identify possible extensions?

Key term

How should an extension be described?

Key term

Why is it useful to say what an extension depends on?

Key term

Why is the guide made accessible from the user interface?

Key term

What should a user guide contain?

Key term

What is the difference between a user guide and technical documentation?

Key term

What has to be in place before a system goes live?

Key term

Why is the backup arrangement tested before going live rather than after?

Key term

Why is most of the money spent on a system spent after it is delivered?

Key term

How does documentation relate to the handover of the system?

Key term

How is testing recorded?

Key term

What documentation is delivered with a completed system?

Key term

What is white box testing?

Key term

Why is evidence captured for each test?

Key term

Why is technical documentation delivered to the client rather than kept by the developer?

Take The Development Project: Build, Testing and Evaluation further

The same content, four other ways.

Commonly confused

Pairs that lose marks when they are blurred together.

  • Regression testing vs Retesting a fix

    Regression testing: repeating checks that already passed, to show nothing else broke. Retesting a fix: repeating the single check that failed, to show the fault is gone.

  • A pilot vs Running two systems side by side

    A pilot: giving the new software to part of the organisation while the rest carries on as before. Running two systems side by side: having everyone doing the work twice for a period.

  • Evaluation vs Testing

    Evaluation: a reasoned judgement of how well the agreed requirements were met. Testing: the systematic search for faults that supplies its evidence.

Questions from this topic

Each one with the model answer underneath.

  1. 1

    On what grounds is development software chosen for a solution?

    Model answer

    Software is chosen on whether it can deliver the designed functionality, whether it runs on the hardware available, whether it is affordable or already licensed, whether the developer and the future maintainer can use it, and whether it produces data in the formats other systems need.

  2. 2

    Why is the choice of software made after the design rather than before it?

    Model answer

    Choosing first makes the design fit the tool, so features are included because the package offers them and requirements are dropped because it does not. Designing first states what is needed, and the package is then judged against it.

  3. 3

    When is a database package the right choice for a solution?

    Model answer

    A database package suits a solution whose core is storing related records and producing queries and reports from them, because the tables, forms, queries and reports are built in and the developer writes far less code.

  4. 4

    When is a general-purpose programming language a better choice?

    Model answer

    A language is better where the solution needs complex processing, an unusual interface, or integration with other systems, because a database package constrains what can be built to what its own tools support.

  5. 5

    When might a spreadsheet be an appropriate development tool?

    Model answer

    A spreadsheet suits a solution that is essentially calculation and modelling over a modest amount of data with a single user, and is a poor choice for anything with related records, several users, or a need for referential integrity.

  6. 6

    What is a rapid application development tool?

    Model answer

    A rapid application development tool builds much of the interface and data handling automatically from the data structure, so a working version appears quickly and can be shown to the user, at the cost of less control over the detail.

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.

The Development Project: Build, Testing and Evaluation revision questions

What does The Development Project: Build, Testing and Evaluation cover in CCEA A-Level Digital Technology?
10 subtopics: choosing software to develop the solution, building the solution, test data and the types of testing, carrying out and recording the testing, documenting a strategy for system implementation, evaluating the solution against the user requirements, identifying extensions to the system, the electronic user guide, bringing the system into use and supporting it and documentation for the completed system. Each one has its own page with questions and model answers.
How is The Development Project: Build, Testing and Evaluation organised?
By the CCEA 2650 specification, subtopic by subtopic, so it matches the order you are taught it in.

Every question in The Development Project: Build, Testing and Evaluation, 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.

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